MAC-VO Dense Mapping mode & adaptation #247
Merged
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
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.
MAC-VO Dense Mapping mode & optimizer adaptation
What does this pull request do?
Upgrade the MAC-VO integration in AirStack to support more optimizers, publishing disparity image, etc.
How did you implement it?
Add the castack/MAC-VO-ROS2 fork to the AirStack repository as a submodule, bump the docker file for robot (rerun visualizer version bump).
Testing
How do you run the tests?
Docker compose up with fixed trajectory (8-figure and circle), visually inspect the MAC-VO estimated pose and ground truth pose.
What do the tests do?
Inspect whether the MAC-VO is having roughly the same trajectory as the drone's ground truth trajectory.
What are the expected results of the tests?
The MAC-VO estimated pose follows the ground truth pose roughly.
Did you update the docs (and where)?
Not yet.