RoboCup 2024 Rule Discussion
Parcour Technical Challenge
-
discussion if hands should be allowed
-
using hands makes it a multi contact whole body motion problem which is scientifically interesting
-
not using hands makes it harder
-
sprint challenge proposed instead as it is more close to the robocup task (and was quite popular at humanoids conference)
Natural Light
-
Some teams are in favor of it
-
depends on venue if available
-
rules already state that robots have to deal with it
Some Technical challenges are only for kid or only for adult
- they make sense in both subleagues so they could be made available to both
Gantries on the Field
-
blocking space of the field
-
maybe designed space next to field could be used instead (like an F1 garage)
-
strecher could be used to carry robots of the field if they are too heavy to carry alone
Pushing and Forceful contact is not called
-
Rules must be made more clear when it should be caled
-
Critique about rule training not clarifying the forceful contact enough were mentioned
-
general problem that often new team members are referees and they do not know the rules that well
GameController is not mentioned in the rules
- there is no notion of the GameController in the rules, the rules could be improved by including information about which button of the GC should be presed when
GameController Undo is not communicated
- the game controller should communicate when undo is pressed as teams can react to this then
Technical challenge description
- Technical Challenge F is not for adult according to rules, this should be fixed
Robot handlers in Adult size
-
difficult as teams do not want their robots falling
-
options to have a transition period
-
increase penalty time for robots with handlers, keep for those without
-
remote controlled stop
-
adult size standup and falling technical challenge
Adult Size 3v3
-
concerns about cost
-
concerns about feasibility when robot handlers are also on the field
-
allows for more strategy as one robot can be dedicated goalie and two can cooperate on the field
Make Game Controller and Standard Protocol
-
could be tested during robot inspection
-
robots should use standard protocol GitHub - RoboCup-Humanoid-TC/RobocupProtocol: Protobuf message protocol for the Robocup Humanoid league to allow for meaningful drop-ins and measuring performance
Measure Basic capabilities
-
measure walking speed, time to position at ball, kicking distance
-
option to use that for seating instead of drop-in games
Cross Team Technical Challenges
-
kick from moving ball could be done with robots from 2 different teams
-
incentivize by awarding additional points
NOTE: The following proposals were presented and only briefly discussed due to time constraints
Kid Size Drop in on Adult Field
More Games for Eliminated Teams (losers bracket) (like in SPL)
Use push stick with force measuring sensor instead of sandbag for push recovery challenge
Scoring in Drop-In games
-
relative scoring per game (e.g. on a -1 to 1 scale for each game)
-
reduce impact of outlier games
-
add penalty for robots that are not on the field when a goal is scored against them (e.g. -2 instead of -1)
Clarify goal kick from moving ball
Robots should wear jerseys
-
many markers are difficult and tedious to inspect during robot inspection
-
t-shirt or 1 solid marker could improve this situation
Emergency buttons
-
proposal to use ISO rules
-
teams would have to know the standard, expensive to buy the document specifying the standard