You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is limited availablity for teams to test their robots in the arenas. We need to plan how we are going to ensure that this time is fairly distributed between teams.
Tinker time slots in the main arena need to be long enough for teams to properly run through their strategies in the actual arena. Conversely, test arena slots need to be regular enough that teams aren't waiting significant times to be able to test.
Required actions:
Decide on the lengths of tinker time and test arena slots
The intention is to try and have this handled by the helpdesk system, so teams can view and book slots from helpdesk, rather than (or at least not only at) staging.
Sounds good. Sounds like we should make sure score entry/competition software coord laptop(s) have access to the Helpdesk system as a Backup for the staging screen.
Is the plan the same for the test arena or are we do the "usual" system for the test arena?
I'd forgotten that was in scope for this ticket. I think that warrants being thought about separately. The helpdesk system will initially just deal with "tinker time". I suspect the "usual" (read: no) system will be used for the test arena, but I'd love to hear from people who have staffed the test arena as to what model works best for them, and whether there's anything we can do to help it.
There is limited availablity for teams to test their robots in the arenas. We need to plan how we are going to ensure that this time is fairly distributed between teams.
Tinker time slots in the main arena need to be long enough for teams to properly run through their strategies in the actual arena. Conversely, test arena slots need to be regular enough that teams aren't waiting significant times to be able to test.
Required actions:
Original
comp/game/tinker-time
Dependencies
The text was updated successfully, but these errors were encountered: