timeline updates + revisions

Landing Pad

-Data and video labelling

-Model Training

• Working model by end of december (trained/testable)

• Set up Pi on the 7th for flight test on the 8th

• Submit request before EOY

GUI

-Demo with map

-Data integration

-QR scanner for T1 (restricted area)

• Live map position and numbers (altitude, GPS coords) - end of december

• with telemetry: second iteration done with all data live by end of first week of Feb.

• Confirm hardware with testing or order if we’re not using WARG laptop before Feb (comp sim)

Telemetry

-Mock module

-EFS issues (anthony?)

-Routing/deciphering for position data: end of december

-Jetson/ZP comms after ground side (or once winter term start). End of Jan

• CV groundside only

• Telemetry is blocking GUI validation, Jan 13th (?!)

Path Op

-Demo comparison

-Reinforcement model for T2

-EFS discussion for T1 and just general implementation

Demo models with mock data/simulators by mid/late december

• Task 1 done in a vacuum

• No updates on Task 2/QR code

Lidar research

-general research schedule

-low prio

-Buy a LIDAR and demo by Feb??

Ardupilot

~0

-Pull people from path auton/GUI?

-maybe set a hard deadline and then grab ppl for it

-Last resort: draft the LIDAR team

• We need to choose by Mid jan/feb for system integration

• Use ardupilot ground system if ours is incomplete

• (add ardupilot waypoints without human input)

• System integration (landing, takeoff etc.)

• Feb

• Use mission planner GUI as altitude control

• Backup telemetry link in case of ZP failure

• Switchover decision by Mid Jan- Jan 27th, pull people if we switch

Auton Landing

-Fisheye correction

-landing pad size

-find distance

-handle other distortion issues caused by single camera

-final step would be converting to vector for ZP/ardupilot

Distance vector from video footage by end of december

• Some demo code done, create kitchen sinks repo and add to it