API to only match maps to existing database (no insertion) #98
Conversation
This file contains hidden or 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
saurabh1002
requested review from
benemer,
mehermvr and
tizianoGuadagnino
as code owners
Contributor
|
Hi Saurabh, thank you! Looking forward to your localization pipeline! |
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.
Feature request from #85, for use in localization mode, where one may not want to
pollutethe HBST database with features from the new query scan/map.@Omega3395, I am adding this bare-minimum API call to the C++ library and will not provide extensive API support for other functionalities right away. You can use this in your fork temporarily while developing the peripheral APIs for your application around it.
We are developing a separate pipeline for localization and tracking to expand its use case. We will make a complete API release for that work later.