Expose SCS contact point parameters#237
Draft
SproutSeeds wants to merge 1 commit into
Draft
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
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
SimulationConstructionSet2convenience methods to get and set contact-point based contact parametersContactPointBasedPhysicsEngineVerification
git show --check --format=short HEAD/home/codacli/tools/gradle-8.14.3/bin/gradle -p /home/codacli/code/ihmcrobotics/simulation-construction-set-2 :scs2-simulation-construction-set:compileJava --rerun-tasks --no-daemon/home/codacli/tools/gradle-8.14.3/bin/gradle -p /home/codacli/code/ihmcrobotics/simulation-construction-set-2 :scs2-simulation-construction-set:build --rerun-tasks --no-daemonFixes #161.
Coordination Note
I also ran a local-only stack sweep for this SCS2 draft set (
#232-#239) on top ofdevelopusingSproutSeeds:cody/scs2-draft-pr-stack-local-sweep-2026-05-08. The branches merged cleanly,git diff --check origin/develop..HEADpassed, and the affected module builds plus nested JavaFX/logger regression test projects passed on Umbra WSL. No separate PR is open for that integration branch; it is just evidence that the draft set composes.