Skip to content
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

Closed
cdraugr opened this issue Nov 24, 2019 · 7 comments
Closed

Calculating ao5 after 4 results introduced #42

cdraugr opened this issue Nov 24, 2019 · 7 comments
Labels
public Public-facing part of the app question Further information is requested

Comments

@cdraugr
Copy link

cdraugr commented Nov 24, 2019

Ao5

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.

@jonatanklosko jonatanklosko added public Public-facing part of the app question Further information is requested labels Nov 26, 2019
@jonatanklosko
Copy link
Member

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.

@AlexKatyukov
Copy link

This is an ideas for that:

  1. Not to show places for people who did not complete a whole average
  2. Not to bold not complete average
  3. Show both best possible average and worst

@danieljames-dj
Copy link
Member

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.

@jonatanklosko
Copy link
Member

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.

@danieljames-dj
Copy link
Member

Oh ya. You have a valid point @jonatanklosko . In that case, I agree with you regarding not to show average.

@AlexKatyukov
Copy link

On hover info is a beautiful idea IMO. Maybe best and worst possible average, personal bests, result in previous round?

@jonatanklosko
Copy link
Member

#179 added predicted BPA and WPA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
public Public-facing part of the app question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants