Bug fix: Consult clock for fixedTimeCondition #1739
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
When doing clamped integration, we need to build fixed-time conditions. These conditions fire after a fixed time, computed in advance for performance. Previously, the fixed time condition reported it would be satisfied in a fixed amount of time, regardless of when it was asked. This is incorrect if the condition is queried at any time later than its creation; the condition appears to "retreat" in time as it's queried. Fix this bug by having the fixedTimeCondition consult the clock, so it can factor in the time elapsed since its creation.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 doing clamped integration, we need to build fixed-time conditions. These conditions fire after a fixed time, computed in advance for performance. Previously, the fixed time condition reported it would be satisfied in a fixed amount of time, regardless of when it was asked. This is incorrect if the condition is queried at any time later than its creation; the condition appears to "retreat" in time as it's queried.
Fix this bug by having the fixedTimeCondition consult the clock, so it can factor in the time elapsed since its creation.
Verification
@bradNASA discovered the faulty behavior, and he tested the change locally for me.
Documentation
N/A
Future work
N/A