Orientation and scale of objects in coords grid (output of geometry model)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- computer-vision, machine-learning
Research direction
Review the Geometry model and refinement-stage documentation or entry points referenced by the issue, if available. Determine whether training used canonical voxelizations or rotated and scaled smooth inputs, then document the confirmed behavior and its implications for object orientation and scale.
Written by the indexing model from the issue text.
Description
Hi, thanks for the great work.
Thanks for the great work, and for releasing the model. I had a question about the output representation of the object voxelization in the Geometry model.
In my tests, the Geometry model does not always seem to output the shape in a canonical pose aligned to fixed axes (e.g., with the longest axis along Z). Moreover, I evaluated the refinement stage model using voxelizations with arbitrary scales and rotations and, as long as the voxelizations are smooth, the output meshes are consistently very good.
I know you are not planning to release the training scripts, but could you please clarify whether this behavior was explicitly encouraged during training (for example, by providing the refinement stage with rotated/scaled smooth voxelizations as input), or whether you trained only on canonical voxelizations and this robustness is an inherent capability of the model?
Thanks again
- Dominant language
- Python
- Stars
- 7.6k
- Forks
- 897
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from facebookresearch/sam-3d-objects
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
V60Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
facebookresearch/sam-3d-objects#202 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in facebookresearch/sam-3d-objects
Similar issues
-
URLValidator ignores an explicit empty scheme allowlistPossibly taken @IlyaKhalafi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
tortoise/tortoise-orm#2393 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
frappe/frappe_docker#2046 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
complete_box_iou_loss / complete_box_iou: NaN gradients for zero-height boxes, NaN for point boxesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
AXI SMU SPEC
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
tenstorrent/tt-oca-harness#3556 ·
Maintainers usually reply within 1 day