microsoft / microsoft/VITRA

Inquiry for the new focal length determined for undistortion

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

Nobody has claimed this yet.

Dominant language
Python
Stars
502
Forks
34
PR merge metrics
No merged PRs in 30d

Description

Hi team:
First, thank you for this excellent data work — the VITRA-1M pipeline is a valuable contribution, and the ego-video → hand-VLA processing is very well thought out.
I have a question about the undistortion step. For videos that require undistortion, I'm trying to understand how the new focal length in new_K is chosen. It seems:

  • For the Ego-Exo4D data, it looks like a fixed value is used.
  • For Ego4D, however, the new focal length does not appear to be a fixed value — it seems to vary per video.

Could you clarify how the new focal length is determined for the Ego4D and Ego-Exo4d?

Thanks in advance!

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by locating the undistortion pipeline and the code that constructs new_K for Ego4D and Ego-Exo4D videos. Trace how each dataset's replacement focal length is selected, then document whether it is fixed or video-dependent and what inputs determine it. Done means the focal-length behavior for both datasets is clearly explained.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
computer-vision
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.