A problem of adding a 3D asset to a trained Gaussian scene
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.7k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
When a single 3D asset's Gaussians are directly added to a trained Gaussian scene through rotation and translation, the rendered 3D asset does not display. It is known that the depth is correct. My plan is to find Gaussians with many intersections, reduce the opacity of the scene Gaussians in the intersecting parts, and increase the opacity of the 3D asset's Gaussians. Is this correct? Or other solutions?
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by reproducing the direct rotation-and-translation addition of a 3D asset to a trained Gaussian scene, then investigate the reported depth and visibility behavior. Done means the added asset renders correctly and the chosen opacity or compositing approach is validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-graphics, machine-learning
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100