#20506: dual variables handling in SDP solver(s)
-------------------------+-------------------------------------------------
Reporter: | Owner:
dimpase | Status: needs_work
Type: | Milestone: sage-7.2
enhancement | Resolution:
Priority: major | Merged in:
Component: | Reviewers: Matthias Koeppe
numerical | Work issues:
Keywords: | Commit:
Authors: Dima | 604153bf8a00375192e0ff304f373101997fae66
Pasechnik | Stopgaps:
Report Upstream: N/A |
Branch: |
u/dimpase/sdpdual |
Dependencies: |
#19072 |
-------------------------+-------------------------------------------------
Comment (by dimpase):
OK, I just found that the problem is not Gentoo-only, it is CPU-related
(Xeon only?)
(is QCD-nzi3 Xeon, too?)
Reproducible on
{{{
Intel(R) Xeon(R) CPU X5660 @ 2.80GHz (UGent, Gentoo)
Intel(R) Xeon(R) CPU @ 2.30GHz (SMC, Ubuntu)
}}}
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`sol = solvers.sdp(c, Gs=G, hs=h)` changes after unrelated
(although in the same code-path) lines 13-27.
--
Ticket URL: <http://trac.sagemath.org/ticket/20506#comment:24>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
