Feature: Bag Recorder #165
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, recording data is disabled. It can be enabled and configured with entries to platform as shown:
Right now, the configuration and launch file are in
clearpath_diagnostics. The config file is parsed and overwritten withextras:ros_parametersand can be completely configured.The ros2bag record node expects the
storage.uripath to point to a directory that does not exist, which it creates and then saves bag files to it. To match the timestamp behaviour of the CLI, the launch file parses the config, reads thestorage.uriparameter, and creates a path to a timestamped subdirectory. This way, restarting the node with the same parameters will not cause overwriting errors because the same folder is used. By default, thestorage.uripoints to/etc/clearpath/bagsand the launch file passes/etc/clearpath/bags/ros2bag_{timestamp}to the node. For more details see theclearpath_robotPR.