This PR adds a carma_debug_msgs package to store messages used purely for debugging and not meant to function as interfaces. This is to support the currently ongoing control system analysis.
I also corrected some of the licenses in the other message package.xml files.
Having array like data published to text logs can be a bit difficult to deal with for debugging and analysis since each node needs a separate script to parse whatever custom layout is used. By having debug topics we can more easily align the data with other rosbag data.
How Has This Been Tested?
Tested as part of a stand alone build at summit point.
Types of changes
[x] Defect fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that cause existing functionality to change)
Checklist:
[ ] I have added any new packages to the sonar-scanner.properties file
[ ] My change requires a change to the documentation.
PR Details
Description
This PR adds a carma_debug_msgs package to store messages used purely for debugging and not meant to function as interfaces. This is to support the currently ongoing control system analysis.
I also corrected some of the licenses in the other message package.xml files.
Related Issue
Any control system issue such as https://github.com/usdot-fhwa-stol/carma-platform/issues/1167 https://github.com/usdot-fhwa-stol/carma-platform/issues/1166
Motivation and Context
Having array like data published to text logs can be a bit difficult to deal with for debugging and analysis since each node needs a separate script to parse whatever custom layout is used. By having debug topics we can more easily align the data with other rosbag data.
How Has This Been Tested?
Tested as part of a stand alone build at summit point.
Types of changes
Checklist: