Hi there - CTO of Rerun here!<p>Rerun is still in beta, but we think it’s already good enough to be useful. It is built on wgpu, Apache Arrow, my own egui.rs library, and it also runs as Wasm in the browser.<p>I'm happy to answer any questions you may have!<p>PS: Thanks for the shoutout fdb!
here are some pictures, if like me you have no idea what this is:<p><a href="https://www.rerun.io/docs/getting-started/examples" rel="nofollow">https://www.rerun.io/docs/getting-started/examples</a>
I’m currently learning Open Drone Map and Nerfstudio. I feed aerial imagery to them, wait a long while, and then evaluate their output. Then I start over. I wonder if I could log intermediate results to Rerun and perhaps see faster how the work goes. Though I’d need to integrate Rerun logging into the pipelines somehow. In any case the demos on the site looked really nice.
The rr command is already somewhat well-known as a debugger from the rr-project[0]. Rerun is definitely inspiring, and good tools do that. Brett Victor is a great inspiration, I’m glad I saw that his work inspired rerun, that’s cool.<p>[0]: <a href="https://rr-project.org/" rel="nofollow">https://rr-project.org/</a>
Exciting! Looks very promising, especially for 3D stuff. I have one task coming up which is to filter somewhat noisy point clouds of body parts. Would you say Rerun is a good tool for that?
Congrats. I'm also a COSS founder and think this is a very smart step for a product like rerun. Feel free to ping me if you want to chat open-source more.
IMO relevant blurb:<p>> Rerun is an SDK for logging data like images, tensors and point clouds, paired with an app that builds visualizations around that data. We built Rerun for computer vision and robotics developers. It makes it easy to debug, explore and understand internal state and data with minimal code. The point is to make it much easier to build computer vision and robotics solutions for the real world.
I got confused by the usage of the term "log" (and the word gets used so much in many pages that I hit semantic satiation).<p>> When you log data to the Rerun SDK, Rerun handles everything needed to visualize it. It handles live streams from multiple processes across the network, as well as simple playback from recordings. That means taking care of serialization, transport, synchronizing streams, out-of-order data, and automatically constructing visualizations with sane defaults.<p>so is "record" / "recording" the right concept? When I think of logging I think of <i>exactly</i> lines in a text file (or maybe the "log" from a logging filesystem).