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

Add option to include 'unknown' feature types in ConvertSfMFormat #584

Merged
merged 1 commit into from
Sep 15, 2019

Conversation

pramukta
Copy link
Contributor

@pramukta pramukta commented Aug 11, 2019

The new ability to output dense point clouds via AliceVision's meshing utility produces an Alembic file that seems to look identical to the normal SfM Alembic files except that the mvgPointCloud entries have their feature type set to unknown. However, this option isn't set as one of the parameters in the ConvertSfMFormat meshroom wrapper. As a result the node always strips out the points. Adding an "unknown" feature type option to the wrapper allows the dense cloud to be converted properly.

If there's a better way, or a different change needed to save dense clouds to non-Alembic formats let me know and can take a look. Thanks for all the great work on AliceVision, I'm a huge fan.

… conversion of dense point clouds via ConvertSfMFormat
@fabiencastan fabiencastan requested a review from yann-lty August 20, 2019 17:43
@simogasp simogasp added the type:pr pull request issue label Sep 9, 2019
@fabiencastan fabiencastan added this to the Meshroom 2019.3.0 milestone Sep 14, 2019
@fabiencastan
Copy link
Member

@pramukta,
Thanks for the PR, you're absolutely right.
And this is needed if we want to use the whiteImageList to select a subset of the input images for the texturing.

@fabiencastan fabiencastan merged commit 37a8d20 into alicevision:develop Sep 15, 2019
@fabiencastan
Copy link
Member

Sorry for the delay in merging that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:pr pull request issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants