Talk:Performance/Status Meetings/2007-June-27: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 1: Line 1:
FWIW, I'm not sure if Tp2 does the calculations properly. I swear I did a recent run where for one of them I had numbers like 100, 120, 110, 1600, 100 and it gave me a median of 800 for that test. Needless to say, that skewed things a bit. It did show the 1600 as grayed out, but it seems it was still factored into the calculation.
FWIW, I'm not sure if Tp2 does the calculations properly. I swear I did a recent run where for one of them I had numbers like 100, 120, 110, 1600, 100 and it gave me a median of 800 for that test. Needless to say, that skewed things a bit. It did show the 1600 as grayed out, but it seems it was still factored into the calculation.
EDIT: OK, I know for sure it's not calculating correctly. Here's five times from a run I just did:
391 296 390 234 297
As intended, it did grey out the 391 value. However, it still calculated a median of 343.50, which is clearly wrong. It should be 296.50. It appears that instead of averaging the middle two remaining numbers, it's averaging the top two remaining numbers.

Revision as of 13:36, 27 June 2007

FWIW, I'm not sure if Tp2 does the calculations properly. I swear I did a recent run where for one of them I had numbers like 100, 120, 110, 1600, 100 and it gave me a median of 800 for that test. Needless to say, that skewed things a bit. It did show the 1600 as grayed out, but it seems it was still factored into the calculation.

EDIT: OK, I know for sure it's not calculating correctly. Here's five times from a run I just did: 391 296 390 234 297

As intended, it did grey out the 391 value. However, it still calculated a median of 343.50, which is clearly wrong. It should be 296.50. It appears that instead of averaging the middle two remaining numbers, it's averaging the top two remaining numbers.