[ONAV-1771] Add support for on_start / on_stop Mission Tasks #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
clearpath_navigation_msgs/Mission.msg
has been updated to include 'on_start' and 'on_stop' Task arrays which are executed when the mission begins and ends respectively (on_stop Tasks will execute regardless of mission failure or success)CreateTask
service has been updated to includeassign_on_start
andassign_on_stop
fields (similar functionality as theassign_to
field)assign_to
field of the CreateTask service has been updated toassign_to_wp
to distinguish it from assign_on_start/assign_on_stop~add_task_to_start
&~add_task_to_stop
- Adds a task to the on_start/on_stop array for given mission~remove_task_from_start
&~remove_task_from_stop
- Removes a task from the on_start/on_stop array for given mission