Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to determine winsize (key images) and refid (neighbors) in mast3r_sfm? #56

Open
Reed-yang opened this issue Oct 6, 2024 · 2 comments

Comments

@Reed-yang
Copy link

I want to commend the use of a Retrieval model to connect views in mast3r_sfm—it's a very smart approach and has worked well in my current image testing.

However, I’ve noticed that in the demo code, the winsize (key images) and refid (neighbors) parameters are fixed and don’t scale with the number of images. For example, even when processing several hundred images (in large-scale scene image sequences), these parameters remain capped at 20 and 10, respectively, which is the same as when working with just a few dozen images.

Here are my questions:

  • For large-scale scenes, do these parameters need to be adjusted manually? Based on your experience, what would be the best way to calculate winsize and refid (depending on num_files) to balance both the final quality and the number of image_pairs effectively?
@michaelyuancb
Copy link

@Reed-yang Have you ever checkout the dense pointclouds quality ? I found the pointclouds split into "patchs" in my setting. I wonder if this is normal phenomenon for Master-Sfm winsize strategy ?

@Reed-yang
Copy link
Author

@michaelyuancb split into "patchs" may have relations with the anchor depth mentioned in the paper, by default, the the num of anchors should be H x W / 64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants