reduce the dimensions of the storage map #179
Open
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.
Hello,
I read the issue #162 and thought I can contribute to the reduction of storage map dimension. I mainly made changes in voxel_mapper and local_global_mapper files. As a result, the storage map is three times larger than the local map and the history voxel information is remained after re-initialization. I wish to get some feedback on what I did and see what else I can do to contribute to it. Also, since I'm a Penn student, I'd love to talk in person if it would be convenient for you. Below are images showing how the storage map is reduced.