Fixed condition under which trajectory linkage reports are generated. #828
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
… as long as linkages are present in the trajectory.
naylor-b
approved these changes
Sep 27, 2022
Kenneth-T-Moore
approved these changes
Sep 27, 2022
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.
Summary
Changes the condition under which a linkage report is generated from "trajectory has more than one phase" to "trajectory contains linkages". This was causing a reports to not be generated in cases where a single-phase trajectory uses linkages to couple the various initial/final conditions of the phase together, such as in the racecar example.
Related Issues
Backwards incompatibilities
None
New Dependencies
None