Allow to consider fixed poses when building edge set#7
Open
SimonTagne wants to merge 3 commits into
Open
Conversation
The rationale is that even if a pose is fixed, there might be connected edges leading to unfixed auxiliary parameters. Example use case: estimate camera calibration using static synthetic GCPs
For use e.g. with a good INS/GNSS solution for boresight calibration.
Takes either a map<timestamp, pose_vector> or a function returning the pose vector given a timestamp. This is useful to implement fixed trajectory (to avoid double interpolation)
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
1 participant
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.
The rationale is that even if a pose is fixed, there might be connected edges leading to unfixed auxiliary
parameters.
Example use case: estimate camera calibration using static synthetic GCPs