Edge cases where coordinates are same #9
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
If coordinate is same, then velocity must be zero as well.
This will be added as a dependency to the multirotor library.
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.
In this pull request, I made the following changes.
Edge cases where coordinates are the same. For example, if a trajectory is being planned for [0,1] to [0,3], then zero velocity/acceleration are needed along the first axis.
Verbosity of log messages. I changed default logging level from
DEBUGtoWARNINGto reduce amount of stdout messages. The users can manually change logger verbosity to print debug messages when needed.Bumped version number to 1.0.2 to reflect these patches.