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

Is there a graph design specifically for room scanning? #337

Closed
sirisian opened this issue Jan 3, 2019 · 6 comments
Closed

Is there a graph design specifically for room scanning? #337

sirisian opened this issue Jan 3, 2019 · 6 comments
Labels
stale for issues that becomes stale (no solution)

Comments

@sirisian
Copy link

sirisian commented Jan 3, 2019

I haven't seen anyone try this, so I took 2,000 4000x4000 high resolution images of a room. They all overlap by a decent amount capturing most of the details of the room. When I run Meshroom with the default settings up to the "Structure from Motion" step it seemingly picks only around 5 pictures and generates part of a wall.

The data set clearly has images that are adjacent to these 5 pictures. The quality of them are also really high with a lot of distinct features that should anchor the algorithm easily.

Is the default graph designed to aggressively remove "background" information and thinks the room is background data? Basically I need a graph that generates every point cloud point possible.

@natowi
Copy link
Member

natowi commented Jan 4, 2019

Read this wiki page

@sirisian
Copy link
Author

It took about 30 days to run feature matching, but I got the same result. In the structure matching it only uses 11 images of the 2,000. Interestingly it's the same 11 images as when it's ran naively. It seems to fixate on those 11 images ignoring other images that are next to those images. Sounds like a complicated bug maybe.

I'll wait a year and try again with new images. Maybe it'll be optimized by then to run with larger datasets.

@natowi
Copy link
Member

natowi commented Mar 8, 2019

I had similar problems with large datasets. There can be multiple causes for this issue. When I have some time, I will look into it. You could try to split your project dataset into parts using the Augment Reconstruction drop field and merge the reconstructed SFM nodes.

@natowi
Copy link
Member

natowi commented Jul 5, 2019

There will be a new version soon [#525], which might fix this problem.

@stale
Copy link

stale bot commented Nov 2, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale for issues that becomes stale (no solution) label Nov 2, 2019
@stale
Copy link

stale bot commented Nov 9, 2019

This issue is closed due to inactivity. Feel free to re-open if new information is available.

@stale stale bot closed this as completed Nov 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale for issues that becomes stale (no solution)
Projects
None yet
Development

No branches or pull requests

2 participants