Add support for compressed trajectories #268
Merged
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
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.
The High Level Commander supports two formats for trajectory data: Poly4D and Compressed. The Poly4d format is already supported but the Compressed format is not and that is what this pull request is intended to fix.
The main change is the introduction of the CompressedStart and CompressedSegment classes in the trajectory memory mapping. These classes allows the user to define compressed trajectories using bezier curves.
The default behavior is unchanged and if nothing else is stated, the expected trajectory format is still Poly4D.
An example for a compressed figure 8 has been added and other examples have been updated.