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

[question] Draft meshing performance #1314

Closed
natowi opened this issue Mar 2, 2021 · 3 comments
Closed

[question] Draft meshing performance #1314

natowi opened this issue Mar 2, 2021 · 3 comments
Labels
stale for issues that becomes stale (no solution) type:question

Comments

@natowi
Copy link
Member

natowi commented Mar 2, 2021

Describe the problem
I noticed considerable improvements of the draft meshing in v2021 compared to v2020 (fewer holes, more complete/robust reconstructions): see end of https://github.com/alicevision/meshroom/wiki/Draft-Meshing

The default draft meshing works fine with the monstree 3img dataset and one can see the improvements:

draft21a

With akaze enabled in all nodes I only get a tiny blob with 162 triangles. I had the same problem in v2020.1, so I disabled akaze in the SfM node to get a far more complete node when using draft meshing. With the 2021 release selecting akaze in featureextraction will also enable akaze in imagematching and structurefrommotion. This is good and intended, but now I can not deselect akaze in the structurefrommotion node to work around this strange behaviour.

Edit: it is possible to deselect the DescriberType by disconnecting it in the node :D

@natowi
Copy link
Member Author

natowi commented Mar 27, 2021

@stale
Copy link

stale bot commented Aug 18, 2021

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 Aug 18, 2021
@stale
Copy link

stale bot commented Sep 6, 2021

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

@stale stale bot closed this as completed Sep 6, 2021
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) type:question
Projects
None yet
Development

No branches or pull requests

1 participant