...
Finish the different stages
current calculations for the AM struct is in autosteer
there is no AM struct back to PM → will have to see where that affects the code
altitude → macro
Determine next directions with the getNextDirectionsCommand
Noticed that fijo may not be recognized
determine if we actually need to #ifdef the whole file or if we can reduce to just snippets of code because I do not like looking through 500+ lines of code
we currently never have an array of waypoints → is this something we should work on implementing
pathStateClasses
look at the resetPassby function
look through drone code part and take out stuff we don’t need (resetPassby? Autosteer?)
need to look at landing and takeoff implementation and fix according to what Gordon wants
CruisingState and WaypointManager
Manav had the idea of having an array that would be constantly updated to hold the previous, current, next waypoints. Need to implement this
just go through code in both files and see what we need to keep/change or yeet
set the current waypoint (given from sensorfusion) → next = target waypoint (given from fijo, using _PathData)
CruisingState
assign waypoint types (depending on the takeoffCommand boolean?)
WaypointManager:
update rest of hpp and cpp
review the math for gps coordinates
Link the current position (given from sensor fusion) and target(future) waypoint (needing for path following math)
calculating desired track between target and waypoint after target (need to also link these)
Pathfollow requires track and position → calculate this
re look at
initialize_waypoint,update_path_nodes,initialize_flight_path,get_next_directions,get_next_directionsIs there a situation where we would need to edit flight path (on the way from a→b, change to a → d → b)
Vector???
