SHOT
executable (SHOT.exe
on Windows) installed on your system, you can call SHOT with the following syntax:--help
shows SHOT's syntax. --opt
which will create the file options.opt in the current directory. To use an option file pass the parameter --opt options.opt
. --osol
, which creates the file options.xml. To use this file pass the parameter --osol options.xml
.--convex
--debug
or --debug=<directory>
--debug
as it will be regarded as the debug directory name. If no directory is specified a directory will be created in the system temp folder.--mip=<cbc|cplex|gurobi>
--nlp=<ipopt|gams>
Subsolver.GAMS.NLP.Solver.
--tree=<single|multi>
--threads=<int>
--absgap=<float
1e-3
.--relgap=<float>
--timelimit=<float>
--osrl path/to/resultfile.osrl
as an argument when calling SHOT. --trc <filename.trc>
flag. If no filename is specified, a filename consisting of the problem file and the suffix .trc
is created in the current directory.--sol <filename.sol>
.Output.Console.LogLevel
, where values between 0 and 6 are allowed. Assuming that the default value 2 is used, first some basic information about the solver, including the current version is provided:Iteration
column shows the current iteration number, as well as the problem type solved (LP=linear programming).Time
column shows the wall clock time in seconds.Cuts
column, the number of linear constraints added in each iteration, as well as the total number of added constraints, are shown. Objective value
column, there are two values, the first corresponding to the solution of the LP problem and the other of the minimal value on the line between the previous solution point and the current. Output.Console.Iteration.Detail=0
. Iteration
column shows the iteration number and type. The type identifier consists of a part showing the problem type, and a part showing the solution status of the iteration. Time
column shows the wall clock time in seconds.Cuts
column, the number of linear constraints added in each iteration, as well as the total number of added constraints, are shown. Objective value - dual
column, the current lower bound (if minimizing) on the objective value is shown. Unless an asterisk *
is added to the value, this is a global lower bound. This value is provided by the underlying MIP solver.Objective value - primal
column, the current upper bound (if minimizing) on the objective value is shown. This value is the current best know solution to the problem and is given by either the MIP solver's solution pool or a primal heuristic, such as solving integer-fixed NLP problems.objective gap
column shows the absolute and relative gap between the lower and upper bounds in the previous columns. Current solution
provides some insight into the objective value and constraint fulfillment of the current iteration (either from the MIP or NLP solver). max.err
column, the nonlinear constraint index with the maximal error in the solution point is shown in addition to the error.--log <filename.log>
. It is possible to control the verbosity of the log file with the parameter Output.File.LogLevel
setting. Output.Debug
flag that, if activated, creates a folder SHOT_debug_*****
in the system temp folder. The destination folder can be specified with the parameter Output.Debug.Path.
or with--debug=<directory>
, where directory is where the debug files should be saved.originalproblem.txt
and reformulatedproblem.txt
which shows how SHOT interprets the given problem and how it is reformulated by SHOT. Also, the intermediate linearized problems solved by the MIP solver in each iteration is provided as LP*.lp
. --show-result
. --solver-options
flag. For example: --solver-options="Termination.TimeLimit=100.0"
will set a time limit of 100 seconds. --solver-options="Termination.TimeLimit=100.0 Termination.ObjectiveGap.Relative=0.01".
MINLP=SHOT
), either in the model itself or in the command line.gamsconfig.yaml
file. See the GAMS documentation for instructions.gamsconfig.yaml
in either the GAMS system directory or one of the other directories specified here. D:\Users\janeDoe\Downloads\gamslink\GamsShot-20.dll
, add the following contents to the yaml file:/path/to/libSHOTSolver.so
, add the following contents to the yaml file:problemfile.sol
. This file is written in the same directory as the nl-file.