rmf_traffic_ros2 package

This package provides interfaces between rmf_traffic and ROS 2 interfaces.

Quality Declaration

This package claims to be in the Quality Level 4 category. See the Quality Declaration for more details.

Changelog for package rmf_traffic_ros2

2.1.6 (2023-06-02)

• Switch to rst changelogs (#276)
• Contributors: Yadunund

2.1.5 (2023-05-20)

• Reformat code to meet expectations of uncrustify-0.72.0: (#274)
• Contributors: Yadunund

2.1.4 (2023-04-27)

2.1.3 (2023-04-26)

2.1.2 (2022-10-10)

2.1.0 (2022-10-03)

• Make async behaviors more robust: (#228)
• Make schedule failover more robust: (#232)
• Ignore conflicts between any plans that have a dependency: (#205)
• Add support for docking in lanes with entry events: (#226)
• Add message conversion functions for the navigation graph: (#207)
• Changes for humble compatibility: (#215)

2.0.0 (2022-03-18)

• Update to the traffic dependency system: (#188)

1.5.0 (2022-02-14)

• Allow participants to sync up with remote databases when discrepancies arise (#145)
• Support for geojson graphs (#142)

1.4.0 (2021-09-01)

• Make traffic schedule updates more efficient: (#86)
• Add redundancy to the traffic schedule node: (#61)

1.3.0 (2021-06-07)

• Use topics to update schedule mirrors: (#17)
• Allow participant descriptions to update: (#17)
• Add persistence to Traffic Schedule Participant IDs: (#242)

1.2.0 (2021-01-05)

• Adding distributed blockade system hooks: (#22)

1.1.0 (2020-09-24)

• Add a schedule node factory to the public API: (#147)
• Allow the Negotiation class to accept callbacks for Table updates: (#140)
• Allow the Negotiation class to provide views for existing Tables: (#140)
• Allow the Negotiation class to store up to a certain number of completed negotiations: (#140)
• Migrating to ROS2 Foxy: (#133)
• Contributors: Aaron Chong, Grey, Yadu, ddengster

1.0.2 (2020-07-27)

• Always respond to negotiations: (#138)

1.0.0 (2020-06-23)

• Provides [rmf_traffic_ros2]{.title-ref} library which offers utilities to wrap [rmf_traffic]{.title-ref} into [ros2]{.title-ref} APIs

  : - [rmf_traffic_ros2::convert(T)]{.title-ref} functions convert between [rmf_traffic]{.title-ref} API data structures and [rmf_traffic_msgs]{.title-ref} message structures -

      [rmf\_traffic\_ros2::schedule]{.title-ref} utilities help to connect [rmf\_traffic]{.title-ref} objects across distributed ROS2 systems
  
      :   -   [MirrorManager]{.title-ref} - Object that maintains
              a [rmf\_traffic::schedule::Mirror]{.title-ref}
              across ROS2 connections
          -   [Writer]{.title-ref} - Factory for
              [rmf\_traffic::schedule::Participant]{.title-ref}
              objects that can talk to a database across ROS2
              connections
          -   [Negotiation]{.title-ref} - Object that manages a
              set of traffic negotiations across ROS2 connections
  

• [rmf_traffic_schedule]{.title-ref} - a ROS2 node that manages a traffic schedule service and judges the outcomes of traffic negotiations

• Contributors: Aaron Chong, Grey, Marco A. Guti