-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support extraction of rrd file content into folders/images/json #6011
Comments
Hello, I also am trying to extract data from an .rrd file, specifically RGB and other images. Is it true that the SDK API doesn't have this functionality yet? If so, what is the status of this user request? |
@nbkn865 There's ongoing work to expose APIs to access the datastore/loaded-rrd files which will land in the next release! Specifically for anything logged as images or a blob the viewer already has an option to save those when selected (look for "save blob"). |
0.19 supports now reading out the data store which allows to extract the data in code and store it into different files as needed.
that said, it's a bit open ended at this point since there's ofc no clear definition of "generate files from this rrd". I'd like to split this up into concrete files that should be either extractble from ui or code (: |
@Wumpf, thanks for replying. I indeed am using version 0.19 now with the Data API to extract data from Rerun files, and it works great. I do have a follow-up question about that, though, where I'm trying to extract images, for example:
I see that the images are stored like so in table images:
They're all 1-D lists, and there don't seem to be any image dimensions in the data, so how does the Rerun viewer process those 1-D lists back into an RGB array for display? I tried searching the documentation and couldn't find anything related to the above question. |
@nbkn865 since those are |
Currently the only one way to see data stored in rrd file is to open it in Visualizer.
It might be useful to be able to extract content into raw individual files.
The text was updated successfully, but these errors were encountered: