Gurobi parameter setting 'outputflag' and 'OutputFlag': same names twice #1373
Unanswered
cchen000
asked this question in
Possible bug or missing functionality
Replies: 1 comment 1 reply
-
Yes, verbosity is controlled in yalmip viathe verbose option, which then alters solver specific settings (outputflag in the case of gurobi), and nonconvex is also controlled by yalmip |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Johan,
I am a Matlab and Gurobi user. Recently, I am learning how to control the output option by parameter settings. This is not a complex task, and I successfully made it by following the way how YALMIP does. Thanks for your project.
And I also find that some name typos (possibly) of optimize options in current project:
outputflag
andOutputFlag
.OutputFlag
.solvers/yalmip2gurobi.m
sets the fieldoutputflag
. So, this creates a new field very similar toOutputFlag
.So, are they the same? Two different fields both exist before calling gurobi function.
If so, from my side, these fields can be unified with a field
OutputFlag
as the official website does. The same goes for another fieldnonconvex
andNonConvex
. Until now, I do not find any numerical error related tooutputflag
andOutputFlag
. This is just a suggestion to regularize the code.--
cc
Beta Was this translation helpful? Give feedback.
All reactions