ofps VS rerun

The overall experience building it was pretty great, with some surprises along the way. Somehow I managed to create a rustc ICE when compiling stable code, but it was very particular to set up, so I am not sure if one could even reproduce it. Rust was a great choice for its performance, type safety and available crates - nalgebra was a true lifesaver here, and integrating egui with wgpu was a really empowering experience. The project is not quite production quality, but it might come in handy for any future computer vision research. I called it OFPS, and you can find it on crates.io or my github.

Maybe the folks at Rerun [1] know something about it? I imagine at least some of their customers are Rust robotics shops.

[1] https://github.com/rerun-io/rerun

Full release notes: https://github.com/rerun-io/rerun/blob/main/CHANGELOG.md

No specific support for audio embeddings yet, though depending on you're specific use-case, you might be able to map your data to more generic primitives such a TimeSeriesScalar, LineStrips2D, BarChart, or Tensor.

We have an open issue for adding more support for audio-based projects -- if you have specific needs feel free to add a comment: https://github.com/rerun-io/rerun/issues/2852

Read the full changelog at https://github.com/rerun-io/rerun/releases/tag/0.6.0

https://github.com/rerun-io/rerun is such a great tool for creating interactive dashboards to look at real-time data. Curious if there are others looking for something like this and what the other use cases would be interesting. I have heard ideas like:

egui's lead author is using it for his computer vision startup.

To test the power draw, I conducted an unscientific experiment by circling the cursor over both a GTK4 app (GNOME Console) and an egui app (Rerun Viewer), while monitoring the CPU/GPU utilization and stabilized power draw with PowerTOP. The results indicated that when circling the cursor over the GTK4 app, the CPU/GPU usage was nearly negligible, and the stabilized power draw was around 13 W. In contrast, when circling the cursor over the egui app, the CPU/GPU usage was considerably higher, resulting in a stabilized power draw of around 21 W. This amounts to an increase of approximately 60%. Taking into account a power draw of around 10 W when doing nothing at all, the increase becomes roughly 260%. I also tried the same experiment with Iced, and while the increase was not as extreme, it still utilized resources when circling the cursor over a blank surface.