RoboCupJunior 2004
DANCE rules
Note: Changes from 2003 rules
are highlighted in red.
1.
Stage.
1.1. Size.
1.1.1.
The dance stage will be a flat area
of 10m x 5m.
1.2. Lighting.
1.2.1.
There will not be any direct
spotlight on the stage.
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.
2.4. Costumes.
2.4.1.
Costumes are
encouraged.
3.
Routine.
3.1. Duration.
3.1.1.
The duration of a routine is no more
than two (2) minutes.
3.2. Music.
3.2.1.
Teams must provide their own audio
source, either:
3.2.1.1.
Compact Disc (CD),
3.2.1.2.
MP3 (Audio
tapes are not acceptable as a music source)
3.2.2.
Teams are strongly encouraged to
bring a good quality audio source that contains only the music for their routine
on it.
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
labeled 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, each team 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 demo of the activity.
4.
Judging.
4.1. Officials.
4.1.1.
Routines will be judged by a panel of
five officials.
4.1.2.
The five officials will be designated
prior to the tournament.
4.1.3.
The officials shall not have any
relationship with any of the teams entered in the tournament.
4.2. Categories.
4.2.1.
Routines will be judged according in
the following categories:
4.2.1.1.
Programming.
4.2.1.2.
Construction.
4.2.1.3.
Costume.
4.2.1.4.
Choreography.
4.2.1.5.
Creativity.
4.2.1.6.
Originality.
4.2.1.7.
Entertainment Value.
4.2.2.
Scores from 1 to 10 (best) will
assigned to each team for each category.
4.3. Winners.
4.3.1.
A winner will be chosen for each
category, as the team with highest total score for that category.
4.3.2.
An overall winner will be chosen, as
the team with highest total score for all categories.
4.3.3.
Ties are
allowed
4.4.
Collegiality.
4.4.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.
6.1.1.
Robots that cause deliberate
interference with other robots or damage to the stage will be disqualified.
6.1.2.
Humans that cause deliberate
interference with robots or damage to the stage will be disqualified.
6.1.3.
The team is responsible
for removing all debris left from their routine that may interfere with the
performance of subsequent activities.
6.1.4.
No wireless or infra-red (IR)
communication devices will be allowed in the tournament hall.
6.1.5.
It is expected that the aim of all
teams is to participate in a fair and clean competition.
6.2. Behavior.
6.2.1.
All movement and behavior is to be of
a subdued nature within the tournament venue.
6.2.2.
Competitors are not to enter setup
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 student’s robots.
6.3.4.
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 RoboCupJunior web site after the event.
6.4.3.
This furthers the mission of RoboCupJunior as an educational initiative.
6.5. Spirit.
6.5.1.
It is expected that all participants,
students and mentors, will respect the RoboCupJunior
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.
7.
Documentation.
7.1.
All teams must bring
written documentation describing their preparation efforts.
7.2.
Teams will be given
public space (approximately 1 by 2 meters) to display their materials on a
poster board.
7.3.
Officials will review the
documentation and discuss the contents with team members. A prize will be
awarded to teams with outstanding presentations.
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.