2018:Programming: Difference between revisions

From 1511Wookiee
Jump to navigationJump to search
mNo edit summary
No edit summary
Line 1: Line 1:
<div class="mw-parser-output">General programming stuff relevant to all subsystems should be documented here.  
<div class="mw-parser-output">General programming stuff relevant to all subsystems should be documented here.  
<div class="mw-parser-output">
== Outstanding Tasks ==
== 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!'''
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)
*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)
*Document on Wiki (or link to gdocs) autonomous modes. Include Names/Number assignments for Dashboard/Controls to use (Kate, Josh)  
* Work with electrical on deciding needed sensors; work with mechanism team to document on mechanism wiki page (Kate, Ethan)
*Controls: '''document '''which specific model of gamepads we will use this year (Kyle)  
* Document on Wiki (or link to gdocs) autonomous modes. Include Names/Number assignments for Dashboard/Controls to use (Kate, Josh)
*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)  
* Controls: document which specific model of gamepads we will use this year (Kyle)  
*Drive: Test/Evaluate new gyro (SPI-based interface instead of analoggyro - already installed on test board) (Josh)  
* 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: Examine auto modes and decide what range(s) of auto driving actions need to work the best, then make them happen (Josh)  
* 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)
*<span style="background-color:#e74c3c">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!&nbsp; </span>(Kate)  
* Drive: Examine auto modes and decide what range(s) of auto driving actions need to work the best, then make them happen (Josh)
*Old robots: Bring 2015, 2016, 2017 all up to 2018 image and ported code. Test. (anyone, but this is super low priority)  
* 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)


&nbsp;
<div class="mw-parser-output"><div class="mw-parser-output">&nbsp;</div> </div> </div>


<div class="mw-parser-output">
<div class="mw-parser-output">
== Programmers: ==
== Programmers: ==


Revision as of 20:33, 29 January 2018

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)
  • 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: Test/Evaluate new gyro (SPI-based interface instead of analoggyro - already installed on test board) (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: 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!  (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: Kate & Josh

Auto: Josh & Kate

Lights: Zack E

 
 

Autonomous

Do nothing

Cross auto line

Sense switch and place cube in switch and cross auto line

Programming Sub-pages and Links

Programming Archives

Retrieved from "https://wiki.penfieldrobotics.com/wiki/index.php?title=2018:Programming&oldid=9324"