Thanks for spotting this! I looked into it, and it seems to be double-counting the most recent result when computing the median. It’s an order-of-initialization issue; it thinks it’s getting all the results except the new one, adding it, then taking the median, but it’s actually getting a list of all the results. The fix is straightforward; I’ll email the admins to apply it.
Thanks for spotting this! I looked into it, and it seems to be double-counting the most recent result when computing the median. It’s an order-of-initialization issue; it thinks it’s getting all the results except the new one, adding it, then taking the median, but it’s actually getting a list of all the results. The fix is straightforward; I’ll email the admins to apply it.
Your fix for the incorrect median calculation has been deployed.
I got a mean of −9.91765890411e+16, so something is still wrong.
No, that’s unfortunate but correct (several people entered things like entered −3e+18 as their estimate).