Google OR-Tools v9.9
a fast and portable software suite for combinatorial optimization
|
Static Public Member Functions | |
static final com.google.protobuf.Descriptors.Descriptor | getDescriptor () |
Protected Member Functions | |
com.google.protobuf.GeneratedMessageV3.FieldAccessorTable | internalGetFieldAccessorTable () |
Contains the definitions for all the sat algorithm parameters and their default values. NEXT TAG: 280
Protobuf type operations_research.sat.SatParameters
Definition at line 13476 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addAllExtraSubsolvers | ( | java.lang.Iterable< java.lang.String > | values | ) |
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;
values | The extraSubsolvers to add. |
Definition at line 23080 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addAllIgnoreSubsolvers | ( | java.lang.Iterable< java.lang.String > | values | ) |
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem.
repeated string ignore_subsolvers = 209;
values | The ignoreSubsolvers to add. |
Definition at line 23235 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addAllRestartAlgorithms | ( | java.lang.Iterable<? extends com.google.ortools.sat.SatParameters.RestartAlgorithm > | values | ) |
The restart strategies will change each time the strategy_counter is increased. The current strategy will simply be the one at index strategy_counter modulo the number of strategy. Note that if this list includes a NO_RESTART, nothing will change when it is reached because the strategy_counter will only increment after a restart. The idea of switching of search strategy tailored for SAT/UNSAT comes from Chanseok Oh with his COMiniSatPS solver, see http://cs.nyu.edu/~chanseok/. But more generally, it seems REALLY beneficial to try different strategy.
repeated .operations_research.sat.SatParameters.RestartAlgorithm restart_algorithms = 61;
values | The restartAlgorithms to add. |
Definition at line 18706 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addAllSubsolverParams | ( | java.lang.Iterable<? extends com.google.ortools.sat.SatParameters > | values | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23497 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addAllSubsolvers | ( | java.lang.Iterable< java.lang.String > | values | ) |
In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters. This field indicates the names of the parameters that are used in multithread. See cp_model_search.cc to see a list of the names and the default value (if left empty) that looks like: - default_lp (linearization_level:1) - fixed (only if fixed search specified or scheduling) - no_lp (linearization_level:0) - max_lp (linearization_level:2) - pseudo_costs (only if objective, change search heuristic) - reduced_costs (only if objective, change search heuristic) - quick_restart (kind of probing) - quick_restart_no_lp (kind of probing with linearization_level:0) - lb_tree_search (to improve lower bound, MIP like tree search) - probing (continuous probing and shaving) Also, note that some set of parameters will be ignored if they do not make sense. For instance if there is no objective, pseudo_cost or reduced_cost search will be ignored. Core based search will only work if the objective has many terms. If there is no fixed strategy fixed will be ignored. And so on. The order is important, as only the first usable "num_workers - min_num_lns_workers" subsolvers will be scheduled. You can see in the log which one are selected for a given run. All the others will be LNS if there is an objective, or randomized SAT search for pure satisfiability problems.
repeated string subsolvers = 207;
values | The subsolvers to add. |
Definition at line 22875 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addExtraSubsolvers | ( | java.lang.String | value | ) |
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;
value | The extraSubsolvers to add. |
Definition at line 23061 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addExtraSubsolversBytes | ( | com.google.protobuf.ByteString | value | ) |
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;
value | The bytes of the extraSubsolvers to add. |
Definition at line 23115 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addIgnoreSubsolvers | ( | java.lang.String | value | ) |
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem.
repeated string ignore_subsolvers = 209;
value | The ignoreSubsolvers to add. |
Definition at line 23216 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addIgnoreSubsolversBytes | ( | com.google.protobuf.ByteString | value | ) |
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem.
repeated string ignore_subsolvers = 209;
value | The bytes of the ignoreSubsolvers to add. |
Definition at line 23270 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addRepeatedField | ( | com.google.protobuf.Descriptors.FieldDescriptor | field, |
java.lang.Object | value ) |
Definition at line 14826 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addRestartAlgorithms | ( | com.google.ortools.sat.SatParameters.RestartAlgorithm | value | ) |
The restart strategies will change each time the strategy_counter is increased. The current strategy will simply be the one at index strategy_counter modulo the number of strategy. Note that if this list includes a NO_RESTART, nothing will change when it is reached because the strategy_counter will only increment after a restart. The idea of switching of search strategy tailored for SAT/UNSAT comes from Chanseok Oh with his COMiniSatPS solver, see http://cs.nyu.edu/~chanseok/. But more generally, it seems REALLY beneficial to try different strategy.
repeated .operations_research.sat.SatParameters.RestartAlgorithm restart_algorithms = 61;
value | The restartAlgorithms to add. |
Definition at line 18680 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addSubsolverParams | ( | com.google.ortools.sat.SatParameters | value | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23404 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addSubsolverParams | ( | com.google.ortools.sat.SatParameters.Builder | builderForValue | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23453 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addSubsolverParams | ( | int | index, |
com.google.ortools.sat.SatParameters | value ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23428 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addSubsolverParams | ( | int | index, |
com.google.ortools.sat.SatParameters.Builder | builderForValue ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23475 of file SatParameters.java.
com.google.ortools.sat.SatParameters.Builder com.google.ortools.sat.SatParameters.Builder.addSubsolverParamsBuilder | ( | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23614 of file SatParameters.java.
com.google.ortools.sat.SatParameters.Builder com.google.ortools.sat.SatParameters.Builder.addSubsolverParamsBuilder | ( | int | index | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23629 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addSubsolvers | ( | java.lang.String | value | ) |
In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters. This field indicates the names of the parameters that are used in multithread. See cp_model_search.cc to see a list of the names and the default value (if left empty) that looks like: - default_lp (linearization_level:1) - fixed (only if fixed search specified or scheduling) - no_lp (linearization_level:0) - max_lp (linearization_level:2) - pseudo_costs (only if objective, change search heuristic) - reduced_costs (only if objective, change search heuristic) - quick_restart (kind of probing) - quick_restart_no_lp (kind of probing with linearization_level:0) - lb_tree_search (to improve lower bound, MIP like tree search) - probing (continuous probing and shaving) Also, note that some set of parameters will be ignored if they do not make sense. For instance if there is no objective, pseudo_cost or reduced_cost search will be ignored. Core based search will only work if the objective has many terms. If there is no fixed strategy fixed will be ignored. And so on. The order is important, as only the first usable "num_workers - min_num_lns_workers" subsolvers will be scheduled. You can see in the log which one are selected for a given run. All the others will be LNS if there is an objective, or randomized SAT search for pure satisfiability problems.
repeated string subsolvers = 207;
value | The subsolvers to add. |
Definition at line 22831 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.addSubsolversBytes | ( | com.google.protobuf.ByteString | value | ) |
In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters. This field indicates the names of the parameters that are used in multithread. See cp_model_search.cc to see a list of the names and the default value (if left empty) that looks like: - default_lp (linearization_level:1) - fixed (only if fixed search specified or scheduling) - no_lp (linearization_level:0) - max_lp (linearization_level:2) - pseudo_costs (only if objective, change search heuristic) - reduced_costs (only if objective, change search heuristic) - quick_restart (kind of probing) - quick_restart_no_lp (kind of probing with linearization_level:0) - lb_tree_search (to improve lower bound, MIP like tree search) - probing (continuous probing and shaving) Also, note that some set of parameters will be ignored if they do not make sense. For instance if there is no objective, pseudo_cost or reduced_cost search will be ignored. Core based search will only work if the objective has many terms. If there is no fixed strategy fixed will be ignored. And so on. The order is important, as only the first usable "num_workers - min_num_lns_workers" subsolvers will be scheduled. You can see in the log which one are selected for a given run. All the others will be LNS if there is an objective, or randomized SAT search for pure satisfiability problems.
repeated string subsolvers = 207;
value | The bytes of the subsolvers to add. |
Definition at line 22960 of file SatParameters.java.
com.google.ortools.sat.SatParameters com.google.ortools.sat.SatParameters.Builder.build | ( | ) |
Definition at line 13772 of file SatParameters.java.
com.google.ortools.sat.SatParameters com.google.ortools.sat.SatParameters.Builder.buildPartial | ( | ) |
Definition at line 13781 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clear | ( | ) |
Definition at line 13504 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAbsoluteGapLimit | ( | ) |
Stop the search when the gap between the best feasible objective (O) and our best objective bound (B) is smaller than a limit. The exact definition is: - Absolute: abs(O - B) - Relative: abs(O - B) / max(1, abs(O)). Important: The relative gap depends on the objective offset! If you artificially shift the objective, you will get widely different value of the relative gap. Note that if the gap is reached, the search status will be OPTIMAL. But one can check the best objective bound to see the actual gap. If the objective is integer, then any absolute gap < 1 will lead to a true optimal. If the objective is floating point, a gap of zero make little sense so is is why we use a non-zero default value. At the end of the search, we will display a warning if OPTIMAL is reported yet the gap is greater than this absolute gap.
optional double absolute_gap_limit = 159 [default = 0.0001];
Definition at line 19699 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAddCgCuts | ( | ) |
Whether we generate and add Chvatal-Gomory cuts to the LP at root node. Note that for now, this is not heavily tuned.
optional bool add_cg_cuts = 117 [default = true];
Definition at line 30267 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAddCliqueCuts | ( | ) |
Whether we generate clique cuts from the binary implication graph. Note that as the search goes on, this graph will contains new binary clauses learned by the SAT engine.
optional bool add_clique_cuts = 172 [default = true];
Definition at line 30451 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAddLinMaxCuts | ( | ) |
For the lin max constraints, generates the cuts described in "Strong mixed-integer programming formulations for trained neural networks" by Ross Anderson et. (https://arxiv.org/pdf/1811.01988.pdf)
optional bool add_lin_max_cuts = 152 [default = true];
Definition at line 30639 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAddLpConstraintsLazily | ( | ) |
If true, we start by an empty LP, and only add constraints not satisfied by the current LP solution batch by batch. A constraint that is only added like this is known as a "lazy" constraint in the literature, except that we currently consider all constraints as lazy here.
optional bool add_lp_constraints_lazily = 112 [default = true];
Definition at line 30791 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAddMirCuts | ( | ) |
Whether we generate MIR cuts at root node. Note that for now, this is not heavily tuned.
optional bool add_mir_cuts = 120 [default = true];
Definition at line 30327 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAddObjectiveCut | ( | ) |
When the LP objective is fractional, do we add the cut that forces the linear objective expression to be greater or equal to this fractional value rounded up? We can always do that since our objective is integer, and combined with MIR heuristic to reduce the coefficient of such cut, it can help.
optional bool add_objective_cut = 197 [default = false];
Definition at line 30207 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAddRltCuts | ( | ) |
Whether we generate RLT cuts. This is still experimental but can help on binary problem with a lot of clauses of size 3.
optional bool add_rlt_cuts = 279 [default = true];
Definition at line 30511 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAddZeroHalfCuts | ( | ) |
Whether we generate Zero-Half cuts at root node. Note that for now, this is not heavily tuned.
optional bool add_zero_half_cuts = 169 [default = true];
Definition at line 30387 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAlsoBumpVariablesInConflictReasons | ( | ) |
When this is true, then the variables that appear in any of the reason of the variables in a conflict have their activity bumped. This is addition to the variables in the conflict, and the one that were used during conflict resolution.
optional bool also_bump_variables_in_conflict_reasons = 77 [default = false];
Definition at line 17617 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAtMostOneMaxExpansionSize | ( | ) |
All at_most_one constraints with a size <= param will be replaced by a quadratic number of binary implications.
optional int32 at_most_one_max_expansion_size = 270 [default = 3];
Definition at line 29183 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearAutoDetectGreaterThanAtLeastOneOf | ( | ) |
If true, then the precedences propagator try to detect for each variable if it has a set of "optional incoming arc" for which at least one of them is present. This is usually useful to have but can be slow on model with a lot of precedence.
optional bool auto_detect_greater_than_at_least_one_of = 95 [default = true];
Definition at line 28185 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearBinaryMinimizationAlgorithm | ( | ) |
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];
Definition at line 17701 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearBinarySearchNumConflicts | ( | ) |
If non-negative, perform a binary search on the objective variable in order to find an [min, max] interval outside of which the solver proved unsat/sat under this amount of conflict. This can quickly reduce the objective domain on some problems.
optional int32 binary_search_num_conflicts = 99 [default = -1];
Definition at line 26615 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearBlockingRestartMultiplier | ( | ) |
optional double blocking_restart_multiplier = 66 [default = 1.4];
Definition at line 19171 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearBlockingRestartWindowSize | ( | ) |
optional int32 blocking_restart_window_size = 65 [default = 5000];
Definition at line 19131 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearBooleanEncodingLevel | ( | ) |
A non-negative level indicating how much we should try to fully encode Integer variables as Boolean.
optional int32 boolean_encoding_level = 107 [default = 1];
Definition at line 29871 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearCatchSigintSignal | ( | ) |
Indicates if the CP-SAT layer should catch Control-C (SIGINT) signals when calling solve. If set, catching the SIGINT signal will terminate the search gracefully, as if a time limit was reached.
optional bool catch_sigint_signal = 135 [default = true];
Definition at line 29247 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearClauseActivityDecay | ( | ) |
Clause activity parameters (same effect as the one on the variables).
optional double clause_activity_decay = 17 [default = 0.999];
Definition at line 18521 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearClauseCleanupLbdBound | ( | ) |
All the clauses with a LBD (literal blocks distance) lower or equal to this parameters will always be kept.
optional int32 clause_cleanup_lbd_bound = 59 [default = 5];
Definition at line 18051 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearClauseCleanupOrdering | ( | ) |
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];
Definition at line 18093 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearClauseCleanupPeriod | ( | ) |
Trigger a cleanup when this number of "deletable" clauses is learned.
optional int32 clause_cleanup_period = 11 [default = 10000];
Definition at line 17825 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearClauseCleanupProtection | ( | ) |
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];
Definition at line 17991 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearClauseCleanupRatio | ( | ) |
During a cleanup, if clause_cleanup_target is 0, we will delete the clause_cleanup_ratio of "deletable" clauses instead of aiming for a fixed target of clauses to keep.
optional double clause_cleanup_ratio = 190 [default = 0.5];
Definition at line 17949 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearClauseCleanupTarget | ( | ) |
During a cleanup, we will always keep that number of "deletable" clauses. Note that this doesn't include the "protected" clauses.
optional int32 clause_cleanup_target = 13 [default = 0];
Definition at line 17885 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearConvertIntervals | ( | ) |
Temporary flag util the feature is more mature. This convert intervals to the newer proto format that support affine start/var/end instead of just variables.
optional bool convert_intervals = 177 [default = true];
Definition at line 29555 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearCoreMinimizationLevel | ( | ) |
If positive, we spend some effort on each core: - At level 1, we use a simple heuristic to try to minimize an UNSAT core. - At level 2, we use propagation to minimize the core but also identify literal in at most one relationship in this core.
optional int32 core_minimization_level = 50 [default = 2];
Definition at line 24257 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearCountAssumptionLevelsInLbd | ( | ) |
Whether or not the assumption levels are taken into account during the LBD computation. According to the reference below, not counting them improves the solver in some situation. Note that this only impact solves under assumptions. Gilles Audemard, Jean-Marie Lagniez, Laurent Simon, "Improving Glucose for Incremental SAT Solving with Assumptions: Application to MUS Extraction" Theory and Applications of Satisfiability Testing - SAT 2013, Lecture Notes in Computer Science Volume 7962, 2013, pp 309-317.
optional bool count_assumption_levels_in_lbd = 49 [default = true];
Definition at line 20539 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearCoverOptimization | ( | ) |
If true, when the max-sat algo find a core, we compute the minimal number of literals in the core that needs to be true to have a feasible solution. This is also called core exhaustion in more recent max-SAT papers.
optional bool cover_optimization = 89 [default = true];
Definition at line 24381 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearCpModelPresolve | ( | ) |
Whether we presolve the cp_model before solving it.
optional bool cp_model_presolve = 86 [default = true];
Definition at line 21079 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearCpModelProbingLevel | ( | ) |
How much effort do we spend on probing. 0 disables it completely.
optional int32 cp_model_probing_level = 110 [default = 2];
Definition at line 21135 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearCpModelUseSatPresolve | ( | ) |
Whether we also use the sat presolve when cp_model_presolve is true.
optional bool cp_model_use_sat_presolve = 93 [default = true];
Definition at line 21191 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearCutActiveCountDecay | ( | ) |
optional double cut_active_count_decay = 156 [default = 0.8];
Definition at line 31155 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearCutCleanupTarget | ( | ) |
Target number of constraints to remove during cleanup.
optional int32 cut_cleanup_target = 157 [default = 1000];
Definition at line 31211 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearCutLevel | ( | ) |
Control the global cut effort. Zero will turn off all cut. For now we just have one level. Note also that most cuts are only used at linearization level >= 2.
optional int32 cut_level = 196 [default = 1];
Definition at line 30075 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearCutMaxActiveCountValue | ( | ) |
These parameters are similar to sat clause management activity parameters. They are effective only if the number of generated cuts exceed the storage limit. Default values are based on a few experiments on miplib instances.
optional double cut_max_active_count_value = 155 [default = 10000000000];
Definition at line 31115 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearDebugCrashOnBadHint | ( | ) |
Crash if we do not manage to complete the hint into a full solution.
optional bool debug_crash_on_bad_hint = 195 [default = false];
Definition at line 24121 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearDebugMaxNumPresolveOperations | ( | ) |
If positive, try to stop just after that many presolve rules have been applied. This is mainly useful for debugging presolve.
optional int32 debug_max_num_presolve_operations = 151 [default = 0];
Definition at line 24065 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearDebugPostsolveWithFullSolver | ( | ) |
We have two different postsolve code. The default one should be better and it allows for a more powerful presolve, but it can be useful to postsolve using the full solver instead.
optional bool debug_postsolve_with_full_solver = 162 [default = false];
Definition at line 24005 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearDefaultRestartAlgorithms | ( | ) |
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];
Definition at line 18798 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearDetectLinearizedProduct | ( | ) |
Infer products of Boolean or of Boolean time IntegerVariable from the linear constrainst in the problem. This can be used in some cuts, altough for now we don't really exploit it.
optional bool detect_linearized_product = 277 [default = false];
Definition at line 31647 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearDetectTableWithCost | ( | ) |
If true, we detect variable that are unique to a table constraint and only there to encode a cost on each tuple. This is usually the case when a WCSP (weighted constraint program) is encoded into CP-SAT format. This can lead to a dramatic speed-up for such problems but is still experimental at this point.
optional bool detect_table_with_cost = 216 [default = false];
Definition at line 21267 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearDisableConstraintExpansion | ( | ) |
If true, it disable all constraint expansion. This should only be used to test the presolve of expanded constraints.
optional bool disable_constraint_expansion = 181 [default = false];
Definition at line 21515 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearDiversifyLnsParams | ( | ) |
If true, registers more lns subsolvers with different parameters.
optional bool diversify_lns_params = 137 [default = false];
Definition at line 28735 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearEncodeComplexLinearConstraintWithInteger | ( | ) |
Linear constraint with a complex right hand side (more than a single interval) need to be expanded, there is a couple of way to do that.
optional bool encode_complex_linear_constraint_with_integer = 223 [default = false];
Definition at line 21575 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearEnumerateAllSolutions | ( | ) |
Whether we enumerate all solutions of a problem without objective. Note that setting this to true automatically disable some presolve reduction that can remove feasible solution. That is it has the same effect as setting keep_all_feasible_solutions_in_presolve. TODO(user): Do not do that and let the user choose what behavior is best by setting keep_all_feasible_solutions_in_presolve ?
optional bool enumerate_all_solutions = 87 [default = false];
Definition at line 27801 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearExpandAlldiffConstraints | ( | ) |
If true, expand all_different constraints that are not permutations. Permutations (#Variables = #Values) are always expanded.
optional bool expand_alldiff_constraints = 170 [default = false];
Definition at line 21395 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearExpandReservoirConstraints | ( | ) |
If true, expand the reservoir constraints by creating booleans for all possible precedences between event and encoding the constraint.
optional bool expand_reservoir_constraints = 182 [default = true];
Definition at line 21455 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearExploitAllLpSolution | ( | ) |
If true and the Lp relaxation of the problem has a solution, try to exploit it. This is same as above except in this case the lp solution might not be an integer solution.
optional bool exploit_all_lp_solution = 116 [default = true];
Definition at line 31403 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearExploitAllPrecedences | ( | ) |
optional bool exploit_all_precedences = 220 [default = false];
Definition at line 25281 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearExploitBestSolution | ( | ) |
When branching on a variable, follow the last best solution value.
optional bool exploit_best_solution = 130 [default = false];
Definition at line 31459 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearExploitIntegerLpSolution | ( | ) |
If true and the Lp relaxation of the problem has an integer optimal solution, try to exploit it. Note that since the LP relaxation may not contain all the constraints, such a solution is not necessarily a solution of the full problem.
optional bool exploit_integer_lp_solution = 94 [default = true];
Definition at line 31339 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearExploitObjective | ( | ) |
When branching an a variable that directly affect the objective, branch on the value that lead to the best objective first.
optional bool exploit_objective = 131 [default = true];
Definition at line 31583 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearExploitRelaxationSolution | ( | ) |
When branching on a variable, follow the last best relaxation solution value. We use the relaxation with the tightest bound on the objective as the best relaxation solution.
optional bool exploit_relaxation_solution = 161 [default = false];
Definition at line 31523 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearExtraSubsolvers | ( | ) |
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;
Definition at line 23098 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFeasibilityJumpDecay | ( | ) |
On each restart, we randomly choose if we use decay (with this parameter) or no decay.
optional double feasibility_jump_decay = 242 [default = 0.95];
Definition at line 26875 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFeasibilityJumpEnableRestarts | ( | ) |
When stagnating, feasibility jump will either restart from a default solution (with some possible randomization), or randomly pertubate the current solution. This parameter selects the first option.
optional bool feasibility_jump_enable_restarts = 250 [default = true];
Definition at line 27179 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFeasibilityJumpLinearizationLevel | ( | ) |
How much do we linearize the problem in the local search code.
optional int32 feasibility_jump_linearization_level = 257 [default = 2];
Definition at line 26931 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFeasibilityJumpMaxExpandedConstraintSize | ( | ) |
Maximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion.
optional int32 feasibility_jump_max_expanded_constraint_size = 264 [default = 100];
Definition at line 27239 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFeasibilityJumpRestartFactor | ( | ) |
This is a factor that directly influence the work before each restart. Setting this to zero disable restart, and increasing it lead to longer restarts.
optional int32 feasibility_jump_restart_factor = 258 [default = 1];
Definition at line 26995 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFeasibilityJumpVarPerburbationRangeRatio | ( | ) |
Max distance between the default value and the pertubated value relative to the range of the domain of the variable.
optional double feasibility_jump_var_perburbation_range_ratio = 248 [default = 0.2];
Definition at line 27115 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFeasibilityJumpVarRandomizationProbability | ( | ) |
Probability for a variable to have a non default value upon restarts or perturbations.
optional double feasibility_jump_var_randomization_probability = 247 [default = 0];
Definition at line 27055 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearField | ( | com.google.protobuf.Descriptors.FieldDescriptor | field | ) |
Definition at line 14810 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFillAdditionalSolutionsInResponse | ( | ) |
If true, the final response addition_solutions field will be filled with all solutions from our solutions pool. Note that if both this field and enumerate_all_solutions is true, we will copy to the pool all of the solution found. So if solution_pool_size is big enough, you can get all solutions this way instead of using the solution callback. Note that this only affect the "final" solution, not the one passed to the solution callbacks.
optional bool fill_additional_solutions_in_response = 194 [default = false];
Definition at line 28049 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFillTightenedDomainsInResponse | ( | ) |
If true, add information about the derived variable domains to the CpSolverResponse. It is an option because it makes the response slighly bigger and there is a bit more work involved during the postsolve to construct it, but it should still have a low overhead. See the tightened_variables field in CpSolverResponse for more details.
optional bool fill_tightened_domains_in_response = 132 [default = false];
Definition at line 27957 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFindBigLinearOverlap | ( | ) |
Try to find large "rectangle" in the linear constraint matrix with identical lines. If such rectangle is big enough, we can introduce a new integer variable corresponding to the common expression and greatly reduce the number of non-zero.
optional bool find_big_linear_overlap = 234 [default = true];
Definition at line 22107 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFindMultipleCores | ( | ) |
Whether we try to find more independent cores for a given set of assumptions in the core based max-SAT algorithms.
optional bool find_multiple_cores = 84 [default = true];
Definition at line 24317 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFixVariablesToTheirHintedValue | ( | ) |
If true, variables appearing in the solution hints will be fixed to their hinted value.
optional bool fix_variables_to_their_hinted_value = 192 [default = false];
Definition at line 25927 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearFpRounding | ( | ) |
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];
Definition at line 28679 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearGlucoseDecayIncrement | ( | ) |
optional double glucose_decay_increment = 23 [default = 0.01];
Definition at line 18425 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearGlucoseDecayIncrementPeriod | ( | ) |
optional int32 glucose_decay_increment_period = 24 [default = 5000];
Definition at line 18465 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearGlucoseMaxDecay | ( | ) |
The activity starts at 0.8 and increment by 0.01 every 5000 conflicts until 0.95. This "hack" seems to work well and comes from: Glucose 2.3 in the SAT 2013 Competition - SAT Competition 2013 http://edacc4.informatik.uni-ulm.de/SC13/solver-description-download/136
optional double glucose_max_decay = 22 [default = 0.95];
Definition at line 18385 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearHintConflictLimit | ( | ) |
Conflict limit used in the phase that exploit the solution hint.
optional int32 hint_conflict_limit = 153 [default = 10];
Definition at line 25799 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearIgnoreNames | ( | ) |
If true, we don't keep names in our internal copy of the user given model.
optional bool ignore_names = 202 [default = true];
Definition at line 21967 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearIgnoreSubsolvers | ( | ) |
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem.
repeated string ignore_subsolvers = 209;
Definition at line 23253 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearInferAllDiffs | ( | ) |
Run a max-clique code amongst all the x != y we can find and try to infer set of variables that are all different. This allows to close neos16.mps for instance. Note that we only run this code if there is no all_diff already in the model so that if a user want to add some all_diff, we assume it is well done and do not try to add more.
optional bool infer_all_diffs = 233 [default = true];
Definition at line 22039 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearInitialPolarity | ( | ) |
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];
Definition at line 17113 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearInitialVariablesActivity | ( | ) |
The initial value of the variables activity. A non-zero value only make sense when use_erwa_heuristic is true. Experiments with a value of 1e-2 together with the ERWA heuristic showed slighthly better result than simply using zero. The idea is that when the "learning rate" of a variable becomes lower than this value, then we prefer to branch on never explored before variables. This is not in the ERWA paper.
optional double initial_variables_activity = 76 [default = 0];
Definition at line 17549 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearInprocessingDtimeRatio | ( | ) |
Proportion of deterministic time we should spend on inprocessing. At each "restart", if the proportion is below this ratio, we will do some inprocessing, otherwise, we skip it for this restart.
optional double inprocessing_dtime_ratio = 273 [default = 0.2];
Definition at line 22231 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearInprocessingMinimizationDtime | ( | ) |
Parameters for an heuristic similar to the one described in "An effective learnt clause minimization approach for CDCL Sat Solvers", https://www.ijcai.org/proceedings/2017/0098.pdf This is the amount of dtime we should spend on this technique during each inprocessing phase. The minimization technique is the same as the one used to minimize core in max-sat. We also minimize problem clauses and not just the learned clause that we keep forever like in the paper.
optional double inprocessing_minimization_dtime = 275 [default = 1];
Definition at line 22379 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearInprocessingProbingDtime | ( | ) |
The amount of dtime we should spend on probing for each inprocessing round.
optional double inprocessing_probing_dtime = 274 [default = 1];
Definition at line 22287 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearInstantiateAllVariables | ( | ) |
If true, the solver will add a default integer branching strategy to the already defined search strategy. If not, some variable might still not be fixed at the end of the search. For now we assume these variable can just be set to their lower bound.
optional bool instantiate_all_variables = 106 [default = true];
Definition at line 28117 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearInterleaveBatchSize | ( | ) |
optional int32 interleave_batch_size = 134 [default = 0];
Definition at line 23773 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearInterleaveSearch | ( | ) |
Experimental. If this is true, then we interleave all our major search strategy and distribute the work amongst num_workers. The search is deterministic (independently of num_workers!), and we schedule and wait for interleave_batch_size task to be completed before synchronizing and scheduling the next batch of tasks.
optional bool interleave_search = 136 [default = false];
Definition at line 23733 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearKeepAllFeasibleSolutionsInPresolve | ( | ) |
If true, we disable the presolve reductions that remove feasible solutions from the search space. Such solution are usually dominated by a "better" solution that is kept, but depending on the situation, we might want to keep all solutions. A trivial example is when a variable is unused. If this is true, then the presolve will not fix it to an arbitrary value and it will stay in the search space.
optional bool keep_all_feasible_solutions_in_presolve = 173 [default = false];
Definition at line 27885 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearLinearizationLevel | ( | ) |
A non-negative level indicating the type of constraints we consider in the LP relaxation. At level zero, no LP relaxation is used. At level 1, only the linear constraint and full encoding are added. At level 2, we also add all the Boolean constraints.
optional int32 linearization_level = 90 [default = 1];
Definition at line 29811 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearLinearSplitSize | ( | ) |
Linear constraints that are not pseudo-Boolean and that are longer than this size will be split into sqrt(size) intermediate sums in order to have faster propation in the CP engine.
optional int32 linear_split_size = 256 [default = 100];
Definition at line 29743 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearLogPrefix | ( | ) |
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];
Definition at line 20186 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearLogSearchProgress | ( | ) |
Whether the solver should log the search progress. This is the maing logging parameter and if this is false, none of the logging (callbacks, log_to_stdout, log_to_response, ...) will do anything.
optional bool log_search_progress = 41 [default = false];
Definition at line 20031 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearLogSubsolverStatistics | ( | ) |
Whether the solver should display per sub-solver search statistics. This is only useful is log_search_progress is set to true, and if the number of search workers is > 1. Note that in all case we display a bit of stats with one line per subsolver.
optional bool log_subsolver_statistics = 189 [default = false];
Definition at line 20099 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearLogToResponse | ( | ) |
Log to response proto.
optional bool log_to_response = 187 [default = false];
Definition at line 20315 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearLogToStdout | ( | ) |
Log to stdout.
optional bool log_to_stdout = 186 [default = true];
Definition at line 20259 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearLpDualTolerance | ( | ) |
optional double lp_dual_tolerance = 267 [default = 1e-07];
Definition at line 29491 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearLpPrimalTolerance | ( | ) |
The internal LP tolerances used by CP-SAT. These applies to the internal and scaled problem. If the domains of your variables are large it might be good to use lower tolerances. If your problem is binary with low coefficients, it might be good to use higher ones to speed-up the lp solves.
optional double lp_primal_tolerance = 266 [default = 1e-07];
Definition at line 29451 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxAllDiffCutSize | ( | ) |
Cut generator for all diffs can add too many cuts for large all_diff constraints. This parameter restricts the large all_diff constraints to have a cut generator.
optional int32 max_all_diff_cut_size = 148 [default = 64];
Definition at line 30575 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxClauseActivityValue | ( | ) |
optional double max_clause_activity_value = 18 [default = 1e+20];
Definition at line 18561 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxConsecutiveInactiveCount | ( | ) |
If a constraint/cut in LP is not active for that many consecutive OPTIMAL solves, remove it from the LP. Note that it might be added again later if it become violated by the current LP solution.
optional int32 max_consecutive_inactive_count = 121 [default = 100];
Definition at line 31051 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxCutRoundsAtLevelZero | ( | ) |
Max number of time we perform cut generation and resolve the LP at level 0.
optional int32 max_cut_rounds_at_level_zero = 154 [default = 1];
Definition at line 30987 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxDeterministicTime | ( | ) |
Maximum time allowed in deterministic time to solve a problem. The deterministic time should be correlated with the real time used by the solver, the time unit being as close as possible to a second.
optional double max_deterministic_time = 67 [default = inf];
Definition at line 19419 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxDomainSizeWhenEncodingEqNeqConstraints | ( | ) |
When loading a*x + b*y ==/!= c when x and y are both fully encoded. The solver may decide to replace the linear equation by a set of clauses. This is triggered if the sizes of the domains of x and y are below the threshold.
optional int32 max_domain_size_when_encoding_eq_neq_constraints = 191 [default = 16];
Definition at line 29939 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxIntegerRoundingScaling | ( | ) |
In the integer rounding procedure used for MIR and Gomory cut, the maximum "scaling" we use (must be positive). The lower this is, the lower the integer coefficients of the cut will be. Note that cut generated by lower values are not necessarily worse than cut generated by larger value. There is no strict dominance relationship. Setting this to 2 result in the "strong fractional rouding" of Letchford and Lodi.
optional int32 max_integer_rounding_scaling = 119 [default = 600];
Definition at line 30723 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxMemoryInMb | ( | ) |
Maximum memory allowed for the whole thread containing the solver. The solver will abort as soon as it detects that this limit is crossed. As a result, this limit is approximative, but usually the solver will not go too much over. TODO(user): This is only used by the pure SAT solver, generalize to CP-SAT.
optional int64 max_memory_in_mb = 40 [default = 10000];
Definition at line 19575 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxNumberOfConflicts | ( | ) |
Maximum number of conflicts allowed to solve a problem. TODO(user): Maybe change the way the conflict limit is enforced? currently it is enforced on each independent internal SAT solve, rather than on the overall number of conflicts across all solves. So in the context of an optimization problem, this is not really usable directly by a client.
optional int64 max_number_of_conflicts = 37 [default = 9223372036854775807];
Definition at line 19499 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxNumCuts | ( | ) |
The limit on the number of cuts in our cut pool. When this is reached we do not generate cuts anymore. TODO(user): We should probably remove this parameters, and just always generate cuts but only keep the best n or something.
optional int32 max_num_cuts = 91 [default = 10000];
Definition at line 30011 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxNumIntervalsForTimetableEdgeFinding | ( | ) |
Max number of intervals for the timetable_edge_finding algorithm to propagate. A value of 0 disables the constraint.
optional int32 max_num_intervals_for_timetable_edge_finding = 260 [default = 100];
Definition at line 25165 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxPairsPairwiseReasoningInNoOverlap2D | ( | ) |
If the number of pairs to look is below this threshold, do an extra step of propagation in the no_overlap_2d constraint by looking at all pairs of intervals.
optional int32 max_pairs_pairwise_reasoning_in_no_overlap_2d = 276 [default = 1250];
Definition at line 25637 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxPresolveIterations | ( | ) |
In case of large reduction in a presolve iteration, we perform multiple presolve iterations. This parameter controls the maximum number of such presolve iterations.
optional int32 max_presolve_iterations = 138 [default = 3];
Definition at line 21023 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxSatAssumptionOrder | ( | ) |
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];
Definition at line 24423 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxSatReverseAssumptionOrder | ( | ) |
If true, adds the assumption in the reverse order of the one defined by max_sat_assumption_order.
optional bool max_sat_reverse_assumption_order = 52 [default = false];
Definition at line 24483 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxSatStratification | ( | ) |
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];
Definition at line 24525 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxSizeToCreatePrecedenceLiteralsInDisjunctive | ( | ) |
Create one literal for each disjunction of two pairs of tasks. This slows down the solve time, but improves the lower bound of the objective in the makespan case. This will be triggered if the number of intervals is less or equal than the parameter and if use_strong_propagation_in_disjunctive is true.
optional int32 max_size_to_create_precedence_literals_in_disjunctive = 229 [default = 60];
Definition at line 24773 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxTimeInSeconds | ( | ) |
Maximum time allowed in seconds to solve a problem. The counter will starts at the beginning of the Solve() call.
optional double max_time_in_seconds = 36 [default = inf];
Definition at line 19355 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMaxVariableActivityValue | ( | ) |
optional double max_variable_activity_value = 16 [default = 1e+100];
Definition at line 18313 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMergeAtMostOneWorkLimit | ( | ) |
optional double merge_at_most_one_work_limit = 146 [default = 100000000];
Definition at line 21687 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMergeNoOverlapWorkLimit | ( | ) |
During presolve, we use a maximum clique heuristic to merge together no-overlap constraints or at most one constraints. This code can be slow, so we have a limit in place on the number of explored nodes in the underlying graph. The internal limit is an int64, but we use double here to simplify manual input.
optional double merge_no_overlap_work_limit = 145 [default = 1000000000000];
Definition at line 21647 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMinimizationAlgorithm | ( | ) |
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];
Definition at line 17659 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMinimizeReductionDuringPbResolution | ( | ) |
A different algorithm during PB resolution. It minimizes the number of calls to ReduceCoefficients() which can be time consuming. However, the search space will be different and if the coefficients are large, this may lead to integer overflows that could otherwise be prevented.
optional bool minimize_reduction_during_pb_resolution = 48 [default = false];
Definition at line 20451 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMinNumLnsWorkers | ( | ) |
Obsolete parameter. No-op.
optional int32 min_num_lns_workers = 211 [default = 2];
Definition at line 22583 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMinOrthogonalityForLpConstraints | ( | ) |
While adding constraints, skip the constraints which have orthogonality less than 'min_orthogonality_for_lp_constraints' with already added constraints during current call. Orthogonality is defined as 1 - cosine(vector angle between constraints). A value of zero disable this feature.
optional double min_orthogonality_for_lp_constraints = 115 [default = 0.05];
Definition at line 30931 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipAutomaticallyScaleVariables | ( | ) |
If true, some continuous variable might be automatically scaled. For now, this is only the case where we detect that a variable is actually an integer multiple of a constant. For instance, variables of the form k * 0.5 are quite frequent, and if we detect this, we will scale such variable domain by 2 to make it implied integer.
optional bool mip_automatically_scale_variables = 166 [default = true];
Definition at line 31911 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipCheckPrecision | ( | ) |
As explained in mip_precision and mip_max_activity_exponent, we cannot always reach the wanted precision during scaling. We use this threshold to enphasize in the logs when the precision seems bad.
optional double mip_check_precision = 128 [default = 0.0001];
Definition at line 32279 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipComputeTrueObjectiveBound | ( | ) |
Even if we make big error when scaling the objective, we can always derive a correct lower bound on the original objective by using the exact lower bound on the scaled integer version of the objective. This should be fast, but if you don't care about having a precise lower bound, you can turn it off.
optional bool mip_compute_true_objective_bound = 198 [default = true];
Definition at line 32351 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipDropTolerance | ( | ) |
Any value in the input mip with a magnitude lower than this will be set to zero. This is to avoid some issue in LP presolving.
optional double mip_drop_tolerance = 232 [default = 1e-16];
Definition at line 32559 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipMaxActivityExponent | ( | ) |
To avoid integer overflow, we always force the maximum possible constraint activity (and objective value) according to the initial variable domain to be smaller than 2 to this given power. Because of this, we cannot always reach the "mip_wanted_precision" parameter above. This can go as high as 62, but some internal algo currently abort early if they might run into integer overflow, so it is better to keep it a bit lower than this.
optional int32 mip_max_activity_exponent = 127 [default = 53];
Definition at line 32215 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipMaxBound | ( | ) |
We need to bound the maximum magnitude of the variables for CP-SAT, and that is the bound we use. If the MIP model expect larger variable value in the solution, then the converted model will likely not be relevant.
optional double mip_max_bound = 124 [default = 10000000];
Definition at line 31711 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipMaxValidMagnitude | ( | ) |
Any finite values in the input MIP must be below this threshold, otherwise the model will be reported invalid. This is needed to avoid floating point overflow when evaluating bounds * coeff for instance. We are a bit more defensive, but in practice, users shouldn't use super large values in a MIP.
optional double mip_max_valid_magnitude = 199 [default = 1e+20];
Definition at line 32423 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipPresolveLevel | ( | ) |
When solving a MIP, we do some basic floating point presolving before scaling the problem to integer to be handled by CP-SAT. This control how much of that presolve we do. It can help to better scale floating point model, but it is not always behaving nicely.
optional int32 mip_presolve_level = 261 [default = 2];
Definition at line 32627 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipScaleLargeDomain | ( | ) |
If this is false, then mip_var_scaling is only applied to variables with "small" domain. If it is true, we scale all floating point variable independenlty of their domain.
optional bool mip_scale_large_domain = 225 [default = false];
Definition at line 31839 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipTreatHighMagnitudeBoundsAsInfinity | ( | ) |
By default, any variable/constraint bound with a finite value and a magnitude greater than the mip_max_valid_magnitude will result with a invalid model. This flags change the behavior such that such bounds are silently transformed to +∞ or -∞. It is recommended to keep it at false, and create valid bounds.
optional bool mip_treat_high_magnitude_bounds_as_infinity = 278 [default = false];
Definition at line 32499 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipVarScaling | ( | ) |
All continuous variable of the problem will be multiplied by this factor. By default, we don't do any variable scaling and rely on the MIP model to specify continuous variable domain with the wanted precision.
optional double mip_var_scaling = 125 [default = 1];
Definition at line 31775 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearMipWantedPrecision | ( | ) |
When scaling constraint with double coefficients to integer coefficients, we will multiply by a power of 2 and round the coefficients. We will choose the lowest power such that we have no potential overflow (see mip_max_activity_exponent) and the worst case constraint activity error does not exceed this threshold. Note that we also detect constraint with rational coefficients and scale them accordingly when it seems better instead of using a power of 2. We also relax all constraint bounds by this absolute value. For pure integer constraint, if this value if lower than one, this will not change anything. However it is needed when scaling MIP problems. If we manage to scale a constraint correctly, the maximum error we can make will be twice this value (once for the scaling error and once for the relaxed bounds). If we are not able to scale that well, we will display that fact but still scale as best as we can.
optional double mip_wanted_precision = 126 [default = 1e-06];
Definition at line 32131 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearName | ( | ) |
In some context, like in a portfolio of search, it makes sense to name a given parameters set for logging purpose.
optional string name = 171 [default = ""];
Definition at line 17011 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearNewConstraintsBatchSize | ( | ) |
Add that many lazy constraints (or cuts) at once in the LP. Note that at the beginning of the solve, we do add more than this.
optional int32 new_constraints_batch_size = 122 [default = 50];
Definition at line 31271 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearNewLinearPropagation | ( | ) |
Experimental. Use new code to propagate linear constraint.
optional bool new_linear_propagation = 224 [default = false];
Definition at line 29679 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearNumConflictsBeforeStrategyChanges | ( | ) |
After each restart, if the number of conflict since the last strategy change is greater that this, then we increment a "strategy_counter" that can be use to change the search strategy used by the following restarts.
optional int32 num_conflicts_before_strategy_changes = 68 [default = 0];
Definition at line 19235 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearNumSearchWorkers | ( | ) |
optional int32 num_search_workers = 100 [default = 0];
Definition at line 22527 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearNumViolationLs | ( | ) |
This will create incomplete subsolvers (that are not LNS subsolvers) that use the feasibility jump code to find improving solution, treating the objective improvement as a hard constraint.
optional int32 num_violation_ls = 244 [default = 0];
Definition at line 27303 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearNumWorkers | ( | ) |
Specify the number of parallel workers (i.e. threads) to use during search. This should usually be lower than your number of available cpus + hyperthread in your machine. A value of 0 means the solver will try to use all cores on the machine. A number of 1 means no parallelism. Note that 'num_workers' is the preferred name, but if it is set to zero, we will still read the deprecated 'num_search_worker'. As of 2020-04-10, if you're using SAT via MPSolver (to solve integer programs) this field is overridden with a value of 8, if the field is not set *explicitly*. Thus, always set this field explicitly or via MPSolver::SetNumThreads().
optional int32 num_workers = 206 [default = 0];
Definition at line 22487 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearOneof | ( | com.google.protobuf.Descriptors.OneofDescriptor | oneof | ) |
Definition at line 14815 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearOnlyAddCutsAtLevelZero | ( | ) |
For the cut that can be generated at any level, this control if we only try to generate them at the root node.
optional bool only_add_cuts_at_level_zero = 92 [default = false];
Definition at line 30135 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearOnlySolveIp | ( | ) |
If one try to solve a MIP model with CP-SAT, because we assume all variable to be integer after scaling, we will not necessarily have the correct optimal. Note however that all feasible solutions are valid since we will just solve a more restricted version of the original problem. This parameters is here to prevent user to think the solution is optimal when it might not be. One will need to manually set this to false to solve a MIP model where the optimal might be different. Note that this is tested after some MIP presolve steps, so even if not all original variable are integer, we might end up with a pure IP after presolve and after implied integer detection.
optional bool only_solve_ip = 222 [default = false];
Definition at line 32011 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearOptimizeWithCore | ( | ) |
The default optimization method is a simple "linear scan", each time trying to find a better solution than the previous one. If this is true, then we use a core-based approach (like in max-SAT) when we try to increase the lower bound instead.
optional bool optimize_with_core = 83 [default = false];
Definition at line 26475 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearOptimizeWithLbTreeSearch | ( | ) |
Do a more conventional tree search (by opposition to SAT based one) where we keep all the explored node in a tree. This is meant to be used in a portfolio and focus on improving the objective lower bound. Keeping the whole tree allow us to report a better objective lower bound coming from the worst open node in the tree.
optional bool optimize_with_lb_tree_search = 188 [default = false];
Definition at line 26547 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearOptimizeWithMaxHs | ( | ) |
This has no effect if optimize_with_core is false. If true, use a different core-based algorithm similar to the max-HS algo for max-SAT. This is a hybrid MIP/CP approach and it uses a MIP solver in addition to the CP/SAT one. This is also related to the PhD work of tobyodavies@ "Automatic Logic-Based Benders Decomposition with MiniZinc" http://aaai.org/ocs/index.php/AAAI/AAAI17/paper/view/14489
optional bool optimize_with_max_hs = 85 [default = false];
Definition at line 26691 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPbCleanupIncrement | ( | ) |
Same as for the clauses, but for the learned pseudo-Boolean constraints.
optional int32 pb_cleanup_increment = 46 [default = 200];
Definition at line 18149 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPbCleanupRatio | ( | ) |
optional double pb_cleanup_ratio = 47 [default = 0.5];
Definition at line 18189 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPermutePresolveConstraintOrder | ( | ) |
optional bool permute_presolve_constraint_order = 179 [default = false];
Definition at line 19927 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPermuteVariableRandomly | ( | ) |
This is mainly here to test the solver variability. Note that in tests, if not explicitly set to false, all 3 options will be set to true so that clients do not rely on the solver returning a specific solution if they are many equivalent optimal solutions.
optional bool permute_variable_randomly = 178 [default = false];
Definition at line 19887 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPolarityRephaseIncrement | ( | ) |
If non-zero, then we change the polarity heuristic after that many number of conflicts in an arithmetically increasing fashion. So x the first time, 2 * x the second time, etc...
optional int32 polarity_rephase_increment = 168 [default = 1000];
Definition at line 17273 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPolishLpSolution | ( | ) |
Whether we try to do a few degenerate iteration at the end of an LP solve to minimize the fractionality of the integer variable in the basis. This helps on some problems, but not so much on others. It also cost of bit of time to do such polish step.
optional bool polish_lp_solution = 175 [default = false];
Definition at line 29379 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPreferredVariableOrder | ( | ) |
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];
Definition at line 17071 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPresolveBlockedClause | ( | ) |
Whether we use an heuristic to detect some basic case of blocked clause in the SAT presolve.
optional bool presolve_blocked_clause = 88 [default = true];
Definition at line 20835 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPresolveBvaThreshold | ( | ) |
Apply Bounded Variable Addition (BVA) if the number of clauses is reduced by stricly more than this threshold. The algorithm described in the paper uses 0, but quick experiments showed that 1 is a good value. It may not be worth it to add a new variable just to remove one clause.
optional int32 presolve_bva_threshold = 73 [default = 1];
Definition at line 20959 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPresolveBveClauseWeight | ( | ) |
During presolve, we apply BVE only if this weight times the number of clauses plus the number of clause literals is not increased.
optional int32 presolve_bve_clause_weight = 55 [default = 3];
Definition at line 20663 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPresolveBveThreshold | ( | ) |
During presolve, only try to perform the bounded variable elimination (BVE) of a variable x if the number of occurrences of x times the number of occurrences of not(x) is not greater than this parameter.
optional int32 presolve_bve_threshold = 54 [default = 500];
Definition at line 20603 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPresolveExtractIntegerEnforcement | ( | ) |
If true, we will extract from linear constraints, enforcement literals of the form "integer variable at bound => simplified constraint". This should always be beneficial except that we don't always handle them as efficiently as we could for now. This causes problem on manna81.mps (LP relaxation not as tight it seems) and on neos-3354841-apure.mps.gz (too many literals created this way).
optional bool presolve_extract_integer_enforcement = 174 [default = false];
Definition at line 21831 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPresolveInclusionWorkLimit | ( | ) |
A few presolve operations involve detecting constraints included in other constraint. Since there can be a quadratic number of such pairs, and processing them usually involve scanning them, the complexity of these operations can be big. This enforce a local deterministic limit on the number of entries scanned. Default is 1e8. A value of zero will disable these presolve rules completely.
optional int64 presolve_inclusion_work_limit = 201 [default = 100000000];
Definition at line 21911 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPresolveProbingDeterministicTimeLimit | ( | ) |
optional double presolve_probing_deterministic_time_limit = 57 [default = 30];
Definition at line 20775 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPresolveSubstitutionLevel | ( | ) |
How much substitution (also called free variable aggregation in MIP litterature) should we perform at presolve. This currently only concerns variable appearing only in linear constraints. For now the value 0 turns it off and any positive value performs substitution.
optional int32 presolve_substitution_level = 147 [default = 1];
Definition at line 21755 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPresolveUseBva | ( | ) |
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
optional bool presolve_use_bva = 72 [default = true];
Definition at line 20891 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearProbingDeterministicTimeLimit | ( | ) |
The maximum "deterministic" time limit to spend in probing. A value of zero will disable the probing. TODO(user): Clean up. The first one is used in CP-SAT, the other in pure SAT presolve.
optional double probing_deterministic_time_limit = 226 [default = 1];
Definition at line 20735 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearProbingNumCombinationsLimit | ( | ) |
How many combinations of pairs or triplets of variables we want to scan.
optional int32 probing_num_combinations_limit = 272 [default = 20000];
Definition at line 26103 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPropagationLoopDetectionFactor | ( | ) |
Some search decisions might cause a really large number of propagations to happen when integer variables with large domains are only reduced by 1 at each step. If we propagate more than the number of variable times this parameters we try to take counter-measure. Setting this to 0.0 disable this feature. TODO(user): Setting this to something like 10 helps in most cases, but the code is currently buggy and can cause the solve to enter a bad state where no progress is made.
optional double propagation_loop_detection_factor = 221 [default = 10];
Definition at line 24613 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPseudoCostReliabilityThreshold | ( | ) |
The solver ignores the pseudo costs of variables with number of recordings less than this threshold.
optional int64 pseudo_cost_reliability_threshold = 123 [default = 100];
Definition at line 26407 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearPushAllTasksTowardStart | ( | ) |
Experimental code: specify if the objective pushes all tasks toward the start of the schedule.
optional bool push_all_tasks_toward_start = 262 [default = false];
Definition at line 28915 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRandomBranchesRatio | ( | ) |
A number between 0 and 1 that indicates the proportion of branching variables that are selected randomly instead of choosing the first variable from the given variable_ordering strategy.
optional double random_branches_ratio = 32 [default = 0];
Definition at line 17409 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRandomizeSearch | ( | ) |
Randomize fixed search.
optional bool randomize_search = 103 [default = false];
Definition at line 28791 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRandomPolarityRatio | ( | ) |
The proportion of polarity chosen at random. Note that this take precedence over the phase saving heuristic. This is different from initial_polarity:POLARITY_RANDOM because it will select a new random polarity each time the variable is branched upon instead of selecting one initially and then always taking this choice.
optional double random_polarity_ratio = 45 [default = 0];
Definition at line 17345 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRandomSeed | ( | ) |
At the beginning of each solve, the random number generator used in some part of the solver is reinitialized to this seed. If you change the random seed, the solver may make different choices during the solving process. For some problems, the running time may vary a lot depending on small change in the solving algorithm. Running the solver with different seeds enables to have more robust benchmarks when evaluating new features.
optional int32 random_seed = 31 [default = 1];
Definition at line 19819 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRelativeGapLimit | ( | ) |
optional double relative_gap_limit = 160 [default = 0];
Definition at line 19739 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRepairHint | ( | ) |
If true, the solver tries to repair the solution given in the hint. This search terminates after the 'hint_conflict_limit' is reached and the solver switches to regular search. If false, then we do a FIXED_SEARCH using the hint until the hint_conflict_limit is reached.
optional bool repair_hint = 167 [default = false];
Definition at line 25867 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRestartAlgorithms | ( | ) |
The restart strategies will change each time the strategy_counter is increased. The current strategy will simply be the one at index strategy_counter modulo the number of strategy. Note that if this list includes a NO_RESTART, nothing will change when it is reached because the strategy_counter will only increment after a restart. The idea of switching of search strategy tailored for SAT/UNSAT comes from Chanseok Oh with his COMiniSatPS solver, see http://cs.nyu.edu/~chanseok/. But more generally, it seems REALLY beneficial to try different strategy.
repeated .operations_research.sat.SatParameters.RestartAlgorithm restart_algorithms = 61;
Definition at line 18731 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRestartDlAverageRatio | ( | ) |
In the moving average restart algorithms, a restart is triggered if the window average times this ratio is greater that the global average.
optional double restart_dl_average_ratio = 63 [default = 1];
Definition at line 18987 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRestartLbdAverageRatio | ( | ) |
optional double restart_lbd_average_ratio = 71 [default = 1];
Definition at line 19027 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRestartPeriod | ( | ) |
Restart period for the FIXED_RESTART strategy. This is also the multiplier used by the LUBY_RESTART strategy.
optional int32 restart_period = 30 [default = 50];
Definition at line 18871 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRestartRunningWindowSize | ( | ) |
Size of the window for the moving average restarts.
optional int32 restart_running_window_size = 62 [default = 50];
Definition at line 18927 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearRootLpIterations | ( | ) |
Even at the root node, we do not want to spend too much time on the LP if it is "difficult". So we solve it in "chunks" of that many iterations. The solve will be continued down in the tree or the next time we go back to the root node.
optional int32 root_lp_iterations = 227 [default = 2000];
Definition at line 30859 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearSearchBranching | ( | ) |
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];
Definition at line 25743 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearSearchRandomVariablePoolSize | ( | ) |
Search randomization will collect the top 'search_random_variable_pool_size' valued variables, and pick one randomly. The value of the variable is specific to each strategy.
optional int64 search_random_variable_pool_size = 104 [default = 0];
Definition at line 28855 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearShareBinaryClauses | ( | ) |
Allows sharing of new learned binary clause between workers.
optional bool share_binary_clauses = 203 [default = true];
Definition at line 23941 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearSharedTreeMaxNodesPerWorker | ( | ) |
In order to limit total shared memory and communication overhead, limit the total number of nodes that may be generated in the shared tree. If the shared tree runs out of unassigned leaves, workers act as portfolio workers. Note: this limit includes interior nodes, not just leaves.
optional int32 shared_tree_max_nodes_per_worker = 238 [default = 128];
Definition at line 27679 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearSharedTreeNumWorkers | ( | ) |
Enables experimental workstealing-like shared tree search. If non-zero, start this many complete worker threads to explore a shared search tree. These workers communicate objective bounds and simple decision nogoods relating to the shared prefix of the tree, and will avoid exploring the same subtrees as one another.
optional int32 shared_tree_num_workers = 235 [default = 0];
Definition at line 27491 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearSharedTreeSplitStrategy | ( | ) |
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];
Definition at line 27721 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearSharedTreeWorkerObjectiveSplitProbability | ( | ) |
After their assigned prefix, shared tree workers will branch on the objective with this probability. Higher numbers cause the shared tree search to focus on improving the lower bound over finding primal solutions.
optional double shared_tree_worker_objective_split_probability = 237 [default = 0.5];
Definition at line 27611 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearShareLevelZeroBounds | ( | ) |
Allows sharing of the bounds of modified variables at level 0.
optional bool share_level_zero_bounds = 114 [default = true];
Definition at line 23885 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearShareObjectiveBounds | ( | ) |
Allows objective sharing between workers.
optional bool share_objective_bounds = 113 [default = true];
Definition at line 23829 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearShavingSearchDeterministicTime | ( | ) |
Specifies the amount of deterministic time spent of each try at shaving a bound in the shaving search.
optional double shaving_search_deterministic_time = 205 [default = 0.001];
Definition at line 26223 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearSolutionPoolSize | ( | ) |
Size of the top-n different solutions kept by the solver. This parameter must be > 0. Currently this only impact the "base" solution chosen for a LNS fragment.
optional int32 solution_pool_size = 193 [default = 3];
Definition at line 28461 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearStopAfterFirstSolution | ( | ) |
For an optimization problem, stop the solver as soon as we have a solution.
optional bool stop_after_first_solution = 98 [default = false];
Definition at line 28241 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearStopAfterPresolve | ( | ) |
Mainly used when improving the presolver. When true, stops the solver after the presolve is complete (or after loading and root level propagation).
optional bool stop_after_presolve = 149 [default = false];
Definition at line 28301 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearStopAfterRootPropagation | ( | ) |
optional bool stop_after_root_propagation = 252 [default = false];
Definition at line 28341 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearStrategyChangeIncreaseRatio | ( | ) |
The parameter num_conflicts_before_strategy_changes is increased by that much after each strategy change.
optional double strategy_change_increase_ratio = 69 [default = 0];
Definition at line 19295 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearSubsolverParams | ( | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23520 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearSubsolvers | ( | ) |
In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters. This field indicates the names of the parameters that are used in multithread. See cp_model_search.cc to see a list of the names and the default value (if left empty) that looks like: - default_lp (linearization_level:1) - fixed (only if fixed search specified or scheduling) - no_lp (linearization_level:0) - max_lp (linearization_level:2) - pseudo_costs (only if objective, change search heuristic) - reduced_costs (only if objective, change search heuristic) - quick_restart (kind of probing) - quick_restart_no_lp (kind of probing with linearization_level:0) - lb_tree_search (to improve lower bound, MIP like tree search) - probing (continuous probing and shaving) Also, note that some set of parameters will be ignored if they do not make sense. For instance if there is no objective, pseudo_cost or reduced_cost search will be ignored. Core based search will only work if the objective has many terms. If there is no fixed strategy fixed will be ignored. And so on. The order is important, as only the first usable "num_workers - min_num_lns_workers" subsolvers will be scheduled. You can see in the log which one are selected for a given run. All the others will be LNS if there is an objective, or randomized SAT search for pure satisfiability problems.
repeated string subsolvers = 207;
Definition at line 22918 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearSubsumptionDuringConflictAnalysis | ( | ) |
At a really low cost, during the 1-UIP conflict computation, it is easy to detect if some of the involved reasons are subsumed by the current conflict. When this is true, such clauses are detached and later removed from the problem.
optional bool subsumption_during_conflict_analysis = 56 [default = true];
Definition at line 17769 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearSymmetryLevel | ( | ) |
Whether we try to automatically detect the symmetries in a model and exploit them. Currently, at level 1 we detect them in presolve and try to fix Booleans. At level 2, we also do some form of dynamic symmetry breaking during search.
optional int32 symmetry_level = 183 [default = 2];
Definition at line 29623 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearTableCompressionLevel | ( | ) |
How much we try to "compress" a table constraint. Compressing more leads to less Booleans and faster propagation but can reduced the quality of the lp relaxation. Values goes from 0 to 3 where we always try to fully compress a table. At 2, we try to automatically decide if it is worth it.
optional int32 table_compression_level = 217 [default = 2];
Definition at line 21335 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearTestFeasibilityJump | ( | ) |
Disable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.
optional bool test_feasibility_jump = 240 [default = false];
Definition at line 26815 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseAbslRandom | ( | ) |
optional bool use_absl_random = 180 [default = false];
Definition at line 19967 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseAreaEnergeticReasoningInNoOverlap2D | ( | ) |
When this is true, the no_overlap_2d constraint is reinforced with an energetic reasoning that uses an area-based energy. This can be combined with the two other overlap heuristics above.
optional bool use_area_energetic_reasoning_in_no_overlap_2d = 271 [default = false];
Definition at line 25573 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseBlockingRestart | ( | ) |
Block a moving restart algorithm if the trail size of the current conflict is greater than the multiplier times the moving average of the trail size at the previous conflicts.
optional bool use_blocking_restart = 64 [default = false];
Definition at line 19091 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseCombinedNoOverlap | ( | ) |
This can be beneficial if there is a lot of no-overlap constraints but a relatively low number of different intervals in the problem. Like 1000 intervals, but 1M intervals in the no-overlap constraints covering them.
optional bool use_combined_no_overlap = 133 [default = false];
Definition at line 29123 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseDisjunctiveConstraintInCumulative | ( | ) |
When this is true, the cumulative constraint is reinforced with propagators from the disjunctive constraint to improve the inference on a set of tasks that are disjunctive at the root of the problem. This additional level supplements the default level of reasoning. Propagators of the cumulative constraint will not be used at all if all the tasks are disjunctive at root node. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_disjunctive_constraint_in_cumulative = 80 [default = true];
Definition at line 25373 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseDualSchedulingHeuristics | ( | ) |
When set, it activates a few scheduling parameters to improve the lower bound of scheduling problems. This is only effective with multiple workers as it modifies the reduced_cost, lb_tree_search, and probing workers.
optional bool use_dual_scheduling_heuristics = 214 [default = true];
Definition at line 25701 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseDynamicPrecedenceInCumulative | ( | ) |
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];
Definition at line 24945 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseDynamicPrecedenceInDisjunctive | ( | ) |
Whether we try to branch on decision "interval A before interval B" rather than on intervals bounds. This usually works better, but slow down a bit the time to find the first solution. These parameters are still EXPERIMENTAL, the result should be correct, but it some corner cases, they can cause some failing CHECK in the solver.
optional bool use_dynamic_precedence_in_disjunctive = 263 [default = false];
Definition at line 24905 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseEnergeticReasoningInNoOverlap2D | ( | ) |
When this is true, the no_overlap_2d constraint is reinforced with energetic reasoning. This additional level supplements the default level of reasoning.
optional bool use_energetic_reasoning_in_no_overlap_2d = 213 [default = false];
Definition at line 25509 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseErwaHeuristic | ( | ) |
Whether we use the ERWA (Exponential Recency Weighted Average) heuristic as described in "Learning Rate Based Branching Heuristic for SAT solvers", J.H.Liang, V. Ganesh, P. Poupart, K.Czarnecki, SAT 2016.
optional bool use_erwa_heuristic = 75 [default = false];
Definition at line 17473 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseExactLpReason | ( | ) |
The solver usually exploit the LP relaxation of a model. If this option is true, then whatever is infered by the LP will be used like an heuristic to compute EXACT propagation on the IP. So with this option, there is no numerical imprecision issues.
optional bool use_exact_lp_reason = 109 [default = true];
Definition at line 29059 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseExtendedProbing | ( | ) |
Use extended probing (probe bool_or, at_most_one, exactly_one).
optional bool use_extended_probing = 269 [default = true];
Definition at line 26047 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseFeasibilityJump | ( | ) |
Parameters for an heuristic similar to the one described in the paper: "Feasibility Jump: an LP-free Lagrangian MIP heuristic", Bjørnar Luteberget, Giorgio Sartor, 2023, Mathematical Programming Computation.
optional bool use_feasibility_jump = 265 [default = true];
Definition at line 26755 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseFeasibilityPump | ( | ) |
Adds a feasibility pump subsolver along with lns subsolvers.
optional bool use_feasibility_pump = 164 [default = true];
Definition at line 28573 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseHardPrecedencesInCumulative | ( | ) |
If true, detect and create constraint for integer variable that are "after" a set of intervals in the same cumulative constraint. Experimental: by default we just use "direct" precedences. If exploit_all_precedences is true, we explore the full precedence graph. This assumes we have a DAG otherwise it fails.
optional bool use_hard_precedences_in_cumulative = 215 [default = false];
Definition at line 25241 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseImpliedBounds | ( | ) |
Stores and exploits "implied-bounds" in the solver. That is, relations of the form literal => (var >= bound). This is currently used to derive stronger cuts.
optional bool use_implied_bounds = 144 [default = true];
Definition at line 29311 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseLbRelaxLns | ( | ) |
Turns on neighborhood generator based on local branching LP. Based on Huang et al., "Local Branching Relaxation Heuristics for Integer Linear Programs", 2023.
optional bool use_lb_relax_lns = 255 [default = false];
Definition at line 28637 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseLnsOnly | ( | ) |
LNS parameters.
optional bool use_lns_only = 101 [default = false];
Definition at line 28397 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseObjectiveLbSearch | ( | ) |
If true, search will search in ascending max objective value (when minimizing) starting from the lower bound of the objective.
optional bool use_objective_lb_search = 228 [default = false];
Definition at line 26283 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseObjectiveShavingSearch | ( | ) |
This search differs from the previous search as it will not use assumptions to bound the objective, and it will recreate a full model with the hardcoded objective value.
optional bool use_objective_shaving_search = 253 [default = false];
Definition at line 26347 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseOptimizationHints | ( | ) |
For an optimization problem, whether we follow some hints in order to find a better first solution. For a variable with hint, the solver will always try to follow the hint. It will revert to the variable_branching default otherwise.
optional bool use_optimization_hints = 35 [default = true];
Definition at line 24189 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseOptionalVariables | ( | ) |
If true, we automatically detect variables whose constraint are always enforced by the same literal and we mark them as optional. This allows to propagate them as if they were present in some situation. TODO(user): This is experimental and seems to lead to wrong optimal in some situation. It should however gives correct solutions. Fix.
optional bool use_optional_variables = 108 [default = false];
Definition at line 28991 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseOverloadCheckerInCumulative | ( | ) |
When this is true, the cumulative constraint is reinforced with overload checking, i.e., an additional level of reasoning based on energy. This additional level supplements the default level of reasoning as well as timetable edge finding. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_overload_checker_in_cumulative = 78 [default = false];
Definition at line 25025 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUsePbResolution | ( | ) |
Whether to use pseudo-Boolean resolution to analyze a conflict. Note that this option only make sense if your problem is modelized using pseudo-Boolean constraints. If you only have clauses, this shouldn't change anything (except slow the solver down).
optional bool use_pb_resolution = 43 [default = false];
Definition at line 20383 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUsePhaseSaving | ( | ) |
If this is true, then the polarity of a variable will be the last value it was assigned to, or its default polarity if it was never assigned since the call to ResetDecisionHeuristic(). Actually, we use a newer version where we follow the last value in the longest non-conflicting partial assignment in the current phase. This is called 'literal phase saving'. For details see 'A Lightweight Component Caching Scheme for Satisfiability Solvers' K. Pipatsrisawat and A.Darwiche, In 10th International Conference on Theory and Applications of Satisfiability Testing, 2007.
optional bool use_phase_saving = 44 [default = true];
Definition at line 17209 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUsePrecedencesInDisjunctiveConstraint | ( | ) |
When this is true, then a disjunctive constraint will try to use the precedence relations between time intervals to propagate their bounds further. For instance if task A and B are both before C and task A and B are in disjunction, then we can deduce that task C must start after duration(A) + duration(B) instead of simply max(duration(A), duration(B)), provided that the start time for all task was currently zero. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_precedences_in_disjunctive_constraint = 74 [default = true];
Definition at line 24701 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseProbingSearch | ( | ) |
If true, search will continuously probe Boolean variables, and integer variable bounds. This parameter is set to true in parallel on the probing worker.
optional bool use_probing_search = 176 [default = false];
Definition at line 25991 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseRinsLns | ( | ) |
Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];
Definition at line 28517 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseSatInprocessing | ( | ) |
Enable or disable "inprocessing" which is some SAT presolving done at each restart to the root level.
optional bool use_sat_inprocessing = 163 [default = true];
Definition at line 22167 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseSharedTreeSearch | ( | ) |
Set on shared subtree workers. Users should not set this directly.
optional bool use_shared_tree_search = 236 [default = false];
Definition at line 27547 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseShavingInProbingSearch | ( | ) |
Add a shaving phase (where the solver tries to prove that the lower or upper bound of a variable are infeasible) to the probing search.
optional bool use_shaving_in_probing_search = 204 [default = true];
Definition at line 26163 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseStrongPropagationInDisjunctive | ( | ) |
Enable stronger and more expensive propagation on no_overlap constraint.
optional bool use_strong_propagation_in_disjunctive = 230 [default = false];
Definition at line 24829 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseTimetableEdgeFindingInCumulative | ( | ) |
When this is true, the cumulative constraint is reinforced with timetable edge finding, i.e., an additional level of reasoning based on the conjunction of energy and mandatory parts. This additional level supplements the default level of reasoning as well as overload_checker. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_timetable_edge_finding_in_cumulative = 79 [default = false];
Definition at line 25105 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearUseTimetablingInNoOverlap2D | ( | ) |
When this is true, the no_overlap_2d constraint is reinforced with propagators from the cumulative constraints. It consists of ignoring the position of rectangles in one position and projecting the no_overlap_2d on the other dimension to create a cumulative constraint. This is done on both axis. This additional level supplements the default level of reasoning.
optional bool use_timetabling_in_no_overlap_2d = 200 [default = false];
Definition at line 25445 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearVariableActivityDecay | ( | ) |
Each time a conflict is found, the activities of some variables are increased by one. Then, the activity of all variables are multiplied by variable_activity_decay. To implement this efficiently, the activity of all the variables is not decayed at each conflict. Instead, the activity increment is multiplied by 1 / decay. When an activity reach max_variable_activity_value, all the activity are multiplied by 1 / max_variable_activity_value.
optional double variable_activity_decay = 15 [default = 0.8];
Definition at line 18273 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearViolationLsCompoundMoveProbability | ( | ) |
Probability of using compound move search each restart. TODO(user): Add reference to paper when published.
optional double violation_ls_compound_move_probability = 259 [default = 0.5];
Definition at line 27419 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clearViolationLsPerturbationPeriod | ( | ) |
How long violation_ls should wait before perturbating a solution.
optional int32 violation_ls_perturbation_period = 249 [default = 100];
Definition at line 27359 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.clone | ( | ) |
Definition at line 14800 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getAbsoluteGapLimit | ( | ) |
Stop the search when the gap between the best feasible objective (O) and our best objective bound (B) is smaller than a limit. The exact definition is: - Absolute: abs(O - B) - Relative: abs(O - B) / max(1, abs(O)). Important: The relative gap depends on the objective offset! If you artificially shift the objective, you will get widely different value of the relative gap. Note that if the gap is reached, the search status will be OPTIMAL. But one can check the best objective bound to see the actual gap. If the objective is integer, then any absolute gap < 1 will lead to a true optimal. If the objective is floating point, a gap of zero make little sense so is is why we use a non-zero default value. At the end of the search, we will display a warning if OPTIMAL is reported yet the gap is greater than this absolute gap.
optional double absolute_gap_limit = 159 [default = 0.0001];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19638 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getAddCgCuts | ( | ) |
Whether we generate and add Chvatal-Gomory cuts to the LP at root node. Note that for now, this is not heavily tuned.
optional bool add_cg_cuts = 117 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30238 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getAddCliqueCuts | ( | ) |
Whether we generate clique cuts from the binary implication graph. Note that as the search goes on, this graph will contains new binary clauses learned by the SAT engine.
optional bool add_clique_cuts = 172 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30420 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getAddLinMaxCuts | ( | ) |
For the lin max constraints, generates the cuts described in "Strong mixed-integer programming formulations for trained neural networks" by Ross Anderson et. (https://arxiv.org/pdf/1811.01988.pdf)
optional bool add_lin_max_cuts = 152 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30608 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getAddLpConstraintsLazily | ( | ) |
If true, we start by an empty LP, and only add constraints not satisfied by the current LP solution batch by batch. A constraint that is only added like this is known as a "lazy" constraint in the literature, except that we currently consider all constraints as lazy here.
optional bool add_lp_constraints_lazily = 112 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30758 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getAddMirCuts | ( | ) |
Whether we generate MIR cuts at root node. Note that for now, this is not heavily tuned.
optional bool add_mir_cuts = 120 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30298 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getAddObjectiveCut | ( | ) |
When the LP objective is fractional, do we add the cut that forces the linear objective expression to be greater or equal to this fractional value rounded up? We can always do that since our objective is integer, and combined with MIR heuristic to reduce the coefficient of such cut, it can help.
optional bool add_objective_cut = 197 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30172 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getAddRltCuts | ( | ) |
Whether we generate RLT cuts. This is still experimental but can help on binary problem with a lot of clauses of size 3.
optional bool add_rlt_cuts = 279 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30482 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getAddZeroHalfCuts | ( | ) |
Whether we generate Zero-Half cuts at root node. Note that for now, this is not heavily tuned.
optional bool add_zero_half_cuts = 169 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30358 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getAlsoBumpVariablesInConflictReasons | ( | ) |
When this is true, then the variables that appear in any of the reason of the variables in a conflict have their activity bumped. This is addition to the variables in the conflict, and the one that were used during conflict resolution.
optional bool also_bump_variables_in_conflict_reasons = 77 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17584 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getAtMostOneMaxExpansionSize | ( | ) |
All at_most_one constraints with a size <= param will be replaced by a quadratic number of binary implications.
optional int32 at_most_one_max_expansion_size = 270 [default = 3];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29154 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getAutoDetectGreaterThanAtLeastOneOf | ( | ) |
If true, then the precedences propagator try to detect for each variable if it has a set of "optional incoming arc" for which at least one of them is present. This is usually useful to have but can be slow on model with a lot of precedence.
optional bool auto_detect_greater_than_at_least_one_of = 95 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28152 of file SatParameters.java.
com.google.ortools.sat.SatParameters.BinaryMinizationAlgorithm com.google.ortools.sat.SatParameters.Builder.getBinaryMinimizationAlgorithm | ( | ) |
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17679 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getBinarySearchNumConflicts | ( | ) |
If non-negative, perform a binary search on the objective variable in order to find an [min, max] interval outside of which the solver proved unsat/sat under this amount of conflict. This can quickly reduce the objective domain on some problems.
optional int32 binary_search_num_conflicts = 99 [default = -1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26582 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getBlockingRestartMultiplier | ( | ) |
optional double blocking_restart_multiplier = 66 [default = 1.4];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19152 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getBlockingRestartWindowSize | ( | ) |
optional int32 blocking_restart_window_size = 65 [default = 5000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19112 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getBooleanEncodingLevel | ( | ) |
A non-negative level indicating how much we should try to fully encode Integer variables as Boolean.
optional int32 boolean_encoding_level = 107 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29842 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getCatchSigintSignal | ( | ) |
Indicates if the CP-SAT layer should catch Control-C (SIGINT) signals when calling solve. If set, catching the SIGINT signal will terminate the search gracefully, as if a time limit was reached.
optional bool catch_sigint_signal = 135 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29216 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getClauseActivityDecay | ( | ) |
Clause activity parameters (same effect as the one on the variables).
optional double clause_activity_decay = 17 [default = 0.999];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18494 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getClauseCleanupLbdBound | ( | ) |
All the clauses with a LBD (literal blocks distance) lower or equal to this parameters will always be kept.
optional int32 clause_cleanup_lbd_bound = 59 [default = 5];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18022 of file SatParameters.java.
com.google.ortools.sat.SatParameters.ClauseOrdering com.google.ortools.sat.SatParameters.Builder.getClauseCleanupOrdering | ( | ) |
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18071 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getClauseCleanupPeriod | ( | ) |
Trigger a cleanup when this number of "deletable" clauses is learned.
optional int32 clause_cleanup_period = 11 [default = 10000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17798 of file SatParameters.java.
com.google.ortools.sat.SatParameters.ClauseProtection com.google.ortools.sat.SatParameters.Builder.getClauseCleanupProtection | ( | ) |
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17969 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getClauseCleanupRatio | ( | ) |
During a cleanup, if clause_cleanup_target is 0, we will delete the clause_cleanup_ratio of "deletable" clauses instead of aiming for a fixed target of clauses to keep.
optional double clause_cleanup_ratio = 190 [default = 0.5];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17918 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getClauseCleanupTarget | ( | ) |
During a cleanup, we will always keep that number of "deletable" clauses. Note that this doesn't include the "protected" clauses.
optional int32 clause_cleanup_target = 13 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17856 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getConvertIntervals | ( | ) |
Temporary flag util the feature is more mature. This convert intervals to the newer proto format that support affine start/var/end instead of just variables.
optional bool convert_intervals = 177 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29524 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getCoreMinimizationLevel | ( | ) |
If positive, we spend some effort on each core: - At level 1, we use a simple heuristic to try to minimize an UNSAT core. - At level 2, we use propagation to minimize the core but also identify literal in at most one relationship in this core.
optional int32 core_minimization_level = 50 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24224 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getCountAssumptionLevelsInLbd | ( | ) |
Whether or not the assumption levels are taken into account during the LBD computation. According to the reference below, not counting them improves the solver in some situation. Note that this only impact solves under assumptions. Gilles Audemard, Jean-Marie Lagniez, Laurent Simon, "Improving Glucose for Incremental SAT Solving with Assumptions: Application to MUS Extraction" Theory and Applications of Satisfiability Testing - SAT 2013, Lecture Notes in Computer Science Volume 7962, 2013, pp 309-317.
optional bool count_assumption_levels_in_lbd = 49 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20496 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getCoverOptimization | ( | ) |
If true, when the max-sat algo find a core, we compute the minimal number of literals in the core that needs to be true to have a feasible solution. This is also called core exhaustion in more recent max-SAT papers.
optional bool cover_optimization = 89 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24350 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getCpModelPresolve | ( | ) |
Whether we presolve the cp_model before solving it.
optional bool cp_model_presolve = 86 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21052 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getCpModelProbingLevel | ( | ) |
How much effort do we spend on probing. 0 disables it completely.
optional int32 cp_model_probing_level = 110 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21108 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getCpModelUseSatPresolve | ( | ) |
Whether we also use the sat presolve when cp_model_presolve is true.
optional bool cp_model_use_sat_presolve = 93 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21164 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getCutActiveCountDecay | ( | ) |
optional double cut_active_count_decay = 156 [default = 0.8];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31136 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getCutCleanupTarget | ( | ) |
Target number of constraints to remove during cleanup.
optional int32 cut_cleanup_target = 157 [default = 1000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31184 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getCutLevel | ( | ) |
Control the global cut effort. Zero will turn off all cut. For now we just have one level. Note also that most cuts are only used at linearization level >= 2.
optional int32 cut_level = 196 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30044 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getCutMaxActiveCountValue | ( | ) |
These parameters are similar to sat clause management activity parameters. They are effective only if the number of generated cuts exceed the storage limit. Default values are based on a few experiments on miplib instances.
optional double cut_max_active_count_value = 155 [default = 10000000000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31084 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getDebugCrashOnBadHint | ( | ) |
Crash if we do not manage to complete the hint into a full solution.
optional bool debug_crash_on_bad_hint = 195 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24094 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getDebugMaxNumPresolveOperations | ( | ) |
If positive, try to stop just after that many presolve rules have been applied. This is mainly useful for debugging presolve.
optional int32 debug_max_num_presolve_operations = 151 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24036 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getDebugPostsolveWithFullSolver | ( | ) |
We have two different postsolve code. The default one should be better and it allows for a more powerful presolve, but it can be useful to postsolve using the full solver instead.
optional bool debug_postsolve_with_full_solver = 162 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23974 of file SatParameters.java.
com.google.ortools.sat.SatParameters com.google.ortools.sat.SatParameters.Builder.getDefaultInstanceForType | ( | ) |
Definition at line 13767 of file SatParameters.java.
java.lang.String com.google.ortools.sat.SatParameters.Builder.getDefaultRestartAlgorithms | ( | ) |
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18750 of file SatParameters.java.
com.google.protobuf.ByteString com.google.ortools.sat.SatParameters.Builder.getDefaultRestartAlgorithmsBytes | ( | ) |
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18769 of file SatParameters.java.
|
static |
Definition at line 13481 of file SatParameters.java.
com.google.protobuf.Descriptors.Descriptor com.google.ortools.sat.SatParameters.Builder.getDescriptorForType | ( | ) |
Definition at line 13762 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getDetectLinearizedProduct | ( | ) |
Infer products of Boolean or of Boolean time IntegerVariable from the linear constrainst in the problem. This can be used in some cuts, altough for now we don't really exploit it.
optional bool detect_linearized_product = 277 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31616 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getDetectTableWithCost | ( | ) |
If true, we detect variable that are unique to a table constraint and only there to encode a cost on each tuple. This is usually the case when a WCSP (weighted constraint program) is encoded into CP-SAT format. This can lead to a dramatic speed-up for such problems but is still experimental at this point.
optional bool detect_table_with_cost = 216 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21230 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getDisableConstraintExpansion | ( | ) |
If true, it disable all constraint expansion. This should only be used to test the presolve of expanded constraints.
optional bool disable_constraint_expansion = 181 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21486 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getDiversifyLnsParams | ( | ) |
If true, registers more lns subsolvers with different parameters.
optional bool diversify_lns_params = 137 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28708 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getEncodeComplexLinearConstraintWithInteger | ( | ) |
Linear constraint with a complex right hand side (more than a single interval) need to be expanded, there is a couple of way to do that.
optional bool encode_complex_linear_constraint_with_integer = 223 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21546 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getEnumerateAllSolutions | ( | ) |
Whether we enumerate all solutions of a problem without objective. Note that setting this to true automatically disable some presolve reduction that can remove feasible solution. That is it has the same effect as setting keep_all_feasible_solutions_in_presolve. TODO(user): Do not do that and let the user choose what behavior is best by setting keep_all_feasible_solutions_in_presolve ?
optional bool enumerate_all_solutions = 87 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27762 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getExpandAlldiffConstraints | ( | ) |
If true, expand all_different constraints that are not permutations. Permutations (#Variables = #Values) are always expanded.
optional bool expand_alldiff_constraints = 170 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21366 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getExpandReservoirConstraints | ( | ) |
If true, expand the reservoir constraints by creating booleans for all possible precedences between event and encoding the constraint.
optional bool expand_reservoir_constraints = 182 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21426 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getExploitAllLpSolution | ( | ) |
If true and the Lp relaxation of the problem has a solution, try to exploit it. This is same as above except in this case the lp solution might not be an integer solution.
optional bool exploit_all_lp_solution = 116 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31372 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getExploitAllPrecedences | ( | ) |
optional bool exploit_all_precedences = 220 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25262 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getExploitBestSolution | ( | ) |
When branching on a variable, follow the last best solution value.
optional bool exploit_best_solution = 130 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31432 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getExploitIntegerLpSolution | ( | ) |
If true and the Lp relaxation of the problem has an integer optimal solution, try to exploit it. Note that since the LP relaxation may not contain all the constraints, such a solution is not necessarily a solution of the full problem.
optional bool exploit_integer_lp_solution = 94 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31306 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getExploitObjective | ( | ) |
When branching an a variable that directly affect the objective, branch on the value that lead to the best objective first.
optional bool exploit_objective = 131 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31554 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getExploitRelaxationSolution | ( | ) |
When branching on a variable, follow the last best relaxation solution value. We use the relaxation with the tightest bound on the objective as the best relaxation solution.
optional bool exploit_relaxation_solution = 161 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31492 of file SatParameters.java.
java.lang.String com.google.ortools.sat.SatParameters.Builder.getExtraSubsolvers | ( | int | index | ) |
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;
index | The index of the element to return. |
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23014 of file SatParameters.java.
com.google.protobuf.ByteString com.google.ortools.sat.SatParameters.Builder.getExtraSubsolversBytes | ( | int | index | ) |
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;
index | The index of the value to return. |
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23028 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getExtraSubsolversCount | ( | ) |
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23001 of file SatParameters.java.
com.google.protobuf.ProtocolStringList com.google.ortools.sat.SatParameters.Builder.getExtraSubsolversList | ( | ) |
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22988 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getFeasibilityJumpDecay | ( | ) |
On each restart, we randomly choose if we use decay (with this parameter) or no decay.
optional double feasibility_jump_decay = 242 [default = 0.95];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26846 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getFeasibilityJumpEnableRestarts | ( | ) |
When stagnating, feasibility jump will either restart from a default solution (with some possible randomization), or randomly pertubate the current solution. This parameter selects the first option.
optional bool feasibility_jump_enable_restarts = 250 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27148 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getFeasibilityJumpLinearizationLevel | ( | ) |
How much do we linearize the problem in the local search code.
optional int32 feasibility_jump_linearization_level = 257 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26904 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getFeasibilityJumpMaxExpandedConstraintSize | ( | ) |
Maximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion.
optional int32 feasibility_jump_max_expanded_constraint_size = 264 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27210 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getFeasibilityJumpRestartFactor | ( | ) |
This is a factor that directly influence the work before each restart. Setting this to zero disable restart, and increasing it lead to longer restarts.
optional int32 feasibility_jump_restart_factor = 258 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26964 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getFeasibilityJumpVarPerburbationRangeRatio | ( | ) |
Max distance between the default value and the pertubated value relative to the range of the domain of the variable.
optional double feasibility_jump_var_perburbation_range_ratio = 248 [default = 0.2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27086 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getFeasibilityJumpVarRandomizationProbability | ( | ) |
Probability for a variable to have a non default value upon restarts or perturbations.
optional double feasibility_jump_var_randomization_probability = 247 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27026 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getFillAdditionalSolutionsInResponse | ( | ) |
If true, the final response addition_solutions field will be filled with all solutions from our solutions pool. Note that if both this field and enumerate_all_solutions is true, we will copy to the pool all of the solution found. So if solution_pool_size is big enough, you can get all solutions this way instead of using the solution callback. Note that this only affect the "final" solution, not the one passed to the solution callbacks.
optional bool fill_additional_solutions_in_response = 194 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28004 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getFillTightenedDomainsInResponse | ( | ) |
If true, add information about the derived variable domains to the CpSolverResponse. It is an option because it makes the response slighly bigger and there is a bit more work involved during the postsolve to construct it, but it should still have a low overhead. See the tightened_variables field in CpSolverResponse for more details.
optional bool fill_tightened_domains_in_response = 132 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27922 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getFindBigLinearOverlap | ( | ) |
Try to find large "rectangle" in the linear constraint matrix with identical lines. If such rectangle is big enough, we can introduce a new integer variable corresponding to the common expression and greatly reduce the number of non-zero.
optional bool find_big_linear_overlap = 234 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22074 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getFindMultipleCores | ( | ) |
Whether we try to find more independent cores for a given set of assumptions in the core based max-SAT algorithms.
optional bool find_multiple_cores = 84 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24288 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getFixVariablesToTheirHintedValue | ( | ) |
If true, variables appearing in the solution hints will be fixed to their hinted value.
optional bool fix_variables_to_their_hinted_value = 192 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25898 of file SatParameters.java.
com.google.ortools.sat.SatParameters.FPRoundingMethod com.google.ortools.sat.SatParameters.Builder.getFpRounding | ( | ) |
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28657 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getGlucoseDecayIncrement | ( | ) |
optional double glucose_decay_increment = 23 [default = 0.01];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18406 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getGlucoseDecayIncrementPeriod | ( | ) |
optional int32 glucose_decay_increment_period = 24 [default = 5000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18446 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getGlucoseMaxDecay | ( | ) |
The activity starts at 0.8 and increment by 0.01 every 5000 conflicts until 0.95. This "hack" seems to work well and comes from: Glucose 2.3 in the SAT 2013 Competition - SAT Competition 2013 http://edacc4.informatik.uni-ulm.de/SC13/solver-description-download/136
optional double glucose_max_decay = 22 [default = 0.95];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18350 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getHintConflictLimit | ( | ) |
Conflict limit used in the phase that exploit the solution hint.
optional int32 hint_conflict_limit = 153 [default = 10];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25772 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getIgnoreNames | ( | ) |
If true, we don't keep names in our internal copy of the user given model.
optional bool ignore_names = 202 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21940 of file SatParameters.java.
java.lang.String com.google.ortools.sat.SatParameters.Builder.getIgnoreSubsolvers | ( | int | index | ) |
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem.
repeated string ignore_subsolvers = 209;
index | The index of the element to return. |
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23169 of file SatParameters.java.
com.google.protobuf.ByteString com.google.ortools.sat.SatParameters.Builder.getIgnoreSubsolversBytes | ( | int | index | ) |
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem.
repeated string ignore_subsolvers = 209;
index | The index of the value to return. |
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23183 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getIgnoreSubsolversCount | ( | ) |
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem.
repeated string ignore_subsolvers = 209;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23156 of file SatParameters.java.
com.google.protobuf.ProtocolStringList com.google.ortools.sat.SatParameters.Builder.getIgnoreSubsolversList | ( | ) |
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem.
repeated string ignore_subsolvers = 209;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23143 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getInferAllDiffs | ( | ) |
Run a max-clique code amongst all the x != y we can find and try to infer set of variables that are all different. This allows to close neos16.mps for instance. Note that we only run this code if there is no all_diff already in the model so that if a user want to add some all_diff, we assume it is well done and do not try to add more.
optional bool infer_all_diffs = 233 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22004 of file SatParameters.java.
com.google.ortools.sat.SatParameters.Polarity com.google.ortools.sat.SatParameters.Builder.getInitialPolarity | ( | ) |
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17091 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getInitialVariablesActivity | ( | ) |
The initial value of the variables activity. A non-zero value only make sense when use_erwa_heuristic is true. Experiments with a value of 1e-2 together with the ERWA heuristic showed slighthly better result than simply using zero. The idea is that when the "learning rate" of a variable becomes lower than this value, then we prefer to branch on never explored before variables. This is not in the ERWA paper.
optional double initial_variables_activity = 76 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17512 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getInprocessingDtimeRatio | ( | ) |
Proportion of deterministic time we should spend on inprocessing. At each "restart", if the proportion is below this ratio, we will do some inprocessing, otherwise, we skip it for this restart.
optional double inprocessing_dtime_ratio = 273 [default = 0.2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22200 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getInprocessingMinimizationDtime | ( | ) |
Parameters for an heuristic similar to the one described in "An effective learnt clause minimization approach for CDCL Sat Solvers", https://www.ijcai.org/proceedings/2017/0098.pdf This is the amount of dtime we should spend on this technique during each inprocessing phase. The minimization technique is the same as the one used to minimize core in max-sat. We also minimize problem clauses and not just the learned clause that we keep forever like in the paper.
optional double inprocessing_minimization_dtime = 275 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22334 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getInprocessingProbingDtime | ( | ) |
The amount of dtime we should spend on probing for each inprocessing round.
optional double inprocessing_probing_dtime = 274 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22260 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getInstantiateAllVariables | ( | ) |
If true, the solver will add a default integer branching strategy to the already defined search strategy. If not, some variable might still not be fixed at the end of the search. For now we assume these variable can just be set to their lower bound.
optional bool instantiate_all_variables = 106 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28084 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getInterleaveBatchSize | ( | ) |
optional int32 interleave_batch_size = 134 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23754 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getInterleaveSearch | ( | ) |
Experimental. If this is true, then we interleave all our major search strategy and distribute the work amongst num_workers. The search is deterministic (independently of num_workers!), and we schedule and wait for interleave_batch_size task to be completed before synchronizing and scheduling the next batch of tasks.
optional bool interleave_search = 136 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23696 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getKeepAllFeasibleSolutionsInPresolve | ( | ) |
If true, we disable the presolve reductions that remove feasible solutions from the search space. Such solution are usually dominated by a "better" solution that is kept, but depending on the situation, we might want to keep all solutions. A trivial example is when a variable is unused. If this is true, then the presolve will not fix it to an arbitrary value and it will stay in the search space.
optional bool keep_all_feasible_solutions_in_presolve = 173 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27844 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getLinearizationLevel | ( | ) |
A non-negative level indicating the type of constraints we consider in the LP relaxation. At level zero, no LP relaxation is used. At level 1, only the linear constraint and full encoding are added. At level 2, we also add all the Boolean constraints.
optional int32 linearization_level = 90 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29778 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getLinearSplitSize | ( | ) |
Linear constraints that are not pseudo-Boolean and that are longer than this size will be split into sqrt(size) intermediate sums in order to have faster propation in the CP engine.
optional int32 linear_split_size = 256 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29712 of file SatParameters.java.
java.lang.String com.google.ortools.sat.SatParameters.Builder.getLogPrefix | ( | ) |
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20126 of file SatParameters.java.
com.google.protobuf.ByteString com.google.ortools.sat.SatParameters.Builder.getLogPrefixBytes | ( | ) |
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20149 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getLogSearchProgress | ( | ) |
Whether the solver should log the search progress. This is the maing logging parameter and if this is false, none of the logging (callbacks, log_to_stdout, log_to_response, ...) will do anything.
optional bool log_search_progress = 41 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20000 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getLogSubsolverStatistics | ( | ) |
Whether the solver should display per sub-solver search statistics. This is only useful is log_search_progress is set to true, and if the number of search workers is > 1. Note that in all case we display a bit of stats with one line per subsolver.
optional bool log_subsolver_statistics = 189 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20066 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getLogToResponse | ( | ) |
Log to response proto.
optional bool log_to_response = 187 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20288 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getLogToStdout | ( | ) |
Log to stdout.
optional bool log_to_stdout = 186 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20232 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getLpDualTolerance | ( | ) |
optional double lp_dual_tolerance = 267 [default = 1e-07];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29472 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getLpPrimalTolerance | ( | ) |
The internal LP tolerances used by CP-SAT. These applies to the internal and scaled problem. If the domains of your variables are large it might be good to use lower tolerances. If your problem is binary with low coefficients, it might be good to use higher ones to speed-up the lp solves.
optional double lp_primal_tolerance = 266 [default = 1e-07];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29416 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMaxAllDiffCutSize | ( | ) |
Cut generator for all diffs can add too many cuts for large all_diff constraints. This parameter restricts the large all_diff constraints to have a cut generator.
optional int32 max_all_diff_cut_size = 148 [default = 64];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30544 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMaxClauseActivityValue | ( | ) |
optional double max_clause_activity_value = 18 [default = 1e+20];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18542 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMaxConsecutiveInactiveCount | ( | ) |
If a constraint/cut in LP is not active for that many consecutive OPTIMAL solves, remove it from the LP. Note that it might be added again later if it become violated by the current LP solution.
optional int32 max_consecutive_inactive_count = 121 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31020 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMaxCutRoundsAtLevelZero | ( | ) |
Max number of time we perform cut generation and resolve the LP at level 0.
optional int32 max_cut_rounds_at_level_zero = 154 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30960 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMaxDeterministicTime | ( | ) |
Maximum time allowed in deterministic time to solve a problem. The deterministic time should be correlated with the real time used by the solver, the time unit being as close as possible to a second.
optional double max_deterministic_time = 67 [default = inf];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19388 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMaxDomainSizeWhenEncodingEqNeqConstraints | ( | ) |
When loading a*x + b*y ==/!= c when x and y are both fully encoded. The solver may decide to replace the linear equation by a set of clauses. This is triggered if the sizes of the domains of x and y are below the threshold.
optional int32 max_domain_size_when_encoding_eq_neq_constraints = 191 [default = 16];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29906 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMaxIntegerRoundingScaling | ( | ) |
In the integer rounding procedure used for MIR and Gomory cut, the maximum "scaling" we use (must be positive). The lower this is, the lower the integer coefficients of the cut will be. Note that cut generated by lower values are not necessarily worse than cut generated by larger value. There is no strict dominance relationship. Setting this to 2 result in the "strong fractional rouding" of Letchford and Lodi.
optional int32 max_integer_rounding_scaling = 119 [default = 600];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30682 of file SatParameters.java.
long com.google.ortools.sat.SatParameters.Builder.getMaxMemoryInMb | ( | ) |
Maximum memory allowed for the whole thread containing the solver. The solver will abort as soon as it detects that this limit is crossed. As a result, this limit is approximative, but usually the solver will not go too much over. TODO(user): This is only used by the pure SAT solver, generalize to CP-SAT.
optional int64 max_memory_in_mb = 40 [default = 10000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19538 of file SatParameters.java.
long com.google.ortools.sat.SatParameters.Builder.getMaxNumberOfConflicts | ( | ) |
Maximum number of conflicts allowed to solve a problem. TODO(user): Maybe change the way the conflict limit is enforced? currently it is enforced on each independent internal SAT solve, rather than on the overall number of conflicts across all solves. So in the context of an optimization problem, this is not really usable directly by a client.
optional int64 max_number_of_conflicts = 37 [default = 9223372036854775807];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19460 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMaxNumCuts | ( | ) |
The limit on the number of cuts in our cut pool. When this is reached we do not generate cuts anymore. TODO(user): We should probably remove this parameters, and just always generate cuts but only keep the best n or something.
optional int32 max_num_cuts = 91 [default = 10000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29976 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMaxNumIntervalsForTimetableEdgeFinding | ( | ) |
Max number of intervals for the timetable_edge_finding algorithm to propagate. A value of 0 disables the constraint.
optional int32 max_num_intervals_for_timetable_edge_finding = 260 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25136 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMaxPairsPairwiseReasoningInNoOverlap2D | ( | ) |
If the number of pairs to look is below this threshold, do an extra step of propagation in the no_overlap_2d constraint by looking at all pairs of intervals.
optional int32 max_pairs_pairwise_reasoning_in_no_overlap_2d = 276 [default = 1250];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25606 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMaxPresolveIterations | ( | ) |
In case of large reduction in a presolve iteration, we perform multiple presolve iterations. This parameter controls the maximum number of such presolve iterations.
optional int32 max_presolve_iterations = 138 [default = 3];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20992 of file SatParameters.java.
com.google.ortools.sat.SatParameters.MaxSatAssumptionOrder com.google.ortools.sat.SatParameters.Builder.getMaxSatAssumptionOrder | ( | ) |
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24401 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getMaxSatReverseAssumptionOrder | ( | ) |
If true, adds the assumption in the reverse order of the one defined by max_sat_assumption_order.
optional bool max_sat_reverse_assumption_order = 52 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24454 of file SatParameters.java.
com.google.ortools.sat.SatParameters.MaxSatStratificationAlgorithm com.google.ortools.sat.SatParameters.Builder.getMaxSatStratification | ( | ) |
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24503 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMaxSizeToCreatePrecedenceLiteralsInDisjunctive | ( | ) |
Create one literal for each disjunction of two pairs of tasks. This slows down the solve time, but improves the lower bound of the objective in the makespan case. This will be triggered if the number of intervals is less or equal than the parameter and if use_strong_propagation_in_disjunctive is true.
optional int32 max_size_to_create_precedence_literals_in_disjunctive = 229 [default = 60];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24738 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMaxTimeInSeconds | ( | ) |
Maximum time allowed in seconds to solve a problem. The counter will starts at the beginning of the Solve() call.
optional double max_time_in_seconds = 36 [default = inf];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19326 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMaxVariableActivityValue | ( | ) |
optional double max_variable_activity_value = 16 [default = 1e+100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18294 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMergeAtMostOneWorkLimit | ( | ) |
optional double merge_at_most_one_work_limit = 146 [default = 100000000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21668 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMergeNoOverlapWorkLimit | ( | ) |
During presolve, we use a maximum clique heuristic to merge together no-overlap constraints or at most one constraints. This code can be slow, so we have a limit in place on the number of explored nodes in the underlying graph. The internal limit is an int64, but we use double here to simplify manual input.
optional double merge_no_overlap_work_limit = 145 [default = 1000000000000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21612 of file SatParameters.java.
com.google.ortools.sat.SatParameters.ConflictMinimizationAlgorithm com.google.ortools.sat.SatParameters.Builder.getMinimizationAlgorithm | ( | ) |
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17637 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getMinimizeReductionDuringPbResolution | ( | ) |
A different algorithm during PB resolution. It minimizes the number of calls to ReduceCoefficients() which can be time consuming. However, the search space will be different and if the coefficients are large, this may lead to integer overflows that could otherwise be prevented.
optional bool minimize_reduction_during_pb_resolution = 48 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20418 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMinNumLnsWorkers | ( | ) |
Obsolete parameter. No-op.
optional int32 min_num_lns_workers = 211 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22556 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMinOrthogonalityForLpConstraints | ( | ) |
While adding constraints, skip the constraints which have orthogonality less than 'min_orthogonality_for_lp_constraints' with already added constraints during current call. Orthogonality is defined as 1 - cosine(vector angle between constraints). A value of zero disable this feature.
optional double min_orthogonality_for_lp_constraints = 115 [default = 0.05];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30896 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getMipAutomaticallyScaleVariables | ( | ) |
If true, some continuous variable might be automatically scaled. For now, this is only the case where we detect that a variable is actually an integer multiple of a constant. For instance, variables of the form k * 0.5 are quite frequent, and if we detect this, we will scale such variable domain by 2 to make it implied integer.
optional bool mip_automatically_scale_variables = 166 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31876 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMipCheckPrecision | ( | ) |
As explained in mip_precision and mip_max_activity_exponent, we cannot always reach the wanted precision during scaling. We use this threshold to enphasize in the logs when the precision seems bad.
optional double mip_check_precision = 128 [default = 0.0001];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32248 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getMipComputeTrueObjectiveBound | ( | ) |
Even if we make big error when scaling the objective, we can always derive a correct lower bound on the original objective by using the exact lower bound on the scaled integer version of the objective. This should be fast, but if you don't care about having a precise lower bound, you can turn it off.
optional bool mip_compute_true_objective_bound = 198 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32316 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMipDropTolerance | ( | ) |
Any value in the input mip with a magnitude lower than this will be set to zero. This is to avoid some issue in LP presolving.
optional double mip_drop_tolerance = 232 [default = 1e-16];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32530 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMipMaxActivityExponent | ( | ) |
To avoid integer overflow, we always force the maximum possible constraint activity (and objective value) according to the initial variable domain to be smaller than 2 to this given power. Because of this, we cannot always reach the "mip_wanted_precision" parameter above. This can go as high as 62, but some internal algo currently abort early if they might run into integer overflow, so it is better to keep it a bit lower than this.
optional int32 mip_max_activity_exponent = 127 [default = 53];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32174 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMipMaxBound | ( | ) |
We need to bound the maximum magnitude of the variables for CP-SAT, and that is the bound we use. If the MIP model expect larger variable value in the solution, then the converted model will likely not be relevant.
optional double mip_max_bound = 124 [default = 10000000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31680 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMipMaxValidMagnitude | ( | ) |
Any finite values in the input MIP must be below this threshold, otherwise the model will be reported invalid. This is needed to avoid floating point overflow when evaluating bounds * coeff for instance. We are a bit more defensive, but in practice, users shouldn't use super large values in a MIP.
optional double mip_max_valid_magnitude = 199 [default = 1e+20];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32388 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getMipPresolveLevel | ( | ) |
When solving a MIP, we do some basic floating point presolving before scaling the problem to integer to be handled by CP-SAT. This control how much of that presolve we do. It can help to better scale floating point model, but it is not always behaving nicely.
optional int32 mip_presolve_level = 261 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32594 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getMipScaleLargeDomain | ( | ) |
If this is false, then mip_var_scaling is only applied to variables with "small" domain. If it is true, we scale all floating point variable independenlty of their domain.
optional bool mip_scale_large_domain = 225 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31808 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getMipTreatHighMagnitudeBoundsAsInfinity | ( | ) |
By default, any variable/constraint bound with a finite value and a magnitude greater than the mip_max_valid_magnitude will result with a invalid model. This flags change the behavior such that such bounds are silently transformed to +∞ or -∞. It is recommended to keep it at false, and create valid bounds.
optional bool mip_treat_high_magnitude_bounds_as_infinity = 278 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32462 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMipVarScaling | ( | ) |
All continuous variable of the problem will be multiplied by this factor. By default, we don't do any variable scaling and rely on the MIP model to specify continuous variable domain with the wanted precision.
optional double mip_var_scaling = 125 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31744 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getMipWantedPrecision | ( | ) |
When scaling constraint with double coefficients to integer coefficients, we will multiply by a power of 2 and round the coefficients. We will choose the lowest power such that we have no potential overflow (see mip_max_activity_exponent) and the worst case constraint activity error does not exceed this threshold. Note that we also detect constraint with rational coefficients and scale them accordingly when it seems better instead of using a power of 2. We also relax all constraint bounds by this absolute value. For pure integer constraint, if this value if lower than one, this will not change anything. However it is needed when scaling MIP problems. If we manage to scale a constraint correctly, the maximum error we can make will be twice this value (once for the scaling error and once for the relaxed bounds). If we are not able to scale that well, we will display that fact but still scale as best as we can.
optional double mip_wanted_precision = 126 [default = 1e-06];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32072 of file SatParameters.java.
java.lang.String com.google.ortools.sat.SatParameters.Builder.getName | ( | ) |
In some context, like in a portfolio of search, it makes sense to name a given parameters set for logging purpose.
optional string name = 171 [default = ""];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 16948 of file SatParameters.java.
com.google.protobuf.ByteString com.google.ortools.sat.SatParameters.Builder.getNameBytes | ( | ) |
In some context, like in a portfolio of search, it makes sense to name a given parameters set for logging purpose.
optional string name = 171 [default = ""];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 16972 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getNewConstraintsBatchSize | ( | ) |
Add that many lazy constraints (or cuts) at once in the LP. Note that at the beginning of the solve, we do add more than this.
optional int32 new_constraints_batch_size = 122 [default = 50];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31242 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getNewLinearPropagation | ( | ) |
Experimental. Use new code to propagate linear constraint.
optional bool new_linear_propagation = 224 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29652 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getNumConflictsBeforeStrategyChanges | ( | ) |
After each restart, if the number of conflict since the last strategy change is greater that this, then we increment a "strategy_counter" that can be use to change the search strategy used by the following restarts.
optional int32 num_conflicts_before_strategy_changes = 68 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19204 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getNumSearchWorkers | ( | ) |
optional int32 num_search_workers = 100 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22508 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getNumViolationLs | ( | ) |
This will create incomplete subsolvers (that are not LNS subsolvers) that use the feasibility jump code to find improving solution, treating the objective improvement as a hard constraint.
optional int32 num_violation_ls = 244 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27272 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getNumWorkers | ( | ) |
Specify the number of parallel workers (i.e. threads) to use during search. This should usually be lower than your number of available cpus + hyperthread in your machine. A value of 0 means the solver will try to use all cores on the machine. A number of 1 means no parallelism. Note that 'num_workers' is the preferred name, but if it is set to zero, we will still read the deprecated 'num_search_worker'. As of 2020-04-10, if you're using SAT via MPSolver (to solve integer programs) this field is overridden with a value of 8, if the field is not set *explicitly*. Thus, always set this field explicitly or via MPSolver::SetNumThreads().
optional int32 num_workers = 206 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22434 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getOnlyAddCutsAtLevelZero | ( | ) |
For the cut that can be generated at any level, this control if we only try to generate them at the root node.
optional bool only_add_cuts_at_level_zero = 92 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30106 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getOnlySolveIp | ( | ) |
If one try to solve a MIP model with CP-SAT, because we assume all variable to be integer after scaling, we will not necessarily have the correct optimal. Note however that all feasible solutions are valid since we will just solve a more restricted version of the original problem. This parameters is here to prevent user to think the solution is optimal when it might not be. One will need to manually set this to false to solve a MIP model where the optimal might be different. Note that this is tested after some MIP presolve steps, so even if not all original variable are integer, we might end up with a pure IP after presolve and after implied integer detection.
optional bool only_solve_ip = 222 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31962 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getOptimizeWithCore | ( | ) |
The default optimization method is a simple "linear scan", each time trying to find a better solution than the previous one. If this is true, then we use a core-based approach (like in max-SAT) when we try to increase the lower bound instead.
optional bool optimize_with_core = 83 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26442 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getOptimizeWithLbTreeSearch | ( | ) |
Do a more conventional tree search (by opposition to SAT based one) where we keep all the explored node in a tree. This is meant to be used in a portfolio and focus on improving the objective lower bound. Keeping the whole tree allow us to report a better objective lower bound coming from the worst open node in the tree.
optional bool optimize_with_lb_tree_search = 188 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26512 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getOptimizeWithMaxHs | ( | ) |
This has no effect if optimize_with_core is false. If true, use a different core-based algorithm similar to the max-HS algo for max-SAT. This is a hybrid MIP/CP approach and it uses a MIP solver in addition to the CP/SAT one. This is also related to the PhD work of tobyodavies@ "Automatic Logic-Based Benders Decomposition with MiniZinc" http://aaai.org/ocs/index.php/AAAI/AAAI17/paper/view/14489
optional bool optimize_with_max_hs = 85 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26654 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getPbCleanupIncrement | ( | ) |
Same as for the clauses, but for the learned pseudo-Boolean constraints.
optional int32 pb_cleanup_increment = 46 [default = 200];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18122 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getPbCleanupRatio | ( | ) |
optional double pb_cleanup_ratio = 47 [default = 0.5];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18170 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getPermutePresolveConstraintOrder | ( | ) |
optional bool permute_presolve_constraint_order = 179 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19908 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getPermuteVariableRandomly | ( | ) |
This is mainly here to test the solver variability. Note that in tests, if not explicitly set to false, all 3 options will be set to true so that clients do not rely on the solver returning a specific solution if they are many equivalent optimal solutions.
optional bool permute_variable_randomly = 178 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19854 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getPolarityRephaseIncrement | ( | ) |
If non-zero, then we change the polarity heuristic after that many number of conflicts in an arithmetically increasing fashion. So x the first time, 2 * x the second time, etc...
optional int32 polarity_rephase_increment = 168 [default = 1000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17242 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getPolishLpSolution | ( | ) |
Whether we try to do a few degenerate iteration at the end of an LP solve to minimize the fractionality of the integer variable in the basis. This helps on some problems, but not so much on others. It also cost of bit of time to do such polish step.
optional bool polish_lp_solution = 175 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29346 of file SatParameters.java.
com.google.ortools.sat.SatParameters.VariableOrder com.google.ortools.sat.SatParameters.Builder.getPreferredVariableOrder | ( | ) |
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17049 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getPresolveBlockedClause | ( | ) |
Whether we use an heuristic to detect some basic case of blocked clause in the SAT presolve.
optional bool presolve_blocked_clause = 88 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20806 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getPresolveBvaThreshold | ( | ) |
Apply Bounded Variable Addition (BVA) if the number of clauses is reduced by stricly more than this threshold. The algorithm described in the paper uses 0, but quick experiments showed that 1 is a good value. It may not be worth it to add a new variable just to remove one clause.
optional int32 presolve_bva_threshold = 73 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20926 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getPresolveBveClauseWeight | ( | ) |
During presolve, we apply BVE only if this weight times the number of clauses plus the number of clause literals is not increased.
optional int32 presolve_bve_clause_weight = 55 [default = 3];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20634 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getPresolveBveThreshold | ( | ) |
During presolve, only try to perform the bounded variable elimination (BVE) of a variable x if the number of occurrences of x times the number of occurrences of not(x) is not greater than this parameter.
optional int32 presolve_bve_threshold = 54 [default = 500];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20572 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getPresolveExtractIntegerEnforcement | ( | ) |
If true, we will extract from linear constraints, enforcement literals of the form "integer variable at bound => simplified constraint". This should always be beneficial except that we don't always handle them as efficiently as we could for now. This causes problem on manna81.mps (LP relaxation not as tight it seems) and on neos-3354841-apure.mps.gz (too many literals created this way).
optional bool presolve_extract_integer_enforcement = 174 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21794 of file SatParameters.java.
long com.google.ortools.sat.SatParameters.Builder.getPresolveInclusionWorkLimit | ( | ) |
A few presolve operations involve detecting constraints included in other constraint. Since there can be a quadratic number of such pairs, and processing them usually involve scanning them, the complexity of these operations can be big. This enforce a local deterministic limit on the number of entries scanned. Default is 1e8. A value of zero will disable these presolve rules completely.
optional int64 presolve_inclusion_work_limit = 201 [default = 100000000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21872 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getPresolveProbingDeterministicTimeLimit | ( | ) |
optional double presolve_probing_deterministic_time_limit = 57 [default = 30];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20756 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getPresolveSubstitutionLevel | ( | ) |
How much substitution (also called free variable aggregation in MIP litterature) should we perform at presolve. This currently only concerns variable appearing only in linear constraints. For now the value 0 turns it off and any positive value performs substitution.
optional int32 presolve_substitution_level = 147 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21722 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getPresolveUseBva | ( | ) |
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
optional bool presolve_use_bva = 72 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20864 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getProbingDeterministicTimeLimit | ( | ) |
The maximum "deterministic" time limit to spend in probing. A value of zero will disable the probing. TODO(user): Clean up. The first one is used in CP-SAT, the other in pure SAT presolve.
optional double probing_deterministic_time_limit = 226 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20700 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getProbingNumCombinationsLimit | ( | ) |
How many combinations of pairs or triplets of variables we want to scan.
optional int32 probing_num_combinations_limit = 272 [default = 20000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26076 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getPropagationLoopDetectionFactor | ( | ) |
Some search decisions might cause a really large number of propagations to happen when integer variables with large domains are only reduced by 1 at each step. If we propagate more than the number of variable times this parameters we try to take counter-measure. Setting this to 0.0 disable this feature. TODO(user): Setting this to something like 10 helps in most cases, but the code is currently buggy and can cause the solve to enter a bad state where no progress is made.
optional double propagation_loop_detection_factor = 221 [default = 10];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24570 of file SatParameters.java.
long com.google.ortools.sat.SatParameters.Builder.getPseudoCostReliabilityThreshold | ( | ) |
The solver ignores the pseudo costs of variables with number of recordings less than this threshold.
optional int64 pseudo_cost_reliability_threshold = 123 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26378 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getPushAllTasksTowardStart | ( | ) |
Experimental code: specify if the objective pushes all tasks toward the start of the schedule.
optional bool push_all_tasks_toward_start = 262 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28886 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getRandomBranchesRatio | ( | ) |
A number between 0 and 1 that indicates the proportion of branching variables that are selected randomly instead of choosing the first variable from the given variable_ordering strategy.
optional double random_branches_ratio = 32 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17378 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getRandomizeSearch | ( | ) |
Randomize fixed search.
optional bool randomize_search = 103 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28764 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getRandomPolarityRatio | ( | ) |
The proportion of polarity chosen at random. Note that this take precedence over the phase saving heuristic. This is different from initial_polarity:POLARITY_RANDOM because it will select a new random polarity each time the variable is branched upon instead of selecting one initially and then always taking this choice.
optional double random_polarity_ratio = 45 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17310 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getRandomSeed | ( | ) |
At the beginning of each solve, the random number generator used in some part of the solver is reinitialized to this seed. If you change the random seed, the solver may make different choices during the solving process. For some problems, the running time may vary a lot depending on small change in the solving algorithm. Running the solver with different seeds enables to have more robust benchmarks when evaluating new features.
optional int32 random_seed = 31 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19780 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getRelativeGapLimit | ( | ) |
optional double relative_gap_limit = 160 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19720 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getRepairHint | ( | ) |
If true, the solver tries to repair the solution given in the hint. This search terminates after the 'hint_conflict_limit' is reached and the solver switches to regular search. If false, then we do a FIXED_SEARCH using the hint until the hint_conflict_limit is reached.
optional bool repair_hint = 167 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25834 of file SatParameters.java.
com.google.ortools.sat.SatParameters.RestartAlgorithm com.google.ortools.sat.SatParameters.Builder.getRestartAlgorithms | ( | int | index | ) |
The restart strategies will change each time the strategy_counter is increased. The current strategy will simply be the one at index strategy_counter modulo the number of strategy. Note that if this list includes a NO_RESTART, nothing will change when it is reached because the strategy_counter will only increment after a restart. The idea of switching of search strategy tailored for SAT/UNSAT comes from Chanseok Oh with his COMiniSatPS solver, see http://cs.nyu.edu/~chanseok/. But more generally, it seems REALLY beneficial to try different strategy.
repeated .operations_research.sat.SatParameters.RestartAlgorithm restart_algorithms = 61;
index | The index of the element to return. |
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18632 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getRestartAlgorithmsCount | ( | ) |
The restart strategies will change each time the strategy_counter is increased. The current strategy will simply be the one at index strategy_counter modulo the number of strategy. Note that if this list includes a NO_RESTART, nothing will change when it is reached because the strategy_counter will only increment after a restart. The idea of switching of search strategy tailored for SAT/UNSAT comes from Chanseok Oh with his COMiniSatPS solver, see http://cs.nyu.edu/~chanseok/. But more generally, it seems REALLY beneficial to try different strategy.
repeated .operations_research.sat.SatParameters.RestartAlgorithm restart_algorithms = 61;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18612 of file SatParameters.java.
java.util.List< com.google.ortools.sat.SatParameters.RestartAlgorithm > com.google.ortools.sat.SatParameters.Builder.getRestartAlgorithmsList | ( | ) |
The restart strategies will change each time the strategy_counter is increased. The current strategy will simply be the one at index strategy_counter modulo the number of strategy. Note that if this list includes a NO_RESTART, nothing will change when it is reached because the strategy_counter will only increment after a restart. The idea of switching of search strategy tailored for SAT/UNSAT comes from Chanseok Oh with his COMiniSatPS solver, see http://cs.nyu.edu/~chanseok/. But more generally, it seems REALLY beneficial to try different strategy.
repeated .operations_research.sat.SatParameters.RestartAlgorithm restart_algorithms = 61;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18592 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getRestartDlAverageRatio | ( | ) |
In the moving average restart algorithms, a restart is triggered if the window average times this ratio is greater that the global average.
optional double restart_dl_average_ratio = 63 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18958 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getRestartLbdAverageRatio | ( | ) |
optional double restart_lbd_average_ratio = 71 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19008 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getRestartPeriod | ( | ) |
Restart period for the FIXED_RESTART strategy. This is also the multiplier used by the LUBY_RESTART strategy.
optional int32 restart_period = 30 [default = 50];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18842 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getRestartRunningWindowSize | ( | ) |
Size of the window for the moving average restarts.
optional int32 restart_running_window_size = 62 [default = 50];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18900 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getRootLpIterations | ( | ) |
Even at the root node, we do not want to spend too much time on the LP if it is "difficult". So we solve it in "chunks" of that many iterations. The solve will be continued down in the tree or the next time we go back to the root node.
optional int32 root_lp_iterations = 227 [default = 2000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30826 of file SatParameters.java.
com.google.ortools.sat.SatParameters.SearchBranching com.google.ortools.sat.SatParameters.Builder.getSearchBranching | ( | ) |
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25721 of file SatParameters.java.
long com.google.ortools.sat.SatParameters.Builder.getSearchRandomVariablePoolSize | ( | ) |
Search randomization will collect the top 'search_random_variable_pool_size' valued variables, and pick one randomly. The value of the variable is specific to each strategy.
optional int64 search_random_variable_pool_size = 104 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28824 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getShareBinaryClauses | ( | ) |
Allows sharing of new learned binary clause between workers.
optional bool share_binary_clauses = 203 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23914 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getSharedTreeMaxNodesPerWorker | ( | ) |
In order to limit total shared memory and communication overhead, limit the total number of nodes that may be generated in the shared tree. If the shared tree runs out of unassigned leaves, workers act as portfolio workers. Note: this limit includes interior nodes, not just leaves.
optional int32 shared_tree_max_nodes_per_worker = 238 [default = 128];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27646 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getSharedTreeNumWorkers | ( | ) |
Enables experimental workstealing-like shared tree search. If non-zero, start this many complete worker threads to explore a shared search tree. These workers communicate objective bounds and simple decision nogoods relating to the shared prefix of the tree, and will avoid exploring the same subtrees as one another.
optional int32 shared_tree_num_workers = 235 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27456 of file SatParameters.java.
com.google.ortools.sat.SatParameters.SharedTreeSplitStrategy com.google.ortools.sat.SatParameters.Builder.getSharedTreeSplitStrategy | ( | ) |
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27699 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getSharedTreeWorkerObjectiveSplitProbability | ( | ) |
After their assigned prefix, shared tree workers will branch on the objective with this probability. Higher numbers cause the shared tree search to focus on improving the lower bound over finding primal solutions.
optional double shared_tree_worker_objective_split_probability = 237 [default = 0.5];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27580 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getShareLevelZeroBounds | ( | ) |
Allows sharing of the bounds of modified variables at level 0.
optional bool share_level_zero_bounds = 114 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23858 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getShareObjectiveBounds | ( | ) |
Allows objective sharing between workers.
optional bool share_objective_bounds = 113 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23802 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getShavingSearchDeterministicTime | ( | ) |
Specifies the amount of deterministic time spent of each try at shaving a bound in the shaving search.
optional double shaving_search_deterministic_time = 205 [default = 0.001];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26194 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getSolutionPoolSize | ( | ) |
Size of the top-n different solutions kept by the solver. This parameter must be > 0. Currently this only impact the "base" solution chosen for a LNS fragment.
optional int32 solution_pool_size = 193 [default = 3];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28430 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getStopAfterFirstSolution | ( | ) |
For an optimization problem, stop the solver as soon as we have a solution.
optional bool stop_after_first_solution = 98 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28214 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getStopAfterPresolve | ( | ) |
Mainly used when improving the presolver. When true, stops the solver after the presolve is complete (or after loading and root level propagation).
optional bool stop_after_presolve = 149 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28272 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getStopAfterRootPropagation | ( | ) |
optional bool stop_after_root_propagation = 252 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28322 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getStrategyChangeIncreaseRatio | ( | ) |
The parameter num_conflicts_before_strategy_changes is increased by that much after each strategy change.
optional double strategy_change_increase_ratio = 69 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19266 of file SatParameters.java.
com.google.ortools.sat.SatParameters com.google.ortools.sat.SatParameters.Builder.getSubsolverParams | ( | int | index | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23339 of file SatParameters.java.
com.google.ortools.sat.SatParameters.Builder com.google.ortools.sat.SatParameters.Builder.getSubsolverParamsBuilder | ( | int | index | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23562 of file SatParameters.java.
java.util.List< com.google.ortools.sat.SatParameters.Builder > com.google.ortools.sat.SatParameters.Builder.getSubsolverParamsBuilderList | ( | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23646 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getSubsolverParamsCount | ( | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23321 of file SatParameters.java.
java.util.List< com.google.ortools.sat.SatParameters > com.google.ortools.sat.SatParameters.Builder.getSubsolverParamsList | ( | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23303 of file SatParameters.java.
com.google.ortools.sat.SatParametersOrBuilder com.google.ortools.sat.SatParameters.Builder.getSubsolverParamsOrBuilder | ( | int | index | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23577 of file SatParameters.java.
java.util.List<? extends com.google.ortools.sat.SatParametersOrBuilder > com.google.ortools.sat.SatParameters.Builder.getSubsolverParamsOrBuilderList | ( | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23596 of file SatParameters.java.
java.lang.String com.google.ortools.sat.SatParameters.Builder.getSubsolvers | ( | int | index | ) |
In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters. This field indicates the names of the parameters that are used in multithread. See cp_model_search.cc to see a list of the names and the default value (if left empty) that looks like: - default_lp (linearization_level:1) - fixed (only if fixed search specified or scheduling) - no_lp (linearization_level:0) - max_lp (linearization_level:2) - pseudo_costs (only if objective, change search heuristic) - reduced_costs (only if objective, change search heuristic) - quick_restart (kind of probing) - quick_restart_no_lp (kind of probing with linearization_level:0) - lb_tree_search (to improve lower bound, MIP like tree search) - probing (continuous probing and shaving) Also, note that some set of parameters will be ignored if they do not make sense. For instance if there is no objective, pseudo_cost or reduced_cost search will be ignored. Core based search will only work if the objective has many terms. If there is no fixed strategy fixed will be ignored. And so on. The order is important, as only the first usable "num_workers - min_num_lns_workers" subsolvers will be scheduled. You can see in the log which one are selected for a given run. All the others will be LNS if there is an objective, or randomized SAT search for pure satisfiability problems.
repeated string subsolvers = 207;
index | The index of the element to return. |
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22709 of file SatParameters.java.
com.google.protobuf.ByteString com.google.ortools.sat.SatParameters.Builder.getSubsolversBytes | ( | int | index | ) |
In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters. This field indicates the names of the parameters that are used in multithread. See cp_model_search.cc to see a list of the names and the default value (if left empty) that looks like: - default_lp (linearization_level:1) - fixed (only if fixed search specified or scheduling) - no_lp (linearization_level:0) - max_lp (linearization_level:2) - pseudo_costs (only if objective, change search heuristic) - reduced_costs (only if objective, change search heuristic) - quick_restart (kind of probing) - quick_restart_no_lp (kind of probing with linearization_level:0) - lb_tree_search (to improve lower bound, MIP like tree search) - probing (continuous probing and shaving) Also, note that some set of parameters will be ignored if they do not make sense. For instance if there is no objective, pseudo_cost or reduced_cost search will be ignored. Core based search will only work if the objective has many terms. If there is no fixed strategy fixed will be ignored. And so on. The order is important, as only the first usable "num_workers - min_num_lns_workers" subsolvers will be scheduled. You can see in the log which one are selected for a given run. All the others will be LNS if there is an objective, or randomized SAT search for pure satisfiability problems.
repeated string subsolvers = 207;
index | The index of the value to return. |
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22748 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getSubsolversCount | ( | ) |
In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters. This field indicates the names of the parameters that are used in multithread. See cp_model_search.cc to see a list of the names and the default value (if left empty) that looks like: - default_lp (linearization_level:1) - fixed (only if fixed search specified or scheduling) - no_lp (linearization_level:0) - max_lp (linearization_level:2) - pseudo_costs (only if objective, change search heuristic) - reduced_costs (only if objective, change search heuristic) - quick_restart (kind of probing) - quick_restart_no_lp (kind of probing with linearization_level:0) - lb_tree_search (to improve lower bound, MIP like tree search) - probing (continuous probing and shaving) Also, note that some set of parameters will be ignored if they do not make sense. For instance if there is no objective, pseudo_cost or reduced_cost search will be ignored. Core based search will only work if the objective has many terms. If there is no fixed strategy fixed will be ignored. And so on. The order is important, as only the first usable "num_workers - min_num_lns_workers" subsolvers will be scheduled. You can see in the log which one are selected for a given run. All the others will be LNS if there is an objective, or randomized SAT search for pure satisfiability problems.
repeated string subsolvers = 207;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22671 of file SatParameters.java.
com.google.protobuf.ProtocolStringList com.google.ortools.sat.SatParameters.Builder.getSubsolversList | ( | ) |
In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters. This field indicates the names of the parameters that are used in multithread. See cp_model_search.cc to see a list of the names and the default value (if left empty) that looks like: - default_lp (linearization_level:1) - fixed (only if fixed search specified or scheduling) - no_lp (linearization_level:0) - max_lp (linearization_level:2) - pseudo_costs (only if objective, change search heuristic) - reduced_costs (only if objective, change search heuristic) - quick_restart (kind of probing) - quick_restart_no_lp (kind of probing with linearization_level:0) - lb_tree_search (to improve lower bound, MIP like tree search) - probing (continuous probing and shaving) Also, note that some set of parameters will be ignored if they do not make sense. For instance if there is no objective, pseudo_cost or reduced_cost search will be ignored. Core based search will only work if the objective has many terms. If there is no fixed strategy fixed will be ignored. And so on. The order is important, as only the first usable "num_workers - min_num_lns_workers" subsolvers will be scheduled. You can see in the log which one are selected for a given run. All the others will be LNS if there is an objective, or randomized SAT search for pure satisfiability problems.
repeated string subsolvers = 207;
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22633 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getSubsumptionDuringConflictAnalysis | ( | ) |
At a really low cost, during the 1-UIP conflict computation, it is easy to detect if some of the involved reasons are subsumed by the current conflict. When this is true, such clauses are detached and later removed from the problem.
optional bool subsumption_during_conflict_analysis = 56 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17736 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getSymmetryLevel | ( | ) |
Whether we try to automatically detect the symmetries in a model and exploit them. Currently, at level 1 we detect them in presolve and try to fix Booleans. At level 2, we also do some form of dynamic symmetry breaking during search.
optional int32 symmetry_level = 183 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29590 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getTableCompressionLevel | ( | ) |
How much we try to "compress" a table constraint. Compressing more leads to less Booleans and faster propagation but can reduced the quality of the lp relaxation. Values goes from 0 to 3 where we always try to fully compress a table. At 2, we try to automatically decide if it is worth it.
optional int32 table_compression_level = 217 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21302 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getTestFeasibilityJump | ( | ) |
Disable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.
optional bool test_feasibility_jump = 240 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26786 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseAbslRandom | ( | ) |
optional bool use_absl_random = 180 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19948 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseAreaEnergeticReasoningInNoOverlap2D | ( | ) |
When this is true, the no_overlap_2d constraint is reinforced with an energetic reasoning that uses an area-based energy. This can be combined with the two other overlap heuristics above.
optional bool use_area_energetic_reasoning_in_no_overlap_2d = 271 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25542 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseBlockingRestart | ( | ) |
Block a moving restart algorithm if the trail size of the current conflict is greater than the multiplier times the moving average of the trail size at the previous conflicts.
optional bool use_blocking_restart = 64 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19060 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseCombinedNoOverlap | ( | ) |
This can be beneficial if there is a lot of no-overlap constraints but a relatively low number of different intervals in the problem. Like 1000 intervals, but 1M intervals in the no-overlap constraints covering them.
optional bool use_combined_no_overlap = 133 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29092 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseDisjunctiveConstraintInCumulative | ( | ) |
When this is true, the cumulative constraint is reinforced with propagators from the disjunctive constraint to improve the inference on a set of tasks that are disjunctive at the root of the problem. This additional level supplements the default level of reasoning. Propagators of the cumulative constraint will not be used at all if all the tasks are disjunctive at root node. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_disjunctive_constraint_in_cumulative = 80 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25328 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseDualSchedulingHeuristics | ( | ) |
When set, it activates a few scheduling parameters to improve the lower bound of scheduling problems. This is only effective with multiple workers as it modifies the reduced_cost, lb_tree_search, and probing workers.
optional bool use_dual_scheduling_heuristics = 214 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25670 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseDynamicPrecedenceInCumulative | ( | ) |
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24926 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseDynamicPrecedenceInDisjunctive | ( | ) |
Whether we try to branch on decision "interval A before interval B" rather than on intervals bounds. This usually works better, but slow down a bit the time to find the first solution. These parameters are still EXPERIMENTAL, the result should be correct, but it some corner cases, they can cause some failing CHECK in the solver.
optional bool use_dynamic_precedence_in_disjunctive = 263 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24868 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseEnergeticReasoningInNoOverlap2D | ( | ) |
When this is true, the no_overlap_2d constraint is reinforced with energetic reasoning. This additional level supplements the default level of reasoning.
optional bool use_energetic_reasoning_in_no_overlap_2d = 213 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25478 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseErwaHeuristic | ( | ) |
Whether we use the ERWA (Exponential Recency Weighted Average) heuristic as described in "Learning Rate Based Branching Heuristic for SAT solvers", J.H.Liang, V. Ganesh, P. Poupart, K.Czarnecki, SAT 2016.
optional bool use_erwa_heuristic = 75 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17442 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseExactLpReason | ( | ) |
The solver usually exploit the LP relaxation of a model. If this option is true, then whatever is infered by the LP will be used like an heuristic to compute EXACT propagation on the IP. So with this option, there is no numerical imprecision issues.
optional bool use_exact_lp_reason = 109 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29026 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseExtendedProbing | ( | ) |
Use extended probing (probe bool_or, at_most_one, exactly_one).
optional bool use_extended_probing = 269 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26020 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseFeasibilityJump | ( | ) |
Parameters for an heuristic similar to the one described in the paper: "Feasibility Jump: an LP-free Lagrangian MIP heuristic", Bjørnar Luteberget, Giorgio Sartor, 2023, Mathematical Programming Computation.
optional bool use_feasibility_jump = 265 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26724 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseFeasibilityPump | ( | ) |
Adds a feasibility pump subsolver along with lns subsolvers.
optional bool use_feasibility_pump = 164 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28546 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseHardPrecedencesInCumulative | ( | ) |
If true, detect and create constraint for integer variable that are "after" a set of intervals in the same cumulative constraint. Experimental: by default we just use "direct" precedences. If exploit_all_precedences is true, we explore the full precedence graph. This assumes we have a DAG otherwise it fails.
optional bool use_hard_precedences_in_cumulative = 215 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25204 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseImpliedBounds | ( | ) |
Stores and exploits "implied-bounds" in the solver. That is, relations of the form literal => (var >= bound). This is currently used to derive stronger cuts.
optional bool use_implied_bounds = 144 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29280 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseLbRelaxLns | ( | ) |
Turns on neighborhood generator based on local branching LP. Based on Huang et al., "Local Branching Relaxation Heuristics for Integer Linear Programs", 2023.
optional bool use_lb_relax_lns = 255 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28606 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseLnsOnly | ( | ) |
LNS parameters.
optional bool use_lns_only = 101 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28370 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseObjectiveLbSearch | ( | ) |
If true, search will search in ascending max objective value (when minimizing) starting from the lower bound of the objective.
optional bool use_objective_lb_search = 228 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26254 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseObjectiveShavingSearch | ( | ) |
This search differs from the previous search as it will not use assumptions to bound the objective, and it will recreate a full model with the hardcoded objective value.
optional bool use_objective_shaving_search = 253 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26316 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseOptimizationHints | ( | ) |
For an optimization problem, whether we follow some hints in order to find a better first solution. For a variable with hint, the solver will always try to follow the hint. It will revert to the variable_branching default otherwise.
optional bool use_optimization_hints = 35 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24156 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseOptionalVariables | ( | ) |
If true, we automatically detect variables whose constraint are always enforced by the same literal and we mark them as optional. This allows to propagate them as if they were present in some situation. TODO(user): This is experimental and seems to lead to wrong optimal in some situation. It should however gives correct solutions. Fix.
optional bool use_optional_variables = 108 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28954 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseOverloadCheckerInCumulative | ( | ) |
When this is true, the cumulative constraint is reinforced with overload checking, i.e., an additional level of reasoning based on energy. This additional level supplements the default level of reasoning as well as timetable edge finding. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_overload_checker_in_cumulative = 78 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24986 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUsePbResolution | ( | ) |
Whether to use pseudo-Boolean resolution to analyze a conflict. Note that this option only make sense if your problem is modelized using pseudo-Boolean constraints. If you only have clauses, this shouldn't change anything (except slow the solver down).
optional bool use_pb_resolution = 43 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20350 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUsePhaseSaving | ( | ) |
If this is true, then the polarity of a variable will be the last value it was assigned to, or its default polarity if it was never assigned since the call to ResetDecisionHeuristic(). Actually, we use a newer version where we follow the last value in the longest non-conflicting partial assignment in the current phase. This is called 'literal phase saving'. For details see 'A Lightweight Component Caching Scheme for Satisfiability Solvers' K. Pipatsrisawat and A.Darwiche, In 10th International Conference on Theory and Applications of Satisfiability Testing, 2007.
optional bool use_phase_saving = 44 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17162 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUsePrecedencesInDisjunctiveConstraint | ( | ) |
When this is true, then a disjunctive constraint will try to use the precedence relations between time intervals to propagate their bounds further. For instance if task A and B are both before C and task A and B are in disjunction, then we can deduce that task C must start after duration(A) + duration(B) instead of simply max(duration(A), duration(B)), provided that the start time for all task was currently zero. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_precedences_in_disjunctive_constraint = 74 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24658 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseProbingSearch | ( | ) |
If true, search will continuously probe Boolean variables, and integer variable bounds. This parameter is set to true in parallel on the probing worker.
optional bool use_probing_search = 176 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25960 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseRinsLns | ( | ) |
Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28490 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseSatInprocessing | ( | ) |
Enable or disable "inprocessing" which is some SAT presolving done at each restart to the root level.
optional bool use_sat_inprocessing = 163 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22138 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseSharedTreeSearch | ( | ) |
Set on shared subtree workers. Users should not set this directly.
optional bool use_shared_tree_search = 236 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27520 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseShavingInProbingSearch | ( | ) |
Add a shaving phase (where the solver tries to prove that the lower or upper bound of a variable are infeasible) to the probing search.
optional bool use_shaving_in_probing_search = 204 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26134 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseStrongPropagationInDisjunctive | ( | ) |
Enable stronger and more expensive propagation on no_overlap constraint.
optional bool use_strong_propagation_in_disjunctive = 230 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24802 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseTimetableEdgeFindingInCumulative | ( | ) |
When this is true, the cumulative constraint is reinforced with timetable edge finding, i.e., an additional level of reasoning based on the conjunction of energy and mandatory parts. This additional level supplements the default level of reasoning as well as overload_checker. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_timetable_edge_finding_in_cumulative = 79 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25066 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.getUseTimetablingInNoOverlap2D | ( | ) |
When this is true, the no_overlap_2d constraint is reinforced with propagators from the cumulative constraints. It consists of ignoring the position of rectangles in one position and projecting the no_overlap_2d on the other dimension to create a cumulative constraint. This is done on both axis. This additional level supplements the default level of reasoning.
optional bool use_timetabling_in_no_overlap_2d = 200 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25410 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getVariableActivityDecay | ( | ) |
Each time a conflict is found, the activities of some variables are increased by one. Then, the activity of all variables are multiplied by variable_activity_decay. To implement this efficiently, the activity of all the variables is not decayed at each conflict. Instead, the activity increment is multiplied by 1 / decay. When an activity reach max_variable_activity_value, all the activity are multiplied by 1 / max_variable_activity_value.
optional double variable_activity_decay = 15 [default = 0.8];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18232 of file SatParameters.java.
double com.google.ortools.sat.SatParameters.Builder.getViolationLsCompoundMoveProbability | ( | ) |
Probability of using compound move search each restart. TODO(user): Add reference to paper when published.
optional double violation_ls_compound_move_probability = 259 [default = 0.5];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27390 of file SatParameters.java.
int com.google.ortools.sat.SatParameters.Builder.getViolationLsPerturbationPeriod | ( | ) |
How long violation_ls should wait before perturbating a solution.
optional int32 violation_ls_perturbation_period = 249 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27332 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAbsoluteGapLimit | ( | ) |
Stop the search when the gap between the best feasible objective (O) and our best objective bound (B) is smaller than a limit. The exact definition is: - Absolute: abs(O - B) - Relative: abs(O - B) / max(1, abs(O)). Important: The relative gap depends on the objective offset! If you artificially shift the objective, you will get widely different value of the relative gap. Note that if the gap is reached, the search status will be OPTIMAL. But one can check the best objective bound to see the actual gap. If the objective is integer, then any absolute gap < 1 will lead to a true optimal. If the objective is floating point, a gap of zero make little sense so is is why we use a non-zero default value. At the end of the search, we will display a warning if OPTIMAL is reported yet the gap is greater than this absolute gap.
optional double absolute_gap_limit = 159 [default = 0.0001];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19609 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAddCgCuts | ( | ) |
Whether we generate and add Chvatal-Gomory cuts to the LP at root node. Note that for now, this is not heavily tuned.
optional bool add_cg_cuts = 117 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30225 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAddCliqueCuts | ( | ) |
Whether we generate clique cuts from the binary implication graph. Note that as the search goes on, this graph will contains new binary clauses learned by the SAT engine.
optional bool add_clique_cuts = 172 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30406 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAddLinMaxCuts | ( | ) |
For the lin max constraints, generates the cuts described in "Strong mixed-integer programming formulations for trained neural networks" by Ross Anderson et. (https://arxiv.org/pdf/1811.01988.pdf)
optional bool add_lin_max_cuts = 152 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30594 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAddLpConstraintsLazily | ( | ) |
If true, we start by an empty LP, and only add constraints not satisfied by the current LP solution batch by batch. A constraint that is only added like this is known as a "lazy" constraint in the literature, except that we currently consider all constraints as lazy here.
optional bool add_lp_constraints_lazily = 112 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30743 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAddMirCuts | ( | ) |
Whether we generate MIR cuts at root node. Note that for now, this is not heavily tuned.
optional bool add_mir_cuts = 120 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30285 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAddObjectiveCut | ( | ) |
When the LP objective is fractional, do we add the cut that forces the linear objective expression to be greater or equal to this fractional value rounded up? We can always do that since our objective is integer, and combined with MIR heuristic to reduce the coefficient of such cut, it can help.
optional bool add_objective_cut = 197 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30156 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAddRltCuts | ( | ) |
Whether we generate RLT cuts. This is still experimental but can help on binary problem with a lot of clauses of size 3.
optional bool add_rlt_cuts = 279 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30469 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAddZeroHalfCuts | ( | ) |
Whether we generate Zero-Half cuts at root node. Note that for now, this is not heavily tuned.
optional bool add_zero_half_cuts = 169 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30345 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAlsoBumpVariablesInConflictReasons | ( | ) |
When this is true, then the variables that appear in any of the reason of the variables in a conflict have their activity bumped. This is addition to the variables in the conflict, and the one that were used during conflict resolution.
optional bool also_bump_variables_in_conflict_reasons = 77 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17569 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAtMostOneMaxExpansionSize | ( | ) |
All at_most_one constraints with a size <= param will be replaced by a quadratic number of binary implications.
optional int32 at_most_one_max_expansion_size = 270 [default = 3];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29141 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasAutoDetectGreaterThanAtLeastOneOf | ( | ) |
If true, then the precedences propagator try to detect for each variable if it has a set of "optional incoming arc" for which at least one of them is present. This is usually useful to have but can be slow on model with a lot of precedence.
optional bool auto_detect_greater_than_at_least_one_of = 95 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28137 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasBinaryMinimizationAlgorithm | ( | ) |
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17671 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasBinarySearchNumConflicts | ( | ) |
If non-negative, perform a binary search on the objective variable in order to find an [min, max] interval outside of which the solver proved unsat/sat under this amount of conflict. This can quickly reduce the objective domain on some problems.
optional int32 binary_search_num_conflicts = 99 [default = -1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26567 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasBlockingRestartMultiplier | ( | ) |
optional double blocking_restart_multiplier = 66 [default = 1.4];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19144 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasBlockingRestartWindowSize | ( | ) |
optional int32 blocking_restart_window_size = 65 [default = 5000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19104 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasBooleanEncodingLevel | ( | ) |
A non-negative level indicating how much we should try to fully encode Integer variables as Boolean.
optional int32 boolean_encoding_level = 107 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29829 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasCatchSigintSignal | ( | ) |
Indicates if the CP-SAT layer should catch Control-C (SIGINT) signals when calling solve. If set, catching the SIGINT signal will terminate the search gracefully, as if a time limit was reached.
optional bool catch_sigint_signal = 135 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29202 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasClauseActivityDecay | ( | ) |
Clause activity parameters (same effect as the one on the variables).
optional double clause_activity_decay = 17 [default = 0.999];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18482 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasClauseCleanupLbdBound | ( | ) |
All the clauses with a LBD (literal blocks distance) lower or equal to this parameters will always be kept.
optional int32 clause_cleanup_lbd_bound = 59 [default = 5];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18009 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasClauseCleanupOrdering | ( | ) |
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18063 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasClauseCleanupPeriod | ( | ) |
Trigger a cleanup when this number of "deletable" clauses is learned.
optional int32 clause_cleanup_period = 11 [default = 10000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17786 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasClauseCleanupProtection | ( | ) |
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17961 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasClauseCleanupRatio | ( | ) |
During a cleanup, if clause_cleanup_target is 0, we will delete the clause_cleanup_ratio of "deletable" clauses instead of aiming for a fixed target of clauses to keep.
optional double clause_cleanup_ratio = 190 [default = 0.5];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17904 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasClauseCleanupTarget | ( | ) |
During a cleanup, we will always keep that number of "deletable" clauses. Note that this doesn't include the "protected" clauses.
optional int32 clause_cleanup_target = 13 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17843 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasConvertIntervals | ( | ) |
Temporary flag util the feature is more mature. This convert intervals to the newer proto format that support affine start/var/end instead of just variables.
optional bool convert_intervals = 177 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29510 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasCoreMinimizationLevel | ( | ) |
If positive, we spend some effort on each core: - At level 1, we use a simple heuristic to try to minimize an UNSAT core. - At level 2, we use propagation to minimize the core but also identify literal in at most one relationship in this core.
optional int32 core_minimization_level = 50 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24209 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasCountAssumptionLevelsInLbd | ( | ) |
Whether or not the assumption levels are taken into account during the LBD computation. According to the reference below, not counting them improves the solver in some situation. Note that this only impact solves under assumptions. Gilles Audemard, Jean-Marie Lagniez, Laurent Simon, "Improving Glucose for Incremental SAT Solving with Assumptions: Application to MUS Extraction" Theory and Applications of Satisfiability Testing - SAT 2013, Lecture Notes in Computer Science Volume 7962, 2013, pp 309-317.
optional bool count_assumption_levels_in_lbd = 49 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20476 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasCoverOptimization | ( | ) |
If true, when the max-sat algo find a core, we compute the minimal number of literals in the core that needs to be true to have a feasible solution. This is also called core exhaustion in more recent max-SAT papers.
optional bool cover_optimization = 89 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24336 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasCpModelPresolve | ( | ) |
Whether we presolve the cp_model before solving it.
optional bool cp_model_presolve = 86 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21040 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasCpModelProbingLevel | ( | ) |
How much effort do we spend on probing. 0 disables it completely.
optional int32 cp_model_probing_level = 110 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21096 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasCpModelUseSatPresolve | ( | ) |
Whether we also use the sat presolve when cp_model_presolve is true.
optional bool cp_model_use_sat_presolve = 93 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21152 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasCutActiveCountDecay | ( | ) |
optional double cut_active_count_decay = 156 [default = 0.8];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31128 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasCutCleanupTarget | ( | ) |
Target number of constraints to remove during cleanup.
optional int32 cut_cleanup_target = 157 [default = 1000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31172 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasCutLevel | ( | ) |
Control the global cut effort. Zero will turn off all cut. For now we just have one level. Note also that most cuts are only used at linearization level >= 2.
optional int32 cut_level = 196 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30030 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasCutMaxActiveCountValue | ( | ) |
These parameters are similar to sat clause management activity parameters. They are effective only if the number of generated cuts exceed the storage limit. Default values are based on a few experiments on miplib instances.
optional double cut_max_active_count_value = 155 [default = 10000000000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31070 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasDebugCrashOnBadHint | ( | ) |
Crash if we do not manage to complete the hint into a full solution.
optional bool debug_crash_on_bad_hint = 195 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24082 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasDebugMaxNumPresolveOperations | ( | ) |
If positive, try to stop just after that many presolve rules have been applied. This is mainly useful for debugging presolve.
optional int32 debug_max_num_presolve_operations = 151 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24023 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasDebugPostsolveWithFullSolver | ( | ) |
We have two different postsolve code. The default one should be better and it allows for a more powerful presolve, but it can be useful to postsolve using the full solver instead.
optional bool debug_postsolve_with_full_solver = 162 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23960 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasDefaultRestartAlgorithms | ( | ) |
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18743 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasDetectLinearizedProduct | ( | ) |
Infer products of Boolean or of Boolean time IntegerVariable from the linear constrainst in the problem. This can be used in some cuts, altough for now we don't really exploit it.
optional bool detect_linearized_product = 277 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31602 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasDetectTableWithCost | ( | ) |
If true, we detect variable that are unique to a table constraint and only there to encode a cost on each tuple. This is usually the case when a WCSP (weighted constraint program) is encoded into CP-SAT format. This can lead to a dramatic speed-up for such problems but is still experimental at this point.
optional bool detect_table_with_cost = 216 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21213 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasDisableConstraintExpansion | ( | ) |
If true, it disable all constraint expansion. This should only be used to test the presolve of expanded constraints.
optional bool disable_constraint_expansion = 181 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21473 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasDiversifyLnsParams | ( | ) |
If true, registers more lns subsolvers with different parameters.
optional bool diversify_lns_params = 137 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28696 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasEncodeComplexLinearConstraintWithInteger | ( | ) |
Linear constraint with a complex right hand side (more than a single interval) need to be expanded, there is a couple of way to do that.
optional bool encode_complex_linear_constraint_with_integer = 223 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21533 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasEnumerateAllSolutions | ( | ) |
Whether we enumerate all solutions of a problem without objective. Note that setting this to true automatically disable some presolve reduction that can remove feasible solution. That is it has the same effect as setting keep_all_feasible_solutions_in_presolve. TODO(user): Do not do that and let the user choose what behavior is best by setting keep_all_feasible_solutions_in_presolve ?
optional bool enumerate_all_solutions = 87 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27744 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasExpandAlldiffConstraints | ( | ) |
If true, expand all_different constraints that are not permutations. Permutations (#Variables = #Values) are always expanded.
optional bool expand_alldiff_constraints = 170 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21353 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasExpandReservoirConstraints | ( | ) |
If true, expand the reservoir constraints by creating booleans for all possible precedences between event and encoding the constraint.
optional bool expand_reservoir_constraints = 182 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21413 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasExploitAllLpSolution | ( | ) |
If true and the Lp relaxation of the problem has a solution, try to exploit it. This is same as above except in this case the lp solution might not be an integer solution.
optional bool exploit_all_lp_solution = 116 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31358 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasExploitAllPrecedences | ( | ) |
optional bool exploit_all_precedences = 220 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25254 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasExploitBestSolution | ( | ) |
When branching on a variable, follow the last best solution value.
optional bool exploit_best_solution = 130 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31420 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasExploitIntegerLpSolution | ( | ) |
If true and the Lp relaxation of the problem has an integer optimal solution, try to exploit it. Note that since the LP relaxation may not contain all the constraints, such a solution is not necessarily a solution of the full problem.
optional bool exploit_integer_lp_solution = 94 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31291 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasExploitObjective | ( | ) |
When branching an a variable that directly affect the objective, branch on the value that lead to the best objective first.
optional bool exploit_objective = 131 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31541 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasExploitRelaxationSolution | ( | ) |
When branching on a variable, follow the last best relaxation solution value. We use the relaxation with the tightest bound on the objective as the best relaxation solution.
optional bool exploit_relaxation_solution = 161 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31478 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFeasibilityJumpDecay | ( | ) |
On each restart, we randomly choose if we use decay (with this parameter) or no decay.
optional double feasibility_jump_decay = 242 [default = 0.95];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26833 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFeasibilityJumpEnableRestarts | ( | ) |
When stagnating, feasibility jump will either restart from a default solution (with some possible randomization), or randomly pertubate the current solution. This parameter selects the first option.
optional bool feasibility_jump_enable_restarts = 250 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27134 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFeasibilityJumpLinearizationLevel | ( | ) |
How much do we linearize the problem in the local search code.
optional int32 feasibility_jump_linearization_level = 257 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26892 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFeasibilityJumpMaxExpandedConstraintSize | ( | ) |
Maximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion.
optional int32 feasibility_jump_max_expanded_constraint_size = 264 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27197 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFeasibilityJumpRestartFactor | ( | ) |
This is a factor that directly influence the work before each restart. Setting this to zero disable restart, and increasing it lead to longer restarts.
optional int32 feasibility_jump_restart_factor = 258 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26950 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFeasibilityJumpVarPerburbationRangeRatio | ( | ) |
Max distance between the default value and the pertubated value relative to the range of the domain of the variable.
optional double feasibility_jump_var_perburbation_range_ratio = 248 [default = 0.2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27073 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFeasibilityJumpVarRandomizationProbability | ( | ) |
Probability for a variable to have a non default value upon restarts or perturbations.
optional double feasibility_jump_var_randomization_probability = 247 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27013 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFillAdditionalSolutionsInResponse | ( | ) |
If true, the final response addition_solutions field will be filled with all solutions from our solutions pool. Note that if both this field and enumerate_all_solutions is true, we will copy to the pool all of the solution found. So if solution_pool_size is big enough, you can get all solutions this way instead of using the solution callback. Note that this only affect the "final" solution, not the one passed to the solution callbacks.
optional bool fill_additional_solutions_in_response = 194 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27983 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFillTightenedDomainsInResponse | ( | ) |
If true, add information about the derived variable domains to the CpSolverResponse. It is an option because it makes the response slighly bigger and there is a bit more work involved during the postsolve to construct it, but it should still have a low overhead. See the tightened_variables field in CpSolverResponse for more details.
optional bool fill_tightened_domains_in_response = 132 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27906 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFindBigLinearOverlap | ( | ) |
Try to find large "rectangle" in the linear constraint matrix with identical lines. If such rectangle is big enough, we can introduce a new integer variable corresponding to the common expression and greatly reduce the number of non-zero.
optional bool find_big_linear_overlap = 234 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22059 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFindMultipleCores | ( | ) |
Whether we try to find more independent cores for a given set of assumptions in the core based max-SAT algorithms.
optional bool find_multiple_cores = 84 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24275 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFixVariablesToTheirHintedValue | ( | ) |
If true, variables appearing in the solution hints will be fixed to their hinted value.
optional bool fix_variables_to_their_hinted_value = 192 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25885 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasFpRounding | ( | ) |
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28649 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasGlucoseDecayIncrement | ( | ) |
optional double glucose_decay_increment = 23 [default = 0.01];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18398 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasGlucoseDecayIncrementPeriod | ( | ) |
optional int32 glucose_decay_increment_period = 24 [default = 5000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18438 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasGlucoseMaxDecay | ( | ) |
The activity starts at 0.8 and increment by 0.01 every 5000 conflicts until 0.95. This "hack" seems to work well and comes from: Glucose 2.3 in the SAT 2013 Competition - SAT Competition 2013 http://edacc4.informatik.uni-ulm.de/SC13/solver-description-download/136
optional double glucose_max_decay = 22 [default = 0.95];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18334 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasHintConflictLimit | ( | ) |
Conflict limit used in the phase that exploit the solution hint.
optional int32 hint_conflict_limit = 153 [default = 10];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25760 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasIgnoreNames | ( | ) |
If true, we don't keep names in our internal copy of the user given model.
optional bool ignore_names = 202 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21928 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasInferAllDiffs | ( | ) |
Run a max-clique code amongst all the x != y we can find and try to infer set of variables that are all different. This allows to close neos16.mps for instance. Note that we only run this code if there is no all_diff already in the model so that if a user want to add some all_diff, we assume it is well done and do not try to add more.
optional bool infer_all_diffs = 233 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21988 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasInitialPolarity | ( | ) |
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17083 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasInitialVariablesActivity | ( | ) |
The initial value of the variables activity. A non-zero value only make sense when use_erwa_heuristic is true. Experiments with a value of 1e-2 together with the ERWA heuristic showed slighthly better result than simply using zero. The idea is that when the "learning rate" of a variable becomes lower than this value, then we prefer to branch on never explored before variables. This is not in the ERWA paper.
optional double initial_variables_activity = 76 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17495 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasInprocessingDtimeRatio | ( | ) |
Proportion of deterministic time we should spend on inprocessing. At each "restart", if the proportion is below this ratio, we will do some inprocessing, otherwise, we skip it for this restart.
optional double inprocessing_dtime_ratio = 273 [default = 0.2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22186 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasInprocessingMinimizationDtime | ( | ) |
Parameters for an heuristic similar to the one described in "An effective learnt clause minimization approach for CDCL Sat Solvers", https://www.ijcai.org/proceedings/2017/0098.pdf This is the amount of dtime we should spend on this technique during each inprocessing phase. The minimization technique is the same as the one used to minimize core in max-sat. We also minimize problem clauses and not just the learned clause that we keep forever like in the paper.
optional double inprocessing_minimization_dtime = 275 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22313 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasInprocessingProbingDtime | ( | ) |
The amount of dtime we should spend on probing for each inprocessing round.
optional double inprocessing_probing_dtime = 274 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22248 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasInstantiateAllVariables | ( | ) |
If true, the solver will add a default integer branching strategy to the already defined search strategy. If not, some variable might still not be fixed at the end of the search. For now we assume these variable can just be set to their lower bound.
optional bool instantiate_all_variables = 106 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28069 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasInterleaveBatchSize | ( | ) |
optional int32 interleave_batch_size = 134 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23746 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasInterleaveSearch | ( | ) |
Experimental. If this is true, then we interleave all our major search strategy and distribute the work amongst num_workers. The search is deterministic (independently of num_workers!), and we schedule and wait for interleave_batch_size task to be completed before synchronizing and scheduling the next batch of tasks.
optional bool interleave_search = 136 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23679 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasKeepAllFeasibleSolutionsInPresolve | ( | ) |
If true, we disable the presolve reductions that remove feasible solutions from the search space. Such solution are usually dominated by a "better" solution that is kept, but depending on the situation, we might want to keep all solutions. A trivial example is when a variable is unused. If this is true, then the presolve will not fix it to an arbitrary value and it will stay in the search space.
optional bool keep_all_feasible_solutions_in_presolve = 173 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27825 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasLinearizationLevel | ( | ) |
A non-negative level indicating the type of constraints we consider in the LP relaxation. At level zero, no LP relaxation is used. At level 1, only the linear constraint and full encoding are added. At level 2, we also add all the Boolean constraints.
optional int32 linearization_level = 90 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29763 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasLinearSplitSize | ( | ) |
Linear constraints that are not pseudo-Boolean and that are longer than this size will be split into sqrt(size) intermediate sums in order to have faster propation in the CP engine.
optional int32 linear_split_size = 256 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29698 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasLogPrefix | ( | ) |
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20115 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasLogSearchProgress | ( | ) |
Whether the solver should log the search progress. This is the maing logging parameter and if this is false, none of the logging (callbacks, log_to_stdout, log_to_response, ...) will do anything.
optional bool log_search_progress = 41 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19986 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasLogSubsolverStatistics | ( | ) |
Whether the solver should display per sub-solver search statistics. This is only useful is log_search_progress is set to true, and if the number of search workers is > 1. Note that in all case we display a bit of stats with one line per subsolver.
optional bool log_subsolver_statistics = 189 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20051 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasLogToResponse | ( | ) |
Log to response proto.
optional bool log_to_response = 187 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20276 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasLogToStdout | ( | ) |
Log to stdout.
optional bool log_to_stdout = 186 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20220 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasLpDualTolerance | ( | ) |
optional double lp_dual_tolerance = 267 [default = 1e-07];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29464 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasLpPrimalTolerance | ( | ) |
The internal LP tolerances used by CP-SAT. These applies to the internal and scaled problem. If the domains of your variables are large it might be good to use lower tolerances. If your problem is binary with low coefficients, it might be good to use higher ones to speed-up the lp solves.
optional double lp_primal_tolerance = 266 [default = 1e-07];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29400 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxAllDiffCutSize | ( | ) |
Cut generator for all diffs can add too many cuts for large all_diff constraints. This parameter restricts the large all_diff constraints to have a cut generator.
optional int32 max_all_diff_cut_size = 148 [default = 64];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30530 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxClauseActivityValue | ( | ) |
optional double max_clause_activity_value = 18 [default = 1e+20];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18534 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxConsecutiveInactiveCount | ( | ) |
If a constraint/cut in LP is not active for that many consecutive OPTIMAL solves, remove it from the LP. Note that it might be added again later if it become violated by the current LP solution.
optional int32 max_consecutive_inactive_count = 121 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31006 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxCutRoundsAtLevelZero | ( | ) |
Max number of time we perform cut generation and resolve the LP at level 0.
optional int32 max_cut_rounds_at_level_zero = 154 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30948 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxDeterministicTime | ( | ) |
Maximum time allowed in deterministic time to solve a problem. The deterministic time should be correlated with the real time used by the solver, the time unit being as close as possible to a second.
optional double max_deterministic_time = 67 [default = inf];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19374 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxDomainSizeWhenEncodingEqNeqConstraints | ( | ) |
When loading a*x + b*y ==/!= c when x and y are both fully encoded. The solver may decide to replace the linear equation by a set of clauses. This is triggered if the sizes of the domains of x and y are below the threshold.
optional int32 max_domain_size_when_encoding_eq_neq_constraints = 191 [default = 16];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29891 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxIntegerRoundingScaling | ( | ) |
In the integer rounding procedure used for MIR and Gomory cut, the maximum "scaling" we use (must be positive). The lower this is, the lower the integer coefficients of the cut will be. Note that cut generated by lower values are not necessarily worse than cut generated by larger value. There is no strict dominance relationship. Setting this to 2 result in the "strong fractional rouding" of Letchford and Lodi.
optional int32 max_integer_rounding_scaling = 119 [default = 600];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30663 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxMemoryInMb | ( | ) |
Maximum memory allowed for the whole thread containing the solver. The solver will abort as soon as it detects that this limit is crossed. As a result, this limit is approximative, but usually the solver will not go too much over. TODO(user): This is only used by the pure SAT solver, generalize to CP-SAT.
optional int64 max_memory_in_mb = 40 [default = 10000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19521 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxNumberOfConflicts | ( | ) |
Maximum number of conflicts allowed to solve a problem. TODO(user): Maybe change the way the conflict limit is enforced? currently it is enforced on each independent internal SAT solve, rather than on the overall number of conflicts across all solves. So in the context of an optimization problem, this is not really usable directly by a client.
optional int64 max_number_of_conflicts = 37 [default = 9223372036854775807];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19442 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxNumCuts | ( | ) |
The limit on the number of cuts in our cut pool. When this is reached we do not generate cuts anymore. TODO(user): We should probably remove this parameters, and just always generate cuts but only keep the best n or something.
optional int32 max_num_cuts = 91 [default = 10000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29960 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxNumIntervalsForTimetableEdgeFinding | ( | ) |
Max number of intervals for the timetable_edge_finding algorithm to propagate. A value of 0 disables the constraint.
optional int32 max_num_intervals_for_timetable_edge_finding = 260 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25123 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxPairsPairwiseReasoningInNoOverlap2D | ( | ) |
If the number of pairs to look is below this threshold, do an extra step of propagation in the no_overlap_2d constraint by looking at all pairs of intervals.
optional int32 max_pairs_pairwise_reasoning_in_no_overlap_2d = 276 [default = 1250];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25592 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxPresolveIterations | ( | ) |
In case of large reduction in a presolve iteration, we perform multiple presolve iterations. This parameter controls the maximum number of such presolve iterations.
optional int32 max_presolve_iterations = 138 [default = 3];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20978 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxSatAssumptionOrder | ( | ) |
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24393 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxSatReverseAssumptionOrder | ( | ) |
If true, adds the assumption in the reverse order of the one defined by max_sat_assumption_order.
optional bool max_sat_reverse_assumption_order = 52 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24441 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxSatStratification | ( | ) |
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24495 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxSizeToCreatePrecedenceLiteralsInDisjunctive | ( | ) |
Create one literal for each disjunction of two pairs of tasks. This slows down the solve time, but improves the lower bound of the objective in the makespan case. This will be triggered if the number of intervals is less or equal than the parameter and if use_strong_propagation_in_disjunctive is true.
optional int32 max_size_to_create_precedence_literals_in_disjunctive = 229 [default = 60];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24722 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxTimeInSeconds | ( | ) |
Maximum time allowed in seconds to solve a problem. The counter will starts at the beginning of the Solve() call.
optional double max_time_in_seconds = 36 [default = inf];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19313 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMaxVariableActivityValue | ( | ) |
optional double max_variable_activity_value = 16 [default = 1e+100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18286 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMergeAtMostOneWorkLimit | ( | ) |
optional double merge_at_most_one_work_limit = 146 [default = 100000000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21660 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMergeNoOverlapWorkLimit | ( | ) |
During presolve, we use a maximum clique heuristic to merge together no-overlap constraints or at most one constraints. This code can be slow, so we have a limit in place on the number of explored nodes in the underlying graph. The internal limit is an int64, but we use double here to simplify manual input.
optional double merge_no_overlap_work_limit = 145 [default = 1000000000000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21596 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMinimizationAlgorithm | ( | ) |
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17629 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMinimizeReductionDuringPbResolution | ( | ) |
A different algorithm during PB resolution. It minimizes the number of calls to ReduceCoefficients() which can be time consuming. However, the search space will be different and if the coefficients are large, this may lead to integer overflows that could otherwise be prevented.
optional bool minimize_reduction_during_pb_resolution = 48 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20403 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMinNumLnsWorkers | ( | ) |
Obsolete parameter. No-op.
optional int32 min_num_lns_workers = 211 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22544 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMinOrthogonalityForLpConstraints | ( | ) |
While adding constraints, skip the constraints which have orthogonality less than 'min_orthogonality_for_lp_constraints' with already added constraints during current call. Orthogonality is defined as 1 - cosine(vector angle between constraints). A value of zero disable this feature.
optional double min_orthogonality_for_lp_constraints = 115 [default = 0.05];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30880 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipAutomaticallyScaleVariables | ( | ) |
If true, some continuous variable might be automatically scaled. For now, this is only the case where we detect that a variable is actually an integer multiple of a constant. For instance, variables of the form k * 0.5 are quite frequent, and if we detect this, we will scale such variable domain by 2 to make it implied integer.
optional bool mip_automatically_scale_variables = 166 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31860 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipCheckPrecision | ( | ) |
As explained in mip_precision and mip_max_activity_exponent, we cannot always reach the wanted precision during scaling. We use this threshold to enphasize in the logs when the precision seems bad.
optional double mip_check_precision = 128 [default = 0.0001];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32234 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipComputeTrueObjectiveBound | ( | ) |
Even if we make big error when scaling the objective, we can always derive a correct lower bound on the original objective by using the exact lower bound on the scaled integer version of the objective. This should be fast, but if you don't care about having a precise lower bound, you can turn it off.
optional bool mip_compute_true_objective_bound = 198 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32300 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipDropTolerance | ( | ) |
Any value in the input mip with a magnitude lower than this will be set to zero. This is to avoid some issue in LP presolving.
optional double mip_drop_tolerance = 232 [default = 1e-16];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32517 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipMaxActivityExponent | ( | ) |
To avoid integer overflow, we always force the maximum possible constraint activity (and objective value) according to the initial variable domain to be smaller than 2 to this given power. Because of this, we cannot always reach the "mip_wanted_precision" parameter above. This can go as high as 62, but some internal algo currently abort early if they might run into integer overflow, so it is better to keep it a bit lower than this.
optional int32 mip_max_activity_exponent = 127 [default = 53];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32155 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipMaxBound | ( | ) |
We need to bound the maximum magnitude of the variables for CP-SAT, and that is the bound we use. If the MIP model expect larger variable value in the solution, then the converted model will likely not be relevant.
optional double mip_max_bound = 124 [default = 10000000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31666 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipMaxValidMagnitude | ( | ) |
Any finite values in the input MIP must be below this threshold, otherwise the model will be reported invalid. This is needed to avoid floating point overflow when evaluating bounds * coeff for instance. We are a bit more defensive, but in practice, users shouldn't use super large values in a MIP.
optional double mip_max_valid_magnitude = 199 [default = 1e+20];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32372 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipPresolveLevel | ( | ) |
When solving a MIP, we do some basic floating point presolving before scaling the problem to integer to be handled by CP-SAT. This control how much of that presolve we do. It can help to better scale floating point model, but it is not always behaving nicely.
optional int32 mip_presolve_level = 261 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32579 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipScaleLargeDomain | ( | ) |
If this is false, then mip_var_scaling is only applied to variables with "small" domain. If it is true, we scale all floating point variable independenlty of their domain.
optional bool mip_scale_large_domain = 225 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31794 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipTreatHighMagnitudeBoundsAsInfinity | ( | ) |
By default, any variable/constraint bound with a finite value and a magnitude greater than the mip_max_valid_magnitude will result with a invalid model. This flags change the behavior such that such bounds are silently transformed to +∞ or -∞. It is recommended to keep it at false, and create valid bounds.
optional bool mip_treat_high_magnitude_bounds_as_infinity = 278 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32445 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipVarScaling | ( | ) |
All continuous variable of the problem will be multiplied by this factor. By default, we don't do any variable scaling and rely on the MIP model to specify continuous variable domain with the wanted precision.
optional double mip_var_scaling = 125 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31730 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasMipWantedPrecision | ( | ) |
When scaling constraint with double coefficients to integer coefficients, we will multiply by a power of 2 and round the coefficients. We will choose the lowest power such that we have no potential overflow (see mip_max_activity_exponent) and the worst case constraint activity error does not exceed this threshold. Note that we also detect constraint with rational coefficients and scale them accordingly when it seems better instead of using a power of 2. We also relax all constraint bounds by this absolute value. For pure integer constraint, if this value if lower than one, this will not change anything. However it is needed when scaling MIP problems. If we manage to scale a constraint correctly, the maximum error we can make will be twice this value (once for the scaling error and once for the relaxed bounds). If we are not able to scale that well, we will display that fact but still scale as best as we can.
optional double mip_wanted_precision = 126 [default = 1e-06];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 32044 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasName | ( | ) |
In some context, like in a portfolio of search, it makes sense to name a given parameters set for logging purpose.
optional string name = 171 [default = ""];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 16936 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasNewConstraintsBatchSize | ( | ) |
Add that many lazy constraints (or cuts) at once in the LP. Note that at the beginning of the solve, we do add more than this.
optional int32 new_constraints_batch_size = 122 [default = 50];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31229 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasNewLinearPropagation | ( | ) |
Experimental. Use new code to propagate linear constraint.
optional bool new_linear_propagation = 224 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29640 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasNumConflictsBeforeStrategyChanges | ( | ) |
After each restart, if the number of conflict since the last strategy change is greater that this, then we increment a "strategy_counter" that can be use to change the search strategy used by the following restarts.
optional int32 num_conflicts_before_strategy_changes = 68 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19190 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasNumSearchWorkers | ( | ) |
optional int32 num_search_workers = 100 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22500 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasNumViolationLs | ( | ) |
This will create incomplete subsolvers (that are not LNS subsolvers) that use the feasibility jump code to find improving solution, treating the objective improvement as a hard constraint.
optional int32 num_violation_ls = 244 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27258 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasNumWorkers | ( | ) |
Specify the number of parallel workers (i.e. threads) to use during search. This should usually be lower than your number of available cpus + hyperthread in your machine. A value of 0 means the solver will try to use all cores on the machine. A number of 1 means no parallelism. Note that 'num_workers' is the preferred name, but if it is set to zero, we will still read the deprecated 'num_search_worker'. As of 2020-04-10, if you're using SAT via MPSolver (to solve integer programs) this field is overridden with a value of 8, if the field is not set *explicitly*. Thus, always set this field explicitly or via MPSolver::SetNumThreads().
optional int32 num_workers = 206 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22409 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasOnlyAddCutsAtLevelZero | ( | ) |
For the cut that can be generated at any level, this control if we only try to generate them at the root node.
optional bool only_add_cuts_at_level_zero = 92 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30093 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasOnlySolveIp | ( | ) |
If one try to solve a MIP model with CP-SAT, because we assume all variable to be integer after scaling, we will not necessarily have the correct optimal. Note however that all feasible solutions are valid since we will just solve a more restricted version of the original problem. This parameters is here to prevent user to think the solution is optimal when it might not be. One will need to manually set this to false to solve a MIP model where the optimal might be different. Note that this is tested after some MIP presolve steps, so even if not all original variable are integer, we might end up with a pure IP after presolve and after implied integer detection.
optional bool only_solve_ip = 222 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 31939 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasOptimizeWithCore | ( | ) |
The default optimization method is a simple "linear scan", each time trying to find a better solution than the previous one. If this is true, then we use a core-based approach (like in max-SAT) when we try to increase the lower bound instead.
optional bool optimize_with_core = 83 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26427 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasOptimizeWithLbTreeSearch | ( | ) |
Do a more conventional tree search (by opposition to SAT based one) where we keep all the explored node in a tree. This is meant to be used in a portfolio and focus on improving the objective lower bound. Keeping the whole tree allow us to report a better objective lower bound coming from the worst open node in the tree.
optional bool optimize_with_lb_tree_search = 188 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26496 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasOptimizeWithMaxHs | ( | ) |
This has no effect if optimize_with_core is false. If true, use a different core-based algorithm similar to the max-HS algo for max-SAT. This is a hybrid MIP/CP approach and it uses a MIP solver in addition to the CP/SAT one. This is also related to the PhD work of tobyodavies@ "Automatic Logic-Based Benders Decomposition with MiniZinc" http://aaai.org/ocs/index.php/AAAI/AAAI17/paper/view/14489
optional bool optimize_with_max_hs = 85 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26637 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPbCleanupIncrement | ( | ) |
Same as for the clauses, but for the learned pseudo-Boolean constraints.
optional int32 pb_cleanup_increment = 46 [default = 200];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18110 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPbCleanupRatio | ( | ) |
optional double pb_cleanup_ratio = 47 [default = 0.5];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18162 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPermutePresolveConstraintOrder | ( | ) |
optional bool permute_presolve_constraint_order = 179 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19900 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPermuteVariableRandomly | ( | ) |
This is mainly here to test the solver variability. Note that in tests, if not explicitly set to false, all 3 options will be set to true so that clients do not rely on the solver returning a specific solution if they are many equivalent optimal solutions.
optional bool permute_variable_randomly = 178 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19839 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPolarityRephaseIncrement | ( | ) |
If non-zero, then we change the polarity heuristic after that many number of conflicts in an arithmetically increasing fashion. So x the first time, 2 * x the second time, etc...
optional int32 polarity_rephase_increment = 168 [default = 1000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17228 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPolishLpSolution | ( | ) |
Whether we try to do a few degenerate iteration at the end of an LP solve to minimize the fractionality of the integer variable in the basis. This helps on some problems, but not so much on others. It also cost of bit of time to do such polish step.
optional bool polish_lp_solution = 175 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29331 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPreferredVariableOrder | ( | ) |
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17041 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPresolveBlockedClause | ( | ) |
Whether we use an heuristic to detect some basic case of blocked clause in the SAT presolve.
optional bool presolve_blocked_clause = 88 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20793 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPresolveBvaThreshold | ( | ) |
Apply Bounded Variable Addition (BVA) if the number of clauses is reduced by stricly more than this threshold. The algorithm described in the paper uses 0, but quick experiments showed that 1 is a good value. It may not be worth it to add a new variable just to remove one clause.
optional int32 presolve_bva_threshold = 73 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20911 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPresolveBveClauseWeight | ( | ) |
During presolve, we apply BVE only if this weight times the number of clauses plus the number of clause literals is not increased.
optional int32 presolve_bve_clause_weight = 55 [default = 3];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20621 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPresolveBveThreshold | ( | ) |
During presolve, only try to perform the bounded variable elimination (BVE) of a variable x if the number of occurrences of x times the number of occurrences of not(x) is not greater than this parameter.
optional int32 presolve_bve_threshold = 54 [default = 500];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20558 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPresolveExtractIntegerEnforcement | ( | ) |
If true, we will extract from linear constraints, enforcement literals of the form "integer variable at bound => simplified constraint". This should always be beneficial except that we don't always handle them as efficiently as we could for now. This causes problem on manna81.mps (LP relaxation not as tight it seems) and on neos-3354841-apure.mps.gz (too many literals created this way).
optional bool presolve_extract_integer_enforcement = 174 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21777 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPresolveInclusionWorkLimit | ( | ) |
A few presolve operations involve detecting constraints included in other constraint. Since there can be a quadratic number of such pairs, and processing them usually involve scanning them, the complexity of these operations can be big. This enforce a local deterministic limit on the number of entries scanned. Default is 1e8. A value of zero will disable these presolve rules completely.
optional int64 presolve_inclusion_work_limit = 201 [default = 100000000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21854 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPresolveProbingDeterministicTimeLimit | ( | ) |
optional double presolve_probing_deterministic_time_limit = 57 [default = 30];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20748 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPresolveSubstitutionLevel | ( | ) |
How much substitution (also called free variable aggregation in MIP litterature) should we perform at presolve. This currently only concerns variable appearing only in linear constraints. For now the value 0 turns it off and any positive value performs substitution.
optional int32 presolve_substitution_level = 147 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21707 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPresolveUseBva | ( | ) |
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
optional bool presolve_use_bva = 72 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20852 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasProbingDeterministicTimeLimit | ( | ) |
The maximum "deterministic" time limit to spend in probing. A value of zero will disable the probing. TODO(user): Clean up. The first one is used in CP-SAT, the other in pure SAT presolve.
optional double probing_deterministic_time_limit = 226 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20684 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasProbingNumCombinationsLimit | ( | ) |
How many combinations of pairs or triplets of variables we want to scan.
optional int32 probing_num_combinations_limit = 272 [default = 20000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26064 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPropagationLoopDetectionFactor | ( | ) |
Some search decisions might cause a really large number of propagations to happen when integer variables with large domains are only reduced by 1 at each step. If we propagate more than the number of variable times this parameters we try to take counter-measure. Setting this to 0.0 disable this feature. TODO(user): Setting this to something like 10 helps in most cases, but the code is currently buggy and can cause the solve to enter a bad state where no progress is made.
optional double propagation_loop_detection_factor = 221 [default = 10];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24550 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPseudoCostReliabilityThreshold | ( | ) |
The solver ignores the pseudo costs of variables with number of recordings less than this threshold.
optional int64 pseudo_cost_reliability_threshold = 123 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26365 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasPushAllTasksTowardStart | ( | ) |
Experimental code: specify if the objective pushes all tasks toward the start of the schedule.
optional bool push_all_tasks_toward_start = 262 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28873 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasRandomBranchesRatio | ( | ) |
A number between 0 and 1 that indicates the proportion of branching variables that are selected randomly instead of choosing the first variable from the given variable_ordering strategy.
optional double random_branches_ratio = 32 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17364 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasRandomizeSearch | ( | ) |
Randomize fixed search.
optional bool randomize_search = 103 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28752 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasRandomPolarityRatio | ( | ) |
The proportion of polarity chosen at random. Note that this take precedence over the phase saving heuristic. This is different from initial_polarity:POLARITY_RANDOM because it will select a new random polarity each time the variable is branched upon instead of selecting one initially and then always taking this choice.
optional double random_polarity_ratio = 45 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17294 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasRandomSeed | ( | ) |
At the beginning of each solve, the random number generator used in some part of the solver is reinitialized to this seed. If you change the random seed, the solver may make different choices during the solving process. For some problems, the running time may vary a lot depending on small change in the solving algorithm. Running the solver with different seeds enables to have more robust benchmarks when evaluating new features.
optional int32 random_seed = 31 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19762 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasRelativeGapLimit | ( | ) |
optional double relative_gap_limit = 160 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19712 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasRepairHint | ( | ) |
If true, the solver tries to repair the solution given in the hint. This search terminates after the 'hint_conflict_limit' is reached and the solver switches to regular search. If false, then we do a FIXED_SEARCH using the hint until the hint_conflict_limit is reached.
optional bool repair_hint = 167 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25819 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasRestartDlAverageRatio | ( | ) |
In the moving average restart algorithms, a restart is triggered if the window average times this ratio is greater that the global average.
optional double restart_dl_average_ratio = 63 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18945 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasRestartLbdAverageRatio | ( | ) |
optional double restart_lbd_average_ratio = 71 [default = 1];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19000 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasRestartPeriod | ( | ) |
Restart period for the FIXED_RESTART strategy. This is also the multiplier used by the LUBY_RESTART strategy.
optional int32 restart_period = 30 [default = 50];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18829 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasRestartRunningWindowSize | ( | ) |
Size of the window for the moving average restarts.
optional int32 restart_running_window_size = 62 [default = 50];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18888 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasRootLpIterations | ( | ) |
Even at the root node, we do not want to spend too much time on the LP if it is "difficult". So we solve it in "chunks" of that many iterations. The solve will be continued down in the tree or the next time we go back to the root node.
optional int32 root_lp_iterations = 227 [default = 2000];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 30811 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasSearchBranching | ( | ) |
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25713 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasSearchRandomVariablePoolSize | ( | ) |
Search randomization will collect the top 'search_random_variable_pool_size' valued variables, and pick one randomly. The value of the variable is specific to each strategy.
optional int64 search_random_variable_pool_size = 104 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28810 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasShareBinaryClauses | ( | ) |
Allows sharing of new learned binary clause between workers.
optional bool share_binary_clauses = 203 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23902 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasSharedTreeMaxNodesPerWorker | ( | ) |
In order to limit total shared memory and communication overhead, limit the total number of nodes that may be generated in the shared tree. If the shared tree runs out of unassigned leaves, workers act as portfolio workers. Note: this limit includes interior nodes, not just leaves.
optional int32 shared_tree_max_nodes_per_worker = 238 [default = 128];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27631 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasSharedTreeNumWorkers | ( | ) |
Enables experimental workstealing-like shared tree search. If non-zero, start this many complete worker threads to explore a shared search tree. These workers communicate objective bounds and simple decision nogoods relating to the shared prefix of the tree, and will avoid exploring the same subtrees as one another.
optional int32 shared_tree_num_workers = 235 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27440 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasSharedTreeSplitStrategy | ( | ) |
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27691 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasSharedTreeWorkerObjectiveSplitProbability | ( | ) |
After their assigned prefix, shared tree workers will branch on the objective with this probability. Higher numbers cause the shared tree search to focus on improving the lower bound over finding primal solutions.
optional double shared_tree_worker_objective_split_probability = 237 [default = 0.5];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27566 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasShareLevelZeroBounds | ( | ) |
Allows sharing of the bounds of modified variables at level 0.
optional bool share_level_zero_bounds = 114 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23846 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasShareObjectiveBounds | ( | ) |
Allows objective sharing between workers.
optional bool share_objective_bounds = 113 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 23790 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasShavingSearchDeterministicTime | ( | ) |
Specifies the amount of deterministic time spent of each try at shaving a bound in the shaving search.
optional double shaving_search_deterministic_time = 205 [default = 0.001];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26181 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasSolutionPoolSize | ( | ) |
Size of the top-n different solutions kept by the solver. This parameter must be > 0. Currently this only impact the "base" solution chosen for a LNS fragment.
optional int32 solution_pool_size = 193 [default = 3];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28416 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasStopAfterFirstSolution | ( | ) |
For an optimization problem, stop the solver as soon as we have a solution.
optional bool stop_after_first_solution = 98 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28202 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasStopAfterPresolve | ( | ) |
Mainly used when improving the presolver. When true, stops the solver after the presolve is complete (or after loading and root level propagation).
optional bool stop_after_presolve = 149 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28259 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasStopAfterRootPropagation | ( | ) |
optional bool stop_after_root_propagation = 252 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28314 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasStrategyChangeIncreaseRatio | ( | ) |
The parameter num_conflicts_before_strategy_changes is increased by that much after each strategy change.
optional double strategy_change_increase_ratio = 69 [default = 0];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19253 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasSubsumptionDuringConflictAnalysis | ( | ) |
At a really low cost, during the 1-UIP conflict computation, it is easy to detect if some of the involved reasons are subsumed by the current conflict. When this is true, such clauses are detached and later removed from the problem.
optional bool subsumption_during_conflict_analysis = 56 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17721 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasSymmetryLevel | ( | ) |
Whether we try to automatically detect the symmetries in a model and exploit them. Currently, at level 1 we detect them in presolve and try to fix Booleans. At level 2, we also do some form of dynamic symmetry breaking during search.
optional int32 symmetry_level = 183 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29575 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasTableCompressionLevel | ( | ) |
How much we try to "compress" a table constraint. Compressing more leads to less Booleans and faster propagation but can reduced the quality of the lp relaxation. Values goes from 0 to 3 where we always try to fully compress a table. At 2, we try to automatically decide if it is worth it.
optional int32 table_compression_level = 217 [default = 2];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 21287 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasTestFeasibilityJump | ( | ) |
Disable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.
optional bool test_feasibility_jump = 240 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26773 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseAbslRandom | ( | ) |
optional bool use_absl_random = 180 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19940 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseAreaEnergeticReasoningInNoOverlap2D | ( | ) |
When this is true, the no_overlap_2d constraint is reinforced with an energetic reasoning that uses an area-based energy. This can be combined with the two other overlap heuristics above.
optional bool use_area_energetic_reasoning_in_no_overlap_2d = 271 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25528 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseBlockingRestart | ( | ) |
Block a moving restart algorithm if the trail size of the current conflict is greater than the multiplier times the moving average of the trail size at the previous conflicts.
optional bool use_blocking_restart = 64 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 19046 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseCombinedNoOverlap | ( | ) |
This can be beneficial if there is a lot of no-overlap constraints but a relatively low number of different intervals in the problem. Like 1000 intervals, but 1M intervals in the no-overlap constraints covering them.
optional bool use_combined_no_overlap = 133 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29078 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseDisjunctiveConstraintInCumulative | ( | ) |
When this is true, the cumulative constraint is reinforced with propagators from the disjunctive constraint to improve the inference on a set of tasks that are disjunctive at the root of the problem. This additional level supplements the default level of reasoning. Propagators of the cumulative constraint will not be used at all if all the tasks are disjunctive at root node. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_disjunctive_constraint_in_cumulative = 80 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25307 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseDualSchedulingHeuristics | ( | ) |
When set, it activates a few scheduling parameters to improve the lower bound of scheduling problems. This is only effective with multiple workers as it modifies the reduced_cost, lb_tree_search, and probing workers.
optional bool use_dual_scheduling_heuristics = 214 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25656 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseDynamicPrecedenceInCumulative | ( | ) |
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24918 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseDynamicPrecedenceInDisjunctive | ( | ) |
Whether we try to branch on decision "interval A before interval B" rather than on intervals bounds. This usually works better, but slow down a bit the time to find the first solution. These parameters are still EXPERIMENTAL, the result should be correct, but it some corner cases, they can cause some failing CHECK in the solver.
optional bool use_dynamic_precedence_in_disjunctive = 263 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24851 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseEnergeticReasoningInNoOverlap2D | ( | ) |
When this is true, the no_overlap_2d constraint is reinforced with energetic reasoning. This additional level supplements the default level of reasoning.
optional bool use_energetic_reasoning_in_no_overlap_2d = 213 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25464 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseErwaHeuristic | ( | ) |
Whether we use the ERWA (Exponential Recency Weighted Average) heuristic as described in "Learning Rate Based Branching Heuristic for SAT solvers", J.H.Liang, V. Ganesh, P. Poupart, K.Czarnecki, SAT 2016.
optional bool use_erwa_heuristic = 75 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17428 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseExactLpReason | ( | ) |
The solver usually exploit the LP relaxation of a model. If this option is true, then whatever is infered by the LP will be used like an heuristic to compute EXACT propagation on the IP. So with this option, there is no numerical imprecision issues.
optional bool use_exact_lp_reason = 109 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29011 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseExtendedProbing | ( | ) |
Use extended probing (probe bool_or, at_most_one, exactly_one).
optional bool use_extended_probing = 269 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26008 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseFeasibilityJump | ( | ) |
Parameters for an heuristic similar to the one described in the paper: "Feasibility Jump: an LP-free Lagrangian MIP heuristic", Bjørnar Luteberget, Giorgio Sartor, 2023, Mathematical Programming Computation.
optional bool use_feasibility_jump = 265 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26710 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseFeasibilityPump | ( | ) |
Adds a feasibility pump subsolver along with lns subsolvers.
optional bool use_feasibility_pump = 164 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28534 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseHardPrecedencesInCumulative | ( | ) |
If true, detect and create constraint for integer variable that are "after" a set of intervals in the same cumulative constraint. Experimental: by default we just use "direct" precedences. If exploit_all_precedences is true, we explore the full precedence graph. This assumes we have a DAG otherwise it fails.
optional bool use_hard_precedences_in_cumulative = 215 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25187 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseImpliedBounds | ( | ) |
Stores and exploits "implied-bounds" in the solver. That is, relations of the form literal => (var >= bound). This is currently used to derive stronger cuts.
optional bool use_implied_bounds = 144 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 29266 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseLbRelaxLns | ( | ) |
Turns on neighborhood generator based on local branching LP. Based on Huang et al., "Local Branching Relaxation Heuristics for Integer Linear Programs", 2023.
optional bool use_lb_relax_lns = 255 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28592 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseLnsOnly | ( | ) |
LNS parameters.
optional bool use_lns_only = 101 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28358 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseObjectiveLbSearch | ( | ) |
If true, search will search in ascending max objective value (when minimizing) starting from the lower bound of the objective.
optional bool use_objective_lb_search = 228 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26241 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseObjectiveShavingSearch | ( | ) |
This search differs from the previous search as it will not use assumptions to bound the objective, and it will recreate a full model with the hardcoded objective value.
optional bool use_objective_shaving_search = 253 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26302 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseOptimizationHints | ( | ) |
For an optimization problem, whether we follow some hints in order to find a better first solution. For a variable with hint, the solver will always try to follow the hint. It will revert to the variable_branching default otherwise.
optional bool use_optimization_hints = 35 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24141 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseOptionalVariables | ( | ) |
If true, we automatically detect variables whose constraint are always enforced by the same literal and we mark them as optional. This allows to propagate them as if they were present in some situation. TODO(user): This is experimental and seems to lead to wrong optimal in some situation. It should however gives correct solutions. Fix.
optional bool use_optional_variables = 108 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28937 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseOverloadCheckerInCumulative | ( | ) |
When this is true, the cumulative constraint is reinforced with overload checking, i.e., an additional level of reasoning based on energy. This additional level supplements the default level of reasoning as well as timetable edge finding. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_overload_checker_in_cumulative = 78 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24968 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUsePbResolution | ( | ) |
Whether to use pseudo-Boolean resolution to analyze a conflict. Note that this option only make sense if your problem is modelized using pseudo-Boolean constraints. If you only have clauses, this shouldn't change anything (except slow the solver down).
optional bool use_pb_resolution = 43 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 20335 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUsePhaseSaving | ( | ) |
If this is true, then the polarity of a variable will be the last value it was assigned to, or its default polarity if it was never assigned since the call to ResetDecisionHeuristic(). Actually, we use a newer version where we follow the last value in the longest non-conflicting partial assignment in the current phase. This is called 'literal phase saving'. For details see 'A Lightweight Component Caching Scheme for Satisfiability Solvers' K. Pipatsrisawat and A.Darwiche, In 10th International Conference on Theory and Applications of Satisfiability Testing, 2007.
optional bool use_phase_saving = 44 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 17140 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUsePrecedencesInDisjunctiveConstraint | ( | ) |
When this is true, then a disjunctive constraint will try to use the precedence relations between time intervals to propagate their bounds further. For instance if task A and B are both before C and task A and B are in disjunction, then we can deduce that task C must start after duration(A) + duration(B) instead of simply max(duration(A), duration(B)), provided that the start time for all task was currently zero. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_precedences_in_disjunctive_constraint = 74 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24638 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseProbingSearch | ( | ) |
If true, search will continuously probe Boolean variables, and integer variable bounds. This parameter is set to true in parallel on the probing worker.
optional bool use_probing_search = 176 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25946 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseRinsLns | ( | ) |
Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 28478 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseSatInprocessing | ( | ) |
Enable or disable "inprocessing" which is some SAT presolving done at each restart to the root level.
optional bool use_sat_inprocessing = 163 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 22125 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseSharedTreeSearch | ( | ) |
Set on shared subtree workers. Users should not set this directly.
optional bool use_shared_tree_search = 236 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27508 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseShavingInProbingSearch | ( | ) |
Add a shaving phase (where the solver tries to prove that the lower or upper bound of a variable are infeasible) to the probing search.
optional bool use_shaving_in_probing_search = 204 [default = true];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 26121 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseStrongPropagationInDisjunctive | ( | ) |
Enable stronger and more expensive propagation on no_overlap constraint.
optional bool use_strong_propagation_in_disjunctive = 230 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 24790 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseTimetableEdgeFindingInCumulative | ( | ) |
When this is true, the cumulative constraint is reinforced with timetable edge finding, i.e., an additional level of reasoning based on the conjunction of energy and mandatory parts. This additional level supplements the default level of reasoning as well as overload_checker. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_timetable_edge_finding_in_cumulative = 79 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25048 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasUseTimetablingInNoOverlap2D | ( | ) |
When this is true, the no_overlap_2d constraint is reinforced with propagators from the cumulative constraints. It consists of ignoring the position of rectangles in one position and projecting the no_overlap_2d on the other dimension to create a cumulative constraint. This is done on both axis. This additional level supplements the default level of reasoning.
optional bool use_timetabling_in_no_overlap_2d = 200 [default = false];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 25394 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasVariableActivityDecay | ( | ) |
Each time a conflict is found, the activities of some variables are increased by one. Then, the activity of all variables are multiplied by variable_activity_decay. To implement this efficiently, the activity of all the variables is not decayed at each conflict. Instead, the activity increment is multiplied by 1 / decay. When an activity reach max_variable_activity_value, all the activity are multiplied by 1 / max_variable_activity_value.
optional double variable_activity_decay = 15 [default = 0.8];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 18213 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasViolationLsCompoundMoveProbability | ( | ) |
Probability of using compound move search each restart. TODO(user): Add reference to paper when published.
optional double violation_ls_compound_move_probability = 259 [default = 0.5];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27377 of file SatParameters.java.
boolean com.google.ortools.sat.SatParameters.Builder.hasViolationLsPerturbationPeriod | ( | ) |
How long violation_ls should wait before perturbating a solution.
optional int32 violation_ls_perturbation_period = 249 [default = 100];
Implements com.google.ortools.sat.SatParametersOrBuilder.
Definition at line 27320 of file SatParameters.java.
|
protected |
Definition at line 13487 of file SatParameters.java.
final boolean com.google.ortools.sat.SatParameters.Builder.isInitialized | ( | ) |
Definition at line 15605 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.mergeFrom | ( | com.google.ortools.sat.SatParameters | other | ) |
Definition at line 14841 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.mergeFrom | ( | com.google.protobuf.CodedInputStream | input, |
com.google.protobuf.ExtensionRegistryLite | extensionRegistry ) throws java.io.IOException |
Definition at line 15610 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.mergeFrom | ( | com.google.protobuf.Message | other | ) |
Definition at line 14832 of file SatParameters.java.
final Builder com.google.ortools.sat.SatParameters.Builder.mergeUnknownFields | ( | final com.google.protobuf.UnknownFieldSet | unknownFields | ) |
Definition at line 32640 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.removeSubsolverParams | ( | int | index | ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23541 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAbsoluteGapLimit | ( | double | value | ) |
Stop the search when the gap between the best feasible objective (O) and our best objective bound (B) is smaller than a limit. The exact definition is: - Absolute: abs(O - B) - Relative: abs(O - B) / max(1, abs(O)). Important: The relative gap depends on the objective offset! If you artificially shift the objective, you will get widely different value of the relative gap. Note that if the gap is reached, the search status will be OPTIMAL. But one can check the best objective bound to see the actual gap. If the objective is integer, then any absolute gap < 1 will lead to a true optimal. If the objective is floating point, a gap of zero make little sense so is is why we use a non-zero default value. At the end of the search, we will display a warning if OPTIMAL is reported yet the gap is greater than this absolute gap.
optional double absolute_gap_limit = 159 [default = 0.0001];
value | The absoluteGapLimit to set. |
Definition at line 19667 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAddCgCuts | ( | boolean | value | ) |
Whether we generate and add Chvatal-Gomory cuts to the LP at root node. Note that for now, this is not heavily tuned.
optional bool add_cg_cuts = 117 [default = true];
value | The addCgCuts to set. |
Definition at line 30251 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAddCliqueCuts | ( | boolean | value | ) |
Whether we generate clique cuts from the binary implication graph. Note that as the search goes on, this graph will contains new binary clauses learned by the SAT engine.
optional bool add_clique_cuts = 172 [default = true];
value | The addCliqueCuts to set. |
Definition at line 30434 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAddLinMaxCuts | ( | boolean | value | ) |
For the lin max constraints, generates the cuts described in "Strong mixed-integer programming formulations for trained neural networks" by Ross Anderson et. (https://arxiv.org/pdf/1811.01988.pdf)
optional bool add_lin_max_cuts = 152 [default = true];
value | The addLinMaxCuts to set. |
Definition at line 30622 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAddLpConstraintsLazily | ( | boolean | value | ) |
If true, we start by an empty LP, and only add constraints not satisfied by the current LP solution batch by batch. A constraint that is only added like this is known as a "lazy" constraint in the literature, except that we currently consider all constraints as lazy here.
optional bool add_lp_constraints_lazily = 112 [default = true];
value | The addLpConstraintsLazily to set. |
Definition at line 30773 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAddMirCuts | ( | boolean | value | ) |
Whether we generate MIR cuts at root node. Note that for now, this is not heavily tuned.
optional bool add_mir_cuts = 120 [default = true];
value | The addMirCuts to set. |
Definition at line 30311 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAddObjectiveCut | ( | boolean | value | ) |
When the LP objective is fractional, do we add the cut that forces the linear objective expression to be greater or equal to this fractional value rounded up? We can always do that since our objective is integer, and combined with MIR heuristic to reduce the coefficient of such cut, it can help.
optional bool add_objective_cut = 197 [default = false];
value | The addObjectiveCut to set. |
Definition at line 30188 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAddRltCuts | ( | boolean | value | ) |
Whether we generate RLT cuts. This is still experimental but can help on binary problem with a lot of clauses of size 3.
optional bool add_rlt_cuts = 279 [default = true];
value | The addRltCuts to set. |
Definition at line 30495 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAddZeroHalfCuts | ( | boolean | value | ) |
Whether we generate Zero-Half cuts at root node. Note that for now, this is not heavily tuned.
optional bool add_zero_half_cuts = 169 [default = true];
value | The addZeroHalfCuts to set. |
Definition at line 30371 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAlsoBumpVariablesInConflictReasons | ( | boolean | value | ) |
When this is true, then the variables that appear in any of the reason of the variables in a conflict have their activity bumped. This is addition to the variables in the conflict, and the one that were used during conflict resolution.
optional bool also_bump_variables_in_conflict_reasons = 77 [default = false];
value | The alsoBumpVariablesInConflictReasons to set. |
Definition at line 17599 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAtMostOneMaxExpansionSize | ( | int | value | ) |
All at_most_one constraints with a size <= param will be replaced by a quadratic number of binary implications.
optional int32 at_most_one_max_expansion_size = 270 [default = 3];
value | The atMostOneMaxExpansionSize to set. |
Definition at line 29167 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setAutoDetectGreaterThanAtLeastOneOf | ( | boolean | value | ) |
If true, then the precedences propagator try to detect for each variable if it has a set of "optional incoming arc" for which at least one of them is present. This is usually useful to have but can be slow on model with a lot of precedence.
optional bool auto_detect_greater_than_at_least_one_of = 95 [default = true];
value | The autoDetectGreaterThanAtLeastOneOf to set. |
Definition at line 28167 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setBinaryMinimizationAlgorithm | ( | com.google.ortools.sat.SatParameters.BinaryMinizationAlgorithm | value | ) |
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];
value | The binaryMinimizationAlgorithm to set. |
Definition at line 17688 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setBinarySearchNumConflicts | ( | int | value | ) |
If non-negative, perform a binary search on the objective variable in order to find an [min, max] interval outside of which the solver proved unsat/sat under this amount of conflict. This can quickly reduce the objective domain on some problems.
optional int32 binary_search_num_conflicts = 99 [default = -1];
value | The binarySearchNumConflicts to set. |
Definition at line 26597 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setBlockingRestartMultiplier | ( | double | value | ) |
optional double blocking_restart_multiplier = 66 [default = 1.4];
value | The blockingRestartMultiplier to set. |
Definition at line 19160 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setBlockingRestartWindowSize | ( | int | value | ) |
optional int32 blocking_restart_window_size = 65 [default = 5000];
value | The blockingRestartWindowSize to set. |
Definition at line 19120 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setBooleanEncodingLevel | ( | int | value | ) |
A non-negative level indicating how much we should try to fully encode Integer variables as Boolean.
optional int32 boolean_encoding_level = 107 [default = 1];
value | The booleanEncodingLevel to set. |
Definition at line 29855 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setCatchSigintSignal | ( | boolean | value | ) |
Indicates if the CP-SAT layer should catch Control-C (SIGINT) signals when calling solve. If set, catching the SIGINT signal will terminate the search gracefully, as if a time limit was reached.
optional bool catch_sigint_signal = 135 [default = true];
value | The catchSigintSignal to set. |
Definition at line 29230 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setClauseActivityDecay | ( | double | value | ) |
Clause activity parameters (same effect as the one on the variables).
optional double clause_activity_decay = 17 [default = 0.999];
value | The clauseActivityDecay to set. |
Definition at line 18506 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setClauseCleanupLbdBound | ( | int | value | ) |
All the clauses with a LBD (literal blocks distance) lower or equal to this parameters will always be kept.
optional int32 clause_cleanup_lbd_bound = 59 [default = 5];
value | The clauseCleanupLbdBound to set. |
Definition at line 18035 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setClauseCleanupOrdering | ( | com.google.ortools.sat.SatParameters.ClauseOrdering | value | ) |
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];
value | The clauseCleanupOrdering to set. |
Definition at line 18080 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setClauseCleanupPeriod | ( | int | value | ) |
Trigger a cleanup when this number of "deletable" clauses is learned.
optional int32 clause_cleanup_period = 11 [default = 10000];
value | The clauseCleanupPeriod to set. |
Definition at line 17810 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setClauseCleanupProtection | ( | com.google.ortools.sat.SatParameters.ClauseProtection | value | ) |
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];
value | The clauseCleanupProtection to set. |
Definition at line 17978 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setClauseCleanupRatio | ( | double | value | ) |
During a cleanup, if clause_cleanup_target is 0, we will delete the clause_cleanup_ratio of "deletable" clauses instead of aiming for a fixed target of clauses to keep.
optional double clause_cleanup_ratio = 190 [default = 0.5];
value | The clauseCleanupRatio to set. |
Definition at line 17932 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setClauseCleanupTarget | ( | int | value | ) |
During a cleanup, we will always keep that number of "deletable" clauses. Note that this doesn't include the "protected" clauses.
optional int32 clause_cleanup_target = 13 [default = 0];
value | The clauseCleanupTarget to set. |
Definition at line 17869 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setConvertIntervals | ( | boolean | value | ) |
Temporary flag util the feature is more mature. This convert intervals to the newer proto format that support affine start/var/end instead of just variables.
optional bool convert_intervals = 177 [default = true];
value | The convertIntervals to set. |
Definition at line 29538 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setCoreMinimizationLevel | ( | int | value | ) |
If positive, we spend some effort on each core: - At level 1, we use a simple heuristic to try to minimize an UNSAT core. - At level 2, we use propagation to minimize the core but also identify literal in at most one relationship in this core.
optional int32 core_minimization_level = 50 [default = 2];
value | The coreMinimizationLevel to set. |
Definition at line 24239 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setCountAssumptionLevelsInLbd | ( | boolean | value | ) |
Whether or not the assumption levels are taken into account during the LBD computation. According to the reference below, not counting them improves the solver in some situation. Note that this only impact solves under assumptions. Gilles Audemard, Jean-Marie Lagniez, Laurent Simon, "Improving Glucose for Incremental SAT Solving with Assumptions: Application to MUS Extraction" Theory and Applications of Satisfiability Testing - SAT 2013, Lecture Notes in Computer Science Volume 7962, 2013, pp 309-317.
optional bool count_assumption_levels_in_lbd = 49 [default = true];
value | The countAssumptionLevelsInLbd to set. |
Definition at line 20516 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setCoverOptimization | ( | boolean | value | ) |
If true, when the max-sat algo find a core, we compute the minimal number of literals in the core that needs to be true to have a feasible solution. This is also called core exhaustion in more recent max-SAT papers.
optional bool cover_optimization = 89 [default = true];
value | The coverOptimization to set. |
Definition at line 24364 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setCpModelPresolve | ( | boolean | value | ) |
Whether we presolve the cp_model before solving it.
optional bool cp_model_presolve = 86 [default = true];
value | The cpModelPresolve to set. |
Definition at line 21064 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setCpModelProbingLevel | ( | int | value | ) |
How much effort do we spend on probing. 0 disables it completely.
optional int32 cp_model_probing_level = 110 [default = 2];
value | The cpModelProbingLevel to set. |
Definition at line 21120 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setCpModelUseSatPresolve | ( | boolean | value | ) |
Whether we also use the sat presolve when cp_model_presolve is true.
optional bool cp_model_use_sat_presolve = 93 [default = true];
value | The cpModelUseSatPresolve to set. |
Definition at line 21176 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setCutActiveCountDecay | ( | double | value | ) |
optional double cut_active_count_decay = 156 [default = 0.8];
value | The cutActiveCountDecay to set. |
Definition at line 31144 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setCutCleanupTarget | ( | int | value | ) |
Target number of constraints to remove during cleanup.
optional int32 cut_cleanup_target = 157 [default = 1000];
value | The cutCleanupTarget to set. |
Definition at line 31196 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setCutLevel | ( | int | value | ) |
Control the global cut effort. Zero will turn off all cut. For now we just have one level. Note also that most cuts are only used at linearization level >= 2.
optional int32 cut_level = 196 [default = 1];
value | The cutLevel to set. |
Definition at line 30058 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setCutMaxActiveCountValue | ( | double | value | ) |
These parameters are similar to sat clause management activity parameters. They are effective only if the number of generated cuts exceed the storage limit. Default values are based on a few experiments on miplib instances.
optional double cut_max_active_count_value = 155 [default = 10000000000];
value | The cutMaxActiveCountValue to set. |
Definition at line 31098 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setDebugCrashOnBadHint | ( | boolean | value | ) |
Crash if we do not manage to complete the hint into a full solution.
optional bool debug_crash_on_bad_hint = 195 [default = false];
value | The debugCrashOnBadHint to set. |
Definition at line 24106 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setDebugMaxNumPresolveOperations | ( | int | value | ) |
If positive, try to stop just after that many presolve rules have been applied. This is mainly useful for debugging presolve.
optional int32 debug_max_num_presolve_operations = 151 [default = 0];
value | The debugMaxNumPresolveOperations to set. |
Definition at line 24049 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setDebugPostsolveWithFullSolver | ( | boolean | value | ) |
We have two different postsolve code. The default one should be better and it allows for a more powerful presolve, but it can be useful to postsolve using the full solver instead.
optional bool debug_postsolve_with_full_solver = 162 [default = false];
value | The debugPostsolveWithFullSolver to set. |
Definition at line 23988 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setDefaultRestartAlgorithms | ( | java.lang.String | value | ) |
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];
value | The defaultRestartAlgorithms to set. |
Definition at line 18786 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setDefaultRestartAlgorithmsBytes | ( | com.google.protobuf.ByteString | value | ) |
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];
value | The bytes for defaultRestartAlgorithms to set. |
Definition at line 18809 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setDetectLinearizedProduct | ( | boolean | value | ) |
Infer products of Boolean or of Boolean time IntegerVariable from the linear constrainst in the problem. This can be used in some cuts, altough for now we don't really exploit it.
optional bool detect_linearized_product = 277 [default = false];
value | The detectLinearizedProduct to set. |
Definition at line 31630 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setDetectTableWithCost | ( | boolean | value | ) |
If true, we detect variable that are unique to a table constraint and only there to encode a cost on each tuple. This is usually the case when a WCSP (weighted constraint program) is encoded into CP-SAT format. This can lead to a dramatic speed-up for such problems but is still experimental at this point.
optional bool detect_table_with_cost = 216 [default = false];
value | The detectTableWithCost to set. |
Definition at line 21247 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setDisableConstraintExpansion | ( | boolean | value | ) |
If true, it disable all constraint expansion. This should only be used to test the presolve of expanded constraints.
optional bool disable_constraint_expansion = 181 [default = false];
value | The disableConstraintExpansion to set. |
Definition at line 21499 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setDiversifyLnsParams | ( | boolean | value | ) |
If true, registers more lns subsolvers with different parameters.
optional bool diversify_lns_params = 137 [default = false];
value | The diversifyLnsParams to set. |
Definition at line 28720 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setEncodeComplexLinearConstraintWithInteger | ( | boolean | value | ) |
Linear constraint with a complex right hand side (more than a single interval) need to be expanded, there is a couple of way to do that.
optional bool encode_complex_linear_constraint_with_integer = 223 [default = false];
value | The encodeComplexLinearConstraintWithInteger to set. |
Definition at line 21559 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setEnumerateAllSolutions | ( | boolean | value | ) |
Whether we enumerate all solutions of a problem without objective. Note that setting this to true automatically disable some presolve reduction that can remove feasible solution. That is it has the same effect as setting keep_all_feasible_solutions_in_presolve. TODO(user): Do not do that and let the user choose what behavior is best by setting keep_all_feasible_solutions_in_presolve ?
optional bool enumerate_all_solutions = 87 [default = false];
value | The enumerateAllSolutions to set. |
Definition at line 27780 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setExpandAlldiffConstraints | ( | boolean | value | ) |
If true, expand all_different constraints that are not permutations. Permutations (#Variables = #Values) are always expanded.
optional bool expand_alldiff_constraints = 170 [default = false];
value | The expandAlldiffConstraints to set. |
Definition at line 21379 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setExpandReservoirConstraints | ( | boolean | value | ) |
If true, expand the reservoir constraints by creating booleans for all possible precedences between event and encoding the constraint.
optional bool expand_reservoir_constraints = 182 [default = true];
value | The expandReservoirConstraints to set. |
Definition at line 21439 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setExploitAllLpSolution | ( | boolean | value | ) |
If true and the Lp relaxation of the problem has a solution, try to exploit it. This is same as above except in this case the lp solution might not be an integer solution.
optional bool exploit_all_lp_solution = 116 [default = true];
value | The exploitAllLpSolution to set. |
Definition at line 31386 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setExploitAllPrecedences | ( | boolean | value | ) |
optional bool exploit_all_precedences = 220 [default = false];
value | The exploitAllPrecedences to set. |
Definition at line 25270 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setExploitBestSolution | ( | boolean | value | ) |
When branching on a variable, follow the last best solution value.
optional bool exploit_best_solution = 130 [default = false];
value | The exploitBestSolution to set. |
Definition at line 31444 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setExploitIntegerLpSolution | ( | boolean | value | ) |
If true and the Lp relaxation of the problem has an integer optimal solution, try to exploit it. Note that since the LP relaxation may not contain all the constraints, such a solution is not necessarily a solution of the full problem.
optional bool exploit_integer_lp_solution = 94 [default = true];
value | The exploitIntegerLpSolution to set. |
Definition at line 31321 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setExploitObjective | ( | boolean | value | ) |
When branching an a variable that directly affect the objective, branch on the value that lead to the best objective first.
optional bool exploit_objective = 131 [default = true];
value | The exploitObjective to set. |
Definition at line 31567 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setExploitRelaxationSolution | ( | boolean | value | ) |
When branching on a variable, follow the last best relaxation solution value. We use the relaxation with the tightest bound on the objective as the best relaxation solution.
optional bool exploit_relaxation_solution = 161 [default = false];
value | The exploitRelaxationSolution to set. |
Definition at line 31506 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setExtraSubsolvers | ( | int | index, |
java.lang.String | value ) |
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;
index | The index to set the value at. |
value | The extraSubsolvers to set. |
Definition at line 23042 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFeasibilityJumpDecay | ( | double | value | ) |
On each restart, we randomly choose if we use decay (with this parameter) or no decay.
optional double feasibility_jump_decay = 242 [default = 0.95];
value | The feasibilityJumpDecay to set. |
Definition at line 26859 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFeasibilityJumpEnableRestarts | ( | boolean | value | ) |
When stagnating, feasibility jump will either restart from a default solution (with some possible randomization), or randomly pertubate the current solution. This parameter selects the first option.
optional bool feasibility_jump_enable_restarts = 250 [default = true];
value | The feasibilityJumpEnableRestarts to set. |
Definition at line 27162 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFeasibilityJumpLinearizationLevel | ( | int | value | ) |
How much do we linearize the problem in the local search code.
optional int32 feasibility_jump_linearization_level = 257 [default = 2];
value | The feasibilityJumpLinearizationLevel to set. |
Definition at line 26916 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFeasibilityJumpMaxExpandedConstraintSize | ( | int | value | ) |
Maximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion.
optional int32 feasibility_jump_max_expanded_constraint_size = 264 [default = 100];
value | The feasibilityJumpMaxExpandedConstraintSize to set. |
Definition at line 27223 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFeasibilityJumpRestartFactor | ( | int | value | ) |
This is a factor that directly influence the work before each restart. Setting this to zero disable restart, and increasing it lead to longer restarts.
optional int32 feasibility_jump_restart_factor = 258 [default = 1];
value | The feasibilityJumpRestartFactor to set. |
Definition at line 26978 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFeasibilityJumpVarPerburbationRangeRatio | ( | double | value | ) |
Max distance between the default value and the pertubated value relative to the range of the domain of the variable.
optional double feasibility_jump_var_perburbation_range_ratio = 248 [default = 0.2];
value | The feasibilityJumpVarPerburbationRangeRatio to set. |
Definition at line 27099 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFeasibilityJumpVarRandomizationProbability | ( | double | value | ) |
Probability for a variable to have a non default value upon restarts or perturbations.
optional double feasibility_jump_var_randomization_probability = 247 [default = 0];
value | The feasibilityJumpVarRandomizationProbability to set. |
Definition at line 27039 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setField | ( | com.google.protobuf.Descriptors.FieldDescriptor | field, |
java.lang.Object | value ) |
Definition at line 14804 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFillAdditionalSolutionsInResponse | ( | boolean | value | ) |
If true, the final response addition_solutions field will be filled with all solutions from our solutions pool. Note that if both this field and enumerate_all_solutions is true, we will copy to the pool all of the solution found. So if solution_pool_size is big enough, you can get all solutions this way instead of using the solution callback. Note that this only affect the "final" solution, not the one passed to the solution callbacks.
optional bool fill_additional_solutions_in_response = 194 [default = false];
value | The fillAdditionalSolutionsInResponse to set. |
Definition at line 28025 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFillTightenedDomainsInResponse | ( | boolean | value | ) |
If true, add information about the derived variable domains to the CpSolverResponse. It is an option because it makes the response slighly bigger and there is a bit more work involved during the postsolve to construct it, but it should still have a low overhead. See the tightened_variables field in CpSolverResponse for more details.
optional bool fill_tightened_domains_in_response = 132 [default = false];
value | The fillTightenedDomainsInResponse to set. |
Definition at line 27938 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFindBigLinearOverlap | ( | boolean | value | ) |
Try to find large "rectangle" in the linear constraint matrix with identical lines. If such rectangle is big enough, we can introduce a new integer variable corresponding to the common expression and greatly reduce the number of non-zero.
optional bool find_big_linear_overlap = 234 [default = true];
value | The findBigLinearOverlap to set. |
Definition at line 22089 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFindMultipleCores | ( | boolean | value | ) |
Whether we try to find more independent cores for a given set of assumptions in the core based max-SAT algorithms.
optional bool find_multiple_cores = 84 [default = true];
value | The findMultipleCores to set. |
Definition at line 24301 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFixVariablesToTheirHintedValue | ( | boolean | value | ) |
If true, variables appearing in the solution hints will be fixed to their hinted value.
optional bool fix_variables_to_their_hinted_value = 192 [default = false];
value | The fixVariablesToTheirHintedValue to set. |
Definition at line 25911 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setFpRounding | ( | com.google.ortools.sat.SatParameters.FPRoundingMethod | value | ) |
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];
value | The fpRounding to set. |
Definition at line 28666 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setGlucoseDecayIncrement | ( | double | value | ) |
optional double glucose_decay_increment = 23 [default = 0.01];
value | The glucoseDecayIncrement to set. |
Definition at line 18414 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setGlucoseDecayIncrementPeriod | ( | int | value | ) |
optional int32 glucose_decay_increment_period = 24 [default = 5000];
value | The glucoseDecayIncrementPeriod to set. |
Definition at line 18454 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setGlucoseMaxDecay | ( | double | value | ) |
The activity starts at 0.8 and increment by 0.01 every 5000 conflicts until 0.95. This "hack" seems to work well and comes from: Glucose 2.3 in the SAT 2013 Competition - SAT Competition 2013 http://edacc4.informatik.uni-ulm.de/SC13/solver-description-download/136
optional double glucose_max_decay = 22 [default = 0.95];
value | The glucoseMaxDecay to set. |
Definition at line 18366 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setHintConflictLimit | ( | int | value | ) |
Conflict limit used in the phase that exploit the solution hint.
optional int32 hint_conflict_limit = 153 [default = 10];
value | The hintConflictLimit to set. |
Definition at line 25784 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setIgnoreNames | ( | boolean | value | ) |
If true, we don't keep names in our internal copy of the user given model.
optional bool ignore_names = 202 [default = true];
value | The ignoreNames to set. |
Definition at line 21952 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setIgnoreSubsolvers | ( | int | index, |
java.lang.String | value ) |
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem.
repeated string ignore_subsolvers = 209;
index | The index to set the value at. |
value | The ignoreSubsolvers to set. |
Definition at line 23197 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setInferAllDiffs | ( | boolean | value | ) |
Run a max-clique code amongst all the x != y we can find and try to infer set of variables that are all different. This allows to close neos16.mps for instance. Note that we only run this code if there is no all_diff already in the model so that if a user want to add some all_diff, we assume it is well done and do not try to add more.
optional bool infer_all_diffs = 233 [default = true];
value | The inferAllDiffs to set. |
Definition at line 22020 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setInitialPolarity | ( | com.google.ortools.sat.SatParameters.Polarity | value | ) |
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];
value | The initialPolarity to set. |
Definition at line 17100 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setInitialVariablesActivity | ( | double | value | ) |
The initial value of the variables activity. A non-zero value only make sense when use_erwa_heuristic is true. Experiments with a value of 1e-2 together with the ERWA heuristic showed slighthly better result than simply using zero. The idea is that when the "learning rate" of a variable becomes lower than this value, then we prefer to branch on never explored before variables. This is not in the ERWA paper.
optional double initial_variables_activity = 76 [default = 0];
value | The initialVariablesActivity to set. |
Definition at line 17529 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setInprocessingDtimeRatio | ( | double | value | ) |
Proportion of deterministic time we should spend on inprocessing. At each "restart", if the proportion is below this ratio, we will do some inprocessing, otherwise, we skip it for this restart.
optional double inprocessing_dtime_ratio = 273 [default = 0.2];
value | The inprocessingDtimeRatio to set. |
Definition at line 22214 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setInprocessingMinimizationDtime | ( | double | value | ) |
Parameters for an heuristic similar to the one described in "An effective learnt clause minimization approach for CDCL Sat Solvers", https://www.ijcai.org/proceedings/2017/0098.pdf This is the amount of dtime we should spend on this technique during each inprocessing phase. The minimization technique is the same as the one used to minimize core in max-sat. We also minimize problem clauses and not just the learned clause that we keep forever like in the paper.
optional double inprocessing_minimization_dtime = 275 [default = 1];
value | The inprocessingMinimizationDtime to set. |
Definition at line 22355 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setInprocessingProbingDtime | ( | double | value | ) |
The amount of dtime we should spend on probing for each inprocessing round.
optional double inprocessing_probing_dtime = 274 [default = 1];
value | The inprocessingProbingDtime to set. |
Definition at line 22272 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setInstantiateAllVariables | ( | boolean | value | ) |
If true, the solver will add a default integer branching strategy to the already defined search strategy. If not, some variable might still not be fixed at the end of the search. For now we assume these variable can just be set to their lower bound.
optional bool instantiate_all_variables = 106 [default = true];
value | The instantiateAllVariables to set. |
Definition at line 28099 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setInterleaveBatchSize | ( | int | value | ) |
optional int32 interleave_batch_size = 134 [default = 0];
value | The interleaveBatchSize to set. |
Definition at line 23762 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setInterleaveSearch | ( | boolean | value | ) |
Experimental. If this is true, then we interleave all our major search strategy and distribute the work amongst num_workers. The search is deterministic (independently of num_workers!), and we schedule and wait for interleave_batch_size task to be completed before synchronizing and scheduling the next batch of tasks.
optional bool interleave_search = 136 [default = false];
value | The interleaveSearch to set. |
Definition at line 23713 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setKeepAllFeasibleSolutionsInPresolve | ( | boolean | value | ) |
If true, we disable the presolve reductions that remove feasible solutions from the search space. Such solution are usually dominated by a "better" solution that is kept, but depending on the situation, we might want to keep all solutions. A trivial example is when a variable is unused. If this is true, then the presolve will not fix it to an arbitrary value and it will stay in the search space.
optional bool keep_all_feasible_solutions_in_presolve = 173 [default = false];
value | The keepAllFeasibleSolutionsInPresolve to set. |
Definition at line 27863 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setLinearizationLevel | ( | int | value | ) |
A non-negative level indicating the type of constraints we consider in the LP relaxation. At level zero, no LP relaxation is used. At level 1, only the linear constraint and full encoding are added. At level 2, we also add all the Boolean constraints.
optional int32 linearization_level = 90 [default = 1];
value | The linearizationLevel to set. |
Definition at line 29793 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setLinearSplitSize | ( | int | value | ) |
Linear constraints that are not pseudo-Boolean and that are longer than this size will be split into sqrt(size) intermediate sums in order to have faster propation in the CP engine.
optional int32 linear_split_size = 256 [default = 100];
value | The linearSplitSize to set. |
Definition at line 29726 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setLogPrefix | ( | java.lang.String | value | ) |
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];
value | The logPrefix to set. |
Definition at line 20170 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setLogPrefixBytes | ( | com.google.protobuf.ByteString | value | ) |
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];
value | The bytes for logPrefix to set. |
Definition at line 20201 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setLogSearchProgress | ( | boolean | value | ) |
Whether the solver should log the search progress. This is the maing logging parameter and if this is false, none of the logging (callbacks, log_to_stdout, log_to_response, ...) will do anything.
optional bool log_search_progress = 41 [default = false];
value | The logSearchProgress to set. |
Definition at line 20014 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setLogSubsolverStatistics | ( | boolean | value | ) |
Whether the solver should display per sub-solver search statistics. This is only useful is log_search_progress is set to true, and if the number of search workers is > 1. Note that in all case we display a bit of stats with one line per subsolver.
optional bool log_subsolver_statistics = 189 [default = false];
value | The logSubsolverStatistics to set. |
Definition at line 20081 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setLogToResponse | ( | boolean | value | ) |
Log to response proto.
optional bool log_to_response = 187 [default = false];
value | The logToResponse to set. |
Definition at line 20300 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setLogToStdout | ( | boolean | value | ) |
Log to stdout.
optional bool log_to_stdout = 186 [default = true];
value | The logToStdout to set. |
Definition at line 20244 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setLpDualTolerance | ( | double | value | ) |
optional double lp_dual_tolerance = 267 [default = 1e-07];
value | The lpDualTolerance to set. |
Definition at line 29480 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setLpPrimalTolerance | ( | double | value | ) |
The internal LP tolerances used by CP-SAT. These applies to the internal and scaled problem. If the domains of your variables are large it might be good to use lower tolerances. If your problem is binary with low coefficients, it might be good to use higher ones to speed-up the lp solves.
optional double lp_primal_tolerance = 266 [default = 1e-07];
value | The lpPrimalTolerance to set. |
Definition at line 29432 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxAllDiffCutSize | ( | int | value | ) |
Cut generator for all diffs can add too many cuts for large all_diff constraints. This parameter restricts the large all_diff constraints to have a cut generator.
optional int32 max_all_diff_cut_size = 148 [default = 64];
value | The maxAllDiffCutSize to set. |
Definition at line 30558 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxClauseActivityValue | ( | double | value | ) |
optional double max_clause_activity_value = 18 [default = 1e+20];
value | The maxClauseActivityValue to set. |
Definition at line 18550 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxConsecutiveInactiveCount | ( | int | value | ) |
If a constraint/cut in LP is not active for that many consecutive OPTIMAL solves, remove it from the LP. Note that it might be added again later if it become violated by the current LP solution.
optional int32 max_consecutive_inactive_count = 121 [default = 100];
value | The maxConsecutiveInactiveCount to set. |
Definition at line 31034 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxCutRoundsAtLevelZero | ( | int | value | ) |
Max number of time we perform cut generation and resolve the LP at level 0.
optional int32 max_cut_rounds_at_level_zero = 154 [default = 1];
value | The maxCutRoundsAtLevelZero to set. |
Definition at line 30972 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxDeterministicTime | ( | double | value | ) |
Maximum time allowed in deterministic time to solve a problem. The deterministic time should be correlated with the real time used by the solver, the time unit being as close as possible to a second.
optional double max_deterministic_time = 67 [default = inf];
value | The maxDeterministicTime to set. |
Definition at line 19402 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxDomainSizeWhenEncodingEqNeqConstraints | ( | int | value | ) |
When loading a*x + b*y ==/!= c when x and y are both fully encoded. The solver may decide to replace the linear equation by a set of clauses. This is triggered if the sizes of the domains of x and y are below the threshold.
optional int32 max_domain_size_when_encoding_eq_neq_constraints = 191 [default = 16];
value | The maxDomainSizeWhenEncodingEqNeqConstraints to set. |
Definition at line 29921 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxIntegerRoundingScaling | ( | int | value | ) |
In the integer rounding procedure used for MIR and Gomory cut, the maximum "scaling" we use (must be positive). The lower this is, the lower the integer coefficients of the cut will be. Note that cut generated by lower values are not necessarily worse than cut generated by larger value. There is no strict dominance relationship. Setting this to 2 result in the "strong fractional rouding" of Letchford and Lodi.
optional int32 max_integer_rounding_scaling = 119 [default = 600];
value | The maxIntegerRoundingScaling to set. |
Definition at line 30701 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxMemoryInMb | ( | long | value | ) |
Maximum memory allowed for the whole thread containing the solver. The solver will abort as soon as it detects that this limit is crossed. As a result, this limit is approximative, but usually the solver will not go too much over. TODO(user): This is only used by the pure SAT solver, generalize to CP-SAT.
optional int64 max_memory_in_mb = 40 [default = 10000];
value | The maxMemoryInMb to set. |
Definition at line 19555 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxNumberOfConflicts | ( | long | value | ) |
Maximum number of conflicts allowed to solve a problem. TODO(user): Maybe change the way the conflict limit is enforced? currently it is enforced on each independent internal SAT solve, rather than on the overall number of conflicts across all solves. So in the context of an optimization problem, this is not really usable directly by a client.
optional int64 max_number_of_conflicts = 37 [default = 9223372036854775807];
value | The maxNumberOfConflicts to set. |
Definition at line 19478 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxNumCuts | ( | int | value | ) |
The limit on the number of cuts in our cut pool. When this is reached we do not generate cuts anymore. TODO(user): We should probably remove this parameters, and just always generate cuts but only keep the best n or something.
optional int32 max_num_cuts = 91 [default = 10000];
value | The maxNumCuts to set. |
Definition at line 29992 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxNumIntervalsForTimetableEdgeFinding | ( | int | value | ) |
Max number of intervals for the timetable_edge_finding algorithm to propagate. A value of 0 disables the constraint.
optional int32 max_num_intervals_for_timetable_edge_finding = 260 [default = 100];
value | The maxNumIntervalsForTimetableEdgeFinding to set. |
Definition at line 25149 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxPairsPairwiseReasoningInNoOverlap2D | ( | int | value | ) |
If the number of pairs to look is below this threshold, do an extra step of propagation in the no_overlap_2d constraint by looking at all pairs of intervals.
optional int32 max_pairs_pairwise_reasoning_in_no_overlap_2d = 276 [default = 1250];
value | The maxPairsPairwiseReasoningInNoOverlap2d to set. |
Definition at line 25620 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxPresolveIterations | ( | int | value | ) |
In case of large reduction in a presolve iteration, we perform multiple presolve iterations. This parameter controls the maximum number of such presolve iterations.
optional int32 max_presolve_iterations = 138 [default = 3];
value | The maxPresolveIterations to set. |
Definition at line 21006 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxSatAssumptionOrder | ( | com.google.ortools.sat.SatParameters.MaxSatAssumptionOrder | value | ) |
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];
value | The maxSatAssumptionOrder to set. |
Definition at line 24410 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxSatReverseAssumptionOrder | ( | boolean | value | ) |
If true, adds the assumption in the reverse order of the one defined by max_sat_assumption_order.
optional bool max_sat_reverse_assumption_order = 52 [default = false];
value | The maxSatReverseAssumptionOrder to set. |
Definition at line 24467 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxSatStratification | ( | com.google.ortools.sat.SatParameters.MaxSatStratificationAlgorithm | value | ) |
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];
value | The maxSatStratification to set. |
Definition at line 24512 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxSizeToCreatePrecedenceLiteralsInDisjunctive | ( | int | value | ) |
Create one literal for each disjunction of two pairs of tasks. This slows down the solve time, but improves the lower bound of the objective in the makespan case. This will be triggered if the number of intervals is less or equal than the parameter and if use_strong_propagation_in_disjunctive is true.
optional int32 max_size_to_create_precedence_literals_in_disjunctive = 229 [default = 60];
value | The maxSizeToCreatePrecedenceLiteralsInDisjunctive to set. |
Definition at line 24754 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxTimeInSeconds | ( | double | value | ) |
Maximum time allowed in seconds to solve a problem. The counter will starts at the beginning of the Solve() call.
optional double max_time_in_seconds = 36 [default = inf];
value | The maxTimeInSeconds to set. |
Definition at line 19339 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMaxVariableActivityValue | ( | double | value | ) |
optional double max_variable_activity_value = 16 [default = 1e+100];
value | The maxVariableActivityValue to set. |
Definition at line 18302 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMergeAtMostOneWorkLimit | ( | double | value | ) |
optional double merge_at_most_one_work_limit = 146 [default = 100000000];
value | The mergeAtMostOneWorkLimit to set. |
Definition at line 21676 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMergeNoOverlapWorkLimit | ( | double | value | ) |
During presolve, we use a maximum clique heuristic to merge together no-overlap constraints or at most one constraints. This code can be slow, so we have a limit in place on the number of explored nodes in the underlying graph. The internal limit is an int64, but we use double here to simplify manual input.
optional double merge_no_overlap_work_limit = 145 [default = 1000000000000];
value | The mergeNoOverlapWorkLimit to set. |
Definition at line 21628 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMinimizationAlgorithm | ( | com.google.ortools.sat.SatParameters.ConflictMinimizationAlgorithm | value | ) |
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];
value | The minimizationAlgorithm to set. |
Definition at line 17646 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMinimizeReductionDuringPbResolution | ( | boolean | value | ) |
A different algorithm during PB resolution. It minimizes the number of calls to ReduceCoefficients() which can be time consuming. However, the search space will be different and if the coefficients are large, this may lead to integer overflows that could otherwise be prevented.
optional bool minimize_reduction_during_pb_resolution = 48 [default = false];
value | The minimizeReductionDuringPbResolution to set. |
Definition at line 20433 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMinNumLnsWorkers | ( | int | value | ) |
Obsolete parameter. No-op.
optional int32 min_num_lns_workers = 211 [default = 2];
value | The minNumLnsWorkers to set. |
Definition at line 22568 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMinOrthogonalityForLpConstraints | ( | double | value | ) |
While adding constraints, skip the constraints which have orthogonality less than 'min_orthogonality_for_lp_constraints' with already added constraints during current call. Orthogonality is defined as 1 - cosine(vector angle between constraints). A value of zero disable this feature.
optional double min_orthogonality_for_lp_constraints = 115 [default = 0.05];
value | The minOrthogonalityForLpConstraints to set. |
Definition at line 30912 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipAutomaticallyScaleVariables | ( | boolean | value | ) |
If true, some continuous variable might be automatically scaled. For now, this is only the case where we detect that a variable is actually an integer multiple of a constant. For instance, variables of the form k * 0.5 are quite frequent, and if we detect this, we will scale such variable domain by 2 to make it implied integer.
optional bool mip_automatically_scale_variables = 166 [default = true];
value | The mipAutomaticallyScaleVariables to set. |
Definition at line 31892 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipCheckPrecision | ( | double | value | ) |
As explained in mip_precision and mip_max_activity_exponent, we cannot always reach the wanted precision during scaling. We use this threshold to enphasize in the logs when the precision seems bad.
optional double mip_check_precision = 128 [default = 0.0001];
value | The mipCheckPrecision to set. |
Definition at line 32262 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipComputeTrueObjectiveBound | ( | boolean | value | ) |
Even if we make big error when scaling the objective, we can always derive a correct lower bound on the original objective by using the exact lower bound on the scaled integer version of the objective. This should be fast, but if you don't care about having a precise lower bound, you can turn it off.
optional bool mip_compute_true_objective_bound = 198 [default = true];
value | The mipComputeTrueObjectiveBound to set. |
Definition at line 32332 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipDropTolerance | ( | double | value | ) |
Any value in the input mip with a magnitude lower than this will be set to zero. This is to avoid some issue in LP presolving.
optional double mip_drop_tolerance = 232 [default = 1e-16];
value | The mipDropTolerance to set. |
Definition at line 32543 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipMaxActivityExponent | ( | int | value | ) |
To avoid integer overflow, we always force the maximum possible constraint activity (and objective value) according to the initial variable domain to be smaller than 2 to this given power. Because of this, we cannot always reach the "mip_wanted_precision" parameter above. This can go as high as 62, but some internal algo currently abort early if they might run into integer overflow, so it is better to keep it a bit lower than this.
optional int32 mip_max_activity_exponent = 127 [default = 53];
value | The mipMaxActivityExponent to set. |
Definition at line 32193 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipMaxBound | ( | double | value | ) |
We need to bound the maximum magnitude of the variables for CP-SAT, and that is the bound we use. If the MIP model expect larger variable value in the solution, then the converted model will likely not be relevant.
optional double mip_max_bound = 124 [default = 10000000];
value | The mipMaxBound to set. |
Definition at line 31694 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipMaxValidMagnitude | ( | double | value | ) |
Any finite values in the input MIP must be below this threshold, otherwise the model will be reported invalid. This is needed to avoid floating point overflow when evaluating bounds * coeff for instance. We are a bit more defensive, but in practice, users shouldn't use super large values in a MIP.
optional double mip_max_valid_magnitude = 199 [default = 1e+20];
value | The mipMaxValidMagnitude to set. |
Definition at line 32404 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipPresolveLevel | ( | int | value | ) |
When solving a MIP, we do some basic floating point presolving before scaling the problem to integer to be handled by CP-SAT. This control how much of that presolve we do. It can help to better scale floating point model, but it is not always behaving nicely.
optional int32 mip_presolve_level = 261 [default = 2];
value | The mipPresolveLevel to set. |
Definition at line 32609 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipScaleLargeDomain | ( | boolean | value | ) |
If this is false, then mip_var_scaling is only applied to variables with "small" domain. If it is true, we scale all floating point variable independenlty of their domain.
optional bool mip_scale_large_domain = 225 [default = false];
value | The mipScaleLargeDomain to set. |
Definition at line 31822 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipTreatHighMagnitudeBoundsAsInfinity | ( | boolean | value | ) |
By default, any variable/constraint bound with a finite value and a magnitude greater than the mip_max_valid_magnitude will result with a invalid model. This flags change the behavior such that such bounds are silently transformed to +∞ or -∞. It is recommended to keep it at false, and create valid bounds.
optional bool mip_treat_high_magnitude_bounds_as_infinity = 278 [default = false];
value | The mipTreatHighMagnitudeBoundsAsInfinity to set. |
Definition at line 32479 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipVarScaling | ( | double | value | ) |
All continuous variable of the problem will be multiplied by this factor. By default, we don't do any variable scaling and rely on the MIP model to specify continuous variable domain with the wanted precision.
optional double mip_var_scaling = 125 [default = 1];
value | The mipVarScaling to set. |
Definition at line 31758 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setMipWantedPrecision | ( | double | value | ) |
When scaling constraint with double coefficients to integer coefficients, we will multiply by a power of 2 and round the coefficients. We will choose the lowest power such that we have no potential overflow (see mip_max_activity_exponent) and the worst case constraint activity error does not exceed this threshold. Note that we also detect constraint with rational coefficients and scale them accordingly when it seems better instead of using a power of 2. We also relax all constraint bounds by this absolute value. For pure integer constraint, if this value if lower than one, this will not change anything. However it is needed when scaling MIP problems. If we manage to scale a constraint correctly, the maximum error we can make will be twice this value (once for the scaling error and once for the relaxed bounds). If we are not able to scale that well, we will display that fact but still scale as best as we can.
optional double mip_wanted_precision = 126 [default = 1e-06];
value | The mipWantedPrecision to set. |
Definition at line 32100 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setName | ( | java.lang.String | value | ) |
In some context, like in a portfolio of search, it makes sense to name a given parameters set for logging purpose.
optional string name = 171 [default = ""];
value | The name to set. |
Definition at line 16994 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setNameBytes | ( | com.google.protobuf.ByteString | value | ) |
In some context, like in a portfolio of search, it makes sense to name a given parameters set for logging purpose.
optional string name = 171 [default = ""];
value | The bytes for name to set. |
Definition at line 17027 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setNewConstraintsBatchSize | ( | int | value | ) |
Add that many lazy constraints (or cuts) at once in the LP. Note that at the beginning of the solve, we do add more than this.
optional int32 new_constraints_batch_size = 122 [default = 50];
value | The newConstraintsBatchSize to set. |
Definition at line 31255 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setNewLinearPropagation | ( | boolean | value | ) |
Experimental. Use new code to propagate linear constraint.
optional bool new_linear_propagation = 224 [default = false];
value | The newLinearPropagation to set. |
Definition at line 29664 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setNumConflictsBeforeStrategyChanges | ( | int | value | ) |
After each restart, if the number of conflict since the last strategy change is greater that this, then we increment a "strategy_counter" that can be use to change the search strategy used by the following restarts.
optional int32 num_conflicts_before_strategy_changes = 68 [default = 0];
value | The numConflictsBeforeStrategyChanges to set. |
Definition at line 19218 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setNumSearchWorkers | ( | int | value | ) |
optional int32 num_search_workers = 100 [default = 0];
value | The numSearchWorkers to set. |
Definition at line 22516 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setNumViolationLs | ( | int | value | ) |
This will create incomplete subsolvers (that are not LNS subsolvers) that use the feasibility jump code to find improving solution, treating the objective improvement as a hard constraint.
optional int32 num_violation_ls = 244 [default = 0];
value | The numViolationLs to set. |
Definition at line 27286 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setNumWorkers | ( | int | value | ) |
Specify the number of parallel workers (i.e. threads) to use during search. This should usually be lower than your number of available cpus + hyperthread in your machine. A value of 0 means the solver will try to use all cores on the machine. A number of 1 means no parallelism. Note that 'num_workers' is the preferred name, but if it is set to zero, we will still read the deprecated 'num_search_worker'. As of 2020-04-10, if you're using SAT via MPSolver (to solve integer programs) this field is overridden with a value of 8, if the field is not set *explicitly*. Thus, always set this field explicitly or via MPSolver::SetNumThreads().
optional int32 num_workers = 206 [default = 0];
value | The numWorkers to set. |
Definition at line 22459 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setOnlyAddCutsAtLevelZero | ( | boolean | value | ) |
For the cut that can be generated at any level, this control if we only try to generate them at the root node.
optional bool only_add_cuts_at_level_zero = 92 [default = false];
value | The onlyAddCutsAtLevelZero to set. |
Definition at line 30119 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setOnlySolveIp | ( | boolean | value | ) |
If one try to solve a MIP model with CP-SAT, because we assume all variable to be integer after scaling, we will not necessarily have the correct optimal. Note however that all feasible solutions are valid since we will just solve a more restricted version of the original problem. This parameters is here to prevent user to think the solution is optimal when it might not be. One will need to manually set this to false to solve a MIP model where the optimal might be different. Note that this is tested after some MIP presolve steps, so even if not all original variable are integer, we might end up with a pure IP after presolve and after implied integer detection.
optional bool only_solve_ip = 222 [default = false];
value | The onlySolveIp to set. |
Definition at line 31985 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setOptimizeWithCore | ( | boolean | value | ) |
The default optimization method is a simple "linear scan", each time trying to find a better solution than the previous one. If this is true, then we use a core-based approach (like in max-SAT) when we try to increase the lower bound instead.
optional bool optimize_with_core = 83 [default = false];
value | The optimizeWithCore to set. |
Definition at line 26457 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setOptimizeWithLbTreeSearch | ( | boolean | value | ) |
Do a more conventional tree search (by opposition to SAT based one) where we keep all the explored node in a tree. This is meant to be used in a portfolio and focus on improving the objective lower bound. Keeping the whole tree allow us to report a better objective lower bound coming from the worst open node in the tree.
optional bool optimize_with_lb_tree_search = 188 [default = false];
value | The optimizeWithLbTreeSearch to set. |
Definition at line 26528 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setOptimizeWithMaxHs | ( | boolean | value | ) |
This has no effect if optimize_with_core is false. If true, use a different core-based algorithm similar to the max-HS algo for max-SAT. This is a hybrid MIP/CP approach and it uses a MIP solver in addition to the CP/SAT one. This is also related to the PhD work of tobyodavies@ "Automatic Logic-Based Benders Decomposition with MiniZinc" http://aaai.org/ocs/index.php/AAAI/AAAI17/paper/view/14489
optional bool optimize_with_max_hs = 85 [default = false];
value | The optimizeWithMaxHs to set. |
Definition at line 26671 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPbCleanupIncrement | ( | int | value | ) |
Same as for the clauses, but for the learned pseudo-Boolean constraints.
optional int32 pb_cleanup_increment = 46 [default = 200];
value | The pbCleanupIncrement to set. |
Definition at line 18134 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPbCleanupRatio | ( | double | value | ) |
optional double pb_cleanup_ratio = 47 [default = 0.5];
value | The pbCleanupRatio to set. |
Definition at line 18178 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPermutePresolveConstraintOrder | ( | boolean | value | ) |
optional bool permute_presolve_constraint_order = 179 [default = false];
value | The permutePresolveConstraintOrder to set. |
Definition at line 19916 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPermuteVariableRandomly | ( | boolean | value | ) |
This is mainly here to test the solver variability. Note that in tests, if not explicitly set to false, all 3 options will be set to true so that clients do not rely on the solver returning a specific solution if they are many equivalent optimal solutions.
optional bool permute_variable_randomly = 178 [default = false];
value | The permuteVariableRandomly to set. |
Definition at line 19869 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPolarityRephaseIncrement | ( | int | value | ) |
If non-zero, then we change the polarity heuristic after that many number of conflicts in an arithmetically increasing fashion. So x the first time, 2 * x the second time, etc...
optional int32 polarity_rephase_increment = 168 [default = 1000];
value | The polarityRephaseIncrement to set. |
Definition at line 17256 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPolishLpSolution | ( | boolean | value | ) |
Whether we try to do a few degenerate iteration at the end of an LP solve to minimize the fractionality of the integer variable in the basis. This helps on some problems, but not so much on others. It also cost of bit of time to do such polish step.
optional bool polish_lp_solution = 175 [default = false];
value | The polishLpSolution to set. |
Definition at line 29361 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPreferredVariableOrder | ( | com.google.ortools.sat.SatParameters.VariableOrder | value | ) |
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];
value | The preferredVariableOrder to set. |
Definition at line 17058 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPresolveBlockedClause | ( | boolean | value | ) |
Whether we use an heuristic to detect some basic case of blocked clause in the SAT presolve.
optional bool presolve_blocked_clause = 88 [default = true];
value | The presolveBlockedClause to set. |
Definition at line 20819 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPresolveBvaThreshold | ( | int | value | ) |
Apply Bounded Variable Addition (BVA) if the number of clauses is reduced by stricly more than this threshold. The algorithm described in the paper uses 0, but quick experiments showed that 1 is a good value. It may not be worth it to add a new variable just to remove one clause.
optional int32 presolve_bva_threshold = 73 [default = 1];
value | The presolveBvaThreshold to set. |
Definition at line 20941 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPresolveBveClauseWeight | ( | int | value | ) |
During presolve, we apply BVE only if this weight times the number of clauses plus the number of clause literals is not increased.
optional int32 presolve_bve_clause_weight = 55 [default = 3];
value | The presolveBveClauseWeight to set. |
Definition at line 20647 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPresolveBveThreshold | ( | int | value | ) |
During presolve, only try to perform the bounded variable elimination (BVE) of a variable x if the number of occurrences of x times the number of occurrences of not(x) is not greater than this parameter.
optional int32 presolve_bve_threshold = 54 [default = 500];
value | The presolveBveThreshold to set. |
Definition at line 20586 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPresolveExtractIntegerEnforcement | ( | boolean | value | ) |
If true, we will extract from linear constraints, enforcement literals of the form "integer variable at bound => simplified constraint". This should always be beneficial except that we don't always handle them as efficiently as we could for now. This causes problem on manna81.mps (LP relaxation not as tight it seems) and on neos-3354841-apure.mps.gz (too many literals created this way).
optional bool presolve_extract_integer_enforcement = 174 [default = false];
value | The presolveExtractIntegerEnforcement to set. |
Definition at line 21811 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPresolveInclusionWorkLimit | ( | long | value | ) |
A few presolve operations involve detecting constraints included in other constraint. Since there can be a quadratic number of such pairs, and processing them usually involve scanning them, the complexity of these operations can be big. This enforce a local deterministic limit on the number of entries scanned. Default is 1e8. A value of zero will disable these presolve rules completely.
optional int64 presolve_inclusion_work_limit = 201 [default = 100000000];
value | The presolveInclusionWorkLimit to set. |
Definition at line 21890 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPresolveProbingDeterministicTimeLimit | ( | double | value | ) |
optional double presolve_probing_deterministic_time_limit = 57 [default = 30];
value | The presolveProbingDeterministicTimeLimit to set. |
Definition at line 20764 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPresolveSubstitutionLevel | ( | int | value | ) |
How much substitution (also called free variable aggregation in MIP litterature) should we perform at presolve. This currently only concerns variable appearing only in linear constraints. For now the value 0 turns it off and any positive value performs substitution.
optional int32 presolve_substitution_level = 147 [default = 1];
value | The presolveSubstitutionLevel to set. |
Definition at line 21737 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPresolveUseBva | ( | boolean | value | ) |
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
optional bool presolve_use_bva = 72 [default = true];
value | The presolveUseBva to set. |
Definition at line 20876 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setProbingDeterministicTimeLimit | ( | double | value | ) |
The maximum "deterministic" time limit to spend in probing. A value of zero will disable the probing. TODO(user): Clean up. The first one is used in CP-SAT, the other in pure SAT presolve.
optional double probing_deterministic_time_limit = 226 [default = 1];
value | The probingDeterministicTimeLimit to set. |
Definition at line 20716 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setProbingNumCombinationsLimit | ( | int | value | ) |
How many combinations of pairs or triplets of variables we want to scan.
optional int32 probing_num_combinations_limit = 272 [default = 20000];
value | The probingNumCombinationsLimit to set. |
Definition at line 26088 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPropagationLoopDetectionFactor | ( | double | value | ) |
Some search decisions might cause a really large number of propagations to happen when integer variables with large domains are only reduced by 1 at each step. If we propagate more than the number of variable times this parameters we try to take counter-measure. Setting this to 0.0 disable this feature. TODO(user): Setting this to something like 10 helps in most cases, but the code is currently buggy and can cause the solve to enter a bad state where no progress is made.
optional double propagation_loop_detection_factor = 221 [default = 10];
value | The propagationLoopDetectionFactor to set. |
Definition at line 24590 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPseudoCostReliabilityThreshold | ( | long | value | ) |
The solver ignores the pseudo costs of variables with number of recordings less than this threshold.
optional int64 pseudo_cost_reliability_threshold = 123 [default = 100];
value | The pseudoCostReliabilityThreshold to set. |
Definition at line 26391 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setPushAllTasksTowardStart | ( | boolean | value | ) |
Experimental code: specify if the objective pushes all tasks toward the start of the schedule.
optional bool push_all_tasks_toward_start = 262 [default = false];
value | The pushAllTasksTowardStart to set. |
Definition at line 28899 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRandomBranchesRatio | ( | double | value | ) |
A number between 0 and 1 that indicates the proportion of branching variables that are selected randomly instead of choosing the first variable from the given variable_ordering strategy.
optional double random_branches_ratio = 32 [default = 0];
value | The randomBranchesRatio to set. |
Definition at line 17392 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRandomizeSearch | ( | boolean | value | ) |
Randomize fixed search.
optional bool randomize_search = 103 [default = false];
value | The randomizeSearch to set. |
Definition at line 28776 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRandomPolarityRatio | ( | double | value | ) |
The proportion of polarity chosen at random. Note that this take precedence over the phase saving heuristic. This is different from initial_polarity:POLARITY_RANDOM because it will select a new random polarity each time the variable is branched upon instead of selecting one initially and then always taking this choice.
optional double random_polarity_ratio = 45 [default = 0];
value | The randomPolarityRatio to set. |
Definition at line 17326 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRandomSeed | ( | int | value | ) |
At the beginning of each solve, the random number generator used in some part of the solver is reinitialized to this seed. If you change the random seed, the solver may make different choices during the solving process. For some problems, the running time may vary a lot depending on small change in the solving algorithm. Running the solver with different seeds enables to have more robust benchmarks when evaluating new features.
optional int32 random_seed = 31 [default = 1];
value | The randomSeed to set. |
Definition at line 19798 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRelativeGapLimit | ( | double | value | ) |
optional double relative_gap_limit = 160 [default = 0];
value | The relativeGapLimit to set. |
Definition at line 19728 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRepairHint | ( | boolean | value | ) |
If true, the solver tries to repair the solution given in the hint. This search terminates after the 'hint_conflict_limit' is reached and the solver switches to regular search. If false, then we do a FIXED_SEARCH using the hint until the hint_conflict_limit is reached.
optional bool repair_hint = 167 [default = false];
value | The repairHint to set. |
Definition at line 25849 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRepeatedField | ( | com.google.protobuf.Descriptors.FieldDescriptor | field, |
int | index, | ||
java.lang.Object | value ) |
Definition at line 14820 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRestartAlgorithms | ( | int | index, |
com.google.ortools.sat.SatParameters.RestartAlgorithm | value ) |
The restart strategies will change each time the strategy_counter is increased. The current strategy will simply be the one at index strategy_counter modulo the number of strategy. Note that if this list includes a NO_RESTART, nothing will change when it is reached because the strategy_counter will only increment after a restart. The idea of switching of search strategy tailored for SAT/UNSAT comes from Chanseok Oh with his COMiniSatPS solver, see http://cs.nyu.edu/~chanseok/. But more generally, it seems REALLY beneficial to try different strategy.
repeated .operations_research.sat.SatParameters.RestartAlgorithm restart_algorithms = 61;
index | The index to set the value at. |
value | The restartAlgorithms to set. |
Definition at line 18653 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRestartDlAverageRatio | ( | double | value | ) |
In the moving average restart algorithms, a restart is triggered if the window average times this ratio is greater that the global average.
optional double restart_dl_average_ratio = 63 [default = 1];
value | The restartDlAverageRatio to set. |
Definition at line 18971 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRestartLbdAverageRatio | ( | double | value | ) |
optional double restart_lbd_average_ratio = 71 [default = 1];
value | The restartLbdAverageRatio to set. |
Definition at line 19016 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRestartPeriod | ( | int | value | ) |
Restart period for the FIXED_RESTART strategy. This is also the multiplier used by the LUBY_RESTART strategy.
optional int32 restart_period = 30 [default = 50];
value | The restartPeriod to set. |
Definition at line 18855 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRestartRunningWindowSize | ( | int | value | ) |
Size of the window for the moving average restarts.
optional int32 restart_running_window_size = 62 [default = 50];
value | The restartRunningWindowSize to set. |
Definition at line 18912 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setRootLpIterations | ( | int | value | ) |
Even at the root node, we do not want to spend too much time on the LP if it is "difficult". So we solve it in "chunks" of that many iterations. The solve will be continued down in the tree or the next time we go back to the root node.
optional int32 root_lp_iterations = 227 [default = 2000];
value | The rootLpIterations to set. |
Definition at line 30841 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSearchBranching | ( | com.google.ortools.sat.SatParameters.SearchBranching | value | ) |
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];
value | The searchBranching to set. |
Definition at line 25730 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSearchRandomVariablePoolSize | ( | long | value | ) |
Search randomization will collect the top 'search_random_variable_pool_size' valued variables, and pick one randomly. The value of the variable is specific to each strategy.
optional int64 search_random_variable_pool_size = 104 [default = 0];
value | The searchRandomVariablePoolSize to set. |
Definition at line 28838 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setShareBinaryClauses | ( | boolean | value | ) |
Allows sharing of new learned binary clause between workers.
optional bool share_binary_clauses = 203 [default = true];
value | The shareBinaryClauses to set. |
Definition at line 23926 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSharedTreeMaxNodesPerWorker | ( | int | value | ) |
In order to limit total shared memory and communication overhead, limit the total number of nodes that may be generated in the shared tree. If the shared tree runs out of unassigned leaves, workers act as portfolio workers. Note: this limit includes interior nodes, not just leaves.
optional int32 shared_tree_max_nodes_per_worker = 238 [default = 128];
value | The sharedTreeMaxNodesPerWorker to set. |
Definition at line 27661 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSharedTreeNumWorkers | ( | int | value | ) |
Enables experimental workstealing-like shared tree search. If non-zero, start this many complete worker threads to explore a shared search tree. These workers communicate objective bounds and simple decision nogoods relating to the shared prefix of the tree, and will avoid exploring the same subtrees as one another.
optional int32 shared_tree_num_workers = 235 [default = 0];
value | The sharedTreeNumWorkers to set. |
Definition at line 27472 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSharedTreeSplitStrategy | ( | com.google.ortools.sat.SatParameters.SharedTreeSplitStrategy | value | ) |
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];
value | The sharedTreeSplitStrategy to set. |
Definition at line 27708 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSharedTreeWorkerObjectiveSplitProbability | ( | double | value | ) |
After their assigned prefix, shared tree workers will branch on the objective with this probability. Higher numbers cause the shared tree search to focus on improving the lower bound over finding primal solutions.
optional double shared_tree_worker_objective_split_probability = 237 [default = 0.5];
value | The sharedTreeWorkerObjectiveSplitProbability to set. |
Definition at line 27594 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setShareLevelZeroBounds | ( | boolean | value | ) |
Allows sharing of the bounds of modified variables at level 0.
optional bool share_level_zero_bounds = 114 [default = true];
value | The shareLevelZeroBounds to set. |
Definition at line 23870 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setShareObjectiveBounds | ( | boolean | value | ) |
Allows objective sharing between workers.
optional bool share_objective_bounds = 113 [default = true];
value | The shareObjectiveBounds to set. |
Definition at line 23814 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setShavingSearchDeterministicTime | ( | double | value | ) |
Specifies the amount of deterministic time spent of each try at shaving a bound in the shaving search.
optional double shaving_search_deterministic_time = 205 [default = 0.001];
value | The shavingSearchDeterministicTime to set. |
Definition at line 26207 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSolutionPoolSize | ( | int | value | ) |
Size of the top-n different solutions kept by the solver. This parameter must be > 0. Currently this only impact the "base" solution chosen for a LNS fragment.
optional int32 solution_pool_size = 193 [default = 3];
value | The solutionPoolSize to set. |
Definition at line 28444 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setStopAfterFirstSolution | ( | boolean | value | ) |
For an optimization problem, stop the solver as soon as we have a solution.
optional bool stop_after_first_solution = 98 [default = false];
value | The stopAfterFirstSolution to set. |
Definition at line 28226 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setStopAfterPresolve | ( | boolean | value | ) |
Mainly used when improving the presolver. When true, stops the solver after the presolve is complete (or after loading and root level propagation).
optional bool stop_after_presolve = 149 [default = false];
value | The stopAfterPresolve to set. |
Definition at line 28285 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setStopAfterRootPropagation | ( | boolean | value | ) |
optional bool stop_after_root_propagation = 252 [default = false];
value | The stopAfterRootPropagation to set. |
Definition at line 28330 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setStrategyChangeIncreaseRatio | ( | double | value | ) |
The parameter num_conflicts_before_strategy_changes is increased by that much after each strategy change.
optional double strategy_change_increase_ratio = 69 [default = 0];
value | The strategyChangeIncreaseRatio to set. |
Definition at line 19279 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSubsolverParams | ( | int | index, |
com.google.ortools.sat.SatParameters | value ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23357 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSubsolverParams | ( | int | index, |
com.google.ortools.sat.SatParameters.Builder | builderForValue ) |
It is possible to specify additional subsolver configuration. These can be referred by their params.name() in the fields above. Note that only the specified field will "overwrite" the ones of the base parameter. If a subsolver_params has the name of an existing subsolver configuration, the named parameters will be merged into the subsolver configuration.
repeated .operations_research.sat.SatParameters subsolver_params = 210;
Definition at line 23382 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSubsolvers | ( | int | index, |
java.lang.String | value ) |
In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters. This field indicates the names of the parameters that are used in multithread. See cp_model_search.cc to see a list of the names and the default value (if left empty) that looks like: - default_lp (linearization_level:1) - fixed (only if fixed search specified or scheduling) - no_lp (linearization_level:0) - max_lp (linearization_level:2) - pseudo_costs (only if objective, change search heuristic) - reduced_costs (only if objective, change search heuristic) - quick_restart (kind of probing) - quick_restart_no_lp (kind of probing with linearization_level:0) - lb_tree_search (to improve lower bound, MIP like tree search) - probing (continuous probing and shaving) Also, note that some set of parameters will be ignored if they do not make sense. For instance if there is no objective, pseudo_cost or reduced_cost search will be ignored. Core based search will only work if the objective has many terms. If there is no fixed strategy fixed will be ignored. And so on. The order is important, as only the first usable "num_workers - min_num_lns_workers" subsolvers will be scheduled. You can see in the log which one are selected for a given run. All the others will be LNS if there is an objective, or randomized SAT search for pure satisfiability problems.
repeated string subsolvers = 207;
index | The index to set the value at. |
value | The subsolvers to set. |
Definition at line 22787 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSubsumptionDuringConflictAnalysis | ( | boolean | value | ) |
At a really low cost, during the 1-UIP conflict computation, it is easy to detect if some of the involved reasons are subsumed by the current conflict. When this is true, such clauses are detached and later removed from the problem.
optional bool subsumption_during_conflict_analysis = 56 [default = true];
value | The subsumptionDuringConflictAnalysis to set. |
Definition at line 17751 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setSymmetryLevel | ( | int | value | ) |
Whether we try to automatically detect the symmetries in a model and exploit them. Currently, at level 1 we detect them in presolve and try to fix Booleans. At level 2, we also do some form of dynamic symmetry breaking during search.
optional int32 symmetry_level = 183 [default = 2];
value | The symmetryLevel to set. |
Definition at line 29605 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setTableCompressionLevel | ( | int | value | ) |
How much we try to "compress" a table constraint. Compressing more leads to less Booleans and faster propagation but can reduced the quality of the lp relaxation. Values goes from 0 to 3 where we always try to fully compress a table. At 2, we try to automatically decide if it is worth it.
optional int32 table_compression_level = 217 [default = 2];
value | The tableCompressionLevel to set. |
Definition at line 21317 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setTestFeasibilityJump | ( | boolean | value | ) |
Disable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.
optional bool test_feasibility_jump = 240 [default = false];
value | The testFeasibilityJump to set. |
Definition at line 26799 of file SatParameters.java.
final Builder com.google.ortools.sat.SatParameters.Builder.setUnknownFields | ( | final com.google.protobuf.UnknownFieldSet | unknownFields | ) |
Definition at line 32634 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseAbslRandom | ( | boolean | value | ) |
optional bool use_absl_random = 180 [default = false];
value | The useAbslRandom to set. |
Definition at line 19956 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseAreaEnergeticReasoningInNoOverlap2D | ( | boolean | value | ) |
When this is true, the no_overlap_2d constraint is reinforced with an energetic reasoning that uses an area-based energy. This can be combined with the two other overlap heuristics above.
optional bool use_area_energetic_reasoning_in_no_overlap_2d = 271 [default = false];
value | The useAreaEnergeticReasoningInNoOverlap2d to set. |
Definition at line 25556 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseBlockingRestart | ( | boolean | value | ) |
Block a moving restart algorithm if the trail size of the current conflict is greater than the multiplier times the moving average of the trail size at the previous conflicts.
optional bool use_blocking_restart = 64 [default = false];
value | The useBlockingRestart to set. |
Definition at line 19074 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseCombinedNoOverlap | ( | boolean | value | ) |
This can be beneficial if there is a lot of no-overlap constraints but a relatively low number of different intervals in the problem. Like 1000 intervals, but 1M intervals in the no-overlap constraints covering them.
optional bool use_combined_no_overlap = 133 [default = false];
value | The useCombinedNoOverlap to set. |
Definition at line 29106 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseDisjunctiveConstraintInCumulative | ( | boolean | value | ) |
When this is true, the cumulative constraint is reinforced with propagators from the disjunctive constraint to improve the inference on a set of tasks that are disjunctive at the root of the problem. This additional level supplements the default level of reasoning. Propagators of the cumulative constraint will not be used at all if all the tasks are disjunctive at root node. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_disjunctive_constraint_in_cumulative = 80 [default = true];
value | The useDisjunctiveConstraintInCumulative to set. |
Definition at line 25349 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseDualSchedulingHeuristics | ( | boolean | value | ) |
When set, it activates a few scheduling parameters to improve the lower bound of scheduling problems. This is only effective with multiple workers as it modifies the reduced_cost, lb_tree_search, and probing workers.
optional bool use_dual_scheduling_heuristics = 214 [default = true];
value | The useDualSchedulingHeuristics to set. |
Definition at line 25684 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseDynamicPrecedenceInCumulative | ( | boolean | value | ) |
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];
value | The useDynamicPrecedenceInCumulative to set. |
Definition at line 24934 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseDynamicPrecedenceInDisjunctive | ( | boolean | value | ) |
Whether we try to branch on decision "interval A before interval B" rather than on intervals bounds. This usually works better, but slow down a bit the time to find the first solution. These parameters are still EXPERIMENTAL, the result should be correct, but it some corner cases, they can cause some failing CHECK in the solver.
optional bool use_dynamic_precedence_in_disjunctive = 263 [default = false];
value | The useDynamicPrecedenceInDisjunctive to set. |
Definition at line 24885 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseEnergeticReasoningInNoOverlap2D | ( | boolean | value | ) |
When this is true, the no_overlap_2d constraint is reinforced with energetic reasoning. This additional level supplements the default level of reasoning.
optional bool use_energetic_reasoning_in_no_overlap_2d = 213 [default = false];
value | The useEnergeticReasoningInNoOverlap2d to set. |
Definition at line 25492 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseErwaHeuristic | ( | boolean | value | ) |
Whether we use the ERWA (Exponential Recency Weighted Average) heuristic as described in "Learning Rate Based Branching Heuristic for SAT solvers", J.H.Liang, V. Ganesh, P. Poupart, K.Czarnecki, SAT 2016.
optional bool use_erwa_heuristic = 75 [default = false];
value | The useErwaHeuristic to set. |
Definition at line 17456 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseExactLpReason | ( | boolean | value | ) |
The solver usually exploit the LP relaxation of a model. If this option is true, then whatever is infered by the LP will be used like an heuristic to compute EXACT propagation on the IP. So with this option, there is no numerical imprecision issues.
optional bool use_exact_lp_reason = 109 [default = true];
value | The useExactLpReason to set. |
Definition at line 29041 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseExtendedProbing | ( | boolean | value | ) |
Use extended probing (probe bool_or, at_most_one, exactly_one).
optional bool use_extended_probing = 269 [default = true];
value | The useExtendedProbing to set. |
Definition at line 26032 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseFeasibilityJump | ( | boolean | value | ) |
Parameters for an heuristic similar to the one described in the paper: "Feasibility Jump: an LP-free Lagrangian MIP heuristic", Bjørnar Luteberget, Giorgio Sartor, 2023, Mathematical Programming Computation.
optional bool use_feasibility_jump = 265 [default = true];
value | The useFeasibilityJump to set. |
Definition at line 26738 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseFeasibilityPump | ( | boolean | value | ) |
Adds a feasibility pump subsolver along with lns subsolvers.
optional bool use_feasibility_pump = 164 [default = true];
value | The useFeasibilityPump to set. |
Definition at line 28558 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseHardPrecedencesInCumulative | ( | boolean | value | ) |
If true, detect and create constraint for integer variable that are "after" a set of intervals in the same cumulative constraint. Experimental: by default we just use "direct" precedences. If exploit_all_precedences is true, we explore the full precedence graph. This assumes we have a DAG otherwise it fails.
optional bool use_hard_precedences_in_cumulative = 215 [default = false];
value | The useHardPrecedencesInCumulative to set. |
Definition at line 25221 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseImpliedBounds | ( | boolean | value | ) |
Stores and exploits "implied-bounds" in the solver. That is, relations of the form literal => (var >= bound). This is currently used to derive stronger cuts.
optional bool use_implied_bounds = 144 [default = true];
value | The useImpliedBounds to set. |
Definition at line 29294 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseLbRelaxLns | ( | boolean | value | ) |
Turns on neighborhood generator based on local branching LP. Based on Huang et al., "Local Branching Relaxation Heuristics for Integer Linear Programs", 2023.
optional bool use_lb_relax_lns = 255 [default = false];
value | The useLbRelaxLns to set. |
Definition at line 28620 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseLnsOnly | ( | boolean | value | ) |
LNS parameters.
optional bool use_lns_only = 101 [default = false];
value | The useLnsOnly to set. |
Definition at line 28382 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseObjectiveLbSearch | ( | boolean | value | ) |
If true, search will search in ascending max objective value (when minimizing) starting from the lower bound of the objective.
optional bool use_objective_lb_search = 228 [default = false];
value | The useObjectiveLbSearch to set. |
Definition at line 26267 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseObjectiveShavingSearch | ( | boolean | value | ) |
This search differs from the previous search as it will not use assumptions to bound the objective, and it will recreate a full model with the hardcoded objective value.
optional bool use_objective_shaving_search = 253 [default = false];
value | The useObjectiveShavingSearch to set. |
Definition at line 26330 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseOptimizationHints | ( | boolean | value | ) |
For an optimization problem, whether we follow some hints in order to find a better first solution. For a variable with hint, the solver will always try to follow the hint. It will revert to the variable_branching default otherwise.
optional bool use_optimization_hints = 35 [default = true];
value | The useOptimizationHints to set. |
Definition at line 24171 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseOptionalVariables | ( | boolean | value | ) |
If true, we automatically detect variables whose constraint are always enforced by the same literal and we mark them as optional. This allows to propagate them as if they were present in some situation. TODO(user): This is experimental and seems to lead to wrong optimal in some situation. It should however gives correct solutions. Fix.
optional bool use_optional_variables = 108 [default = false];
value | The useOptionalVariables to set. |
Definition at line 28971 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseOverloadCheckerInCumulative | ( | boolean | value | ) |
When this is true, the cumulative constraint is reinforced with overload checking, i.e., an additional level of reasoning based on energy. This additional level supplements the default level of reasoning as well as timetable edge finding. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_overload_checker_in_cumulative = 78 [default = false];
value | The useOverloadCheckerInCumulative to set. |
Definition at line 25004 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUsePbResolution | ( | boolean | value | ) |
Whether to use pseudo-Boolean resolution to analyze a conflict. Note that this option only make sense if your problem is modelized using pseudo-Boolean constraints. If you only have clauses, this shouldn't change anything (except slow the solver down).
optional bool use_pb_resolution = 43 [default = false];
value | The usePbResolution to set. |
Definition at line 20365 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUsePhaseSaving | ( | boolean | value | ) |
If this is true, then the polarity of a variable will be the last value it was assigned to, or its default polarity if it was never assigned since the call to ResetDecisionHeuristic(). Actually, we use a newer version where we follow the last value in the longest non-conflicting partial assignment in the current phase. This is called 'literal phase saving'. For details see 'A Lightweight Component Caching Scheme for Satisfiability Solvers' K. Pipatsrisawat and A.Darwiche, In 10th International Conference on Theory and Applications of Satisfiability Testing, 2007.
optional bool use_phase_saving = 44 [default = true];
value | The usePhaseSaving to set. |
Definition at line 17184 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUsePrecedencesInDisjunctiveConstraint | ( | boolean | value | ) |
When this is true, then a disjunctive constraint will try to use the precedence relations between time intervals to propagate their bounds further. For instance if task A and B are both before C and task A and B are in disjunction, then we can deduce that task C must start after duration(A) + duration(B) instead of simply max(duration(A), duration(B)), provided that the start time for all task was currently zero. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_precedences_in_disjunctive_constraint = 74 [default = true];
value | The usePrecedencesInDisjunctiveConstraint to set. |
Definition at line 24678 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseProbingSearch | ( | boolean | value | ) |
If true, search will continuously probe Boolean variables, and integer variable bounds. This parameter is set to true in parallel on the probing worker.
optional bool use_probing_search = 176 [default = false];
value | The useProbingSearch to set. |
Definition at line 25974 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseRinsLns | ( | boolean | value | ) |
Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];
value | The useRinsLns to set. |
Definition at line 28502 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseSatInprocessing | ( | boolean | value | ) |
Enable or disable "inprocessing" which is some SAT presolving done at each restart to the root level.
optional bool use_sat_inprocessing = 163 [default = true];
value | The useSatInprocessing to set. |
Definition at line 22151 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseSharedTreeSearch | ( | boolean | value | ) |
Set on shared subtree workers. Users should not set this directly.
optional bool use_shared_tree_search = 236 [default = false];
value | The useSharedTreeSearch to set. |
Definition at line 27532 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseShavingInProbingSearch | ( | boolean | value | ) |
Add a shaving phase (where the solver tries to prove that the lower or upper bound of a variable are infeasible) to the probing search.
optional bool use_shaving_in_probing_search = 204 [default = true];
value | The useShavingInProbingSearch to set. |
Definition at line 26147 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseStrongPropagationInDisjunctive | ( | boolean | value | ) |
Enable stronger and more expensive propagation on no_overlap constraint.
optional bool use_strong_propagation_in_disjunctive = 230 [default = false];
value | The useStrongPropagationInDisjunctive to set. |
Definition at line 24814 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseTimetableEdgeFindingInCumulative | ( | boolean | value | ) |
When this is true, the cumulative constraint is reinforced with timetable edge finding, i.e., an additional level of reasoning based on the conjunction of energy and mandatory parts. This additional level supplements the default level of reasoning as well as overload_checker. This always result in better propagation, but it is usually slow, so depending on the problem, turning this off may lead to a faster solution.
optional bool use_timetable_edge_finding_in_cumulative = 79 [default = false];
value | The useTimetableEdgeFindingInCumulative to set. |
Definition at line 25084 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setUseTimetablingInNoOverlap2D | ( | boolean | value | ) |
When this is true, the no_overlap_2d constraint is reinforced with propagators from the cumulative constraints. It consists of ignoring the position of rectangles in one position and projecting the no_overlap_2d on the other dimension to create a cumulative constraint. This is done on both axis. This additional level supplements the default level of reasoning.
optional bool use_timetabling_in_no_overlap_2d = 200 [default = false];
value | The useTimetablingInNoOverlap2d to set. |
Definition at line 25426 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setVariableActivityDecay | ( | double | value | ) |
Each time a conflict is found, the activities of some variables are increased by one. Then, the activity of all variables are multiplied by variable_activity_decay. To implement this efficiently, the activity of all the variables is not decayed at each conflict. Instead, the activity increment is multiplied by 1 / decay. When an activity reach max_variable_activity_value, all the activity are multiplied by 1 / max_variable_activity_value.
optional double variable_activity_decay = 15 [default = 0.8];
value | The variableActivityDecay to set. |
Definition at line 18251 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setViolationLsCompoundMoveProbability | ( | double | value | ) |
Probability of using compound move search each restart. TODO(user): Add reference to paper when published.
optional double violation_ls_compound_move_probability = 259 [default = 0.5];
value | The violationLsCompoundMoveProbability to set. |
Definition at line 27403 of file SatParameters.java.
Builder com.google.ortools.sat.SatParameters.Builder.setViolationLsPerturbationPeriod | ( | int | value | ) |
How long violation_ls should wait before perturbating a solution.
optional int32 violation_ls_perturbation_period = 249 [default = 100];
value | The violationLsPerturbationPeriod to set. |
Definition at line 27344 of file SatParameters.java.