OnStage Rules 2023 - FINAL
OnStage Rules 2023 - FINAL
OnStage Rules 2023 - FINAL
These are the official rules for the RoboCupJunior OnStage events in 2023.
They apply to both an on-site competition, as well as an online (virtual) or hybrid event. Teams will be
informed in advance about how each element will be held.
Special rules for on-site competitions are highlighted in blue while virtual elements are highlighted in green.
Sections with no highlighting apply to every kind of competition.
Major changes from the 2022 OnStage rules are written in red.
Teams should make sure to review ALL the pages of these rules. The rules have been changed to deepen
and broaden the educational benefits of competing in RoboCupJunior. It focuses on the evolving technologies
available in our time.
The International Original Rules (in English) have priority over any translations. These rules are the official
rules of the RoboCup Federation.
The rules, score sheets, and all forms of documentation can be downloaded from the official
RoboCupJunior website (https://junior.robocup.org). Each team has a responsibility to verify the latest
version of these documents prior to the competition, as changes may be made at any moment. Teams are
encouraged to study all documents in detail.
RoboCupJunior Forum
For inquiries and questions about the rules or competition updates, the Official RoboCupJunior forum
(https://junior.forum.robocup.org/) can be used to contact the OnStage League Committee. All official
communication from the committee will be published here before and during the competition season.
2 General 5
2.1 Team Size & Membership 5
2.2 Age requirement 5
2.3 General RoboCupJunior Rules 5
7 Code of Conduct 13
7.1 Spirit 13
7.2 Fair play 13
7.3 Behavior 13
7.4 RoboCupJunior Officials 14
7.5 Mentors 14
8 Additional Information 14
8.1 Sharing 14
8.2 Rule Clarification 14
8.3 Information before and during the event 14
8.4 Special Circumstances 14
Teams should describe and provide reasoning for their four chosen features in the Technical Description Poster and
during their Technical Demonstration Video, before being judged on the implementation of these features during the
Performance. In addition, teams should demonstrate their understanding of their systems in the Technical Interview.
For clarification on a teams’ features, please do not hesitate to reach out to the OnStage League committee using the
RoboCupJunior Forum.
2 General
It is the responsibility of the participating team(s) and regional representatives to verify the participants' eligibility
requirements, which are as follows:
The OnStage Performance is an opportunity to demonstrate the design, construction, and technical aspects of the
robot(s) through a performance or stage show. For example, this could be a magic show, theater performance, story,
comedy show, dance, or art installation. Teams are encouraged to be creative, innovative and take risks in their use of
technology and materials when creating their performances.
Teams will present a live performance, in which their routine will be judged. Teams will present and demonstrate the
four features to be judged, and higher marks will be awarded for the integration of these features and the value that
they add to the performance. For more details on this, refer to the OnStage Performance Score Sheet. Teams must show
originality, creativity and innovation throughout their performance routine. It is expected that all participating teams
perform their best.
3.1 Judging
1. Teams have up to two opportunities to perform before the judges. If more than one performance is scheduled,
the highest score from each performance will be used. The top-scoring teams may be invited to perform again
in a final competition.
2. The stage performance will be judged by a panel of at least three officials. At least one of these judges is a
RoboCupJunior official who has judged the Technical Interview as well.
3.3 Restarts
1. Teams can restart their routine if necessary, at the discretion of the judges. There is no limit on the number of
restarts allowed within the stage-time. Penalty marks will be deducted from the score.
2. The team must leave the stage after their time on stage has expired.
3.5 Stage
1. The size of the performance stage area is up to the discretion of the teams. The performance area must be
visible in the camera's field of view. However, the maximum size of the performance stage area is a rectangular
area of 5 x 4 meters (m) for robots with the 5 meter side facing the judges.
2. The judging camera, which shows the entire view of the performing area must be set up as a static camera and
should be placed in approximately the position of the judge’s table at an in-person competition. (APPENDIX A).
3. Teams can use a second camera to show details of their robots during the performance. However, they should
be aware that additional views may detract from the overall performance. Judges must be informed before the
start of the performance where the additional camera(s) will be placed so the correct screen can be pinned
during the performance.
4. The size of the performance stage area is a rectangular area of 5 x 4 meters (m) for robots with the 5 meter
side facing the judges.
5. There is a line marking the edge of the 5 x 4 meter stage. See APPENDIX A.
6. The floor provided shall be made of a flat (non-glossy) white surface, for example, painted MDF (compressed
wood fiber). While floor joints will be made to be as smooth as possible, robots must be prepared for
irregularities of up to 5 mm in the floor surface. Whilst every effort will be made to make the stage flat, this
may not be possible, and teams should be prepared to cope with this uncertainty.
7. Teams should come prepared to calibrate their robots based on the lighting conditions at the venue.
8. Teams using compass sensors should be aware that metal components of the staging may affect the compass
sensor readings. Teams should come prepared to calibrate such sensors.
3.6 Robots
1. Robots must perform autonomously.
2. Laptops, notebooks, mobile phones, tablets, Raspberry Pi, and other similar devices can be used as robotic
controllers.
3.8 Scenery
1. Static props which do not form an integral part of the performance are discouraged since the focus of the
performance should be on robots. The kind of props that are considered "interactive" are:
a. Props interact with robots via sensors
b. Props interact with robots via communication
2. Robots can sense static props to perform a certain task or trigger a performance provided that they are placed
on the defined stage performance area.
3.11 Deductions
1. If a team exceeds the time limits, it will be penalized by the loss of points (see performance score sheet).
2. All robot movements or interactions that happen outside the performance area for on-site performances, or
the judges’ field of view for virtual performances will not be considered for the scoring, but will not lead to
deductions.
3. Teams are reminded that humans triggering the progress of the performance via touch-based sensors will be
considered remote-controlled interaction and therefore will be considered an unplanned human interaction
during the performance.
4. Unless a problem is not the fault of a team, one or more restarts will result in a single score deduction.
5. A team who is not punctual will be penalized. If the team repeats unpunctual behavior, they risk disciplinary
action.
3.14 Content
1. Performances should not include violent, military, threatening, or criminal elements. This includes
inappropriate or offensive words (including music) and/or images.
2. Participants are asked to carefully consider the wording and messages communicated in any aspect of their
performance. What seems acceptable to one group may be offensive to friends from a different country or
culture.
3. A team whose routine may be deemed inappropriate to any particular group will be asked to change their
performance before being allowed to continue in the competition. Teams who wish to clarify their
performance theme or elements of their performance may contact the OnStage League Committee before the
competition. Failure to remove inappropriate content will result in disciplinary action.
The Technical Interview is a live interview between the team and the judges, in which all robots and programming are
judged against technical criteria. Creative and innovative technical features chosen by the team will be rewarded with
higher scores. Judges are interested in determining students' understanding of the robotic technologies they have used.
Teams must show authenticity and originality regarding their robots and performance in this interview.
Teams should inform the judges if robotic components have been featured in previous competitions. To gain marks,
teams should be prepared to provide insight on how substantial changes have been made between competitions as
evidence of the students’ continuing development of the technologies. Teams should specify how innovations have
been done with their technologies and provide documentation to support their claims.
4.2 Translator
1. The Technical Interviews take place in English. If teams require a translator, they should inform the
RoboCupJunior OnStage officials prior to the event to allow translators to be organized.
2. Extra time will not be given for teams with a translator.
Teams are required to submit a recorded demonstration to showcase the capabilities of their robots. The aim of the
technical demonstration is to showcase how well the team integrated their robotics creations into a perfect
performance. They should demonstrate and describe the capabilities of their robots such as interaction with humans or
with each other using mechanisms, sensor systems, and algorithms that have been developed by the team.
1. The maximum length of the video is 5 minutes. If it is longer than 5 minutes, it will be cut to that time for
judging.
2. Robots should be presented without their costumes and key features of the technologies used should be visible
to the audience.
3. The team should explain how the capabilities have been developed, the challenges overcome, and the
technologies integrated. Teams should also provide examples of solutions to any problems/issues during their
project development.
4. Teams will also be required to outline what they believe are their chosen four features that they wish to be
scored on during their OnStage performance (See Overview).
5. Video editing is allowed and should be used to create a technically engaging and informative demonstration of
all robots. Teams may wish to include full English subtitles or transcripts.
6. All team members are encouraged to be actively involved in the presentation.
7. The Technical Demonstration is assessed according to the Technical Demonstration Score Sheet.
8. The demonstration needs to be recorded and the video file must be uploaded by the deadline set by the
OnStage League Committee.
Each team is required to submit a Technical Description Poster by the deadline set by the OnStage League Committee,
which is before the first performance during the RoboCupJunior competition. The purpose of the poster is to explain the
technology used, particularly highlight the four chosen features, as well as to showcase the robots’ software and
hardware. Posters should be made in an interesting and engaging format, as they will be viewed not only by the judges
but also by other teams and visiting members of the public.
4. Teams participating on site will be given public space to display a Technical Poster. Virtual teams may wish to
send their poster with a representative from their country to display at the venue.
6.2 Totaling
1. The total score of each team is calculated by combining the scores from the team’s Technical Interview, the
Technical Demonstration, and the OnStage Performances.
6.3 Feedback
1. RoboCupJunior is an educational project. It is important that team members learn from their experiences with
RCJ, so that they have the opportunity to improve.
2. Feedback and notifications of deductions will be given after the first performance to allow teams to better
prepare for the second performance.
3. A final ranking that includes all teams and their scoring will not be provided to the teams. The teams will get
their approximate ranking and their individual scores for their interview, performance, technical demonstration
video and poster.
4. Feedback will not be accepted as evidence to debate positions, decisions, or competition scores with the
judges.
7 Code of Conduct
7.1 Spirit
1. It is expected that all participants, students, and mentors, will respect the RoboCupJunior mission, values, and
goals.
2. It is not whether you win or lose, but how much you learn that counts. Choosing not to take this opportunity to
collaborate with students and mentors from all over the world means missing out on a lifelong learning
experience. Remember this is a unique moment!
7.3 Behavior
1. All behavior is to be of a subdued nature while at the competition. It is expected that every participant behaves
in a respectful manner towards each other.
2. Participants are not to enter set-up areas of other leagues or other teams unless expressly invited to do so by
other team members. Participants who misbehave may have disciplinary action taken against them.
7.5 Mentors
1. Each team is required to have a mentor to assist with the communication among the team and facilitate their
learning. The mentor receives communications from the committee leading up to and during the competition
via the email address used for their registration.
2. Mentors (defined as teachers, parents, chaperones, translators, or any other adult non-team members) are not
allowed in the student work area except to assist in carrying equipment in or out of the area on the arrival and
departure days.
3. If a problem is encountered that is beyond the team’s capabilities and is clearly beyond the reasonable ability
level of a student to repair, mentors may request assistance from the OnStage League Committee, including
supervised support to conduct repairs.
4. Mentors are not allowed to set up equipment on stage, as this should be the responsibility of team members.
Teams should design all robots and any additional equipment to be carried by team members only.
5. Disciplinary action will be taken should a mentor be found mending, building and/or programming the robot(s),
and/or directing choreography. Judges may question the team’s originality if this occurs and teams may risk
deductions or disqualification.
8 Additional Information
8.1 Sharing
1. It is understood that RCJ events with rich technological and curricular developments should be shared with
other participants.
2. Team materials may be published on the RoboCupJunior media platforms during the event.
3. Sharing information furthers the mission of RoboCupJunior as an educational initiative.