2018:Programming

From 1511Wiki
Jump to: navigation, search
General programming stuff relevant to all subsystems should be documented here.

Outstanding Tasks

Split up by subsystem - responsible veteran student in (), student(s) doing actual code, if different, in []. These are not in any particular order!

  • Review questions for mechanism teams and get answers (Kate, Ethan)
  • Work with electrical on deciding motor controllers for all motors; document on IO Map (Kate, Ethan)
  • Work with electrical on deciding needed sensors; work with mechanism team to document on mechanism wiki page (Kate, Ethan)
  • Document on Wiki (or link to gdocs) autonomous modes. Include Names/Number assignments for Dashboard/Controls to use (Kate, Josh)
  • Controls: document which specific model of gamepads we will use this year (Kyle)
  • Controls: Start deciding and documenting, with controls team and potential drive team input, what buttons/axis/whatever control all mechanisms. Document on IO Map page on wiki (Kyle)
  • Drive: Ensure we have stock of specific Gyro we want to use, else get it on order. Decide where on robot it needs to go, document on drive wiki, and talk to drivebase team leads to make sure it lands there (Josh)
  • Drive: Examine auto modes and decide what range(s) of auto driving actions need to work the best, then make them happen (Josh)
  • Auto/Vision: What camera(s) to use? Do we have stock or need to order? (Kate)
  • Auto/Vision: Where on robot do(es) camera(s) need to go? Document on Robot Design page on Wiki and talk to relevant design teams so they carve out that place! Bring up at integration. (Kate)
  • Old robots: Bring 2015, 2016, 2017 all up to 2018 image and ported code. Test. (anyone, but this is super low priority)


Programmers:

Controls: Kyle & Adrian & Cameron

DriveMeyer: Josh

Arm/Intake: Kate & Ethan

Ramp: TBD

Auto: Josh & Kate

Autonomoose

Do nothing

Cross auto line

Sense switch and place cube in switch and cross auto line

Programming Sub-pages and Links

Programming Archives