Page Comparison

...

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

...

Time

...

Item

...

Presenter

...

Notes

Action items

Decisions

Item
Notes
David
Dave replied! He will be talking to Teerstra.
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

Read thru comp doc https://www.unmannedsystems.ca/wp-content/uploads/2020/01/2020-USC-Student-Competition-CONOPS-and-Rules-V5_17-Jan-20.pdf
1 more person to review unit test integration PR
Get new code w/ unit test integration to compile w/ gmock

Versions Compared

Old Version 1

New Version Current

Key

Things to discuss during the meeting

Discussion topics

Action items

Decisions

Action items

Item	Notes
David	Dave replied! He will be talking to Teerstra.
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