Set some rules regarding the RefBox and its usage

[steup]

THe new refbox has new features, but some of these features may be exploited. Therefore, it is necessary to define some "rules of engagement":

• Task are handed out solely by the refbox (no caching, no self-generation etc ...)
• Information destined to be private needs to stay private to the appropriate group even if eavesdropping is technically possible ( no listening in on other teams task topics, no listening to internal topics of the refbox)
• No control of the refbox by any robot. The control of the refbox is only to be allowed by the designated referee PC. Hacking the protection of control API does not mean it can be used.
• Team shall provide as much state information as possible to enable viewer to understand whats going on: Current arena state, current position of the robot, current configuration of the robot (Arm, Gripper, Inventories), Current navigation path of the robot, currently detected obstacles: (All of this as far as implemented and acceptable performance wise)

[marcomasa]

We tought about the following for the virtual cups:

• OC normally provides the refbox --> not possible for VRC
• Teams provide a map and images of their Arena, which was built regarding some rules we defined
• TC checks the map for suitability of tasks (BTT, final)
• TC creates Tasks for the teams and records bagfiles. Those bagfiles will be distributed to the teams and have to be played to start a competition
• TC agreed on discarding time bonus for perfect runs as this is not comparable for different arena setups

[leanderb]

closed, because the issue is very old and the rulebook have been rewritten in the meantime