Export SOCP

32 views
Skip to first unread message

zoharl

unread,
Jun 12, 2014, 2:08:38 PM6/12/14
to yal...@googlegroups.com

 What should I do in the assign and afterwards for x,t in solve_yalmip_dual_export() to return the same values as in solve_yalmip_dual()?

Johan Löfberg

unread,
Jun 12, 2014, 2:37:18 PM6/12/14
to yal...@googlegroups.com
Since export uses the same crappy setup as a standard call, it introduces dummy variables which must be skipped. They are placed last so that is easily done

assign(recover(recoverymodel.used_variables),res.sol.itr.xx(1:length(recoverymodel.used_variables)));


zoharl

unread,
Jun 12, 2014, 3:44:02 PM6/12/14
to yal...@googlegroups.com
This might get the primal variables, but I get NaN for the dual (x, t).

Johan Löfberg

unread,
Jun 12, 2014, 3:53:18 PM6/12/14
to yal...@googlegroups.com
That's probably going to be messy. Reverse engineering from callmosek and solvesdp leads to something along the lines of

D_struc = (sol.itr.suc-sol.itr.slc);
setduals
(Constraints,D_struc,internalmodel.K);

I think the easiest is to to just wait for my update (I'll probably make a new release tomorrow). Mosek solves the problem in solve_yalmip in 2s while the model you generate via solve_yalmip_dual_export takes 3.5

zoharl

unread,
Jun 12, 2014, 4:19:02 PM6/12/14
to yal...@googlegroups.com
Messy by it works.

Even with your update (not urgent), I still need a working export. Erling, for example, prefers running mosekopt.

zoharl

unread,
Jun 12, 2014, 5:48:05 PM6/12/14
to yal...@googlegroups.com
Right, but I won't need the duals...
Reply all
Reply to author
Forward
0 new messages