Skip to content
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

Fix error in BieglerKKTSystem's solve for nontrivial scaling #71

Merged
merged 13 commits into from
Dec 6, 2023

Conversation

frapac
Copy link
Member

@frapac frapac commented Dec 4, 2023

cc @amontoison : that explains why we observed a large errors in the KKT benchmark.

Copy link

codecov bot commented Dec 4, 2023

Codecov Report

Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (e81bbbd) 76.76% compared to head (cde3740) 69.11%.

Files Patch % Lines
ext/api.jl 0.00% 8 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #71      +/-   ##
==========================================
- Coverage   76.76%   69.11%   -7.65%     
==========================================
  Files          22       28       +6     
  Lines        2152     2409     +257     
==========================================
+ Hits         1652     1665      +13     
- Misses        500      744     +244     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@michel2323 michel2323 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. So ] test now uses CUDA 12.1 for now.

@amontoison
Copy link
Member

Can we use CUDA 12.3 by default?

@michel2323
Copy link
Member

I should mention that ] test fails in CUSOLVERRF with

  The current version of CUDA is not supported.

@amontoison
Copy link
Member

Yes, we only support <= v11.8 or >= v12.3 for the version of CUDA in CUSOLVERREF.jl.

@frapac
Copy link
Member Author

frapac commented Dec 6, 2023

Can we use CUDA 12.3 by default?

Right now, I prefer to keep CUDA runtime 11.8 as the default, as this is the one we are using for our benchmarks. We should be able to replace cusolverRF by CUDSS soon, but I don't know if CUDA 12.3 is available on polaris, which could be a problem for us.

An alternative solution is to test both for CUDA 11.8 and 12.3 in Argos. But that could be addressed in a separate PR.

@frapac frapac merged commit 80d680d into master Dec 6, 2023
5 checks passed
@frapac frapac deleted the fp/fixkktsolve branch December 6, 2023 09:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants