Skip to content

Commit

Permalink
Added Open Technical Demonstration
Browse files Browse the repository at this point in the history
  • Loading branch information
ChristianH99 committed Apr 20, 2024
1 parent cf15755 commit 71bb454
Showing 1 changed file with 36 additions and 10 deletions.
46 changes: 36 additions & 10 deletions onstage_entry_rules/rules.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,8 @@ endif::basebackend-html[]
:icons: font
:numbered:

These are the official rules of the _RoboCup Federation_ for the _RoboCupJunior_ (RCJ) OnStage entry events in 2024.
There will be *no OnStage entry competition at the international level*. The rules are meant to be used at regional and super-regional events.
These are the official rules of the _RoboCup Federation_ for the _RoboCupJunior_ (RCJ) OnStage Entry events in 2024.
There will be *no OnStage Entry competition at the international level*. The rules are meant to be used at regional and super-regional events.

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.

Expand Down Expand Up @@ -48,9 +48,9 @@ RoboCupJunior OnStage invites teams to design, build and program creative and au
[[judging-overview]]
== Judging Overview

All teams are judged in the following areas: Poster, Interview and the Performance. Teams must highlight four 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.
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.

Teams should describe their four 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.
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.

For clarification on a teams’ features, please do not hesitate to reach out to the OnStage League committee using the RoboCupJunior Forum.

Expand All @@ -69,7 +69,7 @@ Each team member needs to carry a role within the team. Each participant can joi
Please note that age and team size restrictions will apply to international competitions for the main OnStage competition.

[[onstage-performance]]
== OnStage Performance (50% of total score)
== Performance (50% of total score)

The OnStage Performance is an opportunity to demonstrate the robot(s) through a performance or stage show.

Expand Down Expand Up @@ -124,7 +124,7 @@ Robots must perform autonomously.

Teams should construct their own robot rather than using the instructions that come with a commercial kit.

Teams are encouraged to design costumes for their robot. If a team wants to use a famous character as their robot, the team should pay attention to the copyright of the character.
Teams are encouraged to *design costumes for their robot*. If a team wants to use a famous character as their robot, the team should pay attention to the copyright of the character.

[[communication-and-localization]]
=== Communication and Localization
Expand Down Expand Up @@ -178,7 +178,7 @@ Lithium batteries must be transported or moved in safety bags.
{++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).++}

[[onstage-interview]]
== OnStage Interview (40% of total score)
== Interview (30% of total score)

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.

Expand All @@ -189,7 +189,7 @@ All teams will have up to 15 minutes of technical interview judging during the c

Teams should have *all* robots present at the interview.

Teams should bring copies of their programm code.
Teams should bring their programm code.

If the judges consider it necessary, teams may be asked to complete a second interview.

Expand All @@ -201,20 +201,41 @@ The Technical Interviews take place in the main language of the event. If teams
Extra time will not be given for teams with a translator.

[[onstage-poster]]
== OnStage Poster (10% of total score)
== Poster (10% of total score)

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.

{++Teams must submit a digital copy of their poster in PDF format (≤ 10 MB)++}.

The size of the poster should be no larger than A1 (60 x 84 cm).

Areas that are useful to be included in the poster are:

- team name and region
- performance description
{++- a description of the features that should be judged during the performance++}
- annotated pictures of the development process

Teams will be given public space to display their Technical Poster.

[[open-technical-demonstration]]
== Open Technical Demonstration (10% of total score)

{++The description of the robots’ capabilities should explain to the judges and audience how the robot’s capabilities have been achieved.++}

{++It's recomended to use slides to introduce the project.++}

[[demonstration-procedure]]
=== Demonstration procedure

{++The duration of the performance routine should be approximately 5 minutes.++}

{++Each team has a total of seven minutes on the stage. This time includes stage set-up, the demonstration, and the time for packing up and clearing the stage. The timer only stops when the entire stage is clear with no remnants from the previous demonstration.++}

{++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.++}

{++Teams are encouraged to remove robots’ costumes for showing detailed design.++}

[[judging]]
== Judging

Expand All @@ -228,10 +249,15 @@ Teams must read the Score Sheets to make sure they create their materials accord
[[totaling]]
=== Totaling

The total score of each team is calculated by combining the scores from the team’s Interview, Poster and the Performance.
The total score of each team is calculated by combining the scores from the team’s Interview, Poster{++, Open Technical Demonstartion++} and the Performance.

If more than one performance is scheduled, the highest of all performance scores will be used.

[[juding-panel]]
=== Judging panel

{++All aspects 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 and documentation as well.++}

[[mentors]]
== Mentors

Expand Down

0 comments on commit 71bb454

Please sign in to comment.