You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: onstage_entry_rules/rules.adoc
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ endif::basebackend-html[]
17
17
:icons: font
18
18
:numbered:
19
19
20
-
These are the official rules of the _RoboCup Federation_ for the _RoboCupJunior_ (RCJ) OnStage Entry events in 2024.
20
+
These are the recommended rules of the _RoboCup Federation_ for the _RoboCupJunior_ (RCJ) OnStage Entry events in 2024.
21
21
There will be *no OnStage Entry competition at the international level*. The rules are meant to be used at regional and super-regional events.
22
22
23
23
Regional and super-regional tournament organizers may use these rules, make changes specific to their regions or not run Entry leagues at all. Contact your regions or super-regions tournament organizers to find out which rules are going to be used at your tournament.
@@ -27,7 +27,7 @@ Regional and super-regional tournament organizers may use these rules, make chan
27
27
//Add line below again once a new version is released
28
28
//Major changes from the 2023 OnStage rules are written in *[red]#red#*.
29
29
30
-
*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.
30
+
*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 the offical rules of the specific event it participates in. Teams are encouraged to study all documents in detail.
31
31
32
32
[discrete]
33
33
== RoboCupJunior Forum
@@ -48,9 +48,9 @@ RoboCupJunior OnStage invites teams to design, build and program creative and au
48
48
[[judging-overview]]
49
49
== Judging Overview
50
50
51
-
All teams are judged in the following areas: Poster, Interview, Open Technical Demonstration and the Performance. Teams must highlight two of their robot(s) *features* in the work they present to the judges. Ask the following question - "What are you most proud of and what do you want to be judged on?" The features have to be of technical nature.
51
+
All teams are judged in the following areas: Poster, Interview, Open Technical Demonstration and OnStage Performance. Teams must highlight two of their robot(s) *features* in the work they present to the judges. Ask the following question - "What are you most proud of and what do you want to be judged on?" The features have to be of technical nature.
52
52
53
-
Teams should describe their two chosen features in the Poster, 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 and Open Technical Demonstration.
53
+
Teams should describe their two chosen features in the Poster. In addition, teams should demonstrate their understanding of their robots' in the Technical Interview and Open Technical Demonstration.
54
54
55
55
For clarification on a teams’ features, please do not hesitate to reach out to the OnStage League committee using the RoboCupJunior Forum.
56
56
@@ -175,12 +175,12 @@ Lithium batteries must be transported or moved in safety bags.
175
175
176
176
{++Participants should design their robot(s) to be a size that they can easily carry by themselves. Robots should be of a weight that team members can carry and lift onto the stage with ease.++}
177
177
178
-
{++To protect participants and comply with occupational health and safety regulations, routines may not include anything that could be considered a projectile, explosions, smoke, or flame, use of water, or any other hazardous substances (contact the committee through the forum when in doubt).++}
178
+
{++To protect participants and comply with occupational health and safety regulations, routines may not include anything that could be considered a projectile, explosions, smoke, or flame, use of water, or any other hazardous substances (contact the committee when in doubt).++}
179
179
180
180
[[onstage-interview]]
181
181
== Interview (30% of total score)
182
182
183
-
The Technical Interview is a live interview between the team and the judges, in which all robots and programming are judged against technical criteria. Judges are interested in determining students' understanding of the robots they have used.
183
+
The Technical Interview is a live interview between the team and the judges, in which all robots and programming are judged against technical criteria. Judges are interested in determining students' understanding of the robots they have developed.
184
184
185
185
[[interview-procedure]]
186
186
=== Interview procedure
@@ -203,7 +203,7 @@ Extra time will not be given for teams with a translator.
203
203
[[onstage-poster]]
204
204
== Poster (10% of total score)
205
205
206
-
Each team is required to bring a Poster. The purpose of the poster is to explain the technology used, as well as to showcase the robots’ software and hardware.
206
+
Each team is required to bring a poster. The purpose of the poster is to explain the technology used, as well as to showcase the robots’ software and hardware.
207
207
208
208
{++Teams must submit a digital copy of their poster in PDF format (≤ 10 MB)++}.
209
209
@@ -216,12 +216,12 @@ Areas that are useful to be included in the poster are:
216
216
{++- a description of the features that should be judged during the performance++}
217
217
- annotated pictures of the development process
218
218
219
-
Teams will be given public space to display their Technical Poster.
219
+
If possible, teams will be given public space to display their Technical Poster.
220
220
221
221
[[open-technical-demonstration]]
222
222
== Open Technical Demonstration (10% of total score)
223
223
224
-
{++The description of the robots’ capabilities should explain to the judges and audience how the robot’s capabilities have been achieved.++}
224
+
{++Through the Open Technical Demonstration, teams should showcase their robots' capabilities and explain how they have been achieved..++}
225
225
226
226
{++It's recomended to use slides to introduce the project.++}
227
227
@@ -234,7 +234,7 @@ Teams will be given public space to display their Technical Poster.
234
234
235
235
{++After the seven minutes have expired the team will be asked to clear the stage and judging will be stopped.++}
236
236
237
-
{++The technical capabilities of their robots should be demonstrated by both describing what has been developed and demonstrating this capability. This could cover any aspect of the performance or technical capabilities of the robot(s), such as interaction with humans, interactions with other robots or the use of a particular sensor.++}
237
+
{++Teams should showcase their robots' technical capabilities by both describing and demonstrating what has been developed. This could cover any aspect of the performance or technical capabilities of the robot(s), such as interaction with humans, interactions with other robots or the use of a particular sensor.++}
238
238
239
239
{++Teams are encouraged to remove robots’ costumes for showing detailed design.++}
240
240
@@ -244,9 +244,9 @@ Teams will be given public space to display their Technical Poster.
244
244
[[judging-criteria]]
245
245
=== Judging criteria
246
246
247
-
The judging criteria and allocation of marks are given in the respective score sheets.
247
+
The judging criteria and allocation of marks are provided in the respective score sheets.
248
248
249
-
Teams must read the Score Sheets to make sure they create their materials according to the judging criteria.
249
+
Teams must read the Score Sheets carefully so that their robot performance covers as much judging criteria as possible.
250
250
251
251
[[totaling]]
252
252
=== Totaling
@@ -263,7 +263,7 @@ If more than one performance is scheduled, the highest of all performance scores
0 commit comments