-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Fix compute_first_contact/air missing transitions as the sensor clock ages #7574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
7a0617d
Default first-transition tolerance to half the sensor update interval
AntoineRichard 6a613b6
Add first-transition tolerance regression tests
AntoineRichard f7a1a4c
Drop kernel-level first-transition tolerance tests
AntoineRichard 5ff9ce0
Refresh outdated buffers before first-transition queries
AntoineRichard File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
10 changes: 10 additions & 0 deletions
10
source/isaaclab/changelog.d/antoiner-first-contact-tolerance.minor.rst
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| Fixed | ||
| ^^^^^ | ||
|
|
||
| * Fixed :meth:`~isaaclab.sensors.contact_sensor.BaseContactSensor.compute_first_contact` and | ||
| :meth:`~isaaclab.sensors.contact_sensor.BaseContactSensor.compute_first_air` silently missing | ||
| touchdowns and lift-offs once the simulation had run for a few seconds (issue #7283). Their | ||
| ``abs_tol`` argument now defaults to ``None``, which resolves to half the sensor update interval | ||
| instead of a fixed ``1e-8``. The old value was around 100x smaller than the float32 rounding | ||
| error of the sensor clock, so most transitions were dropped. Callers that relied on the previous | ||
| behavior can pass ``abs_tol=1e-8`` explicitly. |
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
9 changes: 9 additions & 0 deletions
9
source/isaaclab_newton/changelog.d/antoiner-first-contact-tolerance.minor.rst
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| Fixed | ||
| ^^^^^ | ||
|
|
||
| * Fixed :meth:`compute_first_contact` and :meth:`compute_first_air` on the contact sensor silently | ||
| missing touchdowns and lift-offs once the simulation had run for a few seconds (issue #7283). | ||
| Their ``abs_tol`` argument now defaults to ``None``, which resolves to half the sensor update | ||
| interval instead of a fixed ``1e-8``. The old value was around 100x smaller than the float32 | ||
| rounding error of the sensor clock, so most transitions were dropped. Callers that relied on the | ||
| previous behavior can pass ``abs_tol=1e-8`` explicitly. |
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 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a simulation with a 0.005-second physics step reaches 65536 seconds, the next float32 timestamp increment is 0.0078125 seconds while the new default threshold is only 0.0075 seconds. The strict timer comparison therefore silently drops touchdowns and lift-offs again across all three backends.
Knowledge Base Used: Simulation, rendering, and sensors