Combat log Merging

[GoogleCodeExporter]

This is an Enhancement not a  defect but i couldn't find it :< sadly in the 
templates.

Basically for fights like Sartharion with Drakes up there are portals to the 
nether at which Logging 
becomes inaccurate :< due to portals as in Fights like Kalecgos ... If u could 
:) provide a feature to 
merge logs as well .. Looking for similar events and adding the different 
events that would be 
awesome.

I started using Stasiscl Today morning and i think its the best, and everyone 
here thinks the same, 
Keep it up :) <3.

Original issue reported on code.google.com by Bik...@gmail.com on 29 Jan 2009 at 5:48

[GoogleCodeExporter]

On a side note :) i would like to help with this Project if possible in anyway 
:).

//Narlya

Original comment by Bik...@gmail.com on 29 Jan 2009 at 10:38

[GoogleCodeExporter]

Glad you like it. If you want to help, you probably have a better idea of what 
you can do than anyone else does :)

Original comment by gianmerlino@gmail.com on 30 Jan 2009 at 6:12

• Changed state: Duplicate

[GoogleCodeExporter]

I can most probably :) provide you with logs from 10 mans and 5 mans and 25 
mans :) along my playing, as 
well as, being an early Log parser to have 3.1 in it :) as i am most probably 
going to be on the ulduar PTR 
trying it out with my guild or alone, checking bosses names and encounters.

I could also offer my small very tiny little host :p for any testings, i am not 
that perfect with codes but i can 
try.

Anyway :p the merging issue could be solved with creating a small merger that 
can be run separately as a 
separate Project before stasis or with stasis as in giving stasis a directory 
:) for logs and it just parses all 
what's inside, giving an error if time doesn't match and so on.

Original comment by Bik...@gmail.com on 30 Jan 2009 at 6:43

[GoogleCodeExporter]

It took WWS a long time to get merging working well I proved alot of test 
parses when 
they were doing that. It seems combat data is always given client based 
timestamps in 
the log which makes them subject to both network latency (my client gets a dmg 
doen 
report 0.5 seconds before yours and records the timestamp apropriatly) and 
"Crazy 
clocks" (PC RTC generators are notoriously cheap and inaccurate. They rely on 
internet time syncing at regular intervals to provide anyway accurate real 
world time 
and when it comes to accuracy of events bellow 1 sec intervals like combat logs 
they 
are just a farce). Maybe someone else has  done some groundwork already that it 
might 
be possible to include as a separate script to "roll" the logs into one before 
Parsing with stasis.

No 2 logs will match up time stamp for timestamp. A log rolling script first 
has to 
establish the timezone shift of each log. Then it needs to check to ensure that 
the 
shift is consistent throughout the log and finally it needs to come up with a 
formula 
for adjusting the timestamps to create a synced final log with duplicate 
entries 
removed. We found that WWS log rolling while saying it found "5% new data added 
to 
log" was frequently adding incorrect data to ours. Hard to spot with an extra 
500 dmg 
dot tick here and there but very obvious when say a hunter manages be killed by 
a 
flame patch twice in the same 5 seconds :D

Original comment by Tethal...@gmail.com on 30 Jan 2009 at 12:16

[GoogleCodeExporter]

I am not the expert on this matter, but yeah i do realize that WWS, most of its 
reports are bugged to *....* and 
some even don't include a slight piece of information that is correct and 
specially lately with their problems 
but i do admit that their merger as much as it might duplicate, is more 
accurate than having 1 log on a different realms fight like Kalecgos for 
example or Sartharion with 3 Drakes where portals have to be 
attended.

With this said, i realize that using various logs on such fight will make data 
inaccurate by that (5% that WWS 
says) but it still adds a whole lot of info that is not tracked by 1 log, so 
overall its better.

Now on the other hand, i felt like saying this suggestion, as awkward as it may 
sound ... it could solve it even 
with its complication, Why not search for events that didn't occur rather than 
searching for events that occurred, Make a small time span for the event ... 
like 3 secs (the time it takes for any dot to tick except LB 
and  Penance), i don't know :) as i said ... just assuming.

After all i'd say merging logs on different realm phase fights is overall more 
accurate.

//Narl

Original comment by Bik...@gmail.com on 30 Jan 2009 at 3:47