Remove 2d trajectory #29
Draft
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
haider8645
force-pushed
the
fix/remove_2d_trajectory
branch
from
b390bbd
to
a558a32
Compare
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.
Existing Users:
This PR removes the generation of Trajectory2D. The Trajectory2D was a workaround until the stepping or s-shaped bug in Trajectory3D was not solved. The Trajectory2D is not needed anymore but since many robots/software stacks and orogen component still uses Trajectory2D, therefore this should be merged only after all stacks are updated.
New Users:
New users should directly use the Trajectory3D.