-
Notifications
You must be signed in to change notification settings - Fork 42
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
Using tech:optionfile in mosek_options #231
Comments
What you mean are the solver native options: https://mp.ampl.com/features-guide.html#native-solver-options. This is not implemented for Mosek, I can add this, and hope we can release today or tomorrow. Any suggestions on clearer option names and help text to distinguish driver options vs native options? |
These were renamed from tech:param[:read/:write] Doc: AMPL vs native solver options
Currently native parameters can be controlled via exporting the model as LP/MPS/JTASK etc. and solving by Mosek command-line tool. Implemented and documented the following options for Mosek (and for Gurobi, which had them already, names were changed accordingly):
Among other solvers, only SCIP and GCG have |
Thanks! Using
and
but I get a |
easiest is to say optionnativewrite=opt_default.prom and modify that. Moses docs has no file format description. Basically it adds some header and footer. |
OK, now I see it. I can specify, say,
and then in the file
The MOSEK docs could describe this format, with a reference to one of the MOSEK parameter listing pages, maybe https://docs.mosek.com/latest/cmdtools/param-groups.html. |
Changed option text as follows (to appear in the next release):
|
A user would like to specify the value of the MSK_DPAR_INTPNT_TOL_PFEAS parameter for MOSEK. I thought that should be possible using this option:
I created a file
mosekopt.txt
containing this line,and I gave this command to AMPL before solving:
It appears that MOSEK found the file, but rejected the contents:
Can MSK_DPAR_INTPNT_TOL_PFEAS be specified using this option? And if so, how should it be written?
The text was updated successfully, but these errors were encountered: