PlotJuggler VS ros-noetic

If you use ROS, you will have similar facilities with ROS bags and e.g. PlotJuggler. ROS bags are not as convenient to manipulate as MessagePack/JSON dictionaries, although they hold similar data, because the ecosystem is smaller (i.e. less people manipulating them and developing tools to manipulate them more efficiently).

I can also recommend using Plotjuggler instead: https://github.com/facontidavide/PlotJuggler

This is great!! Also see the open source plot juggler (not mine) https://www.plotjuggler.io/

If you want to visualize data on the plot I would recommend using PlotJuggler. Great piece of visualization tool working with ROS. It is available as snap package, so it will be easy to set up. Here's the link with all the details: https://github.com/facontidavide/PlotJuggler

For work sometimes I will use a program called PlotJuggler, where there is a splash screen but it is just a couple seconds of displaying a random, plotting related meme.

Based on your comment, I assume you mean a GUI program for interactive exploration and manipulation, rather than a library?

This was posted on HN a few months ago and came to mind: https://github.com/facontidavide/PlotJuggler

In a past job, we used the commercial app nCode Glyphworks for graphical / interactive signal processing from field tests with hundreds of sensors.

Check out https://robostack.github.io/. It has distributions of ROS which can be installed on a PinePhone.

Robostack (https://robostack.github.io)

Take a look at robo stack - they distribute ROS through condaforge - https://robostack.github.io/

One could use https://robostack.github.io/ to install ROS tools inside a python environment isolated from the rest of the machine

The Robostack project is packaging ROS core distributions and many third-party ROS packages built against existing conda-forge dependencies as much as possible to make things more convenient for roboticists. That's mostly how I've been using ROS for well over a year now. The virtual env isolation is great, because otherwise robotics code tends to get tied to a specific Linux OS version. Disk space is cheap, I'd rather have the flexibility and a few 4GB environments lying around.