refactor: planning configuration file
All threads resolved
Closes #31 (closed)
changed milestone to %SoAR-2023W19
added Partner::NOC Project::SoAR Status::Sprint Backlog Weight::2 labels
added 1 commit
- 691a23b6 - fix: tests and add beacon_ID field per platform
requested review from @danjon
-
Shift
region_of_interest
to planning config level (not squad level) -
Add
target_altitude
-
Add sensor params fro scanning e.g. swath_width, freq, angle fields (instead of under
additional_data
raw field) -
Add
operator
atsquad and orplatform level— The operator is part of the topic messages are published to. For the autonomy engine and for the abort messages from the UI we need this information included in the configuration message in order to determine how to build the publish topic for a given platform. -
Add
turning_radius
-
Add
beacon_ID
(num) per platform -
remove
squad_state
-
remove
additional_data
from emergency (already has additional data in main schema)
Edited by Trishna Saeharaseelan-
Shift
- Resolved by Dan Jones
- Resolved by Dan Jones
- Resolved by Dan Jones
- Resolved by Dan Jones
added 1 commit
- a7d8fe27 - refactor: swap lats and lons to y and x respectively and field description updates
mentioned in commit e70c8ca8
Please register or sign in to reply