Home

Spring Semester Game Plan

When a software item says finished, it means it should be merged by this date!

• 13 Jan:
  • Decide what to put on the BoM
• 20 Jan:
  • Submit SGB BoM by 23rd
  • SGB meets on the 24th, get funds soon after hopefully. Over $1.2k triggers extra review that happens early next week
  • Obstacle detection V0.1 finished
• 27 Jan:
  • Purchase parts from BoM
  • Sim finished
  • Python version of planner with basic functionality is done (V0.1)
  • GPS navigation finished
  • Vision node code finished (not tuned)
  • Obstacle detection V0.1 finished
• 3 Feb:
• 10 Feb:
  • Begin arena assembly (start earlier if possible)
  • Switch over to new robot platform (V2.0)
• 17 Feb:
  • Should have finished arena assembly
  • Finish transition to V2.0, basic testing to ensure it works as expected
  • Start tuning vision algorithm
  • Create a test plan (Where can we test? How can we get outdoors ASAP? What are we testing?)
• 24 Feb:
  • C++ planner finished (V0.2)
• 3 March:
  • Register for the competition by the 8th - $70 for the team plus $10 per robot
  • Vision tuned - reliably detecting the ramp, hoop, poles
  • Work on gameplay strategy, begin testing full course
• 10 March:
  • Vision / object detection filtering finished
• 17 March:
  • 4 weeks to go - test!
• 24 March:
  • 3 weeks - test!!
• 31 March:
  • 2 weeks - test!!!
• 7 March:
  • 1 week - test!!!!