-
-
Notifications
You must be signed in to change notification settings - Fork 568
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
dual variables handling in SDP solver(s) #20506
Comments
comment:1
the dependence on #19072 may be ignored for all practical purposes. |
comment:2
I'm a bit puzzled why you would want doctests for the particular floating point noise that you get from this version of the solver. Seems like extra work every time the package is upgraded? |
comment:3
Replying to @mkoeppe:
I tried to round things using '...' etc as much as possible. I can in principle go
by
Eventually we should think how to adapt your testing framework to SDP. |
comment:4
How about
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:6
Replying to @mkoeppe:
good idea, fixed! |
comment:7
There are more places in the file that could use the #tol. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:9
Replying to @mkoeppe:
I did add it all over the place, in fact.
OK, see the last commit. |
comment:10
I mean these ones in cvxopt_sdp_backend.
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
The patchbot complains about decreased coverage; probably |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:14
Replying to @mkoeppe:
thanks; hopefully fixed now. |
comment:15
Looking good. |
Reviewer: Matthias Koeppe |
comment:16
|
comment:23
That explains!
This is sage-on-gentoo. Does |
comment:24
OK, I just found that the problem is not Gentoo-only, it is CPU-related (Xeon only?) Reproducible on
Will now see if this is Atlas-related (by trying "dumb" Atlas). But the bug is very unpleasant; in the attached script the result of running |
comment:25
Not an actual Xeon but I am not completely sure
Also, sage-on-gentoo above uses openblas... |
comment:26
On |
comment:27
I will build a vanilla 7.2.beta6 and see what happens. |
comment:28
the failure with xx.sage attachment is also reproducible on OSX (Core2Duo CPU), although it's slightly different (the 2nd and 3rd calls to the solver return "infeasible" rather than bail out with zero division). So this looks like an genuine bug in CVXOPT interface, or in CVXOPT itself, or both. Somehow it seems to retain too much state. I wish we had an OSX patchbot... |
comment:29
For info, vanilla sage same machine
If you think the problem is upstream, they are quite responsive in chasing issue. |
comment:31
Replying to @dimpase:
OSX is fixed by the latest commit. But it does not fix the Gentoo Xeon case... Does it fix sage-on-gentoo with openblas case? |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:33
I will need to put that in a patch and rebuild since it is |
comment:34
No changes for sage-on-gentoo when including the last two commits (and only those not the rest of the branch). |
comment:35
No impact on vanilla sage on the same machine. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:38
I removed the "unstable" example. Now sage4 bot (and the rest) should be happy. |
Changed branch from u/dimpase/sdpdual to |
Changed commit from |
comment:41
Replying to @sagetrac-git:
this is traced down to wrongly set
Will be fixed on #21778 |
At present only primal variables are made available in
SemidefiniteProgram()
, although the dual variables are typically also provided by backends. This ticket added access to dual (and slack) variables.Depends on #19072
CC: @sagetrac-srobik @mkoeppe @kiwifb
Component: numerical
Author: Dima Pasechnik
Branch:
572b630
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/20506
The text was updated successfully, but these errors were encountered: