Dance Rules (2005)

Last updated: Thursday January 20, 2005
by Ian Maud, Jeffrey Johnson, Eduardo Pinto, Amy Eguchi


Note: Changes from 2004 rules are highlighted in red.

1. Stage.

1.1. Size.

1.1.1. The dance stage will be a flat area of approximately 10m x 5m. Robots will be required to perform within a marked rectangular area of 6 X 4m, the 6m side to face the judging panel. Human performers may be outside this marked area.

The boundary of this area will be marked with a 50mm white and black tape line.

The floor provided shall be made of unpainted MDF (compressed wood fibre). Teams are encouraged to practice on the same flooring type to reduce set-up time at the International competition. While floor joints will be taped to make them as smooth as possible, Robots must be prepared for irregularities of up to 3 mm in the floor.



1.2. Lighting.

1.2.1. The organisers may make spotlights available, but teams should not expect the performance area to be able to be darkened, with direct, intense spotlights available.

Hint: It is recommended that teams design their robots to cope with variations in lighting conditions, as lighting naturally varies from venue to venue. If necessary, teams should come prepared to calibrate their robots based on the lighting conditions at the venue.


1.3. Scenery.

1.3.1. Teams are permitted to provide their own scenery.




2. Robots.

2.1. Size.

2.1.1. Robots may be of any size.


2.2. Team.

2.2.1. There may be any number of robots on a team.

2.2.2. Each team may perform one and only one routine.


2.3. Control.

2.3.1. Robots must be controlled autonomously.

2.3.2. Robots may be started by humans, either manually or with remote control. (See also 6.1.3)


2.4. Costumes.

2.4.1. Costumes for robots and/or human performers are encouraged.




3. Routine.

3.1. Duration.

3.1.1. Each team will have a total of 5 minutes for their actuation. NOTE that this time includes the time for set-up, a possible and encouraged introduction and the performance.

3.1.2. The duration of a performance routine is no more than two (2) minutes and no less than one (1) minute.

3.1.3. If a team exceeds the time limits explained in 3.1.1 and 3.1.2 in any way by reasons that are their only fault, it will be penalized in assessment for ‘Entertainment’ category.


3.2. Music.

3.2.1. Teams must provide their own audio source in a Compact Disc (CD-R, CD-RW) in one of the following formats:
- Audio track;
- MP3 file;
These will be the only accepted audio sources with one (and only one!) file or audio track for the entire routine.


3.2.2. Teams are strongly encouraged to bring a good quality audio source, since their evaluation depends also on the music quality.

3.2.3. The music should commence at the beginning of the audio source, after a silent leader of a few seconds.

3.2.4. The audio source should be clearly labelled with the team's name.


3.3. Humans.

3.3.1. Human team members may perform along with their robots.

3.3.2. However, human team members must not touch the robots (except to start them).


3.4. Start of Routine.

3.4.1. An official will start the music for the routine.

3.4.2. One human team member will start each robot, either by hand or remote control.

Hint: Teams are very strongly encouraged to program their robot to begin the routine a few seconds after the music starts. This is because it is extremely difficult to judge precisely when the music will sound after the audio source is started, and it is hard to time the robot's choreography without knowing exactly when the music will begin. Also, depending on the configuration of the dance stage and the sound system at the venue, it is possible that the human starting the robot will not be able to see the official starting the audio source; and vice versa. Teams should come prepared for these conditions.


3.5. Re-starts and repeats.

3.5.1. Teams are allowed to restart their routine if necessary, at the discretion of the officials.

3.5.2. Teams are allowed to repeat their routine, at the discretion of the officials.


3.6. Security.

3.6.1. In order to avoid hazardous situations such as routines including explosions, smoke or flame, each team whose routine includes any situation that could be deemed hazardous must submit a report to the chief judge before the competition, outlining the content of their dance routine. At his/her discretion, the Chief Judge could request a demonstration of the activity. Teams not conforming to this request may not be allowed to present their routine, at the discretion of the Chief Judge.




4. Judging.

4.1.

All teams will be assessed through an interview, and performance of a dance routine.


4.2 Officials.

4.2.1. Routines will be judged by a panel of five officials, two of whom will judge all routines. This panel may be different to that assessing the interviews.

4.2.2. The five officials will be designated prior to the tournament.

4.2.3. The officials shall not have any close relationship with any of the teams entered in the tournament.


4.3. Categories.

4.3.1. Performances will be judged according to the following categories:

A. Programming (e.g.,use of loops, jumps, sub-routines, type of programming language used, etc.)

B. Construction (e.g., robots should be of sound construction, components should not fall off, appropriate use of gearing, smooth and reliable operation, interesting movements, effective use of mechanics to achieve a purpose, etc.)

C. Using Sensors effectively (e.g., to trigger different parts of the program, for detection of boundary line, etc. This category also includes ‘other technologies’ apart from sensors.)

D. Choreography (e.g., robots to move in time with music, and change actions as music changes tempo or rhythm. Choreography of humans and robots will be scored separately, etc.)

E. Costume (Costume of humans and robots will be scored separately)

F. Entertainment Value (e.g., How much does the performance entertain or delight the audience? Originality and creativity of the presentation, etc.)


4.3.2. Each section will be judged out of a maximum score possible of 10 points.

4.3.3. A standard scoresheet will be used for judging the interviews and dance routines: see appendix for scoresheets.


4.4. Awards.

4.4.1. Awards will be made to individual teams that achieve the highest total score in the respective categories for:
- Programming;
- Construction;
- Using sensors;
- Chorography;
- Costume;
- Entertainment Value;

There will be also some specials awards for the following categories:
- Collegiality;
- Best poster or best electronic demonstration;
- Best placed international team. The RCJ Committee encourages the formation of such teams that are the result of a co-operative project between two or more schools from different countries. The team must have students from each school/country present in the team and at the competition, to be eligible to win this special award.


4.4.2. There will be an overall winner for the primary section, and an overall winner for the secondary section. These can be either a pair of single teams or a pair of groups, according to the new competitions organization model that will be announced in due time. In any case, the winner for each of these two sections is the team or group that achieves the highest total score summing performance in all categories: (Programming, Construction, Using sensors, Chorography, Costume and Entertainment Value).

4.4.3. Winning teams will be presented with a award, and a certificate of commendation for their school. In addition, each member of the winning team will receive a medallion. Any further awards are at the discretion of the organising committee.

4.4.4. Ties are allowed.


4.5. Collegiality.

4.5.1 Each participating team will have one vote to nominate the team that displayed the greatest cooperative interaction with other teams. The score will be calculated by the following equation:
score = 10 x (number of votes received)/(number of participating teams)




5. Creativity.

5.1.

The Dance challenge is intended to be very open-ended!!


5.2.

Show off your creative side!!




6. Code of Conduct.

6.1. Fair Play.

(Eliminated rule 6.1.1, from last year)

6.1.1. Humans in any way that cause deliberate interference with robots or damage to the stage will be disqualified, if part of a team. If not part of a team they will be ask to leave the venue.

6.1.2. The team is responsible for removing all debris left from their routine that may interfere with the performance of subsequent activities.

6.1.3. No wireless or infrared (IR) communication devices should be brought into the tournament hall, with the exception of devices used by one member of a team to start their performance. At all other times such devices should be made inoperable.

6.1.4. It is expected that the aim of all teams is to participate in a fair and clean competition.

6.1.5. Remember: "Help those in need, as tomorrow it could be your team needing help!"


6.2. Behaviour.

6.2.1. All movement and behaviour is to be of a subdued nature within the tournament venue.

6.2.2. Competitors are not to enter set-up areas of other leagues or other teams, unless expressly invited to do so by team members.

6.2.3. Participants who misbehave may be asked to leave the building and risk being disqualified from the tournament.

6.2.4. These rules will be enforced at the discretion of the referees, officials, conference organizers and local law enforcement authorities.


6.3. Mentors.

6.3.1. Mentors (teachers, parents, chaperones and other adult team-members) are not allowed in the student work area.

6.3.2. Sufficient seating will be supplied for Mentors to remain in a supervisory capacity around the student work area.

6.3.3. Mentors are not to repair robots or be involved in programming of students’ robots.

6.3.4. Mentor interference with robots or judge's decisions will result in a warning in the first instance. If this recurs, the team will risk being disqualified.


6.4. Sharing.

6.4.1. An understanding that has been a part of World RoboCup Competitions is that any technological and curricular developments should be shared with other participants after the competition.

6.4.2. Any developments may be published on the RoboCup Junior Web site after the event.

6.4.3. This furthers the mission of RoboCup Junior as an educational initiative.


6.5. Spirit.

6.5.1. It is expected that all participants, students and mentors, will respect the RoboCup Junior mission.

6.5.2. The referees and officials will act within the spirit of the event.

6.5.3. It is not whether you win or lose, but how much you learn that counts. You will really lose if you don’t take this opportunity to fraternize with students and mentors from all over the world. Remember this is a unique moment!




7. Documentation.

7.1.

All teams must bring written documentation describing their preparation efforts. This documentation must be present during the interview.


7.2.

Teams will be given some public space to display their materials on a poster board. Since the space available could be limited by the local organisers, teams are encouraged as an alternative to bring some kind of electronic presentation in PowerPoint format that will be displayed in the venue. The organisers will provide screening equipment.


7.3.

Officials will review the documentation and may discuss the contents with team members. A prize will be awarded to the team with the overall most outstanding presentation.


7.4.

Teams are encouraged to visit each other's posters.


7.5.

Teams are encouraged to have a Web site where they describe their projects to the RCJ community.

Last updated by sklar on 01/17/05

[Official Website]