MoGe v2: Merged panorama output not in metric scale
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3k
- Forks
- 234
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I’ve noticed that when using MoGe v2 with panoramas (infer_panorama script), the final merged point cloud is almost identical to v1 and not in metric scale, even though v2 should produce metric outputs.
From what I can tell, this seems to be due to the merging process of the per-view outputs in the panorama pipeline.
Is it possible to obtain a metric result with panoramas using v2, while still preserving the accurate merging?
Thanks!
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
Start with the infer_panorama.py script and trace how the per-view outputs are merged into the final point cloud. Compare the panorama result produced by MoGe v2 with the expected metric output while preserving accurate merging; done means the merged panorama is in metric scale rather than behaving like v1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100