-
Notifications
You must be signed in to change notification settings - Fork 510
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
[FR] Add support for rendering Segmentation
primitives when the corresponding Sample
is a pointcloud/pcd file.
#4204
Comments
Thanks again @SergioRAgostinho ! |
Now you got me hyped. Out of curiosity do you have a "rough" (non-binding) time horizon when we might see this new format being integrated? |
That's awesome! Love to see it. Yeah we will still support For timeline, our initial version will be out in the next few months, depending on when the next few feature releases occur - it's very close to being in |
This is looking really cool. I'll definitely take it for a spin once it lands in The coderabbit.ai demo reviewing #3985 was also pretty amazing. |
Yeah we started trying it out recently, interesting results so far. And free for open source |
Proposal Summary
Add support for rendering
fiftyone.Segmentation
when the correspondingSample
is a pointcloud/pcd file. Currently, semantic segmentation needs to baked into the point cloud's RGB fields. This has two drawbacks:I've noticed
fiftyone.Detection
primitives are rendered correctly already in the 3D viewer, but the segmentation masks seem to be ignored.Motivation
What areas of FiftyOne does this feature affect?
fiftyone
Python libraryDetails
I have a proposal in term of user experience, ideally I would like to see segmentation masks being mapped to into the "Shade by" panel of the 3D viewer. The color assignment for points should follow same policy you're using for segmentation masks in 2D
Willingness to contribute
The FiftyOne Community welcomes contributions! Would you or another member of your organization be willing to contribute an implementation of this feature?
The text was updated successfully, but these errors were encountered: