-
Notifications
You must be signed in to change notification settings - Fork 56
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
[2025.1_Beta1] After the end of a timeout a timeout clock is shown next to a "Lineup" label #710
Comments
Check the scoreboard operator settings tab. There should be drop down for the after timeout display with options of either timeout or lineup. Also be advised of a change
|
That rule change is so stupid and clearly written by someone who never operated the scoreboard. |
Agreed, since the scoreboard is 'the source of truth' for teams, officials, spectators to know what is happening it should be displaying the correct information |
I think it's important to remember, the system was written to the standards guide released by WFTDA.If we believe something should change, it needs to be accurately fed back to the OffComm to change things. We can't drive the change to the standards. I've always "ended the timeout" only to push CRG to a "new state" but it's not needed going forward since it changes it.Sent from my iPhoneOn 10 Jun 2024, at 16:59, Queekusme ***@***.***> wrote:
That rule change is so stupid and clearly written by someone who never operated the scoreboard.
Agreed, since the scoreboard is 'the source of truth' for teams, officials, spectators to know what is happening it should be displaying the correct information
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
As an SBO I will always end a timeout manually when it ends, which is more important now as the scoreboard can be used to output IGRFs for correct inforation logging. 2025.1_Beta starts the lineup clock however does not end the timeout clock which is still shown as counting up on the display view since this is the vew that skaters and officials use, this could be seen as confusing and may lead to people believing that the lineup has run over and taking action that further delays the start of the next jam. it is my belief that it should show the correct timer regardless of which is correct i.e. if 'lineup' text is shown on the display, the lineup clock should be shown, and if 'Time out' text is shown on the view then the timeout clock should be shown... All this 'This is wrong, that is wrong' well the wrong clock is shown when lineup is showing which means something is wrong here. Either the logic should be reverted in 2025.1_Beta1 as per 2023.x or the correct clock should be shown on the display at the correct time. Considering the change in 2025.1_Beta1 to show the lineup clock, it seems as if that decision was already made. Please can you decide how you want it to work and resolve as necessary. Thank you |
That procedure change quoted by @atkinsonm is not coming soon, it is already in effect. (The post says "effective immediately".) The procedure says that in any regulation game we have no choice but to show a timeout clock between the end of a timeout and the start of the next jam or timeout. At the same time the rules require that the state of the game has to be clearly visible to everyone at the game. Since the new procedures also allow the Jam Timer to leave the pivot line once the type of timeout is displayed on the scoreboard, there must be some sort of indication on the scoreboard that the game state has changed from "Timeout" to "Lineup". Since we are not allowed to change the clock as per the above procedure, changing the label next to it is the only option remaining. I fully agree that it is stupid to display the text "Lineup" with a timeout clock next to it. But right now it is the only way to remain compliant with both the rules and officiating procedures without deviation, as mandated for any Regulation game by the WFTDA Sanctioning Policy. I have talked to members of the WFTDA board this weekend and a meeting between the relevant people at WFTDA and myself as CRG maintainer regarding how to make sure procedures and software are aligned (including if this specific procedure is actually needed) will take place relatively soon after the Regionals are done. Thus I hope to be able to change the behaviour before a stable release of CRG v2025. I will leave this ticket open since other people will presumably be stumbling across the same thing. Please abstain from turning this into a discussion on WFTDA rules and procedures. |
Just to make it easier for everyone to find: https://static.wftda.com/officiating/wftda-officiating-procedures.pdf 4.8 When returning from a Timeout, the scoreboard should allow the timeout clock to |
We are almost 3 months beyond Regionals and there has not been any activity (visible to me) towards setting up the promised meeting or any other way of getting the alignment process going. |
@frank-weinberg as the question was already raised in the Facebook group... Was this intended? |
I asked this same question in Slack to Speedy about... 5mins ago, lol
…On Fri, 15 Nov 2024, 21:11 reflexdd, ***@***.***> wrote:
@frank-weinberg <https://github.com/frank-weinberg> as the question was
already raised in the Facebook group...
The default Setting was set back to Lineup in beta 4 but in the current
release the option to choose between lineup and timeout has disappeared
completely.
Was this intended?
—
Reply to this email directly, view it on GitHub
<#710 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG3YNG7LEQ2USXHLWA52GLL2AXCF7AVCNFSM6AAAAABJBHJQI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZYGQ3TINBSGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
From the release notes of 2025.0, section "Headline Changes":
and from the "Changes since 2025-beta4" section:
See also #757 |
What's the correct action from a CRG perspective. Stop the time out (so it
goes to Lineup on the Main Display), or just start the Jam and let the TO
clock run until the next TO starts?
…On Fri, 15 Nov 2024, 21:51 frank-weinberg, ***@***.***> wrote:
From the release notes of 2025.0, section "Headline Changes":
Due to incompatibilities with other features the "Clock after Timeout"
feature had to be removed.
and from the "Changes since 2025-beta4" section:
Hide unstopped timeouts from the main display and overlay in order to
reduce game impact of operator errors (#783
<#783>)
This broke showing a timeout clock after the timeout ended, so the option
has been removed.
See also #757 <#757>
—
Reply to this email directly, view it on GitHub
<#710 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG3YNG27CH7I2NYSGMZ6YAL2AXG3HAVCNFSM6AAAAABJBHJQI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZYGU2DONJTGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
https://github.com/rollerderby/scoreboard/wiki/Scoreboard-Operation#during-a-timeout - last bullet: "When the jam timer blows the rolling whistle to end the timeout, press the "End Timeout" button." |
Describe the bug
When ending a timeout via the top 'End Timeout' button, the timeout clock continues to run (in the score view below the sbo operator panel it shows the correct end time).
Lineup doesn't automatically start (2023.x only), and when in 'Lineup' will show 'Lineup' on the scoreboard view but shows the timer for the timeout rather than the lineup (see image)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Timeout Clock to end at the correct time, Lineup to automatically start (2023.7 only) and it show the correct lineup clock on the scoreboard
Screenshots
Version:
If this issue occurred on a computer, please complete the following information:
Additional context
Tested with OTO/OR/TT and issue is consistant across all timeout types
The text was updated successfully, but these errors were encountered: