OSQP fix after Drake (and OSQP) upgrade#383
Merged
Merged
Conversation
cuie23
approved these changes
Jul 2, 2025
cuie23
left a comment
There was a problem hiding this comment.
Reviewed 12 of 12 files at r1, all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @ebianchi)
ebianchi
added a commit
that referenced
this pull request
Jul 3, 2025
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.
Two changes for interacting with OSQP with upgraded Drake:
linsys_solveras it did with v0.6.2. Given all of our examples so far have only ever used the default solver, this PR removeslinsys_solveras an available setting in our solver yaml files. To keep this as an available setting would require either customizing OSQP or Drake, neither of which felt worth it given we aren't intending to use the feature.adaptive_rho_intervalto be provided as anint(i.e. it now throws an error if this is not the case). Our code previously mixed upintanddoubleinconsistently in a couple places, which eventually gave adoubleto OSQP. This parameter now is appropriately defined as anintconsistently.The jack sampling C3 example did not run before (due to an OSQP error) and now does.
This change is