Fix bug getting states starting between AOUPTARQ and AOMANUVR #199
Conversation
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
|
This is a critical bug so we should get it into 2021.2. |
jeanconn
approved these changes
Feb 2, 2021
This was referenced Feb 2, 2021
Merged
Merged
Closed
2 tasks
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.
Description
When the start time was between AOUPTARQ and AOMANUVR commands, this led to an exception because the code was trying to insert pseudo-commanding for that maneuver, but did not yet have a defined target attitude. This led to a failure in the maneuver generating code since it was being passed
Nonefor an attitude value.Testing
Fixes #198