Open
Description
Using ASL solvers, it was possible to specify an option string that had no space between option specifications. A user has provided this minimal example:
var x;
minimize Obj: x;
subject to Bound: x>=0;
option solver gurobiasl;
option gurobi_options 'outlev 0';
option gurobi_options $gurobi_options 'presolve 0';
solve;
option gurobi_options;
which gives a succesful Gurobi 10.0 run, even though it reports the option string to be 'outlev 0presolve 0'
. When run with the MP-based Gurobi version, however, this example rejects the option string:
option gurobi_options;
Gurobi 10.0.0: Invalid value "0presolve" for option "tech:outlev"
Unknown option or invalid key "0"
tech:outlev=0
exit value 1
<BREAK>
The user was concerned because his old scripts were breaking when he tried to use them with the MP version, and he had to change to, for example,
option gurobi_options 'outlev 0';
option gurobi_options $gurobi_options ' presolve 0';
Should we try to reproduce ASL's option processing (without spaces) in MP, or should we declare that it was an undocumented feature of ASL that we have chosen not to perpetuate?
Metadata
Metadata
Assignees
Labels
No labels