2018:Programming

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!

• Jeff
  • 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())
  • Update webserver output to match new match data (Webserver class)
  • New bluetooth sync
• Alex
  • Feedback from Carol - for scored in switch & scale do the following:
    • Rename DNA to be the verbose version: "Did not attempt"
    • To give more horizontal space and separate things better, move alliance/opponent selections to next line, consider centering them left/right
    • Disable Alliance/Opponent when they don't make sense (you do this by listening to button selections in the Java code for the fragment - see last year commented out code for an example)
    • Default to "Did not attempt"
    • Also default to "Alliance" selected
  • In the data class (ScoutingMatchData) enums for Score, remove "NOT_CHECKED" option;  this is not relevant anymore with defaulting "Did not attempt" to on. The constructor should default score/switch values to "did not attempt" to match the UI.
  • Similar for Scoring on Exchange:
    • DNA should be "Did not attempt" and selected by default
    • Remove "not checked" from data class and default to "did not attempt"
  • For climbing:
    • Make "Not on platform" selected by default
    • Remove "not checked" from data class, default to "did not attempt"
    • Rename the "failed" checkbox to "Climb attempted, but unsuccessful"
  • Add missing files to SVN (on commit screen, click checkbox next to new files) -- ask Mr. Byers or Dan for help if needed!

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

• Documentation
  • WPILib_Screensteps
  • WPILib documentation
• SVN
  • SVN Setup
  • Online browsing of our SVN Tree
• 2018:Robot_IO_Map

Programming Archives

• 2017:Programming
• 2016:Programming
• 2015:Programming
• 2014:Programming
• 2013:Programming
• 2012:Programming
• 2011:Programming
• 2010:Programming
• 2009:Programming