Closed amacneil closed 2 years ago
What if instead we implemented a filter-friendly API in Python, and delivered a mcap_filter.py
wrapper for simple CLI jobs?
Here's my thought process:
frame_id
in a sensor msg or hardware_id
in /diagnostics
c. transformation: reassign all images to one topic, fix timestamps, etc.
ideally users can use tools from the same ecosystem for all of the above.I agree with the use cases you outlined. However, our CLI is very easy to install (brew install mcap
), and at the very least there should be an easy way to split out a single topic or time range (since we already have the ability to merge files from the CLI - seems weird if I can't do the reverse).
Landing more advanced filter features in the python library might be a better place to do it (and improving our python library in general is good). But honestly I think we should ignore more advanced filtering for now until there are requests for it - plenty of other things to work on.
This was completed in https://github.com/foxglove/mcap/pull/445
Ability to filter mcap files, similar to
rosbag filter
: