RCJRescue Line 2023 Rules
RCJRescue Line 2023 Rules
Rules 2023
RoboCupJunior Rescue Committee 2022
Official Resources
RoboCupJunior Official Website RoboCupJunior Official Forum RCJ Rescue Community Website
https://junior.robocup.org https://junior.forum.robocup.org
https://rescue.rcj.cloud
Corrections and clarifications to the rules may be posted on the forum before updating
this rule file. It is the responsibility of the teams to review the forum to have a complete
vision of these rules.
Scenario
The land is too dangerous for humans to reach the victims. Your team has been given a difficult task. The
robot must be able to carry out a rescue mission in a fully autonomous mode with no human assistance.
The robot must be durable and intelligent enough to navigate treacherous terrain with hills, uneven
land, and rubble without getting stuck. The robot must transport rescue first aid kits that can be held
from the beginning of the rescue or picked up on their way to the victims. When the robot reaches the
victims, it has to gently and carefully transport each one to the safe evacuation point, together with the
rescue kit, where humans can take over the rescue. The robot should exit the evacuation zone after a
successful rescue to continue its mission throughout the disaster scene until it leaves the site. Time and
technical skills are essential! Come prepared to be the most successful rescue team.
Teams are not allowed to give their robot any information in advance about the field as the robot is
supposed to recognize the area by itself. The robot earns points as follows:
• 10 points for following the correct path on a tile at an intersection or a dead end.
• 15 points for overcoming each obstacle (bricks, blocks, weights, and other large, heavy items). A
robot is expected to navigate various obstacles.
If the robot gets stuck in the field, it can be restarted at the last visited checkpoint. The robot will earn
points when it reaches new checkpoints. Somewhere on the path, there will be a rectangular zone with
walls (the evacuation zone). The evacuation zone is delimited in the entrance with a reflective silver
tape strip attached to the floor and the exit with a strip of black tape.
Once in the evacuation zone, the robot should locate and transport the victims to the designated
evacuation points. The victims are represented by balls of 4 to 5 cm in diameter. The live victims are
reflective silver which is electrically conductive, and the dead victims are black, which is not electrically
conductive.
A rescue kit will be delivered to the live victims and transported to the designated evacuation point. The
team can earn multipliers for victim evacuations, depending on the difficulty level, rescue order, and
rescue kit delivery. Be prepared to face obstacles, speed bumps, and debris in the evacuation zone. Still,
the robot will not score points by negotiating these difficulties here. The robot should then exit the
evacuation zone and follow the line until the goal tile of the course is reached.
2. The volunteers, referees, and officials will act within the event’s spirit to ensure the competition is
competitive, fair, and, most importantly, fun.
3. It is not whether you win or lose but how much you learn that counts!
2. Humans who cause deliberate interference with robots or damage the field will be disqualified.
1.3. Behavior
1. Each team is responsible for verifying the latest version of the rules on the RoboCupJunior Official
website and additional clarifications/corrections on the official forum made by the RoboCupJunior
Rescue Committee before the competition.
2. Participants should be mindful of other people and their robots when moving around the
tournament venue.
3. Participants are not allowed to enter setup areas of other leagues or teams unless explicitly invited to
do so by team members.
4. Teams will be responsible for checking updated information (schedules, meetings, announcements,
etc.) during the event. The RoboCupJunior Rescue Committee will provide updated information on
notice boards in the venue, the local competition website, or the RoboCupJunior website if possible.
5. Participants and their companions who misbehave may be asked to leave the venue and risk being
disqualified from the tournament.
6. Referees, officials, tournament organizers, and local law enforcement authorities will enforce these
rules equally to all participants.
7. Teams are expected to be at the venue early on the setup day as important activities will occur. These
activities include but are not limited to registration, participation raffle, interviews, captains, and
mentor’s meetings, among others.
1.4. Mentors
1. Non-team members (mentors, teachers, parents and other family, chaperones, translators, and other
adult team members) are not allowed in the student work area.
3. In the first instance, mentor interference with robots or referee decisions will result in a warning. If
this behavior recurs, the team could face a possible elimination from the tournament.
4. Robots have to be the work of the students. Any robot that appears identical to another robot may be
prompted for re-inspection.
a. Mentors working on the software or hardware of student’s robot(s) during the competition.
b. More experienced/advanced groups of students may provide advice but should not do the work
for other groups. Otherwise, the team risks being disqualified.
2. RoboCupJunior reserves the right to revoke an award if fraudulent behavior is proven after the
award ceremony occurs.
3. Suppose it is evident that a mentor intentionally violates the code of conduct and modifies and
works on the student’s robot(s) during the competition. In that case, the mentor will be banned from
future participation in RoboCupJunior competitions.
4. Teams that violate the code of conduct can be disqualified from the tournament. Disqualifying a
single team member from further participation in the tournament is also possible.
5. Referees, officials, tournament organizers, and local law enforcement authorities will give a team a
warning in less severe cases of violations of the code of conduct. A team can be disqualified
immediately without warning for severe or repeated violations of the code of conduct.
1.6. Sharing
1. The spirit of world RoboCup competitions is that teams should share technological and curricular
developments with other participants after the tournament. Sharing furthers the mission of
RoboCupJunior as an educational initiative.
2. The RoboCupJunior Rescue Committee may publish developments on the RoboCupJunior website
after the event.
3. Participants are strongly encouraged to ask questions to their fellow competitors to foster a culture
of curiosity and exploration in the fields of science and technology.
2. Field
2.1. Description
1. The field comprises modular tiles, which the organizers can use to make an endless number of
courses for the robots to traverse.
3. There will be a minimum of 8 tiles in a competition field, excluding the start and goal tiles.
4. There are different tile designs (teams can find examples under 2.3).
2.2. Floor
1. The floor is white. The floor may be either smooth or textured (like linoleum or carpet) and may
have steps of up to 3 mm in height between tiles. Due to the nature of the tiles, there may be a step or
gaps in the construction of the field.
2. Competitors should be aware that tiles may be mounted on thick backing or raised off the ground,
making it difficult to get back on a tile where the robot comes off the course. No provision will be
made to assist robots that drive off a tile to get back onto the tile.
3. Robots must be designed to navigate under tiles that form bridges over other tiles. Tiles placed above
other tiles will be supported by pillars at tile corners with a square cross-section of 25mm x 25mm,
making each tile entrance/exit 25 cm. The minimum height (space between the floor and the ceiling)
will be 25 cm.
2.3. Line
1. The black line, 1-2 cm wide, may be made with standard electrical insulating tape or printed onto
paper or other materials. The black line forms a path on the floor. (The grid lines indicated in the
drawings below are for reference only, and competitors can expect tiles to be added or omitted.)
2. Straight sections of the black line may have gaps with at least 5 cm of the straight line before each
gap as measured from the shortest portion of the straight part of the line. The length of a gap will be
no more than 20 cm.
3. The arrangement of the tiles and paths may vary between rounds.
4. The line will be 10 cm away from any edge of the field, walls, pillars to support ramps, seesaws, and
obstacles that do not lie ahead of the robot’s path.
5. The line will end with a goal tile with a 25mm x 300mm strip of red tape in the center of the tile,
perpendicular to the incoming line.
4. A checkpoint marker is a marker that indicates for humans which tiles are checkpoints. A disk with 5
mm to 12 mm thickness and up to 70 mm in diameter has been used frequently. Still, it can be
different depending on the organizer.
5. The field designers will predetermine the number of checkpoint markers and their locations.
2. Speed bumps may also be placed anywhere in the evacuation zone. Speed bumps in evacuation zone
are not scored.
3. Debris will have a maximum height of 3 mm. The organizers will not fix it to the floor. The debris
consists of small materials such as toothpicks, small wooden dowels, etc.
4. Obstacles may include bricks, blocks, weights, and other large, heavy items. Obstacles will be at least
15 cm high and can be fixed to the floor.
6. A robot is expected to navigate around obstacles. The robot may move obstacles, but obstacles may
be very heavy or fixed to the floor. Obstacles will remain where they were moved to, even if that
prevents the robot from proceeding.
7. Obstacles will not be placed closer than 25 cm from the edge of the field (including edges of tiles that
are elevated by ramps) and inclined tiles.
8. In the evacuation zone, obstacles may be placed anywhere with a minimum of 10 cm clearance from
the wall. Obstacles in the evacuation zone are not scored.
2. Intersections markers are green and 25 mm x 25 mm in dimension. They indicate the direction of the
path the robot should follow.
3. The robot should continue straight ahead if there is no green marker at an intersection.
4. A dead end is when there are two green marks before an intersection (one on each side of the line);
in this case, the robot should turn around.
2.7. Ramps
1. Tiles will be used as ramps to allow the robots to 'climb' up and down from different levels.
3. More than one tile may be used to build one ramp up or down. Despite the number of tiles used in
the construction, the ramp will be scored as one ramp as it takes from one level to another.
4. The ramp will be scored when the robot reaches the horizontal tile at the upper level after an
ascending ramp or the horizontal tile at the bottom level after a descending ramp.
5. The line along the ramps can contain gaps, speed bumps and debris.
2.8. Seesaws
1. A seesaw is a tile that can pivot around a hinge in the center of a regular tile.
2. The seesaw will have an incline less than 20 degrees when tilted to one side.
3. The seesaw tile will have a straight line with no scoring elements present.
2. The black line will begin again at the exit of the evacuation zone.
3. The evacuation zone is 120 cm by 90 cm with walls around the four sides at least 10 cm high and
colored white.
4. At the entrance to the evacuation zone, there is a 25 mm × 250 mm strip of reflective silver tape on
the floor.
5. At the exit of the evacuation zone, there is a 25 mm × 250 mm strip of black tape on the floor.
6. The organizers may place an obstacle inside the evacuation zone. In the evacuation zone, organizers
may put the obstacle anywhere with a minimum of 10 cm clearance from the wall. Obstacles in the
evacuation zone are not scored.
7. Safe evacuation points are defined by right-angled triangles with sides of 30 cm x 30 cm.
a. There will be one red evacuation point where the dead victim must be placed by the robot and,
b. There will be one green evacuation point where the living victims must be placed by the robot.
The robot must also place the rescue kit inside the green evacuation point.
8. Teams can choose between two different structures for evacuation points:
a. Level one: The evacuation points are red and green triangles with a bump of 5mm along the side
that does not touch a wall.
b. Level two: The evacuation points are red and green triangles with 6 cm walls and a hollow
center.
9. The chosen level is applied for both red and green evacuation points.
10. The referee can randomly place the evacuation points in any non-entry/exit corners in the
evacuation zone by rolling a dice.
11. After a Lack of Progress, the referee may roll the dice again and place the evacuation points in new
corners.
12. The organizers will fix the evacuation points to the floor. Still, teams should be prepared for slight
movements in the evacuation points.
2. A victim represents a person and is in the form of a 4-5 cm diameter ball with a maximum weight of
80 g.
b. Living victims are silver, reflect light, and are electrically conductive.
4. Organizers will locate the victims randomly in the evacuation zone. There will be precisely two live
victims and one dead victim placed in the evacuation zone.
a. Level one: carry a rescue kit from the start tile and drop it off at the designated evacuation point,
or
b. Level two: to have the rescue kit on the path towards the evacuation zone.
3. If the team chooses the rescue kit to be placed on the path (level two rescue kit):
a. Organizers will place the rescue kit after the final speed bump and obstacle before the
evacuation zone.
b. When viewed from above, the furthest point of the rescue kit will be a maximum of 5 cm from a
nearby black line.
3. The field may be affected by magnetic fields (e.g., under-floor wiring and metallic objects). Teams
should prepare their robots to handle such interference.
4. The field may be affected by unexpected lighting interference (e.g., camera flash from spectators).
Teams should prepare their robots to handle such interference.
3. Robots
3.1. Control
1. Robots must be controlled autonomously. Using a remote control, manual control, or passing
information (by external sensors, cables, wirelessly, etc.) to the robot is not allowed.
3. Any pre-mapped type of dead reckoning (movements preprogrammed based on known locations or
placement of features in the field) is prohibited.
4. Robots must not damage any part of the field in any way.
3.2. Construction
1. Any robot kit or building blocks, either available on the market or built from raw hardware, may be
used as long as the design and construction of the robot are primarily and substantially the students'
original work.
2. Teams are not permitted to use commercially produced robot kits or sensors components specifically
designed or marketed to complete any single primary task of RoboCupJunior Rescue. Robots that do
not comply will face immediate disqualification from the tournament. If there is any doubt, teams
should consult the RoboCupJunior Rescue Committee before the competition.
3. Only lasers from classes 1 and 2 are allowed for the safety of participants and spectators. The
organizers will check this during the inspection. Teams using lasers must have the datasheet of the
laser and submit them before the competition and be able to show them during the competition.
4. Wireless communication must be used as described on the RoboCupJunior General Rules. Robots
performing other types of wireless communication need to be deleted or disabled. If the robot has
other wireless communication equipment, the team must prove they are disabled. Non-conforming
robots may be immediately disqualified from the tournament.
5. Robots may incur damage by falling off the field, making contact with another robot, or contacting
field elements. The RoboCupJunior Rescue Committee cannot anticipate all potential situations
where damage to the robot may occur. Teams should ensure that all active elements on a robot are
adequately protected with resistant materials. For example, teams must protect electrical circuits
from all human contact and direct contact with other robots and field elements.
6. When batteries are transported, moved, or charged, it is strongly recommended that safety bags be
7. Robots must be equipped with a handle that is to be used to pick them up during the scoring
run.
8. Robots must be equipped with a single physical binary switch/button (with exception of
buttons that are a part of commercial controller), clearly visible to the referee, for starting the
robot at the begining ot run and when a lack of progress occurs. Procedure performed after
LoP occurs can only include this button and at most one more switch for cutting the power.
Team has to notify the referee about their LoP procedure before each scoring run, and only
this procedure is allowed to be performed after a LoP.
3.3. Team
1. Each team must have only one robot on the field.
2. Each team must comply with the RoboCupJunior General Rules regarding the number of members
and each member’s age.
3. Each team member must explain their work and have a specific technical role.
4. A student can be registered on only one team across all RoboCupJunior leagues/sub-leagues.
5. A team can only participate in one league/sub-league across all RoboCupJunior leagues/sub-leagues.
6. Team members may compete in Rescue Line twice (2 international events). After competing in
Rescue Line twice, they must move to another RoboCupJunior sub-league.
7. Mentors/parents are not allowed to be with the students during the competition. The students will
have to govern themselves (without a mentor’s supervision or assistance) during the long stretch of
hours at the competition.
3.4. Inspection
1. A panel of referees will scrutinize the robots before the start of the tournament and at other times
during the competition to ensure that they meet the constraints described in these rules.
2. Using a robot similar to another team’s robot from a previous year or the current year is illegal.
3. The team’s responsibility is to have their robot re-inspected if modified at any time during the
tournament.
4. Students will be asked to explain their robot’s operation to verify that its construction and
programming are their own work.
5. Students will be asked about their preparation efforts. The RoboCupJunior Rescue Committee may
request them to answer surveys and participate in videotaped interviews for research purposes.
6. All teams must complete a web form before the competition to allow referees to prepare better for
the interviews. The RoboCupJunior Rescue Committee will provide instructions on submitting the
form to the teams before the competition.
7. All teams must submit their Technical Description Paper (TDP) before the competition. The TDP is a
8. All teams have to submit their source code before the competition. The organizers will not share the
source code with other teams without the team’s permission. The organizers will request permission
at the registration.
9. All teams must submit their Engineering Journal before the competition. The organizers will not
share the journals with other teams without the team’s permission. The organizers will request
permission at the registration. A guide for the Engineering Journal format and rubrics are available
on the RoboCupJunior Official website.
3.5. Violations
1. Any violations of the inspection rules will prevent the offending robot from competing until
modifications are made, and the robot passes inspection.
2. Teams must make modifications within the schedule of the tournament, and teams cannot delay
tournament play while making modifications.
3. Suppose a robot fails to meet all specifications (even with modifications). In that case, it will be
disqualified from that game (but not from the tournament).
5. Any rule violations may be penalized by disqualification from the tournament or the game or result
in a loss of points at the discretion of the referees, officials, or RoboCupJunior Rescue Committee.
4. Play
4.1. Pre-game Practice
1. When possible, teams will have access to practice fields for calibration and testing throughout the
competition.
2. Whenever there are dedicated independent fields for competition and practice, it is at the
organizers' discretion if testing is allowed on the competition fields.
4.2. Humans
1. Teams should designate one of their members as 'captain' and another as 'co-captain'. Only these two
team members will be allowed access to the competition fields unless directed by a referee. Only the
captain can interact with the robot during a scoring run.
3. Other team members (and any spectators) within the vicinity of the competition field must stand at
least 150 cm away from the field unless directed by a referee.
5. All pre-mapping activities will immediately disqualify the robot for the round. Pre-mapping is the act
of humans providing the robot with information about the field (e.g., location of obstacles, entrance
to the evacuation zone, number of tiles after the evacuation zone, etc…) before the game.
2. Each team has a maximum of 8 minutes for a game. The game includes the time for calibration and
the scoring run.
3. Calibration is taking sensor readings and modifying the robot’s programming to accommodate such
sensor readings. Calibration does not count as pre-mapping.
4. The scoring run is defined as the time when the robot is moving autonomously to navigate the field,
and the referee will record the scores.
5. A game begins at the scheduled starting time, whether or not the team is present or ready. Start
times will be posted around the venue.
6. Once the game has begun, the robot is not permitted to leave the competition area.
7. Teams may calibrate their robot in as many locations as desired on the field, but the clock will
continue to run. Robots are not permitted to move on their own while calibrating.
8. Once a team is ready to start a scoring run, the team must notify the referee. To start a scoring run,
the robot is placed on the start tile of the course, as indicated by the referee. Once a scoring run has
begun, no more calibration is permitted, including changing code/code selection.
9. Teams may choose not to calibrate the robot and immediately start the scoring run instead.
10. Once a robot begins its scoring run, the referee will roll a standard 6-sided dice to determine in
which corner the evacuation points will be located.
11. Individual tiles, obstacles, and other scoring elements may be removed, added, or changed when the
robot starts moving; to prevent teams from pre-mapping the layout of the fields. These changes may
happen based on a die rolled by the referee or with another method of randomization announced by
the organizers. For a particular field during a round, the referee will ensure the difficulty of the field
will be kept similar, and the maximum points are constant.
2. Modifying the robot during a scoring run is prohibited, which includes remounting parts that have
3. Any parts the robot loses intentionally or unintentionally will be left in the field until the run is over.
Team members and referees cannot move or remove elements from the field during a scoring run.
4. Teams cannot give their robot any information about the field. A robot is supposed to recognize the
field elements by itself.
5. The robot must follow the course completely to enter the evacuation zone and then out of the
evacuation zone towards the goal tile.
6. The robot has reached a tile when more than half the robot is within that tile when viewed from
above and robot is actively following the line at that point in time.
b. a robot loses the black line without regaining it by the next tile in the sequence (see figures at the
end of the section).
2. If a lack of progress occurs, the robot must be positioned on the previous checkpoint tile facing the
path towards the goal tile and checked by the referee.
3. After a lack of progress, only the LoP procedure explained to the referee before the run start is
allowed to be performed (see 3.2.8).
5. After three failed attempts to reach a checkpoint, a robot is allowed to proceed to the next
checkpoint.
a. The team captain may make further attempts at the course to earn additional points from scoring
elements that have not already been earned before reaching the next checkpoint.
6. Suppose a lack of progress occurs in the evacuation zone. In that case, all victims (including ones that
have rolled) will remain in their current position. Victims that are held by the robot will be placed
roughly on the robot’s location when a lack of progress occurs in the evacuation zone. Suppose a lack
of progress occurs as the robot exits the evacuation zone while carrying victims. In that case, the
victims will be randomly placed in the evacuation zone.
7. The rescue kit will be left in the exact location (even if it is located on the robot) when a lack of
progress is called.
8. Any seesaws ahead of the robot’s path can be moved in a favorable direction when a lack of progress
is called.
2. Failed attempts at navigating hazards in the field are defined as a Lack of Progress (see 4.5).
3. When a robot reaches a checkpoint tile, it will earn points for each tile it has passed since the
previous checkpoint. The points per tile depending on how many attempts the robot has made to
reach the checkpoint:
5. The referees will not count any hazards in the evacuation zone towards additional points.
6. Successful victim rescue (SVR): Robots are awarded multipliers for successfully rescuing victims. A
successful victim rescue occurs when the victim is entirely moved into the designated evacuation
point, and no part of the robot can be in contact with the victim. When the referee determines there
has been a successful victim rescue, the referee will remove the victim from the evacuation point to
allow more victims to be evacuated. The multipliers are allocated as such:
▪ (SDVR) = × 1.2 per successful rescue of the dead victim if both living victims have already
been successfully evacuated.
▪ (SDVR) = × 1.4 per successful rescue of the dead victim if both living victims have already
been successfully evacuated.
7. Only the victims placed by the robot at the appropriate evacuation point will be awarded multipliers.
8. When a lack of progress occurs between checkpoints (or a checkpoint and the goal) containing an
evacuation zone, each of the (SVR) obtained multipliers will be deducted:
a. Level one evacuation point: (EZLP) = -0.025 x (number of lack of progresses in the area
containing an evacuation zone)
b. Level two evacuation point: (EZLP) = -0.05 x (number of lack of progresses in the area containing
an evacuation zone)
10. An additional multiplier will be awarded for the rescue kit placed completely inside the green
evacuation point, as such:
◦ Level one evacuation point & Level one rescue kit: (RK) = × 1.1
◦ Level one evacuation point & Level two rescue kit: (RK) = × 1.3
◦ Level two evacuation point & Level one rescue kit: (RK) = × 1.2
◦ Level two evacuation point & Level two rescue kit: (RK) = × 1.6
12. An exit bonus is awarded when the robot has reached the goal tile and has completely stopped for
more than 5 seconds (this time is included in the total 8 minutes). The exit bonus is a non-negative
number and is given by
13. The multipliers from successful evacuations are multiplied by the score obtained from the line
tracing course.
(FIELD SCORE) = (LINE TRACING SCORE + EXIT BONUS) x (EVACUATION ZONE MULTIPLIER)
14. The field score for every round will be normalized with the score of the best team of that round:
15. The final score is made up of a weighted sum of normalized scores from the field score and the
rubrics as such:
(TOTAL SCORE) = 0.8 x (MEAN OF NORMALIZED FIELD SCORES) + 0.2 x (NORMALIZED RUBRICS
SCORE)
16. The normalized rubrics score is made up of a sum of normalized scores for the individual rubrics as
follows:
17. The Rubrics for TDP, Engineering Journal, and Poster will be available on the RoboCupJunior website
and the RCJ Rescue Community website.
c. the robot reaches the goal tile and completely stops for 5 seconds
2. Judges will circulate and interact with the teams. The Open Technical Evaluation is intended to be a
casual conversation with a question-and-answer atmosphere.
◦ creativity
◦ cleverness
◦ simplicity
◦ functionality
2. Your 'work' can include (but is not limited to) one of the following aspects:
3. Teams must provide documents that explain their work. Each invention must be supported by
concise but clear documentation. The documents must show precise steps towards the creation of
the invention.
4. Documents must include one Technical Description Paper (TDP), one poster and one Engineering
Journal. Teams should be prepared to explain their work.
5. TDP should describe your team’s project planning, robot’s mechanical and electronics design, your
software architecture and solutions and, the applied process on performance evaluation. A template
for the TDP and rubrics are available on the RoboCupJunior Official website.
6. Engineering Journals should demonstrate your best practices in the development process. A guide
for the Engineering Journal format and rubrics are available on the RoboCupJunior Official website.
7. The poster should include but is not limited to: the name of the team, country, league, robot
description, robot capabilities, controller, the programming language used, sensors included, method
of construction, time used for development, cost of materials, and awards won by the team in its
country, etc. A guide for the poster format and rubrics are available on the RoboCupJunior Official
website.
5.3. Sharing
1. Teams are encouraged to review others' posters, TDPs and presentations.
2. Teams awarded certificates must post their documents and presentation online when the
RoboCupJunior Rescue Committee asks.
2. During gameplay, the decisions made by the referee or the referee assistant are final.
3. After gameplay, the referee will ask the captain to sign the score sheet. Captains will be given a
maximum of 1 minute to review the score sheet and sign it. By signing the score sheet, the captain
accepts the final score on behalf of the entire team. In case of further clarification, the team captain
should write their comments on the score sheet and sign it.
2. If necessary, even during a tournament, a rule clarification may be made by members of the
International RoboCupJunior Rescue Committee.
2. Suppose team captains/mentors do not attend the team meetings to discuss problems, and the
resulting rule modifications described at 6.3.1. In that case, the organizers will understand that they
agreed and were aware of the changes.