You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear friends,
I am formulating my problem as an MISDP in Java (it must be in Java because of the preliminary work). I want to solve it using SCIP-SDP. As described in your readme file, SCIP-SDP can be incorporated into other codes. Does it mean that I can construct MISDP problems using your Java API, JSCIPOpt? If so, can you provide any example code? (I know there are example cbf files in the SCIP-SDP repository, and there are example Java codes for non-SDP problems in the JSCIPOpt repository, but I am looking for example Java codes to construct MISDP problems directly). Thank you!
The text was updated successfully, but these errors were encountered:
@pfetsch Thanks for your reply! So, I have a further question. Do you think this is a good way to construct and solve MISDPs using Java? : (1) write an SDP using the Java interface of Mosek (which I know is well-supported), (2) write the SDP problem to a .cbf file using Mosek, (3) directly modify the .cbf file to add in integrality constraints on certain variables, (4) call SCIP-SDP to solve the new .cbf file.
Thank you for confirming. That is what I am concerning. I need to solve millions of MISDPs, file IO overhead would be a problem. Anyway, I will try small demos first in this way.
Dear friends,
I am formulating my problem as an MISDP in Java (it must be in Java because of the preliminary work). I want to solve it using SCIP-SDP. As described in your readme file, SCIP-SDP can be incorporated into other codes. Does it mean that I can construct MISDP problems using your Java API, JSCIPOpt? If so, can you provide any example code? (I know there are example cbf files in the SCIP-SDP repository, and there are example Java codes for non-SDP problems in the JSCIPOpt repository, but I am looking for example Java codes to construct MISDP problems directly). Thank you!
The text was updated successfully, but these errors were encountered: