Changelog for package clearpath_navigation_msgs

0.10.0 (2024-07-04)

• Merge pull request #46 from clearpathrobotics/0.13/features 0.13/features
• fix endline
• 0.13/features: Changed the ptz constant for poi's
• Merge remote-tracking branch 'refs/remotes/origin/poi' into 0.13/features
• create new camera msg package with InspectPOI action
• added InspectPOI action
• consistency fix from network to map
• Merge branch 'poi' of github.com:clearpathrobotics/clearpath_msgs into poi
• Remove quotation marks around string constants; they are not needed
• added network goto poi values
• added a boolean enable_heading flag (#44)
• Add new Mission Manager messages & services related to POI creation/deletion/modification (#42)
  • Add tag constants for PTZ and GoTo labels. Add initial services for creating & updating POIs, creating Waypoints from POIs
  • Add accessors for the points of interest
  • Add the clone point of interest service
  • Add the new_name field to the POI clone service
  • Add service for adding/removing tags
• Merge pull request #41 from clearpathrobotics/ONAV-2371 added point of interest message
• added newline
• added point of interest message
• Add: Publish the robot's current high-level plan as part of NetworkGotoFeedback (#36)
• Merge pull request #35 from clearpathrobotics/mod/onav_msg_updates ONav message type changes
• Add: Boolean '.paused' field to AutonomyStatus
• Mod: Add result message + rename feedback.state to feedback.message for waypoint mission types
• Contributors: Chris Iverach-Brereton, Drew O'Brien, José Mastrangelo, Stephen Phillips, Tony Baltovski, jmastrangelo-cpr, stephen-cpr

0.9.9 (2024-03-14)

• Message updates for onav-0.12 (#34)
  • Add the size_exceeded field to NetworkMapState
  • Mod: Update dock messages for new 0.12 docking APIs
  • Mod: Add new autonomy API types to AutonomyStatus.msg
  • Mod: Use float64 version of Vector2D for returning path recording lat-lons

  * Mod: Add header field to RunNetworkGoToPlanner.action feedback ---------Co-authored-by: Chris Iverach-Brereton <<civerachb@clearpathrobotics.com>>

• Contributors: stephen-cpr

0.9.8 (2024-03-11)

• Add additional messages for Network of Paths
• Contributors: Chris Iverach-Brereton <<civerachb@clearpathrobotics.com>>, Stephen Phillips <<stphillips@clearpathrobotics.com>>

0.9.7 (2024-02-05)

0.9.6 (2023-12-21)

0.9.5 (2023-11-03)

• [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 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

0.9.4 (2023-10-20)

0.9.3 (2023-10-19)

0.9.2 (2023-10-17)

• [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

0.9.1 (2023-08-22)

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

0.9.0 (2023-07-05)

• Initial release