CicleCI Build Status | Sonar Code Quality | DockerHub Release | DockerHub Release Candidate | DockerHub Develop |
---|---|---|---|---|
CARMAMsgs contains all the CARMAPlatform-specific ROS message definitions used by the CARMAPlatform
This package is required for building most of the CARMAPlatform nodes
To add this package to your CARMAPlatform project simply clone this repository into your colcon workspace.
There are both ROS1 and ROS2 packages in this repo. Building of these packages will automatically toggle based on your ROS version, however, it is important to be careful to not mix the install path for the distributions. Therefore different install and build paths should be used for each ROS version.
For example:
ROS 2
colcon build
ROS 1
colcon build --install-base install_ros1 --build-base build_ros1
The primary CARMAPlatform repository can be found here and is part of the USDOT FHWA STOL github organization. Documentation on how the CARMAPlatform functions, how it will evolve over time, and how you can contribute can be found at the above links as well
The current CARMA Platform system operates as a hybrid of ROS 1 Noetic and ROS 2 Foxy components. While nearly all components have been upgraded to ROS 2 Foxy, a small amount of ROS 1 Noetic content still exists within the system, including some packages in this repository. Additionally, this repository contains the build instructions for building the ros1_bridge
, which enables bi-directional communication between ROS 1 Noetic and ROS 2 Foxy portions of the CARMA Platform system. For more information, please see the relevant documentation in the carma-config repository.
Welcome to the CARMA contributing guide. Please read this guide to learn about our development process, how to propose pull requests and improvements, and how to build and test your changes to this project. CARMA Contributing Guide
Please read our CARMA Code of Conduct which outlines our expectations for participants within the CARMA community, as well as steps to reporting unacceptable behavior. We are committed to providing a welcoming and inspiring community for all and expect our code of conduct to be honored. Anyone who violates this code of conduct may be banned from the community.
The development team would like to acknowledge the people who have made direct contributions to the design and code in this repository. CARMA Attribution
By contributing to the Federal Highway Administration (FHWA) Connected Automated Research Mobility Applications (CARMA), you agree that your contributions will be licensed under its Apache License 2.0 license. CARMA License
Please click on the CARMA logo below to visit the Federal Highway Adminstration(FHWA) CARMA website. For technical support from the CARMA team, please contact the CARMA help desk at CAVSupportServices@dot.gov.