CARMA Platform is built on robot operating system (ROS) and utilizes open source software (OSS) that enables Cooperative Driving Automation (CDA) features to allow Automated Driving Systems to interact and cooperate with infrastructure and other vehicles through communication. Doxygen Source Code Documentation :
[ ] Anomaly report (something appears to not work correctly)
[X] Enhancement request (describe the enhancement being requested)
[ ] Other (please ensure the description clarifies why the issue doesn’t fall into either of the above categories)
Descriptive summary
Integration test of ROS2 Guidance package nodes: Arbitrator, Plan Delegator, and Trajectory Executor. Vehicle should be able initialize CARMA, select a route, and the ROS2 Guidance package nodes should be able to begin planning and trajectory generation in coordination with ROS1 Plugins. Test should be conducted at TFHRC using a basic route to demonstrate functionality. Plugins to be included in test should be the ROS1 versions of Route Following, ILC, and Pure Pursuit Control. These plugins will be tested in their ROS2 port under a separate integration test story.
msmcconnell
commented
2 years ago
Types of Issue
Descriptive summary
Integration test of ROS2 Guidance package nodes: Arbitrator, Plan Delegator, and Trajectory Executor. Vehicle should be able initialize CARMA, select a route, and the ROS2 Guidance package nodes should be able to begin planning and trajectory generation in coordination with ROS1 Plugins. Test should be conducted at TFHRC using a basic route to demonstrate functionality. Plugins to be included in test should be the ROS1 versions of Route Following, ILC, and Pure Pursuit Control. These plugins will be tested in their ROS2 port under a separate integration test story.
Carma version where this issue was discovered
Expected behavior
Vehicle is able to make a simple travel at TFHRC.
Actual behavior
NA
Steps to reproduce the actual behavior
NA
Related work