2018:Programming: Difference between revisions
From 1511Wookiee
Jump to navigationJump to search
Programming (talk | contribs) No edit summary |
Programming (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
<div class="mw-parser-output"><div class="mw-parser-output">General programming stuff relevant to all subsystems should be documented here. <div class="mw-parser-output"><div class="mw-parser-output"> | <div class="mw-parser-output"><div class="mw-parser-output">General programming stuff relevant to all subsystems should be documented here. <div class="mw-parser-output"><div class="mw-parser-output"> | ||
<div class="mw-parser-output"> | |||
<div class="mw-parser-output"> | <div class="mw-parser-output"> | ||
== Outstanding Tasks - Robot Code == | == Outstanding Tasks - Robot Code == | ||
| Line 12: | Line 13: | ||
*Drive: Test/Evaluate new gyro (SPI-based interface instead of analoggyro - already installed on test board) (Josh) | *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) | *Drive: Examine auto modes and decide what range(s) of auto driving actions need to work the best, then make them happen (Josh) | ||
*< | *<s>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)</s> | ||
*Old robots: Bring 2015, 2016, 2017 all up to 2018 image and ported code. Test. (anyone, but this is super low priority) | *Old robots: Bring 2015, 2016, 2017 all up to 2018 image and ported code. Test. (anyone, but this is super low priority) | ||
| | ||
<div class="mw-parser-output"> </div> </div> | <div class="mw-parser-output"> </div> </div></div> | ||
= Outstanding Tasks - Scouting App = | = Outstanding Tasks - Scouting App = | ||
Revision as of 08:38, 3 February 2018
General programming stuff relevant to all subsystems should be documented here.
Outstanding Tasks - Robot Code
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 on the controls wiki (Kyle)
- Controls: Get details on to IO map wiki page for both game pad operations (Kyle)
- Controls: Implement controls code on robot (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)
Outstanding Tasks - Scouting App
In no particular order!
- Update tables classes to define new db schema for 2018 (thunderscout.db package, class ResultsTable)
- Update EventStorage class to create new tables (EventDbHelper internal class)
- Update EventStorage class to read/write new tables (methods getAllSavedMatches() and saveMatchData())
- Continue work on UI screens (layout XML mostly)
- Update webserver output to match new match data (Webserver class)
Programmers:
Programming Lead: Zack E
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 lineProgramming Sub-pages and Links
- Documentation
- SVN
- 2018:Robot_IO_Map
