DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to open an existing .rrd recording in the Dalaran viewer with Dalaran

Replay an upstream .rrd recording on one timeline without converting it first.

Who it is forA robotics engineer who already has .rrd recordings from earlier runs and wants to review them in Dalaran.

The problemOld recordings are stored in a format that other tools cannot read in a synchronized way, so reviewing a run takes extra conversion work.

The outcomeThe recording opens directly in the viewer with entity paths, timelines, and data from all sensors visible together.

What you need first

  • Python with pip, or Rust with cargo, to install the Dalaran SDK or viewer
  • A terminal to run the dalaran command
  • An existing .rrd, .dlr, or MCAP recording, or a ROS 2 setup with rosbag2 files, for the replay use cases

Steps

  1. Run pip install dalaran-sdk to install the Python package that ships the viewer.
  2. Run dalaran recording.rrd in the folder that holds your recording, replacing recording.rrd with your file name.
  3. Scrub the timeline and check that the point clouds, camera frames, and transforms line up with each other.
  4. If you want a normalized copy, run dalaran convert as described in the README and open the new .dlr file.

Prompt for your agent

Using the Flaminis/Dalaran repository, install dalaran-sdk with pip and open <recording_path> with the dalaran command. Report whether the viewer opens the file and list the entity paths you can see. Verify that the timeline shows data from more than one sensor.

Caveat. The README says blueprints saved in upstream recordings may be ignored while the data still loads, so the saved layout may not appear.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page