-
-
Notifications
You must be signed in to change notification settings - Fork 374
Optional violation correction in velocity solver #116
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
sebcrozet
merged 18 commits into
dimforge:master
from
EmbarkStudios:corrective-velocity-solve
Mar 2, 2021
Merged
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
21247a1
Add restorative impulse in velocity solver
emilk 4162aed
Add params.velocity_based_erp_inv_dt() helper
emilk 3f26b46
Implement ball wide
emilk ede4f0f
cleanup
emilk d3f39a9
Implemented prismatic narrow. Needs testing and close review
emilk 48708d9
Implement revolute narrow
emilk 27366e2
Implement fixed wide
emilk 89de690
Implement prismatic wide
emilk 48afbac
Implement revolute wide
emilk b94cdfa
Implement ground wide
emilk 59796e4
fix
emilk 4ee09a8
Fix the narrow pismatic velocity constraint
emilk 9bbb081
fix narrow revolute velocity
emilk a082477
fix the revolute wide
emilk 4ef7b1c
Fix primatic wide
emilk 54eae9b
simplify prismatic limits
emilk f517601
Final cleanup
emilk 115bae1
fix the body-body revolute angle velocity erp
emilk 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
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
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
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.
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.
The names here are wildly inconsistent between files. It seems more common that
let anchor1 = position1 * self.local_anchor1;(e.g. inball_position_constraint.rs). Also sometimes the wordslocalandworldare part of the names (yay!) but sometimes not (😢 ). My approach is to try to make the smallest change possible to minimize conflicts.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.
It seems what is here called
anchor1is often calledr1.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.
You are right, the names are very inconsistent. I think the naming I would prefer are:
anchor1/anchor2to identify the world-space anchors.r1/r2to indentify the vector between the world-space anchor and the world-space center-of-mass.But there is no need to unify this in this PR.