FIRST-Tech-Challenge / scorekeeper

FIRST Tech Challenge Live Scorekeeper Software
86 stars 21 forks source link

Hide Scores From Audience When Match Ends #250

Open jkelbick opened 5 years ago

jkelbick commented 5 years ago

The FRC scoring software has done this for a while. As soon as each match ends, the on-screen scores should disappear so that the referees have a chance to enter their scores and to allow the MC to build up some drama as scores are announced. If the final scores are public before the MC announces them, it basically steals their thunder.

cmacfarl commented 5 years ago

A scorekeeper can do this at present by loading the next match.

jkelbick commented 5 years ago

On the FRC side it hides automatically and that's a fantastic solution. This way the audience cannot see what changes as the refs finalize their scores until the MC announces it.

jvens commented 5 years ago

If you choose to add this feature please make it optional and off by default. At most of our league meets we don't have any game announcer or MC and this would add unnecessary complexity in my opinion.

Also, I am a bit confused. To my understanding the score is not shown until "Post" is clicked. There is the "Commit & Post" button which will show the score, but if this is a concern, couldn't you just click "Commit" when the match is finished and then "Post" when you want to display the score?

jkelbick commented 5 years ago

@jvens The field displays keep showing the score and actively adding points as the refs finalize their scores even after the match has ended. If you don't have a field displays, this might not be a problem.

adwiii commented 5 years ago

In FRC the scores do not go away when the match ends. For example, see the Finals 1 from Houston Einstein.

To be clear, the displayed score does not change if both referees have entered review. If one referee is in review and one has submitted review, then the changes submitted after review will be shown when the referee adjusts scores, or 10 seconds pass.

I am not in favor of hiding scores from the audience as that defeats the purpose of live scoring, but as @cmacfarl points out, the scorekeeper can make this happen if they so choose. I would like the scores to remain displayed as what they were "at the end of the match" until the final match score is posted - this is what FRC does. We can look into making this easier in software, but for now the solution is that both referees need to enter review before one of them submits. Ideally, normal flow is that both referees enter review within a few seconds of the match ending, so this should happen naturally.

tvbarnette999 commented 5 years ago

@jkelbick Unless FMS's operation has changed since Steamworks, FRC does the same thing we do, which is to freeze the displayed scores after referees are done, which usually happens by T+3 (or tablets start blinking at you). If the referees can still edit scores, they continue to appear in real time. Once it's in the scorekeeper's hands or the HR has initiates a ref review, the AD is frozen. We have an additional step of a referee review phase, during which as @adwiii mentioned, our AD is frozen as well. At no point will any edits made by a Scorekeeper appear on the AD until the scores are Posted.

Any score hiding in FRC is done by AV, and I remember FRC Scorekeeper training making a point 2 years ago to tell your AV people NOT to hide the scores (since it would result in the missing of the animation).

slacter commented 5 years ago

A scorekeeper can do this at present by loading the next match.

In a dual field event using displays bound to their respective fields, loading the next match does not do this. A round on Field 1 does not get hidden when loading the next match, which is on Field 2. Since only one match at a time can be loaded, hiding the previous match will not occur in a dual field event.

cheer4ftc commented 5 years ago

I also suggest holding the scores on the screen. One very large benefit of livescoring is it allows teams to check their scores immediately after a match is over and alert a ref if something seems amiss (e.g., "it looks like our alliance only got credit for one end-game latch: could you check to see that both of our latches were scored?").