ros-noetic-clearpath-navigation-msgs (0.9.5-1focal) focal; urgency=high

  * [ONAV-1772] Add 'allow_failure' boolean to Task message type
    - When set to True, any missions that execute this task will be allowed to continue if the task fails
  * Merge pull request #18 <https://github.com/clearpathrobotics/clearpath_msgs/issues/18> from stephen-cpr/ONAV-1771/on_start_stop_tasks
    [ONAV-1771] Add support for on_start / on_stop Mission Tasks
  * Merge remote-tracking branch 'origin/noetic-devel' into ONAV-1771/on_start_stop_tasks
  * [ONAV-1771] Add support for on_start / on_stop Mission Tasks
    - 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)
    - The CreateTask service has been updated to include 'assign_on_start' and 'assign_on_stop' fields (similar functionality as the 'assign_to' field)
    - The 'assign_to' field of the CreateTask service has been updated to 'assign_to_wp' to distinguish it from assign_on_start/assign_on_stop
    - Added the following service endpoints to mission_manager (using the AddRemoveById.srv type):
    - ~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
  * Contributors: Stephen Phillips, Tony Baltovski

 -- José Mastrangelo <jmastrangelo@clearpathrobotics.com>  Fri, 03 Nov 2023 04:00:00 -0000

ros-noetic-clearpath-navigation-msgs (0.9.4-1focal) focal; urgency=high



 -- José Mastrangelo <jmastrangelo@clearpathrobotics.com>  Fri, 20 Oct 2023 04:00:00 -0000

ros-noetic-clearpath-navigation-msgs (0.9.3-1focal) focal; urgency=high



 -- José Mastrangelo <jmastrangelo@clearpathrobotics.com>  Thu, 19 Oct 2023 04:00:00 -0000

ros-noetic-clearpath-navigation-msgs (0.9.2-1focal) focal; urgency=high

  * [ONAV-1546] Add autonomy API option to start mission from current position
    - Changes to the ExecuteMissionByUuid.action and Mission.action to support 'Resuming' missions and starting missions from specified waypoints.
    - The combination of the 'from_start' and 'start_waypoint' field determine the behavior:
    - from_start == True will always force the mission to run from the beginning
    - from_start == False AND start_waypoint_uuid/start_waypoint == Null will let autonomy decide where to start the mission ('closest' waypoint)
    - from_start == False AND start_waypoint_uuid/start_waypoint != Null will tell autonomy to start the mission from the specified waypoint (useful in area-coverage type applications)
  * Fix over & underline length in changelogs
  * Contributors: Chris Iverach-Brereton, Stephen Phillips, Tony Baltovski

 -- José Mastrangelo <jmastrangelo@clearpathrobotics.com>  Tue, 17 Oct 2023 04:00:00 -0000

ros-noetic-clearpath-navigation-msgs (0.9.1-1focal) focal; urgency=high

  * Add comments to Waypoint message to match documentation
  * Added Metrics.msg
  * Contributors: Chris Iverach-Brereton, José Mastrangelo

 -- José Mastrangelo <jmastrangelo@clearpathrobotics.com>  Tue, 22 Aug 2023 04:00:00 -0000

ros-noetic-clearpath-navigation-msgs (0.9.0-1focal) focal; urgency=high

  * Initial release

 -- José Mastrangelo <jmastrangelo@clearpathrobotics.com>  Wed, 05 Jul 2023 04:00:00 -0000


