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

Organise how arena testing slots will be booked #1451

Open
1 task done
Tracked by #1457
github-actions bot opened this issue Aug 13, 2024 · 5 comments
Open
1 task done
Tracked by #1457

Organise how arena testing slots will be booked #1451

github-actions bot opened this issue Aug 13, 2024 · 5 comments
Assignees
Labels
AO: Game I: Should Have This task is relatively high priority, but we can survive without

Comments

@github-actions
Copy link

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
  • Decide how tinker time slots are booked
  • Decide how test arena slots are booked
  • Decide where teams book their slots

Original

comp/game/tinker-time

Dependencies

Preview Give feedback
  1. AO: Game I: Must Have
    samjmartin04 sedders123
@github-actions github-actions bot added AO: Game I: Should Have This task is relatively high priority, but we can survive without labels Aug 13, 2024
@github-actions github-actions bot added this to the SR2025 Competition Prep milestone Aug 13, 2024
@RealOrangeOne
Copy link
Member

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.

@RealOrangeOne RealOrangeOne self-assigned this Nov 21, 2024
@samjmartin04
Copy link

Does this mean we'll need a device that has access to the Helpdesk system at staging for booking or do we want to move to only booking at Helpdesk(s)?

@RealOrangeOne
Copy link
Member

The current plan is to do bookings only at helpdesk, and perhaps unofficially at staging (score entry could do it if necessary).

We'll create a screen to show on the shepherding screen for staging to be able to read the schedule without a device.

@samjmartin04
Copy link

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?

@RealOrangeOne
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AO: Game I: Should Have This task is relatively high priority, but we can survive without
Projects
Status: Todo
Development

No branches or pull requests

2 participants