-
Notifications
You must be signed in to change notification settings - Fork 136
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
Optimization is not solved because of "FATAL: syev failure, info = -5" #238
Comments
It looks like an issue with type sizes, do you know 1) what size integer SCS is compiled with and 2) what size integer your BLAS/LAPACK lib is compiled with? The two should match. |
If that's not it then feel free to send me the data dump following the instructions here: https://www.cvxgrp.org/scs/help/index.html |
Good morning, basically by using YALMIP the only parameters that I can set are: |
If you can edit the point at which yalmip calls SCS you can pass the arg in there. Otherwise I'm not sure what's going on. I think YALMIP is matlab only, right? If so SCS should be 64 bit ints and mwlapack/mwblas should be 64 bit ints too. The matlab tests appear to be passing (on ubuntu anyway): https://github.com/bodono/scs-matlab |
I am using scs-matlab,scs-3.2.3, octave-10.0.0 and YALMIP on Fedora39. I think this problem occurs because in src/cones.c : set_up_sd_cone_work_space(), n_max==0 is passed to dsyev.f as both the third argument, N, and the fifth argument, LDA. The in-line documentation for dsyev.f says that for argument 5, LDA>=max(1,N). I seem to have fixed this by initialising n_max to 1. |
Thanks @robertgj ! I created a pull request with that change. Does this look right? |
Yes, that is what I did. |
Thanks! |
Good evening, I am currently trying to solve an optimization problem with the solver scs (I am currently using it inside the YALMIP toolbox) but at the first iteration I get the following output:
I have tried to fix this issue by myself but I have not found anything related to this problem.
The text was updated successfully, but these errors were encountered: