% !TeX root = ../Rules.tex % !TeX spellcheck = en_US \law{3}{Teams and Players} \label{sec:teams_and_players} \sublaw{Divisions and Configurations} \label{sec:divisions} A team belongs to one division, which is one of Small, Middle and Large. Main competition matches only take place between members in the same division. Teams in each division can choose to play in two team configurations: Foundation - with a smaller number of players; and Advanced - with a larger number of players. If in a game one of the teams chooses to play in a Foundation configuration, then both teams must play in this configuration to ensure fairness. The maximum number of players in a game for each configuration is shown in Table \ref{tab:number_of_players}. In the Middle division, starting from the quarter-finals onwards, all matches will be played in the Advanced configuration. The division and the configuration preference of a team must be submitted before the competition. The division must not change during the competition itself. The division must be submitted at the time of team registration. In addition, each team shall submit its preferred configuration prior to the competition, by a deadline specified by the organizers, in order to enable proper field planning. A team may request to play in a different configuration during the competition by submitting a request to the organizers. Approval of such a request is at the sole discretion of the organizers. \sublaw{Number of Players} \label{sec:number_of_players} A match is played by two teams, each with a \textbf{maximum} number of players determined by the division the game takes place in and the configuration level of the playing teams, as illustrated by the following table: \begin{table}[h] \centering \begin{tblr}{ colspec = {X[l] X[c] X[c]}, width=\linewidth, hlines, vlines, row{1} = {font=\bfseries}, % header }% begin tblr Division & Foundation teams & Advanced teams\\ Small & 4 & 7 \\ Mid & 3 & 5 \\ Large & 3 & 5 \\ \end{tblr} \caption{Number of players} \label{tab:number_of_players} \end{table} At most one player per team on the field may be designated as \emph{goalkeeper}, the others are all \emph{field players}. When playing at full strength, a team must have a \emph{goalkeeper} on the field. \sublaw{Number of Substitutes} \label{sec:number_of_substitutes} In addition, each team may prepare \emph{substitute players} outside the field. The number of substitute players is not limited. A \emph{substitute player} may be substituted in to become a \emph{field player} or \emph{goalkeeper}. \sublaw{Substitution Procedure} \label{sec:substitution_procedure} To replace a player with a substitute, the following conditions must be observed: \begin{itemize} \item The substitution may only occur during the \texttt{initial}, \texttt{set} and \texttt{finished} states (after any penalties are assigned). Robots subject to a standard removal penalty may also be substituted during a brief stop. See \cref{sec:robot_states} for details on the game states. \item The team requests the substitution to the head referee. The substitution can only be made if the head referee approves. \item If the player being substituted is on the field, it must first be removed from the field. \item The substitution is input in the GameController. \item If the player being substituted is not subject to a standard removal penalty, the substitute can either enter the game immediately or remain in the team area for further maintenance and enter at any later time. In either case, when the substitute is ready to enter, it must be given to a robot handler for placement on the standard re-entry point (see \cref{sec:removal_penalty}), and the GameController operator must be informed. The robot will join the game immediately after. \item If the player being substituted is subject to a standard removal penalty, the substitute inherits its penalty state and penalty timer. It then behaves like any other penalized robot, and re-enters the game according to the corresponding rules (see \cref{sec:removal_penalty}). \item Robots that have been sent off cannot be replaced by a substitute (see \cref{sec:caution_sendoff}). \end{itemize} \paragraph{Changing the Goalkeeper} Any of the other players may change places with the goalkeeper, provided that: \begin{itemize} \item The referee is informed before the change is made. \item The change is approved by the head referee. \item The change is requested during the \texttt{initial}, \texttt{set} or \texttt{finished} state. \end{itemize} \sublaw{Robot Players} \label{sec:robot_players} \paragraph{The Design of the Robots} \label{sec:design_of_robots} Robots participating in the \leaguenameabbr must have a human-like body shape with a torso, head, two arms, and two legs, as well as human-like symmetry and proportions regarding sizes of the body parts and weight distribution. The robots must be able to stand upright on their feet, to walk on their legs and to be able to recover from a fall (get back to a standing position). The only allowed modes of locomotion are bipedal walking, running, and jumping. Soccer related movements such as dribbling, kicking, or other forms of ball handling are also allowed. The design of the robot's arms, including their length and placement, shall permit arm use and behaviors that are reasonably comparable to those of humans. Examples of permitted uses include assisting in getting up after a fall or picking up and throwing the ball (where otherwise allowed by the rules). Arm configurations that enable behaviors significantly different from those of humans are not permitted. In particular, robots must not use their arms to provide continuous support for locomotion, such as walking on arms or using arms as additional legs. \paragraph{Size Restrictions} All robots participating in the \leaguenameabbr must comply with the following restrictions: The length of the legs $H_{leg}$, including the feet, satisfies 0.35{\textperiodcentered}$H_{top}$ ${\leq}$ $H_{leg}$ ${\leq}$ 0.7{\textperiodcentered}$H_{top}$, where $H_{top}$ is the height of the top of the robot. The length of the leg is measured from the first rotating joint where its axis lies in the plane parallel to the standing ground to the tip of the foot. A classic piece of human anatomy and art history, Leonardo da Vinci’s “Vitruvian Man” famously depicts a man whose arm span is equal to his height, creating a 1:1 ratio. Therefore, the arm span, $A_{span}$, including the hands, should satisfy 0.8{\textperiodcentered}$H_{top}$ ${\leq}$ $A_{span}$ ${\leq}$ 1.2{\textperiodcentered}$H_{top}$. Based on $H_{top}$, the following size restrictions apply for each division: % \begin{itemize} \item Small: $H_{top}$ ${\leq}$ 1.1 meters; \item Middle: $H_{top}$ ${\leq}$ 1.25 meters; \item Large: $H_{top}$ ${\leq}$ 1.9 meters. \end{itemize} $H_{top}$ is defined as the height of the robot when standing upright (with fully extended knees). $H_{top}$ is measured with the head of the robot oriented in such a way that it is tilted to either its maximum upwards tilt angle or the horizon line, whichever is lower. The height of the head $H_{head}$, including the neck, satisfies $0.1 \cdot H_{top} \leq H_{head} \leq 0.3 \cdot H_{top}$, where $H_{head}$ is defined as the vertical distance from the axis of the first arm joint at the shoulder to the top of the head. \paragraph{Weight Restrictions} The robot's Body-Mass Index (BMI) is defined as follows: $\mathrm{BMI} = \frac{M}{{H_{top}}^2}$, where $M$ is the mass of the robot in kg and $H_{top}$ its height in meters. The Body Mass Index (BMI) of the robot should be: $5 \leq \mathrm{BMI} \leq 30$. The following weight restrictions apply for each division: % \begin{itemize} \item Small: Weight${\leq}$ 15 kilograms; \item Middle: Weight ${\leq}$ 25 kilograms; \item Large: Weight ${\leq}$ 80 kilograms. \end{itemize} \sublaw{Approved Standard Platforms} \label{sec:approved-standard-platforms} The following commercially available robotic platforms are approved for participation in the \leaguenameabbr. The following are the list of pre-approved standard platforms that require no modifications: \begin{tblr}{ width=1.0\linewidth, colspec = {Q[l]Q[l]X[l]}, row{1}={fg=black, font=\bfseries}, %, hline{2} = {solid}, hline{3-Y} = {dashed}, vline{2,3} = {abovepos = -1, belowpos = -1}, } Manufacturer & Model & Restrictions\\ % Aldebaran & Nao V5, and Nao V6 \\ Robotis & DARwIn-OP \\ Booster & T1, and K1 \\ Fourier & GR1, GR1-Pro, and GR2 \\ Unitree & G1++, H1++ \\ \end{tblr} Additional humanoid robot platforms can be approved upon request. Please send your request for approval to \url{hsl_tc@lists.robocup.org}. \sublaw{Hardware} \label{sec:hardware} Modifications or additions to the robot hardware are permitted as long as the resulting robot does not become non-compliant with these rules. No off-board sensing or processing systems are permitted. \sublaw{Sensors} \label{sec:sensors} Teams participating in the \leaguenameabbr competitions are encouraged to equip their robots with sensors that have an equivalent in human senses. These sensors must be placed at a position roughly equivalent to the location of the human's biological sensors. The sensors and their placement shall be chosen such that they allow the robot a spatial perception similar to humans. % The sensors are evaluated along the following two general guidelines: \begin{enumerate} \item \emph{Foster and encourage research and development towards human-like perception capabilities.}\\ Sensors aiming to directly emulate human senses, like a camera or a microphone. Use of such sensors is explicitly \emph{encouraged}. \item \emph{Enable research and development under the constraints of the current state of the art in technology and research, as long as this does not undermine current research efforts as declared in point 1.} \\ Sensors that compensate for current shortcomings in technology and state of research, like one-dimensional distance sensors with limited range, or two vertically arranged cameras in the robot NAO. \end{enumerate} Generally, \emph{passive sensors} are preferred to \emph{active} sensors that actively emit signals. \paragraph{Intrinsic Perception and Proprioception} Any sensing capability aiming at measuring the internal state of the robot is permitted. This includes temperature, current consumed by the motors, joint positions, etc. \paragraph{Visual Perception} The visual sensors, e.g., cameras of the robot shall be arranged such that the combined visual field is \emph{contiguous} and limited to dimensions similar to a human, which corresponds to limitations in the opening angle: horizontal $\leq$ \SI{220}{\degree} and vertical $\leq$ \SI{160}{\degree}. Please note that these ranges may be adjusted to more human-like viewing angles in the future. The visual sensors shall be located in the head of the robot. The combined dynamic visual field that can be observed by the robot solely by moving its cameras (similar to human eye movements) and the head is limited to horizontal $\leq$ \SI{340}{\degree} and vertical $\leq$ \SI{220}{\degree}. The cameras are restricted to visual information in the range of the light visible to humans. The cameras can provide dense visual information, such as a rasterized image, or sparse information, such as visual events (event cameras). \paragraph{Visual (dense) Depth Perception} Passive integrated devices that provide dense depth information, such as stereo cameras, are permitted and encouraged. Active integrated devices that provide depth information, such as cameras with an active infrared projector or time-of-flight cameras, are permitted but discouraged. Their use might be prohibited in the future. \paragraph{Orientation} Sensors providing information regarding the robot's orientation in space with relation to the ground are permitted. This includes sensors such as gyrometer, accelerometer, as well as integrated inertial measurement units (IMU), as long as they provide only relative measurements and no measurements of the absolute direction, such as a compass. An IMU with an integrated compass can be used as long as the compass is not used. The sensors can be placed in the head and/or in the torso of the robot. \paragraph{Sound Perception} The sound sensors, e.g., microphones, shall be placed in the head of the robot. The number of microphones is not limited. \paragraph{Haptic Sensing} Any passive sensor allowing haptic measurement is permitted, such as force sensors, touch sensors, buttons/bumpers, capacitive touch sensors. Haptic sensors can be placed at any location of the robot's body and are not limited in number. \paragraph{Distance Sensing} Active and passive sensors for one-dimensional distance sensing with a limited range are permitted if their use is limited to compensate for shortcomings in the spatial awareness of the robot in the close proximity. %The range is limited to ... The number of such distance sensors is limited to 4. The use of distance sensors is discouraged and might be prohibited in the future. \paragraph{Summary} The \Cref{tab:sensors} summarizes the approved sensors. The use of listed sensors that are considered human-like is encouraged. The use of listed sensors that are not considered human-like is accepted, but discouraged and might be prohibited or limited in the future. \begin{table}[ht] \centering \begin{tblr}{ width=1.0\linewidth, colspec = {Q[l]Q[l]X[l]}, row{1}={fg=black, font=\bfseries}, %, hline{2} = {solid}, hline{3-Y} = {dashed}, vline{2,3} = {abovepos = -1, belowpos = -1}, } Sensor Type & Human-Like & Comments \\ %Visual Perception RGB camera & yes & opening angle limit: horizontal $\leq$ \SI{180}{\degree}, vertical $\leq$ \SI{140}{\degree}\\ Stereo camera & yes & \\ Event camera & yes & \\ Active RGB-D based on infrared projection & no & discouraged\\ Active RGB-D based on time of flight (TOF) & no & discouraged\\ % sound perception Microphone array & yes & \\ % Orientation Gyro & yes & \\ Accelerometer & yes & \\ Compass & no & magnetic measurement sensors are not allowed\\ Integrated inertial measurement units (IMU) & yes & no compass or must be disabled and not used\\ % Haptic sensing Force sensors & yes & \\ Touch sensors & yes & \\ Buttons / Bumpers & yes & \\ Capacitive touch sensors & yes & \\ % Distance sensing Near range infrared sensor & no & \\ Sonar / ultrasound sensors & no & \\ 1D LIDAR and laser range sensor & no & with limited range \\ % Intrinsic sensors Intrinsic sensors & yes & temperature, current, joint positions, etc. \\ \end{tblr} \caption{Summary of approved sensor types.} \label{tab:sensors} \end{table} \sublaw{Communication} \label{sec:communication} Robots participating in the \leaguenameabbr competitions must act autonomously during a game. Any use of external power supplies, teleoperation, remote control, remote processing, remote sensing, or remote brain of any kind is prohibited. Communication is only allowed among robots on the field, between the robots and the referees, and between the robots and the GameController. \paragraph{Acoustic and Visual Communication} \label{sec:acoustic} %In general, there are no restrictions on communication between robots in play on the field using visual signaling (\eg, gestures) or the robot's built-in microphones, speakers, and infrared transceivers. The robots are permitted to communicate through visual signaling (\eg, gestures) and/or acoustic signaling using the robot's built-in microphones and speakers. Communication that causes excessive discomfort to an audience, affects the safety of an audience, or violates normal playing rules is not permitted. \paragraph{Wireless Communications:} \label{sec:wireless} The robots are permitted to communicate through WiFi using built-in wireless adapters. % technical A field is equipped with a wireless access point that must be used for any wireless communication during the game. Only the teams involved in the game are permitted to use the access point during a match. Each team will be assigned a range of IP addresses that can be used both for their robots and their computers. The network configuration (\eg IP addresses, channels, SSIDs, and required encryption) of the fields will be announced at the competition site. Wireless equipment and access points will be provided by the organizers of the competition. No other \qty{2.4}{\giga\hertz} or \qty{5}{\giga\hertz} radio equipment (including cellular phones and/or Bluetooth devices) is allowed to be used close to the field. \paragraph{Wireless Robot-To-Robot Communication:} \label{sec:robot-to-robot} % AP Wireless robot-to-robot communication between the robot players is allowed and must use the access points provided by the event organizers. Direct wireless communication between the robots (using the so-called ad-hoc mode) is prohibited. % protocol Messages must be sent via UDP broadcast. Each message's payload size must not exceed \qty{\UDPPacketSize}{\byte}. Each team will be allocated a single UDP port on which to send/receive their team messages. Specifically, a team's port will be 10000 plus that team's GameController number. Unicast communication between robots is prohibited. % event based %Each team is allowed to send a maximum of \UDPPacketLimit{} UDP packets of up to \qty{\UDPPacketSize}{\byte} per game, %in addition to \UDPDebugPacketRate{} packet per second per robot to a single team device on the wired network for debugging purposes %(no size constraint for debug packets, but must be within the maximum single UDP packet size). Each team is allowed to send in total a maximum of \UDPPacketLimit{} messages during a complete game. This limit can change during a game only in these cases: \begin{itemize} \item For each minute of additional time added by the \emph{Allowance for time lost} rule (see Section \ref{sec:allowance_time_lost}), the limit is immediately increased by 600 packets. \item If the game proceeds to extra time (see Section \ref{sec:permitted_tiebreakers}), the limit is increased by 6000 packets before the beginning of the first half of extra time. \end{itemize} % when to count? Only messages sent by the robot players in the following game states count towards the communication limit: \texttt{ready}, \texttt{set} and \texttt{playing}. Any messages sent during other game states do not count towards the teams message budget. Limits do not apply during penalty kick shoot-out. The number and the size of the messages sent by each team is monitored by the GameController. A violation of the permitted maximal size of a message or the maximal number of messages is subject to penalty (see Section \ref{sec:jamming}). The limit of allowed packets will be lowered in future competitions to encourage a progress towards human-like communication and coordination. \paragraph{GameController Communication:} The GameController will communicate at \GameControllerPacketRate{} packet(s) per second. Robots are required to respond to GameController messages and send status update packets to the GameController. The format for the GameController messages and for the responses is defined in the official GameController.\footnote{\url{https://github.com/RoboCup-HumanoidSoccerLeague/GameController/blob/master/game_controller_msgs/headers/RoboCupGameControlData.h}} \paragraph{Debug Communication:} %in addition to \UDPDebugPacketRate{} packet per second per robot to a single team device on the wired network for debugging purposes % Team specific debug information may be sent to an external computer owned by the team. Each robot may send debug information in a single UDP packet to a single team device on the wired network. The robot may send at most \UDPDebugPacketRate{} packet(s) per second. The size of a single packet is not explicitly restricted, but must be within the maximum single UDP packet size (typically 64kB). \sublaw{Safety} \label{sec:robot_safety} \paragraph{Dangerous Equipment} A player must not use equipment or wear anything that is dangerous to himself or another player. \paragraph{Physical Stop} Robot handlers must be able to immediately and physically bring a robot to a safe state at any point in the game (\cf~\Cref{sec:robot_handlers}). It is the responsibility of the teams to ensure that a robot can be physically stopped by their handler in case of emergency. %Most important is that robot operators are able to bring a robot to a safe state in an emergency. %The mechanism used to do this (e.g. emergency button on the robot, remote emergency button) is secondary. %Robots are encouraged to be equipped with an emergency stop button that makes the robot immediately desist with all motions, or ideally go limp and/or cut power to the actuators. The team must be able to demonstrate their ability to physically stop their robots on request at any time during the competition. In order to ensure that a robot can be physically stopped at any time, the robots can be equipped with dedicated safety features. \subparagraph{Passive Features} The robot can be equipped with passive components that allow for it to be physically restrained without danger to the human handler. Examples of such components are grips or handles on the back of the robot, and design features of the robot's body that allows a human to safely hold the robot. \subparagraph{Active Features} The robot can be equipped with active components that make the robot immediately stop all movements and assume a safe posture. Examples for such components are a physical button on the robot, emergency switch on the robot, remote emergency button. \subparagraph{Remote Emergency Button} Robots can be equipped with a remote emergency button. A remote emergency button is a device that is not physically attached to the robot and can send a remote signal to the robot causing it to stop all movement and assume a safe posture. Each emergency stop button can only be connected to one specific robot. Manufacturer(s) of standard platform robots may provide a remote emergency button (or functionality) as part of the operating procedures of the robot. Unless otherwise listed in \Cref{sec:approved-standard-platforms} these may be available at all times. Where a robot is equipped with a remote emergency button in addition to manufacturer provisions, the remote emergency button should not perform any additional functions. Where a remote emergency stop is activated via a device that performs other functions (such as teleoperated control of the robot), during game play the device must be placed in a specially marked zone within the team's Technical Area (\cf~\Cref{sec:robot_handlers}). Further, the device may only be touched for the purpose activating the remote emergency button. Any other interaction with the device will result in a penalty against the team (\cf~\Cref{sec:penalties_against_humans}). \paragraph{GameController Stop} The robots must comply with the GameController protocol and immediately assume a safe pose when the command is sent by the GameController as formulated in \Cref{sec:state_emergency_stop,sec:wireless}. \law{4}{The Players' Equipment} \sublaw{Team Markers} \label{sec:team_markers} Robot bodies must be colored mostly with a neutral color, such as black, gray, white, or silver, and be non-reflective. Robots must use colored jersey shirts as team markers. A jersey is a tank top-style shirt that may start at the neck and go down to the waistline, and does not cover the arms of the robots. It must cover at least 50\% of the upper body of the robot. Each robot has a unique jersey number from the set $\{1, 2, 3, \ldots, 20\}$. Jerseys must have a primary color that comprises more than half of the jersey. The primary color must be recognizable from the front and back. Jerseys should not contain distracting patterns that could be confused with other elements of the soccer field, such as field lines or the ball. Jersey material must be non-reflecting, non-shiny, and non-glittery. Jerseys may be manufactured from fabric and fine mesh. The two teams must wear colors that distinguish them from each other and also the referee and the assistant referees. Each team must provide two jersey designs in distinctly different solid colors. The jersey color must clearly contrast with any uncovered parts of the robot to ensure reliable identification. Robots must display clear identification numbers (player number): a large number on the back and a smaller number on the front. The goalkeeper robot must be uniquely marked so that it can be easily distinguished from the other robots on the same team by the referees. Some possible examples of markings: \begin{itemize} \item A distinct jersey color. The goalkeeper is allowed to wear a jersey with a different primary color from the rest of the team, either by wearing the team's second kit or by introducing a new color entirely. If the goalkeeper does use a distinct jersey color, it must be different from the field players of both teams, and it should also be different from the opposing goalkeeper if possible. Jersey numbers must still be unique among all the robots of one team currently on the field. \item The jersey number. Informing the referees before the game starts of which jersey number will act as the goalkeeper is considered a sufficient marking. The goalkeeper may use any of the allowed jersey numbers. \end{itemize} \paragraph*{Sponsorship logos.} Sponsorship logos on the jerseys are allowed on the arms and legs of the robots, as well as the jerseys. Logos on the arms and legs must not cover more than $25\%$ of the limb, and logos on jerseys must not occupy more than $50\%$ of the surface, ensuring that a suitable portion of the robot remains in the respective primary color. Logos, like the other aesthetic elements, must not interfere with the player numbers, and they must not include distracting patterns and colors that could be confused with other elements of the soccer field, such as the field lines or the ball. \paragraph*{Approval.} Jersey designs must be submitted for approval prior to the competition by a deadline specified by the organizers. Jerseys shall be reviewed and approved by the technical committee prior to the competition.