Closed merforga closed 5 years ago
I will attempt to explain the result required using butchered SQL
FOR EACH ENCOUNTER in RAIDS SELECT Player.Professsion, Player.Elite,,Player.Archetype, Skills.damage, Skills.count, Player.TotalDPS, Player.CleaveDPS WHERE Player.Percentile => 0.95 AND IN Era.Current
Also just to clarify, I believe he wants the data down to per player (participant) level rather than aggregate . e.g instead of aggregate of all Soulbeasts in 95th in VG, it should show Soulbeast A, Soulbeast B etc etc
Bright :
all right,
python3 bin/overachievers.py | bzip2 > ~/overachievers.jsonl.bz2
should give you~/overachievers.jsonl.bz2
. there's one already generated at~amadan/...
. Check it usingbzless ~amadan/overachievers.jsonl.bz2
. Hope that's okay. I'm about to go unconscious. o/
I haven't had a chance to look at the result of the above yet but just got some further clarification from the CC
How does this sound?
For all encounters 7/12 and beyond for players performing in the 95% since then
Performance based on profession broken down by boss including: Skill damage (MIN)(If Condi Break down Condi/Physical) Skill damage (MAX)(If Condi Break down Condi/Physical), Skill damage (AVG)(If Condi Break down Condi/Physical), Hits (AVG)(If Condi Break down Condi/Physical), Crit Rate (AVG per skill), Total Damage (AVG), Total Damage Taken (AVG), Total Condition Damage (AVG), Total Physical Damage (AVG)
So looks like he want just by profession now T__T per boss. (it's ok if it's at player level, we can just aggregate it manually after if too hard to bring it back up a level)
We don't have a lot of those info in the DB. What we have is what I extracted (per-skill DPS, per-skill total damage, per-skill crit rate, all power I think). No mins or maxes. AFAICR we can't know condi damage per skill since condis are not tied to skills like power damage is. So while we have power damage for Burning Retreat, we have condi damage for Bleeding (with no idea which skill caused Bleeding in the first place). (Also, oopsie but skill names is whatever the client reports them to be, so we have Searing Fissure but also Versengender Spalt...)
Hmmm I thought we had count of skill usage though no? If so we can manually calculate some of them.
Hmm some how ensolyss CM snuck into the data O_O
If anyone is interested in how I cut the data.
Update:
from ChrisCleary sent 1 day ago Last week was crazy but I'll have my team parse through this next week. Thanks a ton for getting this to me. Looks like I'm going to have to join skills together because of languages heh. I'm sure it's going to be a mess swapping over to skill ID, but that's one way to easily handle localization on the backend and allow frontent language configuration.
I'll get back to you sometime next week. TY