Operator table

[jara001]

What do we think of an "operator table" where teams place a laptop on in front of a judge? This would ensure only one laptop is used for telemetry and no tuning is done on the fly from a laptop (i.e adjusting speeds or racelines).

Originally posted by @AhmadAmine998 in #2 (comment)

TODO: Discuss this further and find out how/if can we do this.

Felix:
@jara001 and I have been looking into some network issues we encountered with ROS2 (especially FastDDS, but generally all RMW implementations), and we would highly recommend limiting the number of wireless connections. In our case, this means connecting everything except the car with LAN cables, which could get messy with the "operator table".

I think for Vienna, we could provide LAN infrastructure between the team's tables and the "operator table". But this could be tricky for future races...

Otherwise, I'm in full support of this idea!

[jara001]

I am also in for this. I think it should be then way clearer whether the teams are doing something against the rules or not.

[AhmadAmine998]

I think the operator table would pair well with many of the other rules. It would enable enforcing reconfiguration and stops for crashing and similar edge-cases. If we need to limit wireless connections, then we should do that. All teams that are not currently competing and are not coming up next should have their connections completely shutdown. If need be we may allow the next-to-next if a team needs time to setup (i.e router takes long to turn on or similar). Ideally we should have all teams be able to be ready within 10 minutes to ensure everyone can be ready on time for their slots.

[jara001]

I'll leave it open for now. Issues with that:

• It might be very hard for some team to be able to use the operator table (e.g., moving network stuff).