Skip to content

Autonomous Meeting Task List 12_13_2016

admin4571 edited this page Dec 13, 2016 · 19 revisions

I. Today ( 12/13/2016 )

A. Housekeeping

  1. Get names of students in attendance
  2. Get list of Github accounts of all Autonomous team members
  3. Enquire status of smartboard, computer setups, auto shutdown
  4. Ask about StuySplash
  5. Who wrote any code this past week? I see zero checkins, one pull requests ( point out why it is wrong )
  6. Shuffle R2D2[ Mahim, Jia, Leslie, Arlenis, Mohammed, Sharom], C3P0 [ Ben, Marsala, Loren, Carlo,Nathaniel, Nourin ] This removes people from subsystems assigned last week.
  7. Who read the code from other teams?
  8. Get status update of weekly progress and highlight issues faced
  9. How should you communicate issues you have ( Remind + Error stack + code snippet )
  10. Communication on Remind or my email if you cant send via remind ---CORE CRITICAL---
  11. Mohammed, Mahim, Arlenis are being active with their feedback. Props!
  12. Keep checking in your code!!! Do not use pastebin etc. Github, Github, Github.

  1. Discuss build season

  1. Explain CI/CD to the team ( Gradle - https://gradle.org/eclipse/, Travis, Docker ) {Optional}
  2. Using Git to clone feature branch, add to staging, commit, pull request workflow understanding
  3. Writing robust tests

  1. Internship update
  2. Incremental v/s All-at-once approach [Not either or, just a preference]

  1. Talk about goals for next week ( Learning assignments + coding assignments )
  2. Get old code from Arlenis

B. Technical Items

  1. KEEP IT SIMPLE!!!
  2. Go over issues people faced during the week
  3. Deal with git issues [Arjun] { http://rogerdudler.github.io/git-guide/ }
  4. Explain how hardware and software interact [Arjun,Arlenis,Conor]
  5. Code review for all subsystems[Arjun/Inyong]

  1. Everybody writes
    • One simple class to add 2 numbers and print out the result. Pass in arguments from the main method
    • Add a method to add the same 2 numbers 50 times in a loop and return the sum
    • Add a method to show difference between constants and variables in this number addition. To add a twist, import the constant from another class. Also add a function that returns a number to the other class so that you can show the difference between instantiating a class v/s using a static final constant
  2. Decide what features of each subsystem need to be implemented for the course of the week [Inyong/Arjun/R2D2/C3P0]
  3. Start looking into Autonomous functionality [R2D2]
  4. Continue with CodeAcademy [C3P0]
  5. Writing tests for all code [R2D2]

  1. Demo the Roborio [Inyong]
  2. Someone checks out the master code [Student]
  3. Show how to build the master code [Arjun] { Needs the Gradle plugin- Buildship Gradle }
  4. Deploy one benchtop test program [Inyong]

II. This week ( 12/14 - 12/20 )

A. Housekeeping

  1. Set up the new computers with the new LAN/subnet/full-admin-access/FIRST software
  2. Prepping for the 2017 code update
  3. Everyone should have their own computer

B. Learning assignments

  1. Continue reading code of [R2D2]
  2. Start looking into vision tracking [Mohammed]
  3. Vision tracking camera : http://charmedlabs.com/default/pixy-cmucam5/ [Mohammed]
  4. Vision tracking basics :
  5. Using PID controllers : http://www.simbotics.org/files/pdf/programming-pid.pdf [Mahim,Leslie]
  6. Using RobotBuilder and SmartDashboard [Nathaniel, Carlo] {https://wpilib.screenstepslive.com/s/4485/m/26401}
  7. Get familiar with the Roborio and Gradle build system [Arlenis,Sharom,Jia]
  8. 2017 software update [Ben, Marsala, Nourin] {https://wpilib.screenstepslive.com/s/4485/m/23527}

C. Coding assignments [https://github.com/frc4571/CrateRobot]

Goal : Have clean, compiled code for 3 subsytems of the robot in place that we will deploy the next Tuesday to see work. Write autonomous code. Clean up teleop code.

  1. Assignment of work

  2. Continue working on the same feature branches for this week

  3. By Monday, each subteam should create a pull request for their code to be merged into master so that we(Inyong/Arjun) can do code reviews before we get there on Tuesday.