-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calculating ao5 after 4 results introduced #42
Comments
I wasn't sure what's best here, on one side I see it'd be quite convenient, but technically a person with pending solves doesn't have an average, so showing it could cause some confusion. |
This is an ideas for that:
|
Should we really allow to submit an attempt with empty results unless the solves didn't meet the cutoff? Can we just disable the submit button in case any of the attempts are not entered? Otherwise, there are chances that the delegate submits results forgetting to enter the last solve(s) as DNS. |
Submitting empty attempts is actually very intentional, it's the proper value when submitting partial results, e.g. filling remaining FMC attempts with DNS is not really accurate and introduces unnecessary noise to the results list (same for MBLD), the same goes for head-to-head finals if the results are entered in real-time. Thinking about the issue again, I don't quite like the idea of showing the average before the results is actually valid. One idea that sounds better to me would be showing some information when hovering over a person (e.g. best/worst possible average, current mean of times), but that's also just an idea. |
Oh ya. You have a valid point @jonatanklosko . In that case, I agree with you regarding not to show average. |
On hover info is a beautiful idea IMO. Maybe best and worst possible average, personal bests, result in previous round? |
#179 added predicted BPA and WPA. |
Is it possible to calculate ao5 in cases like this?
It's more comfortable to check results during live finals like 5th solves is DNF / DNS.
The text was updated successfully, but these errors were encountered: