-
Notifications
You must be signed in to change notification settings - Fork 3
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
Writing SDPA-formatted file using sdpa.jl #31
Comments
It's not stored in SOItoMOIBridge, it is stored in the solver.
The naming is based on the dual (D) of that webpage. |
Thanks for the reply. As far as printing the SDPA-formatted file is concerned, it seems possible to load the problem into the mock optimizer by defining
and then it is possible to load the problem using the This is of course a temporary measure but I will be sure to post any updates here. Once again thank you for the help! |
Note that you can print use the primal sdpa form for printing by combining this with AutomaticDualization.jl |
Hi @blegat ,
I am a summer student working with @ericphanson. Following up the discussion at jump-dev/SDPA.jl#19 about
SDPA.jl
not fully implementingSemidefiniteOptInterface
interface, we have been exploring the possibility of writing SDPA-formatted file by directing those missing functions, such asgetconstraintconstant
, to problem parameters already cached in theSemidefiniteOptInterface.SOItoMOIBridge()
object.However, looking at
SemidefiniteOptInterface.jl/src/sdpa.jl
Line 24 in c83bfe9
getconstraintconstant()
doesn't seem to be related to any one of the fields inSOItoMOIBridge
. Could you perhaps specify how fields inSOItoMOIBridge
parameterize the problem, and in particular which parameter shouldgetconstraintconstant()
refer to?On the other hand, comparing the code with the standard SDPA format (http://plato.asu.edu/ftp/sdpa_format.txt), it seems that this line should be
getobjectivecoefficient()
instead? Swappinggetconstraintconstant()
andgetobjectivecoefficient()
in the code would seem to make more sense but would you also kindly clarify this? Thanks.The text was updated successfully, but these errors were encountered: