Skip to content

[workspace] Upgrade osqp_internal,qdldl_internal to latest #22870

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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jwnimmer-tri
Copy link
Collaborator

@jwnimmer-tri jwnimmer-tri commented Apr 7, 2025

OSQP repaved a lot of their API in this release. See https://github.com/osqp/osqp/blob/master/docs/get_started/migration_guide.rst for details.

This PR is still a WIP for now, while I continue adapting to the changes.

Upgrade osqp_internal to latest release v1.0.0.
Upgrade qdldl_internal to latest release v0.1.8.


This change is Reviewable

@jwnimmer-tri
Copy link
Collaborator Author

+@hongkai-dai maybe you can help me out here?

OSQP has released a major upgrade to 1.0.0. (See link atop the pull request.)

I believe I've adapted the build system and API calls correctly now, but I there are still test failures. Several tests are testing to tolerance 1e-10 but OSQP results are around 1e-6. I wonder if possibly some OSQP defaults have changed? Or my code changes to the settings handling are wrong?

Do you have some time to investigate?

Upgrade osqp_internal to latest release 1.0.0.
Upgrade qdldl_internal to latest release 0.1.8.
@jwnimmer-tri
Copy link
Collaborator Author

I wonder if possibly some OSQP defaults have changed?

From an eyeball skim of the two OSQP releases, I don't see any defaults that have changed. There are a few new gc_... settings added in 1.0, but they don't seem to have any effect on at least the TestUnconstrainedQP case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low release notes: fix This pull request contains fixes (no new features) status: do not merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants