Add ros-z MCAP topic recording - #2667
Draft
schmidma wants to merge 5 commits into
Draft
Conversation
schmidma
force-pushed
the
ros-z-mcap-recording-v1-design
branch
from
July 2, 2026 03:16
3ba6abd to
dd57257
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
ros-z-recordingcrate for MVP MCAP topic recordingrosz record [--output <path>] <topic>...with text summaries, existing-output preflight, and configurable CLI node identityMotivation
This gives developers a local ros-z topic recorder without adding robot-side services, replay support, or broader recording workflow changes.
Implementation
The recording backend resolves requested topics at startup with normal ros-z topic qualification rules, writes raw Zenoh sample payloads to MCAP with
ros-z.schema.v1schemas andros-z.cdrmessages, and finalizes on Ctrl-C or internal recording failure. The MVP keeps publisher provenance, drop counts, replay, and JSON record output out of scope. The CLI rejects--json recordbefore graph setup.Verification
cargo nextest run -p ros-z-recording -p ros-z-clicargo test --doc -p ros-z-recording -p ros-z-clicargo clippy -p ros-z-recording -p ros-z-cli --all-targets --locked -- -D warningsgit diff --check ddf687a4393935f18781a57ea7cfa001cfd2c557..HEAD