Data collection framework update to Lyrical, Jazzy and Rolling
Data collection framework update to Lyrical, Jazzy and Rolling
The ROS2 community is updated on a significant release of the open-source Data Collection (DC) project. The tool now supports the Lyrical, Jazzy, and Rolling distributions, featuring new capabilities for uploading maps, camera frames, and videos to object storage via verified, resumable transfers. The update also includes deployment files for Compose, Quadlet, and Kubernetes, while dropping support for Fluent Bit in favor of Vector. The author notes that DC writes validated records into user-managed PostgreSQL databases rather than acting as a full data platform like Foxglove.
The author, a principal developer of the open-source Data Collection (DC) project for ROS2, announces support for Lyrical, Jazzy, and Rolling distributions, detailing architectural changes such as switching from Fluent Bit to Vector for log management and adding Kubernetes/Quadlet deployment files.
Source: ROS Discourse — Community updates · Read original article ↗
Article text · Original source · English
Hi ROS2 community!
3 years and ~150 commits since my last announcement, my open-source data collection project for ros2 is now able to run on lyrical, jazzy and rolling.
DC runs on the robot. It collects measurements, validates every record against a JSON schema, and ships them to your own PostgreSQL or object storage.
It was already released some years ago and here is what changed since recently:
- Jazzy, Lyrical and Rolling are now three maintained distros, each with its own container images on ghcr.
- A new uploader moves maps, camera frames and videos to object storage over verified, resumable transfers. Every file’s metadata becomes a queryable record.
- Deployment files ship for Compose, Quadlet and Kubernetes, and the docs are versioned per distro.
To do all of this, I had to drop Fluent bit support and use Vector instead. Integration became much easier.
What about Foxglove for example? It is a full data platform: live visualization, teleop, recording, searchable replay, collaboration. DC is narrower. It writes validated records into your own PostgreSQL, where a question like “what happened across the fleet since March” is a SQL query you can join with anything else you keep there.
I received many emails from professionals and researches over the years have shown me DC is in use. We are now at 119 stars on GitHub, so…I wonder: are you using it, how?
I wrote a bit about it on my blog DC 0.2: Data Collection for ROS 2 on Jazzy, Lyrical and Rolling — At the Edge
Thanks to all
What the source reports
Publisher-reported claims, with original evidence. These results have not been independently verified by RoboSignal.
Reported numbers
commits
≈150
View original evidence
Hi ROS2 community! 3 years and ~150 commits since my last announcement , my open-source data collection project for ros2 is now able to run on lyrical, jazzy and rolling. DC runs on the robot. It collects measurements, validates every record against a JSON schema, and ships them to your own PostgreSQL or object storage. It was already released some years ago and here is what changed since recently: Jazzy, Lyrical and
Open source S2stars
119
View original evidence
over the years have shown me DC is in use. We are now at 119 stars on GitHub, so…I wonder: are you using it, how? I wrote a bit about it on my blog DC 0.2: Data Collection for ROS 2 on Jazzy, Lyrical and Rolling — At the Edge Thanks to all
Open source S5years
3
View original evidence
Hi ROS2 community! 3 years and ~150 commits since my last announcement , my open-source data collection project for ros2 is now able to run on lyrical, jazzy and rolling. DC runs on the robot. It collects measurements, validates every record against a JSON schema, and ships them to your own PostgreSQL or object storage. It was already released some years ago and here is what changed since recently: Jazzy, Lyrical and
Open source S2
- paper: not_reported
- weights: not_reported
- dataset: not_reported
- code: not_reported
What remains unknown
Dataset licensing and commercial-use rights are not established here.
Source excerpts and review record
Automatically extracted; no manual editorial approval recorded.
Hi ROS2 community! 3 years and ~150 commits since my last announcement , my open-source data collection project for ros2 is now able to run on lyrical, jazzy and rolling. DC runs on the robot. It collects measurements, validates every record against a JSON schema, and ships them to your own PostgreSQL or object storage. It was already released some years ago and here is what changed since recently: Jazzy, Lyrical and
Open source S2
over the years have shown me DC is in use. We are now at 119 stars on GitHub, so…I wonder: are you using it, how? I wrote a bit about it on my blog DC 0.2: Data Collection for ROS 2 on Jazzy, Lyrical and Rolling — At the Edge Thanks to all
Open source S5
Data collection framework update to Lyrical, Jazzy and Rolling
Open source S1
Rolling are now three maintained distros, each with its own container images on ghcr. A new uploader moves maps, camera frames and videos to object storage over verified, resumable transfers. Every file’s metadata becomes a queryable record. Deployment files ship for Compose, Quadlet and Kubernetes, and the docs are versioned per distro. To do all of this, I had to drop Fluent bit support and use Vector instead. Int
Open source S3
egration became much easier. What about Foxglove for example? It is a full data platform: live visualization, teleop, recording, searchable replay, collaboration. DC is narrower. It writes validated records into your own PostgreSQL, where a question like “what happened across the fleet since March” is a SQL query you can join with anything else you keep there. I received many emails from professionals and researches
Open source S4
Implications for data suppliers
RoboSignal interpretation and collection questions, not statements of buyer demand.
- Confirm the required data type and collection setting with the buyer; this source does not establish a complete collection specification.
- Compare the reported units and scope before using these quantities in a budget. Recording hours, sensor-hours and trajectories are different measures.
- Validate demand and acceptance criteria with a buyer before scaling. Publication, popularity and a research result do not establish a purchase commitment.
Source：ROS Discourse — Community updates · discourse.openrobotics.org