recently, PlotJuggler reached an important milestone: support for ROS2!
This has been on my todo list for a long time. Now that it is done, it is time to look forward and think of what the future hold.I wonder if there is any hard-core users (or company) that want to join the discussion on what should be the most important features to add.
A new data structure with more semantic about the relationship between timeseries. This should open the door to new plugins that allow easy visualization of specific data (images, laser, diagnostic, etc.)
About the last point: this means that we might have something like an image plugin integrated into the visual space like this (photoshopped image):
I don’t have any requests but just wanted to say thanks for this amazing tool! PlotJuggler had probably saved me days of debugging time! Many thanks for all the hard work on it!
Huuuuuge fans and power users over here at Greenzie. Just sent this link over to our team slack to see if we can contribute to roadmap.
While I love the idea of the image plugin to visualize sensor data alongside charts and think it is rad, my gut says I love plot juggler for the plotting and charting and raw data/transforming capabilities. I’m also that guy who is always trying to remove features from our product and simplify (my team gets annoyed with me about this), so take that with a grain of salt. But I could totally see it.
My plan is to start adding these new features in a dev branch. This means that enthusiastic users may have an “early preview” of these new features, mostly to get an idea about usability, UX and “look and feel”.
Once all of these features are mature, I will probably release it to the wild, but considering that PlotJuggler is a side project, this will probably happen in autumn
I want to join the @msadowski. I love using PlotJuggler, such a great tool!
Few ideas of my own:
Ability to open rosbags in parallel to PX4 ulog, in the same plotjuggler session
Making the custom function a bit more user friendly when working with several timeseries - for example pitch_from_quaternion: maybe selecting the 4 relevant timeseries and apply the function on them.
Some TF support? Don’t have the exact requirement, but maybe visualizing data in the eye of a different TF origin?
Anyway, wanted to thank you for all your great work @facontidavide
The quaternion to RPY is an example of multiple-input, multiple-output data transformation that is very cumbersome to do right now and that I want to improve.
I would say that the biggest challenge is not the programming part but rather the UX part
But this is certainly one of the things I want to address.
