Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Date

Participants

Things to discuss during the meeting

  • Talking to David status

  • Architecture status

  • Unit test integration PR status

  • Sensor interfaces status

  • CV update

  • Moving forward with implementing the state machines

  • S2020 Scheduling

Discussion topics

Item

Notes

David

  • David has yet to respond 😞 did he retire?

  • Maybe reach out to Derek Wright to see if he’s willing to back the team? Or Teerstra directly to see if we can take some of our stuff back

Architecture

  • Now on Confluence, Anthony added some details from last weeks meeting

  • Should probably redo the block diagrams

  • As the term goes on the architecture docs should become more and more robust

Unit Test

  • Was building fine without gmock, but there could be some unforeseen bugs that is preventing the code to compile

CV

  • 2 people want to do CV! 4th CS students

  • Anthony sent them over the CV Bootcamp and they’re doing v well w/ the bootcamp

  • Once they submit bootcamp, send over comp rules/goals? Get them on board, maybe add them to the meetings…?

  • To discuss more next week

Sensor Interfaces

  • Lucy took IMU.hpp

  • Anthony took GPS.hpp

  • Annie picked up Airspeed.hpp

  • Elton to pick one up some time

  • Aim to get interfaces done by next week (31st):

    • 1. need to get unit testing integration merged into devel branch (needs 1 more reviewer)

    • 2. need to get code to compile w/ gmock

    • 1 and 2 should be completed by…May 26 or 27th

Moving forward with implementing the state machines

  • To be discussed next week - dependent on sensor interfaces being implemented

S2020 Scheduling

  • Goals atm:

    • Implementing all 3 state machines

      • Both state machines should be tested and ready to go by fall term

      • Port over PICPilot communication/downlink state machine for

      • Ideally: By end of term, have all these high-level state machines ready and only have to write sensor drivers

    • Figure out what to do w/ CV (go thru comp rules, repo)

      • Potential: Ask them to do what was done in previous years to set up a good foundation

    • Set up fall recruitment plan

      • Find balance between knowledge transfer and getting shit done

      • To further discuss

Action items

  • No labels