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_rules/rules.adoc
+5-52Lines changed: 5 additions & 52 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ Ressources for participating in the OnStage league can be found on the OnStage c
42
42
43
43
Examples of good performances and documentation can be found on the *Official RoboCupJunior OnStage YouTube channel* (https://www.youtube.com/@rcjonstage).
44
44
45
-
[discrete]
45
+
[[general-overview]]
46
46
== Overview
47
47
48
48
RoboCupJunior OnStage invites teams to design, build and program creative and autonomous physical robots. The objective is to create a live robotic performance that uses a wide variety of technology to engage an audience. This includes a range of possible performances, such as dance, storytelling, theater, or art installations. The performance may involve music, but this is optional. The league is intended to be open-ended. Teams are encouraged to be creative, innovative, and entertaining, in both the design of the robots and in the design of the overall performance.
@@ -82,29 +82,8 @@ Teams should describe and provide reasoning for their four chosen features in th
82
82
83
83
For clarification on a teams’ features, please do not hesitate to reach out to the OnStage League committee using the *RoboCupJunior Forum* (https://junior.forum.robocup.org/c/robocupjunior-onstage).
84
84
85
-
[[general]]
86
-
== General
87
-
88
-
It is the responsibility of the participating team(s) and regional representatives to verify the participants' eligibility requirements, which are as follows:
89
-
90
-
[[team-size-membership]]
91
-
=== Team Size & Membership
92
-
93
-
Each team must have *2 to 5 members*. Each team member needs to carry a technical role within the team, such as Electrical, Mechanical, Software etc. Each participant can join only one team. No members can be shared between teams and/or leagues.
94
-
95
-
[[age-requirement]]
96
-
=== Age requirement
97
-
98
-
All team members must be aged 14 to 19 years old (ages as of 1st of July).
99
-
100
-
[[general-robocupjunior-rules]]
101
-
=== General RoboCupJunior Rules
102
-
103
-
All RoboCupJunior OnStage Teams must also comply with the RoboCupJunior General Rules which can be found at: https://junior.robocup.org/robocupjunior-general-rules/
104
-
105
-
106
85
[[authenticity-and-originality]]
107
-
=== Authenticity and originality
86
+
== Authenticity and originality
108
87
109
88
Teams who, in the opinion of the judges, have knowingly produced duplicate robots, costumes, or performance movements (duplicate music is allowed) of another team will be subject to penalties. This applies to any previous RoboCupJunior Dance or OnStage performance. In case of doubts, the team must be able to provide clear documentation of their preparations and how they have come to their idea.
110
89
@@ -172,8 +151,7 @@ If music is used, teams must provide their own audio music source. The preferred
172
151
173
152
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.
174
153
175
-
//TO DO: fix link to appendix in PDF
176
-
There is a line marking the edge of the 5 x 4 meter stage. See appendix a.
154
+
There is a line marking the edge of the 5 x 4 meter stage. See <<appendix-a>>.
177
155
178
156
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.
179
157
@@ -203,7 +181,7 @@ It is the team’s responsibility to make sure that their communication function
203
181
204
182
{--No team is permitted to use other radio frequency (RF) signals (like Wi-Fi or Z waves) as this may interfere with robots in other RoboCup leagues. If you are unsure, please check with the OnStage League Committee before your performance.--}
205
183
206
-
Teams should prepare for disruptions in communication protocols and unavailability of Wifi (as outlined in the general rules) before and during the setup and stage time.
184
+
Teams should prepare for disruptions in communication protocols before and during the setup and stage time.
207
185
208
186
Any localization beacons or markers for a robot's localization system should be placed within the confines of the stage.
209
187
@@ -356,7 +334,7 @@ Robots should be presented without their costumes and key features of the techno
356
334
357
335
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.
358
336
359
-
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>>).
337
+
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 <<general-overview>>).
360
338
361
339
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.
362
340
@@ -449,25 +427,6 @@ It is expected that all participants, students, and mentors, will respect the Ro
449
427
450
428
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!
451
429
452
-
[[fair-play]]
453
-
=== Fair play
454
-
455
-
It is expected that the aim of all teams is to participate in a fair and clean competition.
456
-
457
-
Humans that may cause deliberate interference with robots, robots' performance and/or damage to the stage will be subject to disciplinary action. This will be decided by the OnStage League Committee and RoboCupJunior Officials.
458
-
459
-
Remember, helping those in need and demonstrating friendship and cooperation is the spirit of RoboCupJunior, as well as helping make the world a better place.
460
-
461
-
Participants are encouraged to help each other.
462
-
463
-
[[behavior]]
464
-
=== Behavior
465
-
466
-
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.
467
-
468
-
Participants are not allowed to enter team- 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.
469
-
470
-
A team who is not punctual will be penalized. If the team repeats unpunctual behavior, they risk disciplinary action.
471
430
472
431
[[robocupjunior-officials]]
473
432
=== RoboCupJunior Officials
@@ -481,8 +440,6 @@ The RoboCupJunior officials shall not have a close relationship with any of the
481
440
482
441
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.
483
442
484
-
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.
485
-
486
443
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.
487
444
488
445
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.
@@ -497,8 +454,6 @@ Disciplinary action will be taken should a mentor be found mending, building and
497
454
498
455
It is understood that RoboCupJunior events with rich technological and curricular developments should be shared with other participants.
499
456
500
-
Team materials may be published on the RoboCupJunior media platforms during the event.
501
-
502
457
Sharing information furthers the mission of RoboCupJunior as an educational initiative.
503
458
504
459
[[rule-clarification]]
@@ -522,7 +477,6 @@ If special circumstances occur, such as unforeseen problems or capabilities of a
522
477
523
478
If any of the team leaders/mentors are not present at the team meetings to discuss the problems and the resulting rule modifications, they consent to the rule modifications and are not permitted to challenge them at a later time.
524
479
525
-
[discrete]
526
480
[[appendix-a]]
527
481
== Appendix A
528
482
@@ -533,7 +487,6 @@ If any of the team leaders/mentors are not present at the team meetings to discu
533
487
|===
534
488
535
489
536
-
[discrete]
537
490
[[appendix-b]]
538
491
== Appendix B - Ressources to be released during the season
0 commit comments