How do I quote the parse data like pchan did?
All intervals are just 95% confidence
4348 rounds, 811 DAs, 18.65% average DA rate (+/- 1.16%)
DA rate was unaffected by missing the first swing, and the hit rate of DAs was not significantly different than normal hit rate (58.81% +/-1.34%)
Box Step hit rate was 62.43% +/- 2.42%, so steps either have a modest accuracy bonus over normal hits or double attack can proc on them. 62.43/(1+.1865*.5881) = 56.26, and the way the script is set up there are actually more box steps later in the DA cycle, iirc.
Crit rate was 14% +/- 1%
It's going to take me a bit to count the 3 minute blocks by hand. First I'm going to **** around trying to get it into matlab with space delimiters to see if I can make a pretty graph of it.
Okay, I can move all the extra attacks into matlab and turn the timestamp from the extra details into a timestamp (number in seconds) and pull out the number of attacks at that timestamp. Then I subtract off the offset (started at 8:30ish) and divide by my cycle time (181 seconds) to make it cyclical. From there I subtract off the whole number (so I'm just left with a fraction out of 181) and sort high to low. Now I'm attempting to sum the number of hits in every "second window," and I'm semi-convinced my code is working now <_<. http://img854.imageshack.us/img854/4285/unsmoothed.jpg http://img195.imageshack.us/img195/7229/boxavg.jpg
The first is unsmoothed and relative to position in the cycle. It's rough because there are only about 25 samples for each point. Despite the obvious spike at the beginning (and end), I'm not entirely sure where along the cycle I used Saber Dance. Obviously I'd guess the beginning, but I don't really know.
The second is smoothed (average over 10 bins, relative to the frequency in each bin), but there's still no guarantee that every point is equally represented. I think maybe I just need more sample size, so I'm letting it run another 10 hours. Edited, May 4th 2011 6:01pm by Byrthnoth