Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

MoGe v2: Merged panorama output not in metric scale

Open
#97 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

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.

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!

Dominant language
JavaScript
Stars
3k
Forks
241
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/MoGe

All issues in microsoft/MoGe

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.