iARoC Rules


Competition Environment


  • All competition arenas will be made from 24” segments of 3” dia. white PVC pipe, joined by “elbow connectors” that result in cells that measure 27” center-to-center with an open area of 24”. The pipe will be adhered to the tile floor using tape/velcro.
  • The lighting of the arena environment is fluorescent and with no natural light (i.e. no windows).
  • Every effort will be made by the competition judges to ensure the conditions of each arena are consistent for each team and do not affect the running of the robots.
  • Teams may hang banners and posters around the competition area and/or their pit area providing they are easily removable and do not leave marks on the walls.

Team Prep Areas


  • Each team will be assigned a “Prep Area”. Teams will restrict themselves to their designated area and not enter another team’s space unless invited to do so.
  • All teams are responsible for maintaining the cleanliness and safety of their assigned area. All team items (including trash) must be removed from the Prep Areas at the end of the competition.
  • The Prep Areas will be on the same floor, but separate from the main competition arenas, so teams will be required to transport their robot and all other required equipment to and from each event at the appropriate time.

Event Schedule


Each team will be presented with the competition schedule at the start of each competition day when they report to the event. It is the team’s responsibility to be at the designated competition arena at their event start time. Every effort will be made to find the team, but the event clock will start ticking even if they are not present.

Judging


  • The Chief Judge will be the final and absolute authority on the interpretation and application of all rules and decisions.
  • Each event arena will also have an Arena Judge who will apply the rules to the operation of their individual arena.
  • Teams may not appeal any ruling or scoring decision, once they have used their allocated time and moved away from the competition arena.

Competition


Event 1 – The Speed Event


The object of this event is for a robot to travel from the start to the end of the competition arena as quickly as possible. The sides of the arena will contain PVC pipe joints that are pointed inward to create obstacles for wall huggers or wall skimmers (see below). Robots may autonomously return to the start area to score additional points.

  • Each arena will have its own Arena Judge.
  • Only one robot will be in the Arena at any time.
  • Each team will have 20 minutes to complete a maximum of 3 attempts at this event.
  • The robot must start completely behind the start line.
  • The robot must start centered between the sides of the arena.
  • The Arena Judge will say “Go” when starting the timer for each attempt.
  • The Arena Judge will stop the time when any part of the robot crosses the finish line.

Points

  • Each team will be awarded a number of “speed points” equal to the number of teams they have out-paced.
  • Robots will be given 5 “no touch” bonus points at the start of each attempt. One “no touch” point will be subtracted for each wall segment they touch during the run.
  • If at the end of the speed run, the robot can autonomously return from the Finish area to the Start area, the team will be awarded a “return” bonus of 5 points.



Event 2 – The Navigation Event


This object of this event is for a robot to navigate a maze, similar to (but not the same as) the one shown below. Teams will be rewarded for fastest speed of navigation and shortest distance traveled through the maze.

  • Each arena will have its own Arena Judge.
  • Only one robot will be in the Arena at any time.
  • Each team will have 20 minutes to complete this event and may make multiple attempts, but only one attempt will be scored for the competition.
  • The team must tell the Arena Judge which of their attempts is to be scored before leaving the arena. They may not return and change their selection after another team has entered the arena.
  • The robot must start completely in the Start cell of the maze.
  • The Arena Judge will say “Go” when starting the timer for each attempt.
  • The Arena Judge will stop the time when the entire robot is inside the Finish cell.

Points

  • Each team that successfully reaches the End cell of the maze will receive 5 “completion points”.
  • Teams will also be awarded a number of “speed points” equal to the number of teams they have out-paced.
  • Teams will be given 5 “efficiency” bonus points at the start of each attempt to solve the maze. One “efficiency” point will be subtracted for each maze cell they enter that is off the shortest path through the maze.


Event 3 – The Target Acquisition Event


This object of this event is for a robot to “claim” a designated target as quickly as possible. Once a target has been claimed, it is not available to other competitors.

  • The Arena will have an overall Judge and one Judge for each of the designated targets contained within the Arena.
  • All competing robots will be in the Arena at the same time.
  • Team captains will be asked to choose a start location that must be against the Arena boundary. The team with the fewest accumulated points to date will get to choose their start position first. The team with the most accumulated points to date will choose last. In the event of a tie, a random drawing will determine order of selection.
  • The Arena Judge will say “Go” to begin the event.
  • The competition will end when all designated targets have been “claimed” as determined by the Arena Judge.

Points

  • Only teams that successfully claim a target will be awarded points.
  • Teams will be awarded speed points equal to the number of teams they have out-paced in claiming a target.


Event 4 – Team Technical Briefing


The goal of the Team Technical Briefing is to briefly communicate the coding strategies of each of the robot’s programs to a Judging Committee.

  • All team members must participate in the explanation of the details of the software developed by their team.
  • Team briefings may not exceed 10 minutes.
  • Judges may ask questions after the briefing, but will not exceed an additional 10 minutes.
  • Presentations should include:
  • The relationship between the hardware and software.
  • Strategies and algorithms used for each element of the competition, including how autonomy and challenge learning have been implemented.
  • An overview of the decision-making strategies used during the team’s development process. What was tried, what worked, what roadblocks (if any) were encountered, and what lessons were learned.
  • Every attempt will be made to provide WiFi access to teams during their briefing. However, teams should make provisions for loss of Internet access during their assigned briefing period.

Points

  • Teams will be awarded points for:
  • Technical Content
  • Quality of Presentation
  • Team Participation

Rules are subject to change.