Main Page
|
Course Admin
|
Course Resources
|
Rules & Regulations
|
Team Profiles
|
Photo Gallery
|
Contact Info
 
  You are here: RoboFlag Main Page > Course Changes


 

Capture The Flag - Game Ideas


General Ideas

  • robots are going to be playing capture the flag (rather than tag)
  • teams of three (manager, software, electrical) build one robot that can play the game
  • during the first term, teams build a robot that can detect the flag, detect the different zones in the arena, detect other robots, etc, and is able to navigate around the arena
  • at Christmas or in early January, the six 'teams' will join into three smaller 'groups', so each group (six students) will consist of two teams (three students each)
    • each team is still only responsible for their own robot, and will be graded for the design & performance of their own robot, but:
      • cooperation between the two teams in a group is essential, however, if the group would like to do well
      • the two robots are expected to communicate with each other via RF
    • the two teams within each group must cooperate in regards to gameplay strategy, ie:
      • one robot might be offensive (trying to capture the other group's flag), while the other could be defensive (defending their own group's flag)
      • both robots might work together to capture the other team's flag, while leaving their own flag un-guarded
      • etc.
    • the teams in each group will continue to present their robot design work separately:
      • groups will not give oral presentations, teams will each be responsible for presenting their design work (all three students will present in the same 45-minute presentation, but each individual will be graded)
      • teams will mostly be graded separately during the final competition, although part of the grade will be based on how their group performs


Game Ideas

  • the arena will consist of a 12'x8' plywood floor, 12" black (non-reflective) walls, and a few simple walls in the middle to break up a direct line of sight from one team zone to the other
  • the arena will be aligned with the 12' length in a North-South (or East-West) direction, with two group zones at either end
  • the group zone areas will be 1' wide, and will run the entire width (8') of the arena - the zones will be marked with different floor colours (red & blue)
  • each group will consist of two robots and a flag - both robots and the flag will start the game inside their group zone
  • when the game starts, the robots can move around the arena attempting to retrieve the other group flag, or attempting to defend their own flag
  • the game is over when one group has both group robots AND the other group flag in the group zone - the winning group's flag doesn't need to be in the group zone
  • a game might look like:
    • group RED, robots R1 and R2, starting in the RED corner with the RED flag
    • group BLUE, robots B1 and B2, started in the BLUE corner with the BLUE flag
    • the game starts, and both red robots (R1, R2) go on the offensive, while one blue robot (B1) goes on the offensive, and the other blue robot (B2) moves into a defensive position
    • after navigating around the few inner-maze walls, the red robots get to the blue zone, and the blue robot gets to the red zone
    • the blue defensive robot blocks the blue flag and pushes against one of the red robots, while the blue offensive robot locates and grabs the red flag
    • the red robots manage to circumvent the defender and one manages to attach itself to the blue flag, but the blue defender pushes the red robot into a wall
    • the blue offensive robot, and the red flag, return to the blue side of the arena and B1 signals the blue defensive robot to also return to the blue zone
    • the two blue robots and the red flag get inside the blue zone before the red robots and the red flag can even get across the arena - blue wins!

Technical Ideas

  • robots:
    • will each have an infrared beacon to broadcast their location to other robots within the arena (somewhat like the beacon used last year in RoboTag)
    • must be able to detect other robot beacons (beacon detectors)
    • must be able to navigate the arena and detect the two different zones (zone detectors)
  • flags:
    • will be a cylinder ~4" in diameter, and ~12" tall, with a multi-directional roller
    • will have a flashing light on top, visible to all 360-degrees, that robots can detect (RED flag might blink at 2Hz, BLUE flag might blink at 20Hz)
    • will have a "grab bar" and "push bumper" surrounding the cylinder at certain height so robots can grab (and pull) or push the flag around

Capture The Flag - Changes From Last Year


Objective Changes

  • robots are going to be playing capture the flag (rather than tag)
  • teams of three build one robot each (instead of a pair of 'bots) - ie: one team of three students builds one robot
  • team-members are responsible for individual roles (electrical design, software design, management + systems design) plus all are responsible for building and mechanics
  • two teams will cooperate to form a group of six students, and will work together to compete against other groups in the final competition


Competition Changes

  • official inspection before the competition (ie: document any problems that exist to make scorekeeping easier at a later date)
  • competition venue will be changing to accomodate the larger crowds we'll be aiming for (high-school kids on their March Break) - probably to Bell Theatre in the Minto Centre
  • arena will be known and static (ie: it won't change during the competition, and you'll have access to it throughout the course)
  • the competition will be projected onto the Bell Theatre screen for viewers sitting further back in the theatre


Schedule Changes

  • formal design review has been moved forward a week to push teams to do more work earlier in the term (when fewer time demands are placed on the team)
  • background / research chapter due in first term to offset problems writing the final report all in the last three weeks of the course
  • competition date moved forward two weeks into the high-school march break, so students can be lured into attending Carleton based on the coolness of the engineering program
  • in-house competition date has been moved to the weekend _after_ the final competition, so we can concentrate on fun first, and real technical presentation second


 
 
Main Page
|
Course Admin
|
Course Resources
|
Rules & Regulations
|
Team Profiles
|
Photo Gallery
|
Contact Info