Parameters with prefix misc. More...
Variables | |
constexpr Param< bool > | ALLOWSTRONGDUALREDS { "misc/allowstrongdualreds" } |
should strong dual reductions be allowed in propagation and presolving? | |
constexpr Param< bool > | ALLOWWEAKDUALREDS { "misc/allowweakdualreds" } |
should weak dual reductions be allowed in propagation and presolving? | |
constexpr Param< bool > | AVOIDMEMOUT { "misc/avoidmemout" } |
try to avoid running into memory limit by restricting plugins like heuristics? | |
constexpr Param< bool > | CALCINTEGRAL { "misc/calcintegral" } |
should SCIP calculate the primal dual integral value? | |
constexpr Param< bool > | CATCHCTRLC { "misc/catchctrlc" } |
should the CTRL-C interrupt be caught by SCIP? | |
constexpr Param< bool > | ESTIMEXTERNMEM { "misc/estimexternmem" } |
should the usage of external memory be estimated? | |
constexpr Param< bool > | FINITESOLUTIONSTORE { "misc/finitesolutionstore" } |
should SCIP try to remove infinite fixings from solutions copied to the solution store? | |
constexpr Param< bool > | IMPROVINGSOLS { "misc/improvingsols" } |
should only solutions be checked which improve the primal bound | |
constexpr Param< bool > | OUTPUTORIGSOL { "misc/outputorigsol" } |
should the best solution be transformed to the orignal space and be output in command line run? | |
constexpr Param< bool > | PRINTREASON { "misc/printreason" } |
should the reason be printed if a given start solution is infeasible | |
constexpr Param< double > | REFERENCEVALUE { "misc/referencevalue" } |
objective value for reference purposes | |
constexpr Param< bool > | RESETSTAT { "misc/resetstat" } |
should the statistics be reset if the transformed problem is freed (in case of a Benders' decomposition this parameter should be set to FALSE) | |
constexpr Param< bool > | SCALEOBJ { "misc/scaleobj" } |
should the objective function be scaled so that it is always integer? | |
constexpr Param< bool > | SHOWDIVINGSTATS { "misc/showdivingstats" } |
should detailed statistics for diving heuristics be shown? | |
constexpr Param< bool > | TRANSORIGSOLS { "misc/transorigsols" } |
should SCIP try to transfer original solutions to the transformed space (after presolving)? | |
constexpr Param< bool > | TRANSSOLSORIG { "misc/transsolsorig" } |
should SCIP try to transfer transformed solutions to the original space (after solving)? | |
constexpr Param< bool > | USECONSTABLE { "misc/useconstable" } |
should a hashtable be used to map from constraint names to constraints? | |
constexpr Param< bool > | USESMALLTABLES { "misc/usesmalltables" } |
should smaller hashtables be used? yields better performance for small problems with about 100 variables | |
constexpr Param< int > | USESYMMETRY { "misc/usesymmetry" } |
bitset describing used symmetry handling technique (0: off; 1: polyhedral (orbitopes and/or symresacks); 2: orbital fixing; 3: orbitopes and orbital fixing; 4: Schreier Sims cuts; 5: Schreier Sims cuts and orbitopes); 6: Schreier Sims cuts and orbital fixing; 7: Schreier Sims cuts, orbitopes, and orbital fixing, see type_symmetry.h. | |
constexpr Param< bool > | USEVARTABLE { "misc/usevartable" } |
should a hashtable be used to map from variable names to variables? | |
Parameters with prefix misc.
|
constexpr |
should strong dual reductions be allowed in propagation and presolving?
Definition at line 4426 of file parameters.hpp.
|
constexpr |
should weak dual reductions be allowed in propagation and presolving?
Definition at line 4428 of file parameters.hpp.
|
constexpr |
try to avoid running into memory limit by restricting plugins like heuristics?
Definition at line 4414 of file parameters.hpp.
|
constexpr |
should SCIP calculate the primal dual integral value?
Definition at line 4420 of file parameters.hpp.
|
constexpr |
should the CTRL-C interrupt be caught by SCIP?
Definition at line 4397 of file parameters.hpp.
|
constexpr |
should the usage of external memory be estimated?
Definition at line 4412 of file parameters.hpp.
|
constexpr |
should SCIP try to remove infinite fixings from solutions copied to the solution store?
Definition at line 4422 of file parameters.hpp.
|
constexpr |
should only solutions be checked which improve the primal bound
Definition at line 4408 of file parameters.hpp.
|
constexpr |
should the best solution be transformed to the orignal space and be output in command line run?
Definition at line 4424 of file parameters.hpp.
|
constexpr |
should the reason be printed if a given start solution is infeasible
Definition at line 4410 of file parameters.hpp.
|
constexpr |
objective value for reference purposes
Definition at line 4434 of file parameters.hpp.
|
constexpr |
should the statistics be reset if the transformed problem is freed (in case of a Benders' decomposition this parameter should be set to FALSE)
Definition at line 4406 of file parameters.hpp.
|
constexpr |
should the objective function be scaled so that it is always integer?
Definition at line 4430 of file parameters.hpp.
|
constexpr |
should detailed statistics for diving heuristics be shown?
Definition at line 4432 of file parameters.hpp.
|
constexpr |
should SCIP try to transfer original solutions to the transformed space (after presolving)?
Definition at line 4416 of file parameters.hpp.
|
constexpr |
should SCIP try to transfer transformed solutions to the original space (after solving)?
Definition at line 4418 of file parameters.hpp.
|
constexpr |
should a hashtable be used to map from constraint names to constraints?
Definition at line 4401 of file parameters.hpp.
|
constexpr |
should smaller hashtables be used? yields better performance for small problems with about 100 variables
Definition at line 4403 of file parameters.hpp.
|
constexpr |
bitset describing used symmetry handling technique (0: off; 1: polyhedral (orbitopes and/or symresacks); 2: orbital fixing; 3: orbitopes and orbital fixing; 4: Schreier Sims cuts; 5: Schreier Sims cuts and orbitopes); 6: Schreier Sims cuts and orbital fixing; 7: Schreier Sims cuts, orbitopes, and orbital fixing, see type_symmetry.h.
Definition at line 4439 of file parameters.hpp.
|
constexpr |
should a hashtable be used to map from variable names to variables?
Definition at line 4399 of file parameters.hpp.