3D TSDF Mesh Export in AssetsWriter #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 11 commits
November 12, 2021 18:14
bhirschel
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request is associated with Task #2967. It restructures the TSDF meshing capabilities so that non ROS related parts of the code are transferred to the main cartographer project. Additionally provides an TSDF meshing points processor that can be enabled in the assets writer post processing pipeline. It constructs a TSDF grid from bag files and subsequently creates a mesh surface representation in binary ply format.
This pull request enables PCL by default. It is therefore necessary to perform a clean build.