RoboCupJunior Soccer Rules 2014
RoboCupJunior Soccer Technical Committee 2014:
Katsumi Masaoka (Japan), CHAIR, Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
Luis José López (Mexico), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
Maverick Luk (Macao & Hong Kong), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
Paul Manns (Germany), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
Rob Quatrone (USA), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
Gio Spina (Canada), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
These are the official rules for RoboCupJunior 2014. They are released by the RoboCupJunior
Soccer
Technical Committee for Soccer. These rules have priority over any translations.
Teams are advised to check the RoboCupJunior Soccer site ( http://rcj.robocup.org/soccer.html )
for OC
procedures and requirements for the competition.
Preface:
In the RoboCupJunior soccer challenge, teams of two autonomous mobile robots compete against
another team in matches. They must look for an infrared-light-emitting ball, trying to score
into a color-coded goal in a special field built in a way that resembles the actual field for
human soccer. Robots are required to have full autonomy from humans, technical designs, and
ingenious programming by their developers.
Participants of this challenge are required to give the best of their abilities in programming,
robotics, electronics and mechatronics, but also to contribute on teamwork and knowledge sharing
with other participants, regardless of culture, age or result in the competition. All are expected
to compete, learn, have fun and grow.
The changes determined by the Technical Committee for this year’s rules aimed to favor skills over
brute force in the games, with safer conditions for both robots and humans. The rules
better work out situations of aggressive robots that cause damage to IR balls, robots and
fields; control unrealistic kicker force that cause damage to IR balls and referees; and reduce
the excessive need for human intervention in a stressful attempt to maintain game continuity.
0. Construction and Programming have to be performed exclusively by the students
Robots must be constructed and programmed exclusively by student members of the team. Mentors,
teachers, parents or companies should not be involved in the programming and debugging of robots.
1. TEAM
1.1 Regulations
A team consists of two or more members.
Each team must have a captain. The captain is the person responsible for communication with
referees. The team can replace its captain during the competition. Team is allowed to have only the
fewest possible members beside the field during game play: they will usually be the captain and an
assistant team member.
1.2 Violations
Teams that do not abide by the rules are not allowed to participate.
Any person close to the playing field is not allowed to wear any yellow or blue clothes that can be
seen by the robots (to avoid interference with the goal color). A referee can require a team member
to change clothes or to be replaced by another team member if interference with goal color is
suspected.
The referee can interrupt a game in progress if any kind of interference from spectators is
suspected (color clothing, IR emitters, camera flashes, mobile phones, radios, computers, etc.).
2. ROBOTS
2.1 Number of robots / substitution
Each team is allowed to have at most two robots. The substitution of robots during the competition
within the team or with other teams is forbidden.
2.2 Interference
Robots are not allowed to be colored yellow or blue in order to avoid interference with the goal
colors. Yellow or blue parts used in the construction of the robot must either be occluded by other
parts from the perception by other robots or be taped/painted with a neutral color.
The robot must not emit infrared light. However, optical sensors (e.g. infrared-distance-sensors)
may be used as long as they do not affect other robots. This needs to be proved by a referee or an
OC member if a claim is placed by the other team.
Infrared light reflecting materials must not be used on the outside. If robots are painted, they
must be painted matte. Minor parts that reflect infrared light could be used as long as other
robots are not affected. A team claiming that their robot is affected by the other team’s
robot reflecting infrared light has to show the proof/evidence of the interference.
2.3 Control
The use of remote control of any kind is not allowed. Robots must be started manually by
humans and be controlled autonomously.
2.4 Communication
Robots are not allowed to use any kind of communication during game play unless the communication
between two robots is via Bluetooth class 2 or class 3 (range shorter than 20 meters)
or via ZigBee. Teams are responsible for their communication. The availability of frequencies
cannot be guaranteed.
2.5 Agility
Robots must be constructed and programmed in a way that their movement is not limited to only one
dimension (that means one axis). They must move in all directions, for example by turning. Robots
must respond to the ball in a direct forward movement. For example, it is not enough to basically
just move left and right in front of their own goal, but also to move directly towards the ball in
a forward movement. At least one team robot must be able to seek and approach the ball anywhere on
the field, unless the team has only one robot on the field at that time.
Robots must be constructed and programmed in a way that they do not enter the goal. Robots are
allowed to use the cross-bar.
2.6 Handle
All robots must have a stable handle to hold and to lift them. The handle must be easily
accessible, for example on top of a robot. The dimensions of the handle may exceed the 22 cm
height limitation, but the part of the handle that exceeds this 22 cm limit cannot be used to
mount components of the robot.
2.7 Additional regulations of the sub-leagues
A tournament may be organized in different sub-leagues. Each sub-league (e.g. “Open League”
and “Light Weight League”) may have its own additional regulations, including regulations
affecting the construction of robots. Such regulations will be published by the RoboCupJunior
Soccer Technical Committee and become a part of this rule.
2.8 Violations
Robots that do not abide by the specifications/regulations are not allowed to play. If
violations are detected during a running game the team is disqualified for that game. If similar
violations occur repeatedly, the team can be disqualified from the tournament.
3. FIELD
3.1 Kind of field
There is only one kind of field for all sub-leagues.
3.2 Dimensions of the field
The playing-field is 122 cm by 183 cm. The field is marked by a white line which is part of the
playing-field. Around the playing-field, beyond the white line, is an outer area of 30 cm width.
The floor near the exterior wall includes a wedge, which is an incline with a 10 cm base and 1 cm
rise for allowing the ball to roll back into play when it leaves the playing field. Total
dimensions of the field, including the outer area, are 182 cm by 243 cm. It is recommended that the
field be positioned 70 to 90 cm off the ground.
3.3 Walls
Walls are placed all around the field, including behind the goals and the out-area. The height of
the walls is 14 cm. The walls are painted matte black.
3.4 Goals
The field has two goals, centered on each of the shorter sides of the playing field. The goal inner
space is 60 cm width, 10 cm high and 74 mm deep, box shaped. It has a cross-bar on top (to prevent
robots from entering the goal and to allow checking if the ball scored). The goal “posts” are
positioned over the white line marking the limits of the field. The cross-bar is exactly over the
white line. The interior walls and the cross-bar of each goal are painted, one goal yellow, the
other goal blue. The exterior (including the goal post and frame) are painted black (see the field
diagrams).
3.5 Floor
The floor consists of green carpet on top of a hard level surface. The carpet should be of a
quality that will resist the wear and tear of spinning wheels. All straight lines on the field
should be painted and have a width of 20 mm.
3.6 Neutral spots
There are five neutral spots defined in the field. One is in the center of the field. The other
four are adjacent to each corner, located 45 cm along the long edge of the field, aligned with each
goal post towards the middle of the field (from the goal post). The neutral spots can be drawn with
a thin black marker.
3.7 Center circle
A center circle will be drawn on the field. It is 60 cm in diameter. It is a thin black marker
line. It is there for
Referees and Captains as guidance during kick-off.
3.8 Penalty areas
In front of each goal there is a 30 cm wide and 90 cm long penalty area.
The penalty areas are marked by a black line of 20 mm width. The line is part of the area. A robot
is considered inside the Penalty Area when it is completely inside.
3.9 Lighting and Magnetic Conditions
The fields should be placed in a way that the influence by external infrared light is as low as
possible and that the magnetic field of the earth is disturbed as little as possible.
Perfect conditions cannot be guaranteed, however. Teams must come to tournaments being prepared
to calibrate their robots based on the lighting and magnetic conditions at the venue.
4. BALL
4.1 General ball specification
A well-balanced electronic ball shall be used. The ball will emit infrared (IR) light set to pulsed
mode.
4.2 Official suppliers for pulsed balls
Currently, there is one ball that has been approved by the RoboCupJunior Soccer Technical
Committee:
● RoboSoccer RCJ-05 ball operating in MODE A (pulsed) made by EK Japan/Elekit (www.elekit.co.jp)
Technical details are in the Appendix: “Technical Specification for Pulsed Soccer Ball”.
4.3 Tournament balls
Balls for the tournament must be made available by the organizers. Organizers are not responsible
for providing balls for practice.
5. GAMEPLAY
5.1 Game procedure and length of a game
The game will consist of two halves. The duration of each half is 10-minutes. There will be a
5-minute break in between the halves.
The game clock will run for the duration of the halves without stopping (except if or when a
referee wants to consult an official). The game clock will be run by a referee or a
referee assistant (see Rule 7.1 for the description of a referee assistant).
Teams are supposed to be at their field table 5 minutes before their game starts. To be at the
inspection table does not count in favor of this time limit. Teams can be penalized one goal per
minute at the referee's discretion if they are late for the game start. If a team does not report
within 5 minutes of the game start, it forfeits the game and the winning team is awarded a 5-0 win.
5.2 Pre-match meeting
At the start of the first half of the game, a referee will toss a coin. The team mentioned first in
the draw shall call the coin. The winner of the toss can choose either which end to kick to, or to
kick off first. The loser of the toss will settle for the other option. After the first half, teams
will switch sides. The team not kicking off in the first half of the game will kick off to begin
the second half of the game.
5.3 Kick-off
Each half of the game begins with a kick-off. All robots must be located on their own side of the
field. All robots must be halted. The ball is positioned by a referee in the center of the field.
The team kicking off places their robots on the field first. Robots cannot be placed nor remain
behind the goal line or in the outer area. Robots cannot be repositioned once they have been
placed.
The team not kicking off will now place their robots on the defensive end of the field. All robots
on the team not kicking off must be at least 30 cm away from the ball (that means outside the
center circle).
The referee may adjust the placement of the robots to make sure that the robots are placed properly
within the field positions.
On the referee's command (usually by whistle), all robots will be started immediately by each
captain. Any robots that are started early will be removed by the referee from the field and
treated as a damaged robot.
5.4 Human interference
Except for the kick-off, human interference from the teams (e.g. touching the robots) during the
game is not allowed unless explicitly permitted by a referee. Violating team/team member(s) can
be disqualified from the game.
The referee or a referee assistant can help robots to get unstuck, but only if the ball is not
being disputed near them, and also if that situation was created from the interaction between
robots (i.e. it was not a design or programming flaw of the robot alone). The referee or a referee
assistant will pull back the robots just enough for them to be able to move freely again.
5.5 Ball movement
A robot cannot hold a ball. Holding a ball means taking full control of the ball by removing all of
its degrees of freedom. Examples for ball holding include fixing a ball to the robot's body,
surrounding a ball using the robot's body to prevent access by others, encircling the ball or
somehow trapping the ball with any part of the robot's body. If a ball stops rolling while a robot
is moving or a ball does not rebound when rolled into a robot, it is a good indication that the
ball is trapped.
The only exception to holding is the use of a rotating drum that imparts dynamic back spin on the
ball to keep the ball on its surface. Such a device is called a dribbler.
Other players must be able to access the ball.
5.6 Scoring
A goal is scored when the ball strikes or touches the back wall of the goal. Goals scored either by
an attacking or defending robot have the same end result: they give one goal to the team on the
opposite side. After a goal, game will be restarted with a kick-off from the team who
received the goal against. Before a kick-off, all damaged or out-of-bounds robots are allowed
to return to the playing field immediately if they are ready and fully functional.
5.7 Goalie
The robot moving first into the penalty area on a team’s defending side completely (with every part
of it) is designated as goalie until a part of it leaves the penalty area.
5.8 Pushing
Within the penalty area, the goalie has priority. Attacking robots are not supposed to push the
goalie in any way. If the attacker and the goalie touch each other and at least one of them has
physical contact with the ball, the ball will be moved to the nearest unoccupied neutral spot immediately.
If a goal is scored as a result of this pushed-situation, it will not be granted.
5.9 Lack of progress
Lack of progress occurs if there is no progress in the gameplay for a reasonable period of time and
the situation is not likely to change. Typical lack of progress situations are when the ball is
stuck between robots, when there is no change in ball and robot’s positions, or when the ball is
beyond detection or reach capability of all robots on the field. After a visible and loud count,
(usually a count of five, the length of the count could be decided by the OC before a competition
as long as it’s the same length within a sub-league) a referee will call “lack of progress” and
will move the ball to the nearest unoccupied neutral spot. If this does not solve the lack
of progress, the referee can move the ball to different neutral spots.
5.10 Out of bounds
If a robot’s entire body moves out beyond the white line of the field completely, it will be called
for being out of bounds. When this situation arises, the robot is given a one-minute penalty, and
the team is asked to remove the robot from the field. There is no time stoppage for the game
itself.
The one-minute penalty starts when the robot is removed from play. Furthermore, any
goal scored by the penalized team while the penalized robot is on the field will not be granted.
Out-of-bounds robots can be fixed if the team needs to do so.
After the penalty time has passed, robot will be placed on the unoccupied neutral spot nearest to
where it has been taken off, and not directly aiming towards the ball.
A referee can waive the penalty if the robot was accidentally pushed out of bounds by any other
robot. In such a case, the referee may have to slightly push the robot back onto the field.
The ball can leave and bounce back into the playing field. The referee calls “out of reach”, and
will move the ball to the nearest unoccupied neutral spot when one of the following condition
occurs:
1) the ball remains outside the playing field too long,
2) any of the robots are unable to return it into the playing field (without their whole body
leaving the playing field), or
3) the referee determines that the ball will not come back into the playing field.
5.11 Damaged robots
If a robot is damaged, it has to be taken off the field and must be fixed before it can play again.
A damaged robot must remain off the field for at least one minute.
A robot is damaged especially when:
● it does not respond to the ball, or is not able to move (it lost pieces, power, etc.).
● it continually moves into the goal or out of the playing field.
● it turns over on its own accord.
Computers and repair equipment are not permitted in the playing area during gameplay.
Usually, a team member will need to take the damaged robot to an “approved repair table” near the
playing area, located inside the competitors working area. A referee may permit robot sensor
calibration, computers and other tools in the playing area, only for the 5 minutes before the start
of each half.
After a robot has been fixed, it will be placed on the unoccupied neutral spot nearest to where it
has been taken off, and not directly aiming towards the ball. A robot can only be returned to the
field if the damage has been repaired. If the referee notices that the robot was returned to the
field with the same original problem, s/he could ask the robot to be removed, and proceed the game
as if the robot had not been returned.
Only the referee decides whether a robot is damaged. A robot can only be taken off or
returned with the referee’s permission.
If both robots from the same team are deemed damaged during gameplay, the clock continues and the
remaining team gets one initial goal and rests while waiting for the opponent's return to play. The
remaining team will also get one additional goal for each minute the opponent's robots remain
damaged. After five minutes of absence, the team with no functional robots forfeits the game.
However, these rules only apply when none of the two robots from the same team were damaged as the
result of the opponent team violating the rules.
5.12 Multiple defense
Multiple defense occurs if more than one robot from the defending team enters its penalty area with
some part and substantially affects the game. The robot farther from the ball will be moved to the
center neutral spot. If multiple defense happens repeatedly, the robot will be deemed damaged.
5.13 Interruption of Game
In principle, a game will not be stopped.
A referee can stop the game if there is a situation on or around the field which the referee wants
to discuss with an official of the tournament or if the ball malfunctions and a replacement is not
readily available.
When the referee has stopped the game, all robots must be stopped and remain on the field
untouched. The referee may decide whether the game will be continued/resumed from the
situation in which the game was stopped or by a kick-off.
6. CODE OF CONDUCT
6.1 Fair Play
It is expected that the aim of all teams is to play a fair and clean game of robot soccer. It is
expected that all robots will be built with consideration to other participants. Robots are not allowed to cause deliberate interference with or damage to other robots during normal game play. Robots are not allowed to cause damage to the field or to the ball during normal game play.
Humans are not allowed to cause deliberate interference with robots or damage to the field or the ball.
6.2 Behavior
All participants are expected to behave themselves. All movement and behavior is to be of a
subdued nature within the tournament venue.
6.3 Help
Mentors (teachers, parents, chaperones, and other adult team-members including translators) are not
allowed in the student work area unless it is explicitly but temporarily permitted by a member of
the organizing committee. Only participating students are allowed to be inside the work area.
Mentors must not touch, build, repair or program any robots.
6.4 Sharing
The understanding that any technological and curricular developments should be shared among the
RoboCup and RoboCupJunior participants after the tournament has been a part of world RoboCup
competitions.
6.5 Spirit
It is expected that all participants, students, mentors and parents alike, will respect the
RoboCupJunior mission.
It is not whether you win or lose, but how much you learn that counts!
6.6 Violations / Disqualification
Teams that violate the code of conduct can be disqualified from the tournament. It is also possible
to disqualify only single person or single robot from further participation in the tournament.
In less severe cases of violations of the code of conduct, a team will be given a warning by
showing it a yellow card. In severe or repeated cases of violations of the code of conduct a team
can be disqualified immediately without a warning by showing it the red card.
7. CONFLICT RESOLUTION
7.1 Referee and referee assistant
All decisions during the game are made by the referee or the referee assistant who are in charge of
a field, and the persons and the objects surrounding the field. During gameplay, the decisions made
by the referee and/or the referee assistant are final.
Any argument with the referee or the referee assistant can result in a warning. If the argument
continues or another argument occurs, this may result in immediate disqualification from the game.
At the conclusion of the game, the referee will ask the captains to sign the score sheet. By
signing the score sheet the captains accept the final score on behalf of the entire team.
7.2 Rule clarification
Rule clarification may be made by members of the RoboCupJunior Soccer Technical
Committee and Organizing Committee, if necessary even during a tournament.
7.3 Rule modification
If special circumstances, such as unforeseen problems or capabilities of a robot occur, rules may
be modified by the RoboCupJunior Soccer Organizing Committee Chair in conjunction with
available Technical Committee and Organizing Committee members, if necessary even during a
tournament.
7.4 Regulatory statutes
Each RoboCupJunior competition may have its own regulatory statutes to define the procedure of the
tournament (for example the SuperTeam system, game modes, the inspection of robots, interviews,
schedules, etc.). Regulatory statutes become a part of this rule.
League Regulations 2014
1. Preamble
According to rule 2.7 of the RoboCupJunior Soccer Rules, each league has its own additional
regulations. They become a part of the rules.
Soccer will consist of two sub-leagues. These sub-leagues are called “Open League” and
“Light Weight
League” (See 2.1 Dimensions). Each sub-league can be further divided into primary and secondary.
For RoboCupJunior 2014, there are three sub-leagues as follows:
● Light Weight League – Primary
● Light Weight League – Secondary
● Open League
2. Regulations
2.1 Dimensions
Robots will be measured in an upright position with all parts extended. A robot’s dimensions must
not exceed the following limits:
sub-league Open League
Light Weight League
size / diameter Ø 22.0 cm
Ø 22.0 cm
height 22.0 cm *
22.0 cm *
weight 2400 g **
1100 g **
ball-capturing zone 3.0 cm
3.0 cm
voltage 15.0 V
12.0 V
* The handle of a robot may exceed the height.
** The weight of the robot includes that of the handle.
Ball-capturing zone is defined as any internal space created when a straight edge is placed on the
protruding points of a robot. This means the ball must not enter the concave hull of a robot by
more than 3 cm. Furthermore, it must be possible for another robot to take possession of the ball.
2.2 Limitations
Voltage pump circuits are permitted only for a kicker solenoid drive. All other electrical circuits
inside the robot cannot exceed 15.0 V for Open League and 12.0 V for Light Weight League. Each
robot must be designed to allow verifying the voltage of power packs and its circuits, unless the
nominal voltage is obvious by looking at the robot, its power packs and connections.
Pneumatic devices are allowed to use natural air only.
Kicker strength is subject to compliance check at any time during the competition. During gameplay,
a referee can ask to see a sample kick on the field before each half, when a damaged robot is
returned to the field, or when the game is about to be restarted after a goal. If the referee
strongly suspects that a kicker exceeds the power limit, he can require an official measurement with the 'Kicker Power Measure Device'. (See
the Appendix ‘Kicker Power Measure Device’ for details.)
2.3 Construction
Robots must be constructed exclusively by the student members of a team. Mentors,
teachers, parents or companies may not be involved in the design, construction, and assembly of
robots.
For the construction of a robot, any robot kit or building block may be used as
long as the design and construction are primarily and substantially the original work of a
team. This means that commercial kits may be used but must be substantially modified by the team.
It is neither allowed to mainly follow a construction manual, nor to just change unimportant parts.
Indications for violations are the use of commercial kits that can basically only be assembled in
one way or the fact that robots from different team(s), build from the same commercial kit, all
basically look or function the same.
Robots must be constructed in a way that they can be started by the captain without the help of
another person. Since a contact with an opponent robot and/or dribbler that might damage some parts
of robots cannot be fully anticipated, robots must have all its active elements properly protected with resistant
materials. For example, electrical circuits and pneumatic devices, such as pipelines and bottles, must be
protected from all human contact and direct contact with other robots. When batteries are
transported or moved, it is recommended that safety bags be used. Reasonable efforts should be
made to make sure that in all circumstances robots avoid short-circuits and chemical or air leaks.
2.4 Programming
Robots must be programmed exclusively by student members of the team. Mentors,
teachers, parents or companies should not be involved in the programming and debugging of robots.
For the programming of the robots, any programming language, interface or
integrated development environment (IDE) may be used. The use of programs that come together
with a commercial kit (especially sample programs or presets) or substantial parts of such
programs are not allowed. It is not allowed to use sample programs, not even if they are
modified.
2.5 Inspection and Interviews
Robots must be inspected and certified every day before the first game is played. The Organizing
Committee may request other inspections if necessary. The routine inspections include:
● Weight restrictions for the particular sub-league (see 2.1).
● Robot dimensions (see 2.1).
● Voltage restrictions (see 2.1 and 2.2).
● Kicker strength limits, if the robot has a kicker. (See the Appendix ‘Kicker Power Check
Device’.)
Proof must be provided by each team that its robots comply with these regulations, for example, by
a detailed documentation or log book. Teams may be interviewed about their robots and the
development process at any time during a tournament.
The Organizing Committee will arrange to interview teams during the first few days of the event
(see 2.3, 2.4, and 2.6). Teams must bring both robots and their computer code to the interview.
During an interview, at least one member from each team must be able to explain particularities
about the team's robots, especially with regards to its construction and its programming. An
interviewer may ask the team for a demonstration. The interviewer may also ask the team to write a simple program during the interview
to verify that the team is able to program its robot.
2.6 Violations
Robots that do not comply with the above regulations are not allowed to play. If violations are
detected during a game play, the team is disqualified for that game. If similar
violations occur repeatedly, the team can be disqualified from the tournament.
Technical Specification for pulsed Soccer Ball
1. Preamble
Answering to the request for a soccer ball for RCJ tournaments that would be more robust to
interfering lights, less energy consuming and mechanically more resistant, the RCJ Soccer
Technical Committee defined the following technical specifications with the special
collaboration from EK Japan and HiTechnic.
Producers of these balls must apply for a certification process upon which they can exhibit the
RCJ-compliant label and their balls used in RCJ tournaments.
Balls with these specifications can be detected using specific sensors from HiTechnic (IRSeeker -
information on distance and angle) but also common IR remote control receivers
(TSOP1140, TSOP31140, GP1UX511QS, ... - on-off detection with a possible gross indication of
distance).
2. Specifications
2.1 IR light
The ball emits infra-red (IR) light of wavelengths in the range 920nm - 960nm, pulsed at a
square-wave carrier frequency of 40 KHz. The ball should have enough ultra-bright, wide angle LEDs
to minimize unevenness of the IR output.
2.2 Diameter
The diameter of the ball is required to be 74mm. A well-balanced ball shall be used.
2.3 Drop Test
The ball must be able to resist normal game play. As an indication of its durability, it should be
able to survive, undamaged, a free-fall from 1.5 meters onto a hardwood table or floor.
2.4 Modulation
The 40 KHz carrier output of the ball shall be modulated with a trapezoidal (stepped) waveform of
frequency 1.2 kHz. Each 833-microsecond cycle of the modulation waveform shall comprise 8 carrier
pulses at full intensity, followed (in turn) by 4 carrier pulses at 1/4 of full intensity, four
pulses at 1/16 of full intensity and four pulses at 1/64 of full intensity, followed by a space
(i.e. zero intensity) of about 346 microseconds. The peak current level in the LEDs shall be
within the range 45-55mA. The radiant intensity shall be more than
20mW/sr per LED.
2.5 Battery Life
If the ball has an embedded rechargeable battery, when new and fully charged it should last for
more than 3 hours of continuous use before the brightness of the LEDs drops to 90% of the initial
value. If the ball uses replaceable batteries, a set of new high-quality alkaline batteries should
last for more than 8 hours of continuous use before the brightness of the LEDs drops to 90% of the
initial value.
2.6 Coloration
The ball shall be neutral in color. In particular, it must not have any green, blue or yellow
coloration (to avoid confusion with the colors of the field and goals).
Kicker Power Measuring Device
1. Preamble
This Kicker Power Measuring Device can measure the power of a robot’s kicker. It is easy to build
with commonly accessible materials.
This device can measure the power of a robot’s kicker up to a length of 22cm.
2. Materials
Plastic Board A4 paper size
M3 Spacers (40mm length) 5
M3 Screw 10
3. Device schematics
The device schematics can be printed out from the diagram located at the end of the
document. Please be advised to check that the software you use to print the schematic does not
have a “scale to fit” option activated (i.e. check that it is configured to print at 100% or
“actual size” scale).
Note: The device schematics shows a straight line past the 22cm mark, while the photo shows the
line at that point to be curved. Either straight or curved lines are acceptable, but a curved line
will request more difficult cutting and the attached device schematic is simple enough for quick
construction.
4. Example of device construction
a. Print out the device schematics.
b. Paste the paper on a plastic board. The incline line (red lines) should be straight.
c. Cut out along the lines, and drill the holes.
d. The two boards should be connected using the 40mm spacers.
5. Inspection
a. Place a ball at the bottom of the ramp run of the device, and put the robot in front of the
ball, aiming the kicker towards the top of the ramp.
b. Activate the robot’s kicker for a single shot.
c. Measure the distance that the ball travelled on the device. The distance should not exceed 22
cm.
RoboCupJunior Dance Rules 2014
RoboCupJunior Dance Technical Committee 2014:
Shoko Niwa - CHAIR (Japan), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
Nicky Hughes (UK), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
(general co-chair) Li Shi (China), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
Lisbeth Uribe (USA), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
Rui Baptista (Portugal), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
Sara Iatauro (Canada), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
These are the official rules for RoboCupJunior Dance event 2014. They are released by the
RoboCupJunior Dance Technical Committee. These rules have priority over any translations.
The following dance rules provide a framework for how to structure a robot dance performance. Changes from 2013 rules are highlighted in red. The rules have changed significantly for 2014 so teams should make sure they study the new rules.
PREFACE:
Robot dance means that one or more robots and humans come together with music and move in creative harmony. RoboCupJunior Dance allows teams to present a 1 to 2 minute creative stage performance using autonomous robots that the teams have designed, built and programmed. The Dance challenge is intended to be very open-ended! Teams are encouraged to be as creative, innovative and entertaining as they can.
Robot dance performances are marked based on the score sheet that has been published along with this dance rules. Judging will be conducted in three styles during the international event and there is a particular score sheet for each judging. The purposes of each judging are as follows:
ll Technical Interview is an interview examination in which all robots and programming are judged against technical criteria. Creative and innovative aspects are rewarded with higher scores. Also judges are interested in determining students' understanding of the robotic technologies they have used. Teams must show authenticity and originality with regard to their robots and performance in this interview.
ll Original Dance Performance is an individual team's stage performance in which a performance routine is judged according to creative, innovative and entertainment criteria. Teams must show originality, creativity and innovation throughout their performance routine. It is important for teams to execute and demonstrate what they have planned. It is expected that all participating teams perform their performance at their best.
ll SuperTeam Performance is a spontaneous robotic dance performance created by cooperating teams.
Teams are given a short period of time for collaboration at the competition venue. In this limited time, the SuperTeam teams must create a new performance that incorporates the work of each participating team. SuperTeam teams are encouraged to create an exciting and entertaining performance that entertains the audience and express their friendship. It is hoped that all participating teams will demonstrate how well they have collaborated and worked together.
RoboCupJunior Dance Rules 2014 2
The SuperTeam Performance is a special program for the international event and is not obligatory for regional events. The rules of the SuperTeam Performance are not described in this dance rule document. Team members who participate in the international event are strongly encouraged to look over the Dance SuperTeam rules 2014 before embarking on their journey.
1. GENERAL INFORMATION
1.1. Requirements
1.1.1. All team members must be the correct age for the primary and secondary categories as stated on the
RCJ website http://rcj.robocup.org/about.html under "Ages".
1.1.2. The maximum recommended number of ‘human’ members allowed on each team is 10; the minimum is 2. Any deviation from these numbers must be referred for adjudication to the Chief Judge before registration.
1.2. Download
The dance rules, score sheets, and all forms of documentation can be downloaded from the official RoboCupJunior website (http://robocupjunior.org/). Teams are encouraged to study the score sheets in detail in order to understand how they will be scored.
2. PERFORMANCE ROUTINE
2.1. Overview
The main emphasis of the Dance challenge is the technical aspects of the robot design and construction (including sensors and actuators) and the programming that creates the performance. The RoboCupJunior Dance Technical Committee would like to encourage teams to be creative, innovative and take risks in their use of technology and materials when creating their performances.
2.2. Kind of performance
2.2.1. Teams can choose to create either a Dance or a Theatre performance.
ll Dance is a performance closely synchronized to the music. The robot(s) and humans are required to move in time to the beat or rhythm of the music selected in the same way that a human may listen to the beat of music and dance to it. The Dance assessment focuses on the choreography and movement of robot(s) and humans synchronization to music beats.
ll Theatre is a performance in which the robots and humans tell a story or act out a play that is supported by music. Theatre assessment is focused on the overall theatrical performance. The performance will be judged by how effectively the robot(s) are used to present a theatrical theme. Examples: Nursery rhymes, movie-inspired performance, sporting theme, sustainability theme etc.
2.2.2. Before creating a performance routine, teams must carefully decide the performance category (Dance or Theatre) so that teams can clarify the aim of their performance. The following guidelines can help teams make the category decision:
A Dance performance will:
RoboCupJunior Dance Rules 2014 3
• Use choreography of the robots to music as the focus of the performance.
A Theatre performance will:
• Use movement and music to create a performance that tells a story. Music is used as background to supplement the performance.
• Use a story as a focus of the performance.
2.3. Music
Teams can use any kind of music for the performance. Teams are encouraged to select music that entertains the audiences or represents an atmosphere of the performance theme.
2.4. Duration
The duration of the performance routine must be no less than 1 minute and no more than 2 minutes.
2.5. Stage
2.5.1. The size of the performance stage area will be marked in a rectangular area of 6 x 4 meters (m) for robots with the 6m side facing the judges.
2.5.2. The boundary of the performance stage area will be marked with a 50 millimetre (mm) black
tape-line, surrounded by a 20mm red tape line. Teams are allowed to use the black and red line tape boundary to program a robot to identify the performance stage area.
2.5.3. The floor provided shall be made of flat (non-glossy) white painted MDF (compressed wood fiber).
2.6. Scenery and presentations
2.6.1. Teams are encouraged to provide their own scenery.
2.6.2. Teams are encouraged to provide a visual or multimedia presentation as part of their performance.
This can take the form of a video, animation, slideshow etc. Teams are encouraged to be creative when designing the presentation. Organizers will try their best to provide a projector and a projection screen for teams wishing to incorporate a presentation as part of their performance.
2.7. Human team members
2.7.1. Human team members are encouraged to perform with their robots. There is no penalty for humans not performing with their robots.
2.7.2. Human performers may be inside and outside the marked area.
2.7.3. The only physical contact humans may have with their robots is to start the robot(s) at the beginning of a performance routine. One human team member or several members using multiple robots and props may start each robot, either by hand or by remote control.
RoboCupJunior Dance Rules 2014 4
2.8. Content
Any performance that includes violent, military, threatening or criminal elements will be excluded. Any team using an inappropriate name or logo will also be excluded. Participants are asked to carefully consider the wording and messages communicated in any aspect of their performance. What seems acceptable to one group may be offensive to friends from a different country or culture.
2.9. Security and safety
2.9.1. In order to protect participants, RoboCupJunior officials and bystanders, routines may not include explosions, smoke or flame, use of water, or any other hazardous substances.
2.9.2. A team whose routine includes any situation that could be deemed hazardous, including the possibility of damaging the stage, must submit a report outlining the content of their dance routine to the Chief Judge BEFORE arriving at the competition. The Chief Judge may also request a demonstration of the activity before the stage performance. Teams not conforming to this rule may not be allowed to present their routine.
2.10. Authenticity and originality
The performance is to be unique and have never been used in a RoboCupJunior dance competition in any previous years’ at national or international competitions. Teams are encouraged to carefully check that all robots, props and costumes conform to this rule.
2.11. Additional instructions for creating a performance
2.11.1. Teams are strongly encouraged to program their robot(s) to begin the performance routine a few seconds after the music starts as it is extremely difficult to judge precisely when the music will sound after the audio source is started. Teams may find it useful to include a “beep” at the beginning of their music as a start signal.
2.11.2. Teams are encouraged to practice on the same flooring type to have a better simulation for robot conditions and reduce the set-up time at the RoboCupJunior competition.
3. ROBOTS
3.1. Robot technology
Any technology can be used to create the robots. Teams are encouraged to use technologies creatively. Innovative or unusual use of technology (including sensors) is encouraged and will be rewarded. For example laptops, notebooks, mobile phones, tablets, Raspberry Pi and other similar devices MAY be used as robotic controllers but no mains power should be used while on stage. Teams are encouraged to use technology in unusual, innovative or inspired ways to create an engaging performance. If you are unsure whether the technology you are using is appropriate please contact the Chief Judge before the competition.
RoboCupJunior Dance Rules 2014 5
Robots may be of any size. Any robot(s) or prop(s) taller than 4 meters from the stage floor must be discussed with the judges and permission sought.
3.3. Number of robots
There may be any number of robots on a team. However, using multiple robots does not necessarily result in obtaining higher points.
3.4. Costumes
Costumes for robots are encouraged. Additional points will be awarded if the costumes are handmade by the competitors.
3.5. Communication
3.5.1. During the performance, any robot on stage may communicate with another robot on stage from the same team. There must be no communication with off-stage devices. The source of communication must be infrared (IR), Ultrasonic, Bluetooth and ZigBee. It is the teams’ responsibility to be aware that their communication does not interfere with other teams' robots when practicing or performing.
3.5.2. No team is permitted to use radio frequency (RF) signals (like Wi-Fi or “radio control”) as this may interfere with robots in other leagues. The only exception is the use of ZigBee. Take care to make sure you are not using any radio frequency signals as part of remote control of the robots; Teams have inadvertently used radio frequencies in the past. If you are unsure please check with the Chief Judge before your performance.
3.5.3. Teams with robot communication MUST explain the communication to the judges at the Technical
Interview.
3.6. Control
3.6.1. Robots must be controlled autonomously. No member of the team may make physical contact with the robot during its performance UNLESS the contact has been discussed and approved by the judges PRIOR to the performance.
3.6.2. Human interference and interactions with robots' sensor might be judged as a kind of remote control. If a team plans to use this in their performance routine, it must be discussed and approved by the judges prior to the performance.
3.6.3. Robots may be started manually by human contact or with remote control (see 3.5) at the beginning of the performance. See also 2.7.3.
3.7. Additional instructions for designing and constructing robots
3.7.1. Under no circumstances will mains electricity be allowed to use on the stage. This includes the use of mains electricity for robots, scenery and props.
RoboCupJunior Dance Rules 2014 6
irregularities of up to 3 mm in the floor surface. Whilst every effort will be made to make the stage
flat this may not be possible in all venues. Teams should be prepared for some irregularities in the surface of the stage.
3.7.3. Although The RoboCupJunior organizers endeavour to make variable lighting including spotlights available, we cannot guarantee direct or intense spotlights to be available. In the same way, teams should not expect the performance stage area to necessarily be able to be darkened. It is recommended that teams design their robots to cope with variations in lighting conditions, as lighting naturally varies from venue to venue. Teams should come prepared to calibrate their robots based on the lighting conditions at the venue.
3.7.4. Teams using compass sensors should be aware that metal components of the staging may affect the compass sensor readings. Teams should come prepared to calibrate such sensors based on the conditions at the venue.
4. PREPARATIONS FOR THE EVENT
4.1. Music data
4.1.1. Teams must provide their own audio music source. Teams are strongly encouraged to bring a good quality audio music source file since their evaluation also depends on the music quality.
4.1.2. The preferred transport method is to place the sound file on a memory stick as a MP3 file. The memory stick should be clearly labeled with the team name and category (primary or secondary) and should hold only the MP3 file. It is essential that the music should be given to the RoboCupJunior officials acting as sound technicians before the team's practice period. Teams are encouraged to bring multiple copies of the audio source file.
4.1.3. The music should start at the beginning of the audio music source with a few seconds of silent lead-time.
4.2. Documents
4.2.1. A Technical Sheet should be carefully completed by each team for each robot. The Technical Sheet (as a document) will be posted online with the score sheets. This is similar to a resume for each robot. Every team must prepare one sheet for each robot. The technical sheet gives teams the opportunity to explain the technical aspects of each robot to the judges.
4.2.2. Teams should complete a Stage Script describing the dance movements of the robots during the overall performance.
4.2.3. The Technical Sheet(s) and the Stage Script must be submitted to the judges before judging. These documents should be sent to the Chief Judge via email before departing to the event. Teams who could not send these documents must hand those to the judges as soon as possible on arrival to the competition venue.
4.3. Poster display
4.3.1. Teams will be given public space to display a poster board. The size of the poster should be no larger than A1 (60 x 84 cm). The poster should be brought to the Technical Interview. After the
RoboCupJunior Dance Rules 2014 7
4.3.2. The purpose of the poster is to introduce the team, explain the technology used in the robots and document the preparation work. Posters should be made in an interesting and entertaining format. They will be viewed not only by the judges, but also by other teams and visiting members of the public. The poster should provide information about the team and the development of the robot(s) (in particular any innovative technologies that the team has used).
4.3.3. Areas that need to be covered include: team name, division (primary or secondary), a picture of your team, your country and your location in your country, a little about the area in which you live, pictures of the robot(s) under development at various stages and information about your robot technology. Also, please include any interesting or unusual feature about the team, robot, your background or your entry.
4.3.4. The poster display must be presented during the interview, and may be called upon to help establish the authenticity of a teams’ performance.
5. TECHNICAL INTERVIEW
5.1. Procedure of the interview judging
5.1.1. All teams will have a 15 minutes interview judging during the competition.
5.1.2. Interviews will be judged by at least two RoboCupJunior officials.
5.1.3. The Dance Interview Score Sheet is used in the interview judging. It is strongly suggested for teams to read the Dance Interview Score Sheet before the interview to make good use of the interview.
5.1.4. Teams should ensure that they bring all their robots, props, posters, and copies of the programs.
They should be prepared to demonstrate and discuss the use of all the sensors, electronics and technology that they have used. They should be prepared to demonstrate their robots and other technologies used.
5.1.5. The documents the team must supply for the interview judging are the poster, a technical sheet for each robot, a stage script and listings of all programs.
5.2. Demonstration during the Technical Interview
Teams are strongly encouraged to demonstrate their robots working during the Technical Interviews. Especially, the innovative or special functions of their robot(s), such as complex mechanisms for a dynamic movement, innovative use of sensor, or an original electronic/electrical device should be shown in front of the judges. Only a short amount of time will be available (maximum 5 minutes). Teams should be prepared to demonstrate the key features of their robots in this time.
5.3. Translator
Interviews will take place in English. If teams require a translator they should inform the local organizing committee by e-mail prior to the event to allow translators to be organized.
5.4. Second interview
If the judges consider it necessary, teams may be asked to complete a second interview. If this occurs the score from the second interview will be used to calculate the total score of the individual team.
RoboCupJunior Dance Rules 2014 8
6. ORIGINAL DANCE PERFORMANCE
6.1. Performance judging for individual teams
6.1.1. The stage performances will be judged by a panel of at least three officials. One of the performance judges is a RoboCupJunior official who judges the Technical Interview as well.
6.1.2. The Dance Performance Score Sheet is used in the Original Dance Performance judging.
6.1.3. All teams will be given 2 opportunities to perform their performances before the judges. The highest performance score will be used to calculate an individual team's total score.
6.2. Stage performance
6.2.1. Each team will have a total of 5 minutes for their performance. This time includes stage set- up, introduction and performance routine, including any re-starts due to factors under the teams’ control. It does not include time needed for packing up and clearing the stage.
6.2.2. A judge starts a stopwatch when a team member steps a foot on the stage for the maximum five minute period and following 1 minute to clear the stage. If the time limit is exceeded due to circumstances outside the team’s control (for example problems with starting the music by the technicians) there will be no time penalty. The judges have the final say on any time penalties.
6.2.3. A RoboCupJunior official will start the music and the audio visual/multimedia presentation for the performance routine.
6.2.4. Each team may perform one and only one Dance or Theatre performance routine. Some minor modifications (improvements) of the performance using the same music may be accepted. Any questions or concerns on performance and/or robot modifications at the venue should be discussed with the Chief Judge.
6.3. Stage setup time
Teams are strongly encouraged to use the time while they are setting up the stage for their performance to introduce to the audience the features of their robots, technology used and highlights of the robotic performance and to introduce their team. Any format is acceptable for the
introduction including video, slideshow or a team member talking. The introduction must be within the total time allocation for the performance.
6.4. Clearing the stage
Following each performance, a team must fully tidy up the stage, pack up and remove any objects related to their performance. The performing team has a maximum of one minute to clear the stage after the end of their performance. The maximum time onstage is therefore six minutes.
6.5. Restarts
Teams are allowed to restart their routine if necessary, at the discretion of the judges. There is no limit on the number of restarts a team can perform within their 5 minutes performance time. Penalty marks will be deducted from the score. The team will be asked to leave the stage after 5 minutes.
RoboCupJunior Dance Rules 2014 9
6.6. Penalties
6.6.1. If a team exceeds the time limits explained in 2.4, 6.2 and 6.4 the team will be penalized by the loss of marks.
6.6.2. If the entire body of a robot (main body of robot not including any large extensions from the body) moves outside the marked boundary of the performance area the team will receive a penalty score. If in doubt please consult with the Chief Judge for clarification of “robot body” in relation to your robot design.
6.6.3. Physical contact between a human and a robot or human interference to robots' sensor will be penalized by the loss of marks. If contact between a human and a robot is part of the performance, the interaction must be discussed with and approved by the judges BEFORE the performance to ensure all the robotic performance is autonomous and aware.
6.6.4. Unless a problem is not the fault of the team, any restart will result in a score penalty.
6.6.5. Teams who, in the opinion of the judges, have knowingly produced duplicate robots, costumes, props or performance movement (duplicate music is allowed) of another team or reused previous years' robots, costumes, props or performance of the same team will be subject to penalties. Penalties range from score reduction to a maximum penalty of exclusion from the competition.
6.7. Preparation for the stage performance
6.7.1. It is the responsibility of the team to ensure that the music is playing correctly before their first performance by liaising with the RoboCupJunior officials.
6.7.2. Teams should ensure that any presentation is displayed correctly before their first performance by liaising with the RoboCupJunior officials.
6.7.3. 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 RoboCupJunior official starting the audio source; and vice versa. Teams should come prepared for these conditions.
6.8. Practice on the main stage
6.8.1. The main performance dance stage will be made available for teams to practice on. In fairness to all teams who may wish to practice, a booking sheet will be used to reserve the stage for a short practice time. Please be respectful of the allocated time.
6.8.2. The last team to practice on this stage before performance time starts must fully clean up the stage and clear the stage area at least 3 minutes before the performance start time.
7. JUDGING AND COMMENDING
7.1. Judging criteria
The mark's criteria of judging are as follows:
ll The Technical Interview:
Design
RoboCupJunior Dance Rules 2014 10
Use of sensors
Programing
Evidence of authenticity
ll The Original Dance Performance: Choreography and storytelling Entertainment value
Effective use of technology Execution of performance Judge's discretion
7.2. Totaling
The total score of each team is calculated by combining the scores from the team’s Technical
Interview and Original Dance Performance.
7.3. Prizes and awards
7.3.1. The following prizes will be awarded in each age category (primary and secondary):
ll The RCJ International Dance team of the Year is awarded to the team with the highest combined total of the Technical Interview and the Original Dance Performance scores.
ll The RCJ International Dance SuperTeam of the Year is awarded to a SuperTeam that gained the highest SuperTeam performance score.
7.3.2. Awards will also be given to individual teams in the following categories:
Best Design
Best Construction
Best Use of electronic devices
Best Use of sensors
Best Programming
Best Stage Performance
The awards will be awarded based on both the Technical Interview and the Original Dance
Performance scores at the discretion of the judges. Individual teams can receive only one award.
7.3.3. There will also be certificates awarded for the following categories:
Best Team Collegiality: This award goes to the team who, by popular vote, has given the greatest support to the other teams – the support can be demonstrated in a number of ways, such as providing assistance with components, developing friendships and/or giving encouragement to other teams. The vote described in section 8.4.2 will be used for selecting the best Collegiality Award.
Best Poster: This award goes to the team who, at the discretion of the judges, has produced the best poster that describes the team and robot technology used.
Best Creative Presentation: This award goes to the team who, at the discretion of the judges, has produced the most creative and technically interesting digital display that supports and enhances the robot performance. This could be a video, slideshow, images or any other form of digital product that is displayed during the performance.
RoboCupJunior Dance Rules 2014 11
Best Novice Team: This award goes to the primary and the secondary teams who have placed highest in the competition overall and have not received another award, and where ALL members of the team are competing at RCJ international for the first time (this does not include a team having a team member(s) who has (have) competed in other RCJI categories).
7.3.4. No one team shall receive more than 3 prizes, awards and/or certificates excluding the SuperTeam awards.
7.4. Feedback
RoboCupJunior is an educational project. It is important that team members learn from their experiences with RCJ, and have the opportunity to improve in later years if they so choose. The organizers will provide feedback on each team's performance at the conclusion of competition. The sheet will indicate to the team their areas of strength and also areas needing improvement. It is important to note that these sheets are not to be used to debate positions, decisions or competition scores with the judges.
8. CODE OF CONDUCT
8.1. Spirit
8.1.1. It is expected that all participants, students and mentors, will respect the RoboCupJunior mission.
In addition, participants should keep in mind the values and goals of RoboCupJunior.
8.1.2. It is not whether you win or lose, but how much you learn that counts. You will really miss out on a lifelong learning experience if you don't take this opportunity to collaborate with students and mentors from all over the world. Remember this is a unique moment!
8.2. Fair Play
8.2.1. It is expected that the aim of all teams is to participate in a fair and clean competition.
8.2.2. Humans that may 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.
8.2.3. The team is responsible for removing all debris left from their routine that may interfere with the performance of subsequent activities.
8.2.4. Remember: Helping those in need and demonstrating friendship and cooperation are the spirit of
RoboCupJunior as well as making the world a better place.
8.3. Sharing
8.3.1. It is understood that RCJI events with rich technological and curricular developments should be shared with other participants after the competition.
8.3.2. Any developments may be published on the RoboCupJunior Web site following the event.
8.3.3. Sharing information furthers the mission of RoboCupJunior as an educational initiative.
RoboCupJunior Dance Rules 2014 12
8.4. COLLEGIALITY
8.4.1. Each participating team will have one vote to nominate the team that displayed the greatest cooperative interactions and shared support with other teams. Please refer to section 7 for Collegiality Award.
8.4.2. In keeping with the spirit and collegiality aspects of RCJI, the organizers will provide a party for all team members, mentors and supporters. It is strongly requested that all such individuals delay their departure sufficiently to attend the party, even if the event is held after the finals and prize giving ceremony. The organizers request all team members bring business-sized cards to share with other teams at the party. These cards could include the team name, its members' name(s) and contact details, so students can remain in contact with each other after the event. This is optional, but encouraged. It is also requested, but not compulsory, for team members to wear either national dress, or some icon that identifies them with their country. This can be done in a humorous manner, such as an animal mascot from their country or another creative idea.
8.5. Behavior
8.5.1. All movement and behavior is to be of a subdued nature within the event venue.
8.5.2. Competitors are not to enter set-up areas of other leagues or other teams, unless expressly invited to do so by other team members.
8.5.3. Participants who misbehave may be asked to leave the building and risk being disqualified from the event.
8.6. RoboCupJunior Officials
8.6.1. The officials will act within the spirit of the event.
8.6.2. The RoboCupJunior officials shall not have close relationship with any of the teams in the age group they judge.
8.7. Mentors
8.7.1. Mentors (defined as teachers, parents, chaperones, translator or any other non team-member) are
not allowed in the student work area except to assist carrying equipment in or out of the area on the arrival and departure days.
8.7.2. If a problem is encountered with a computer or other device that is clearly beyond the reasonable ability level of a student to repair, a mentor may request permission from the organizers to enter the work area for the sole purpose of advising on that repair. They must leave the work area immediately after this is completed. Rule 8.7.1 still applies at these times.
8.7.3. Mentors are not allowed to set up equipment on stage, as this should be the responsibility of team members. Organizers will assign volunteers to teams that need an assistant for stage set-up. Teams should request this assistance to the officials.
8.7.4. A mentor found in the student work area without an acceptable reason may lose his/her access to the venue and the team will be penalized.
8.7.5. A mentor found to be involved with mending, building or programming the robot(s) and/or
RoboCupJunior Dance Rules 2014 13
9. ADDITIONAL INFORMATIONS
9.1. Information about the event
9.1.1. Teams will be responsible for checking for updated information during the event. Updated information will be provided on notice boards in the venue and (if possible) on the RoboCupJunior website. The updated information will be announced at the beginning of the event and will be posted on the notice boards as well.
9.1.2. Newsletters will be disseminated during the event to ensure teams and mentors have the latest information.
9.2. Contact
Queries regarding the rules or their interpretation may be sent to the Dance 2014 Chair of the
Technical Committee: Shoko Niwa (Japan), Ova e-mail adresa je zaštićena od spambota. Potrebno je omogućiti JavaScript da je vidite.
.
Broj računa PBZ:
2340009-1110491689
IBAN:
HR6723400091110491689