-
Notifications
You must be signed in to change notification settings - Fork 388
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
Make Pinhole
archetype in Rust eager serialized
#8789
Conversation
…ty methods to them
// TODO(andreas): Give this another pass and think about how we can remove this. | ||
// Being disconnected from the blueprint & fallbacks makes this a weird snowflake with unexpected behavior. | ||
// Also, figure out how this might actually relate to the transform cache. | ||
pub fn query_pinhole_and_view_coordinates_from_store_without_blueprint( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is essentially what query_pinhole_legacy
used to do. But with an EVEN scarier name!
Web viewer failed to build. | Result | Commit | Link | Manifest | Note: This comment is updated whenever you push a commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was a big surgery
### Related * sister PR to.. * #8789 * #8785 * #8793 * missed piece of #7245 ### What Ports the Tensor archetype in rust to the new eager serialized interface. Unfortunately this meant I had to remove some direct access methods of the underlying tensor data. Curiously, this didn't affect any of our test/snippet/example code. While doing so I also fixed some wording issues in the (very similar) C++ implementation of `with_dim_names`
Related
Box
/AssetVideo
/ViewCoordinates
/Asset3D
eager serialized in Rust #8785Image
&Mesh3D
archetypes in Rust eager serialized #8793What
Deprecates a bunch of methods on
Pinhole
, all of them still functional though through ad-hoc deserialization utilities.In the Viewer (concrete,
re_spatial_view
) we don't use any of that and have now a new purpose-built type - I considered using the generated (attr.rust.archetype_native
) type, but a custom built made a lot more sense for untangling the mess of adhoc queries we have around Pinhole. It might not look like it but the aspiration here was to not change how things work by much while having things better decoupled & cleaner.Bonus: the odd resolution oracle we already used is now visible on the pinhole visualizers's ui