NVIDIAGameWorks / NVIDIAGameWorks/kaolin
trace failed when ray origin is inside of normalization range
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.2k
- Forks
- 629
- Avg merge
- 53m
- Merged PRs (30d)
- 2
Description
Hi, thanks for a great work.
I have a point cloud that is normalized to [-1, 1], as described in documentation, and use it to generate a spc. When I apply spc tracing from ray whose origin is inside of the normalization field, that is all three axis of the ray's origin is in [-1, 1], there will be no intersection returned; but if the ray origin is outside of normalization field(by reducing normalization field), tracing can found correct intersections.
Is there a solution to this problem? I'm using kaolin 0.9.1.
Contributor 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.
Research direction
Start by reproducing SPC tracing in Kaolin 0.9.1 with a point cloud normalized to [-1, 1] and a ray origin inside that range. Investigate the SPC tracing entry point and compare it with a ray whose origin is outside the normalization field. Done means tracing returns the expected intersections for rays originating inside the normalized field.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100