public static final class SatParameters.Builder extends com.google.protobuf.GeneratedMessage.Builder<SatParameters.Builder> implements SatParametersOrBuilder
Contains the definitions for all the sat algorithm parameters and their default values. NEXT TAG: 284Protobuf type
operations_research.sat.SatParameters| Modifier and Type | Method and Description |
|---|---|
SatParameters.Builder |
addAllExtraSubsolvers(java.lang.Iterable<java.lang.String> values)
A convenient way to add more workers types.
|
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.
|
SatParameters.Builder |
addAllRestartAlgorithms(java.lang.Iterable<? extends SatParameters.RestartAlgorithm> values)
The restart strategies will change each time the strategy_counter is
increased.
|
SatParameters.Builder |
addAllSubsolverParams(java.lang.Iterable<? extends SatParameters> values)
It is possible to specify additional subsolver configuration.
|
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.
|
SatParameters.Builder |
addExtraSubsolvers(java.lang.String value)
A convenient way to add more workers types.
|
SatParameters.Builder |
addExtraSubsolversBytes(com.google.protobuf.ByteString value)
A convenient way to add more workers types.
|
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.
|
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.
|
SatParameters.Builder |
addRestartAlgorithms(SatParameters.RestartAlgorithm value)
The restart strategies will change each time the strategy_counter is
increased.
|
SatParameters.Builder |
addSubsolverParams(int index,
SatParameters.Builder builderForValue)
It is possible to specify additional subsolver configuration.
|
SatParameters.Builder |
addSubsolverParams(int index,
SatParameters value)
It is possible to specify additional subsolver configuration.
|
SatParameters.Builder |
addSubsolverParams(SatParameters.Builder builderForValue)
It is possible to specify additional subsolver configuration.
|
SatParameters.Builder |
addSubsolverParams(SatParameters value)
It is possible to specify additional subsolver configuration.
|
SatParameters.Builder |
addSubsolverParamsBuilder()
It is possible to specify additional subsolver configuration.
|
SatParameters.Builder |
addSubsolverParamsBuilder(int index)
It is possible to specify additional subsolver configuration.
|
SatParameters.Builder |
addSubsolvers(java.lang.String value)
In multi-thread, the solver can be mainly seen as a portfolio of solvers
with different parameters.
|
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.
|
SatParameters |
build() |
SatParameters |
buildPartial() |
SatParameters.Builder |
clear() |
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.
|
SatParameters.Builder |
clearAddCgCuts()
Whether we generate and add Chvatal-Gomory cuts to the LP at root node.
|
SatParameters.Builder |
clearAddCliqueCuts()
Whether we generate clique cuts from the binary implication graph.
|
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.
|
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.
|
SatParameters.Builder |
clearAddMirCuts()
Whether we generate MIR cuts at root node.
|
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.
|
SatParameters.Builder |
clearAddRltCuts()
Whether we generate RLT cuts.
|
SatParameters.Builder |
clearAddZeroHalfCuts()
Whether we generate Zero-Half cuts at root node.
|
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.
|
SatParameters.Builder |
clearAtMostOneMaxExpansionSize()
All at_most_one constraints with a size <= param will be replaced by a
quadratic number of binary implications.
|
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.
|
SatParameters.Builder |
clearBinaryMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST]; |
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.
|
SatParameters.Builder |
clearBlockingRestartMultiplier()
optional double blocking_restart_multiplier = 66 [default = 1.4]; |
SatParameters.Builder |
clearBlockingRestartWindowSize()
optional int32 blocking_restart_window_size = 65 [default = 5000]; |
SatParameters.Builder |
clearBooleanEncodingLevel()
A non-negative level indicating how much we should try to fully encode
Integer variables as Boolean.
|
SatParameters.Builder |
clearCatchSigintSignal()
Indicates if the CP-SAT layer should catch Control-C (SIGINT) signals
when calling solve.
|
SatParameters.Builder |
clearClauseActivityDecay()
Clause activity parameters (same effect as the one on the variables).
|
SatParameters.Builder |
clearClauseCleanupLbdBound()
All the clauses with a LBD (literal blocks distance) lower or equal to this
parameters will always be kept.
|
SatParameters.Builder |
clearClauseCleanupOrdering()
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY]; |
SatParameters.Builder |
clearClauseCleanupPeriod()
Trigger a cleanup when this number of "deletable" clauses is learned.
|
SatParameters.Builder |
clearClauseCleanupProtection()
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE]; |
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.
|
SatParameters.Builder |
clearClauseCleanupTarget()
During a cleanup, we will always keep that number of "deletable" clauses.
|
SatParameters.Builder |
clearConvertIntervals()
Temporary flag util the feature is more mature.
|
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.
|
SatParameters.Builder |
clearCountAssumptionLevelsInLbd()
Whether or not the assumption levels are taken into account during the LBD
computation.
|
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.
|
SatParameters.Builder |
clearCpModelPresolve()
Whether we presolve the cp_model before solving it.
|
SatParameters.Builder |
clearCpModelProbingLevel()
How much effort do we spend on probing.
|
SatParameters.Builder |
clearCpModelUseSatPresolve()
Whether we also use the sat presolve when cp_model_presolve is true.
|
SatParameters.Builder |
clearCutActiveCountDecay()
optional double cut_active_count_decay = 156 [default = 0.8]; |
SatParameters.Builder |
clearCutCleanupTarget()
Target number of constraints to remove during cleanup.
|
SatParameters.Builder |
clearCutLevel()
Control the global cut effort.
|
SatParameters.Builder |
clearCutMaxActiveCountValue()
These parameters are similar to sat clause management activity parameters.
|
SatParameters.Builder |
clearDebugCrashOnBadHint()
Crash if we do not manage to complete the hint into a full solution.
|
SatParameters.Builder |
clearDebugMaxNumPresolveOperations()
If positive, try to stop just after that many presolve rules have been
applied.
|
SatParameters.Builder |
clearDebugPostsolveWithFullSolver()
We have two different postsolve code.
|
SatParameters.Builder |
clearDefaultRestartAlgorithms()
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"]; |
SatParameters.Builder |
clearDetectLinearizedProduct()
Infer products of Boolean or of Boolean time IntegerVariable from the
linear constrainst in the problem.
|
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.
|
SatParameters.Builder |
clearDisableConstraintExpansion()
If true, it disable all constraint expansion.
|
SatParameters.Builder |
clearDiversifyLnsParams()
If true, registers more lns subsolvers with different parameters.
|
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.
|
SatParameters.Builder |
clearEnumerateAllSolutions()
Whether we enumerate all solutions of a problem without objective.
|
SatParameters.Builder |
clearExpandAlldiffConstraints()
If true, expand all_different constraints that are not permutations.
|
SatParameters.Builder |
clearExpandReservoirConstraints()
If true, expand the reservoir constraints by creating booleans for all
possible precedences between event and encoding the constraint.
|
SatParameters.Builder |
clearExploitAllLpSolution()
If true and the Lp relaxation of the problem has a solution, try to exploit
it.
|
SatParameters.Builder |
clearExploitAllPrecedences()
optional bool exploit_all_precedences = 220 [default = false]; |
SatParameters.Builder |
clearExploitBestSolution()
When branching on a variable, follow the last best solution value.
|
SatParameters.Builder |
clearExploitIntegerLpSolution()
If true and the Lp relaxation of the problem has an integer optimal
solution, try to exploit it.
|
SatParameters.Builder |
clearExploitObjective()
When branching an a variable that directly affect the objective,
branch on the value that lead to the best objective first.
|
SatParameters.Builder |
clearExploitRelaxationSolution()
When branching on a variable, follow the last best relaxation solution
value.
|
SatParameters.Builder |
clearExtraSubsolvers()
A convenient way to add more workers types.
|
SatParameters.Builder |
clearFeasibilityJumpDecay()
On each restart, we randomly choose if we use decay (with this parameter)
or no decay.
|
SatParameters.Builder |
clearFeasibilityJumpEnableRestarts()
When stagnating, feasibility jump will either restart from a default
solution (with some possible randomization), or randomly pertubate the
current solution.
|
SatParameters.Builder |
clearFeasibilityJumpLinearizationLevel()
How much do we linearize the problem in the local search code.
|
SatParameters.Builder |
clearFeasibilityJumpMaxExpandedConstraintSize()
Maximum size of no_overlap or no_overlap_2d constraint for a quadratic
expansion.
|
SatParameters.Builder |
clearFeasibilityJumpRestartFactor()
This is a factor that directly influence the work before each restart.
|
SatParameters.Builder |
clearFeasibilityJumpVarPerburbationRangeRatio()
Max distance between the default value and the pertubated value relative to
the range of the domain of the variable.
|
SatParameters.Builder |
clearFeasibilityJumpVarRandomizationProbability()
Probability for a variable to have a non default value upon restarts or
perturbations.
|
SatParameters.Builder |
clearFillAdditionalSolutionsInResponse()
If true, the final response addition_solutions field will be filled with
all solutions from our solutions pool.
|
SatParameters.Builder |
clearFillTightenedDomainsInResponse()
If true, add information about the derived variable domains to the
CpSolverResponse.
|
SatParameters.Builder |
clearFindBigLinearOverlap()
Try to find large "rectangle" in the linear constraint matrix with
identical lines.
|
SatParameters.Builder |
clearFindMultipleCores()
Whether we try to find more independent cores for a given set of
assumptions in the core based max-SAT algorithms.
|
SatParameters.Builder |
clearFixVariablesToTheirHintedValue()
If true, variables appearing in the solution hints will be fixed to their
hinted value.
|
SatParameters.Builder |
clearFpRounding()
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED]; |
SatParameters.Builder |
clearGlucoseDecayIncrement()
optional double glucose_decay_increment = 23 [default = 0.01]; |
SatParameters.Builder |
clearGlucoseDecayIncrementPeriod()
optional int32 glucose_decay_increment_period = 24 [default = 5000]; |
SatParameters.Builder |
clearGlucoseMaxDecay()
The activity starts at 0.8 and increment by 0.01 every 5000 conflicts until
0.95.
|
SatParameters.Builder |
clearHintConflictLimit()
Conflict limit used in the phase that exploit the solution hint.
|
SatParameters.Builder |
clearIgnoreNames()
If true, we don't keep names in our internal copy of the user given model.
|
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.
|
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.
|
SatParameters.Builder |
clearInitialPolarity()
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE]; |
SatParameters.Builder |
clearInitialVariablesActivity()
The initial value of the variables activity.
|
SatParameters.Builder |
clearInprocessingDtimeRatio()
Proportion of deterministic time we should spend on inprocessing.
|
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.
|
SatParameters.Builder |
clearInprocessingProbingDtime()
The amount of dtime we should spend on probing for each inprocessing round.
|
SatParameters.Builder |
clearInstantiateAllVariables()
If true, the solver will add a default integer branching strategy to the
already defined search strategy.
|
SatParameters.Builder |
clearInterleaveBatchSize()
optional int32 interleave_batch_size = 134 [default = 0]; |
SatParameters.Builder |
clearInterleaveSearch()
Experimental.
|
SatParameters.Builder |
clearKeepAllFeasibleSolutionsInPresolve()
If true, we disable the presolve reductions that remove feasible solutions
from the search space.
|
SatParameters.Builder |
clearLinearizationLevel()
A non-negative level indicating the type of constraints we consider in the
LP relaxation.
|
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.
|
SatParameters.Builder |
clearLogPrefix()
Add a prefix to all logs.
|
SatParameters.Builder |
clearLogSearchProgress()
Whether the solver should log the search progress.
|
SatParameters.Builder |
clearLogSubsolverStatistics()
Whether the solver should display per sub-solver search statistics.
|
SatParameters.Builder |
clearLogToResponse()
Log to response proto.
|
SatParameters.Builder |
clearLogToStdout()
Log to stdout.
|
SatParameters.Builder |
clearLpDualTolerance()
optional double lp_dual_tolerance = 267 [default = 1e-07]; |
SatParameters.Builder |
clearLpPrimalTolerance()
The internal LP tolerances used by CP-SAT.
|
SatParameters.Builder |
clearMaxAllDiffCutSize()
Cut generator for all diffs can add too many cuts for large all_diff
constraints.
|
SatParameters.Builder |
clearMaxClauseActivityValue()
optional double max_clause_activity_value = 18 [default = 1e+20]; |
SatParameters.Builder |
clearMaxConsecutiveInactiveCount()
If a constraint/cut in LP is not active for that many consecutive OPTIMAL
solves, remove it from the LP.
|
SatParameters.Builder |
clearMaxCutRoundsAtLevelZero()
Max number of time we perform cut generation and resolve the LP at level 0.
|
SatParameters.Builder |
clearMaxDeterministicTime()
Maximum time allowed in deterministic time to solve a problem.
|
SatParameters.Builder |
clearMaxDomainSizeWhenEncodingEqNeqConstraints()
When loading a*x + b*y ==/!= c when x and y are both fully encoded.
|
SatParameters.Builder |
clearMaxIntegerRoundingScaling()
In the integer rounding procedure used for MIR and Gomory cut, the maximum
"scaling" we use (must be positive).
|
SatParameters.Builder |
clearMaxLinMaxSizeForExpansion()
If the number of expressions in the lin_max is less that the max size
parameter, model expansion replaces target = max(xi) by linear constraint
with the introduction of new booleans bi such that bi => target == xi.
|
SatParameters.Builder |
clearMaxMemoryInMb()
Maximum memory allowed for the whole thread containing the solver.
|
SatParameters.Builder |
clearMaxNumberOfConflicts()
Maximum number of conflicts allowed to solve a problem.
|
SatParameters.Builder |
clearMaxNumCuts()
The limit on the number of cuts in our cut pool.
|
SatParameters.Builder |
clearMaxNumIntervalsForTimetableEdgeFinding()
Max number of intervals for the timetable_edge_finding algorithm to
propagate.
|
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.
|
SatParameters.Builder |
clearMaxPresolveIterations()
In case of large reduction in a presolve iteration, we perform multiple
presolve iterations.
|
SatParameters.Builder |
clearMaxSatAssumptionOrder()
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER]; |
SatParameters.Builder |
clearMaxSatReverseAssumptionOrder()
If true, adds the assumption in the reverse order of the one defined by
max_sat_assumption_order.
|
SatParameters.Builder |
clearMaxSatStratification()
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT]; |
SatParameters.Builder |
clearMaxSizeToCreatePrecedenceLiteralsInDisjunctive()
Create one literal for each disjunction of two pairs of tasks.
|
SatParameters.Builder |
clearMaxTimeInSeconds()
Maximum time allowed in seconds to solve a problem.
|
SatParameters.Builder |
clearMaxVariableActivityValue()
optional double max_variable_activity_value = 16 [default = 1e+100]; |
SatParameters.Builder |
clearMergeAtMostOneWorkLimit()
optional double merge_at_most_one_work_limit = 146 [default = 100000000]; |
SatParameters.Builder |
clearMergeNoOverlapWorkLimit()
During presolve, we use a maximum clique heuristic to merge together
no-overlap constraints or at most one constraints.
|
SatParameters.Builder |
clearMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE]; |
SatParameters.Builder |
clearMinimizeReductionDuringPbResolution()
A different algorithm during PB resolution.
|
SatParameters.Builder |
clearMinNumLnsWorkers()
Obsolete parameter.
|
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.
|
SatParameters.Builder |
clearMipAutomaticallyScaleVariables()
If true, some continuous variable might be automatically scaled.
|
SatParameters.Builder |
clearMipCheckPrecision()
As explained in mip_precision and mip_max_activity_exponent, we cannot
always reach the wanted precision during scaling.
|
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.
|
SatParameters.Builder |
clearMipDropTolerance()
Any value in the input mip with a magnitude lower than this will be set to
zero.
|
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.
|
SatParameters.Builder |
clearMipMaxBound()
We need to bound the maximum magnitude of the variables for CP-SAT, and
that is the bound we use.
|
SatParameters.Builder |
clearMipMaxValidMagnitude()
Any finite values in the input MIP must be below this threshold, otherwise
the model will be reported invalid.
|
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.
|
SatParameters.Builder |
clearMipScaleLargeDomain()
If this is false, then mip_var_scaling is only applied to variables with
"small" domain.
|
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.
|
SatParameters.Builder |
clearMipVarScaling()
All continuous variable of the problem will be multiplied by this factor.
|
SatParameters.Builder |
clearMipWantedPrecision()
When scaling constraint with double coefficients to integer coefficients,
we will multiply by a power of 2 and round the coefficients.
|
SatParameters.Builder |
clearName()
In some context, like in a portfolio of search, it makes sense to name a
given parameters set for logging purpose.
|
SatParameters.Builder |
clearNewConstraintsBatchSize()
Add that many lazy constraints (or cuts) at once in the LP.
|
SatParameters.Builder |
clearNewLinearPropagation()
The new linear propagation code treat all constraints at once and use
an adaptation of Bellman-Ford-Tarjan to propagate constraint in a smarter
order and potentially detect propagation cycle earlier.
|
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.
|
SatParameters.Builder |
clearNumSearchWorkers()
optional int32 num_search_workers = 100 [default = 0]; |
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.
|
SatParameters.Builder |
clearNumWorkers()
Specify the number of parallel workers (i.e.
|
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.
|
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.
|
SatParameters.Builder |
clearOptimizeWithCore()
The default optimization method is a simple "linear scan", each time trying
to find a better solution than the previous one.
|
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.
|
SatParameters.Builder |
clearOptimizeWithMaxHs()
This has no effect if optimize_with_core is false.
|
SatParameters.Builder |
clearPbCleanupIncrement()
Same as for the clauses, but for the learned pseudo-Boolean constraints.
|
SatParameters.Builder |
clearPbCleanupRatio()
optional double pb_cleanup_ratio = 47 [default = 0.5]; |
SatParameters.Builder |
clearPermutePresolveConstraintOrder()
optional bool permute_presolve_constraint_order = 179 [default = false]; |
SatParameters.Builder |
clearPermuteVariableRandomly()
This is mainly here to test the solver variability.
|
SatParameters.Builder |
clearPolarityRephaseIncrement()
If non-zero, then we change the polarity heuristic after that many number
of conflicts in an arithmetically increasing fashion.
|
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.
|
SatParameters.Builder |
clearPreferredVariableOrder()
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER]; |
SatParameters.Builder |
clearPresolveBlockedClause()
Whether we use an heuristic to detect some basic case of blocked clause
in the SAT presolve.
|
SatParameters.Builder |
clearPresolveBvaThreshold()
Apply Bounded Variable Addition (BVA) if the number of clauses is reduced
by stricly more than this threshold.
|
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.
|
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.
|
SatParameters.Builder |
clearPresolveExtractIntegerEnforcement()
If true, we will extract from linear constraints, enforcement literals of
the form "integer variable at bound => simplified constraint".
|
SatParameters.Builder |
clearPresolveInclusionWorkLimit()
A few presolve operations involve detecting constraints included in other
constraint.
|
SatParameters.Builder |
clearPresolveProbingDeterministicTimeLimit()
optional double presolve_probing_deterministic_time_limit = 57 [default = 30]; |
SatParameters.Builder |
clearPresolveSubstitutionLevel()
How much substitution (also called free variable aggregation in MIP
litterature) should we perform at presolve.
|
SatParameters.Builder |
clearPresolveUseBva()
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
|
SatParameters.Builder |
clearProbingDeterministicTimeLimit()
The maximum "deterministic" time limit to spend in probing.
|
SatParameters.Builder |
clearProbingNumCombinationsLimit()
How many combinations of pairs or triplets of variables we want to scan.
|
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.
|
SatParameters.Builder |
clearPseudoCostReliabilityThreshold()
The solver ignores the pseudo costs of variables with number of recordings
less than this threshold.
|
SatParameters.Builder |
clearPushAllTasksTowardStart()
Experimental code: specify if the objective pushes all tasks toward the
start of the schedule.
|
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.
|
SatParameters.Builder |
clearRandomizeSearch()
Randomize fixed search.
|
SatParameters.Builder |
clearRandomPolarityRatio()
The proportion of polarity chosen at random.
|
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.
|
SatParameters.Builder |
clearRelativeGapLimit()
optional double relative_gap_limit = 160 [default = 0]; |
SatParameters.Builder |
clearRepairHint()
If true, the solver tries to repair the solution given in the hint.
|
SatParameters.Builder |
clearRestartAlgorithms()
The restart strategies will change each time the strategy_counter is
increased.
|
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.
|
SatParameters.Builder |
clearRestartLbdAverageRatio()
optional double restart_lbd_average_ratio = 71 [default = 1]; |
SatParameters.Builder |
clearRestartPeriod()
Restart period for the FIXED_RESTART strategy.
|
SatParameters.Builder |
clearRestartRunningWindowSize()
Size of the window for the moving average restarts.
|
SatParameters.Builder |
clearRootLpIterations()
Even at the root node, we do not want to spend too much time on the LP if
it is "difficult".
|
SatParameters.Builder |
clearSearchBranching()
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH]; |
SatParameters.Builder |
clearSearchRandomVariablePoolSize()
Search randomization will collect the top
'search_random_variable_pool_size' valued variables, and pick one randomly.
|
SatParameters.Builder |
clearShareBinaryClauses()
Allows sharing of new learned binary clause between workers.
|
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.
|
SatParameters.Builder |
clearSharedTreeNumWorkers()
Enables experimental workstealing-like shared tree search.
|
SatParameters.Builder |
clearSharedTreeOpenLeavesPerWorker()
How many open leaf nodes should the shared tree maintain per worker.
|
SatParameters.Builder |
clearSharedTreeSplitStrategy()
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO]; |
SatParameters.Builder |
clearSharedTreeWorkerMinRestartsPerSubtree()
Minimum number of restarts before a worker will replace a subtree
that looks "bad" based on the average LBD of learned clauses.
|
SatParameters.Builder |
clearSharedTreeWorkerObjectiveSplitProbability()
After their assigned prefix, shared tree workers will branch on the
objective with this probability.
|
SatParameters.Builder |
clearShareLevelZeroBounds()
Allows sharing of the bounds of modified variables at level 0.
|
SatParameters.Builder |
clearShareObjectiveBounds()
Allows objective sharing between workers.
|
SatParameters.Builder |
clearShavingSearchDeterministicTime()
Specifies the amount of deterministic time spent of each try at shaving a
bound in the shaving search.
|
SatParameters.Builder |
clearSolutionPoolSize()
Size of the top-n different solutions kept by the solver.
|
SatParameters.Builder |
clearStopAfterFirstSolution()
For an optimization problem, stop the solver as soon as we have a solution.
|
SatParameters.Builder |
clearStopAfterPresolve()
Mainly used when improving the presolver.
|
SatParameters.Builder |
clearStopAfterRootPropagation()
optional bool stop_after_root_propagation = 252 [default = false]; |
SatParameters.Builder |
clearStrategyChangeIncreaseRatio()
The parameter num_conflicts_before_strategy_changes is increased by that
much after each strategy change.
|
SatParameters.Builder |
clearSubsolverParams()
It is possible to specify additional subsolver configuration.
|
SatParameters.Builder |
clearSubsolvers()
In multi-thread, the solver can be mainly seen as a portfolio of solvers
with different parameters.
|
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.
|
SatParameters.Builder |
clearSymmetryLevel()
Whether we try to automatically detect the symmetries in a model and
exploit them.
|
SatParameters.Builder |
clearTableCompressionLevel()
How much we try to "compress" a table constraint.
|
SatParameters.Builder |
clearTestFeasibilityJump()
Disable every other type of subsolver, setting this turns CP-SAT into a
pure local-search solver.
|
SatParameters.Builder |
clearUseAbslRandom()
optional bool use_absl_random = 180 [default = false]; |
SatParameters.Builder |
clearUseAreaEnergeticReasoningInNoOverlap2D()
When this is true, the no_overlap_2d constraint is reinforced with
an energetic reasoning that uses an area-based energy.
|
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.
|
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.
|
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.
|
SatParameters.Builder |
clearUseDualSchedulingHeuristics()
When set, it activates a few scheduling parameters to improve the lower
bound of scheduling problems.
|
SatParameters.Builder |
clearUseDynamicPrecedenceInCumulative()
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false]; |
SatParameters.Builder |
clearUseDynamicPrecedenceInDisjunctive()
Whether we try to branch on decision "interval A before interval B" rather
than on intervals bounds.
|
SatParameters.Builder |
clearUseEnergeticReasoningInNoOverlap2D()
When this is true, the no_overlap_2d constraint is reinforced with
energetic reasoning.
|
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.
|
SatParameters.Builder |
clearUseExactLpReason()
The solver usually exploit the LP relaxation of a model.
|
SatParameters.Builder |
clearUseExtendedProbing()
Use extended probing (probe bool_or, at_most_one, exactly_one).
|
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.
|
SatParameters.Builder |
clearUseFeasibilityPump()
Adds a feasibility pump subsolver along with lns subsolvers.
|
SatParameters.Builder |
clearUseHardPrecedencesInCumulative()
If true, detect and create constraint for integer variable that are "after"
a set of intervals in the same cumulative constraint.
|
SatParameters.Builder |
clearUseImpliedBounds()
Stores and exploits "implied-bounds" in the solver.
|
SatParameters.Builder |
clearUseLbRelaxLns()
Turns on neighborhood generator based on local branching LP.
|
SatParameters.Builder |
clearUseLns()
Testing parameters used to disable all lns workers.
|
SatParameters.Builder |
clearUseLnsOnly()
Experimental parameters to disable everything but lns.
|
SatParameters.Builder |
clearUseObjectiveLbSearch()
If true, search will search in ascending max objective value (when
minimizing) starting from the lower bound of the objective.
|
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.
|
SatParameters.Builder |
clearUseOptimizationHints()
For an optimization problem, whether we follow some hints in order to find
a better first solution.
|
SatParameters.Builder |
clearUseOptionalVariables()
If true, we automatically detect variables whose constraint are always
enforced by the same literal and we mark them as optional.
|
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.
|
SatParameters.Builder |
clearUsePbResolution()
Whether to use pseudo-Boolean resolution to analyze a conflict.
|
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().
|
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.
|
SatParameters.Builder |
clearUseProbingSearch()
If true, search will continuously probe Boolean variables, and integer
variable bounds.
|
SatParameters.Builder |
clearUseRinsLns()
Turns on relaxation induced neighborhood generator.
|
SatParameters.Builder |
clearUseSatInprocessing()
Enable or disable "inprocessing" which is some SAT presolving done at
each restart to the root level.
|
SatParameters.Builder |
clearUseSharedTreeSearch()
Set on shared subtree workers.
|
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.
|
SatParameters.Builder |
clearUseStrongPropagationInDisjunctive()
Enable stronger and more expensive propagation on no_overlap constraint.
|
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.
|
SatParameters.Builder |
clearUseTimetablingInNoOverlap2D()
When this is true, the no_overlap_2d constraint is reinforced with
propagators from the cumulative constraints.
|
SatParameters.Builder |
clearVariableActivityDecay()
Each time a conflict is found, the activities of some variables are
increased by one.
|
SatParameters.Builder |
clearViolationLsCompoundMoveProbability()
Probability of using compound move search each restart.
|
SatParameters.Builder |
clearViolationLsPerturbationPeriod()
How long violation_ls should wait before perturbating a solution.
|
double |
getAbsoluteGapLimit()
Stop the search when the gap between the best feasible objective (O) and
our best objective bound (B) is smaller than a limit.
|
boolean |
getAddCgCuts()
Whether we generate and add Chvatal-Gomory cuts to the LP at root node.
|
boolean |
getAddCliqueCuts()
Whether we generate clique cuts from the binary implication graph.
|
boolean |
getAddLinMaxCuts()
For the lin max constraints, generates the cuts described in "Strong
mixed-integer programming formulations for trained neural networks" by Ross
Anderson et.
|
boolean |
getAddLpConstraintsLazily()
If true, we start by an empty LP, and only add constraints not satisfied
by the current LP solution batch by batch.
|
boolean |
getAddMirCuts()
Whether we generate MIR cuts at root node.
|
boolean |
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.
|
boolean |
getAddRltCuts()
Whether we generate RLT cuts.
|
boolean |
getAddZeroHalfCuts()
Whether we generate Zero-Half cuts at root node.
|
boolean |
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.
|
int |
getAtMostOneMaxExpansionSize()
All at_most_one constraints with a size <= param will be replaced by a
quadratic number of binary implications.
|
boolean |
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.
|
SatParameters.BinaryMinizationAlgorithm |
getBinaryMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST]; |
int |
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.
|
double |
getBlockingRestartMultiplier()
optional double blocking_restart_multiplier = 66 [default = 1.4]; |
int |
getBlockingRestartWindowSize()
optional int32 blocking_restart_window_size = 65 [default = 5000]; |
int |
getBooleanEncodingLevel()
A non-negative level indicating how much we should try to fully encode
Integer variables as Boolean.
|
boolean |
getCatchSigintSignal()
Indicates if the CP-SAT layer should catch Control-C (SIGINT) signals
when calling solve.
|
double |
getClauseActivityDecay()
Clause activity parameters (same effect as the one on the variables).
|
int |
getClauseCleanupLbdBound()
All the clauses with a LBD (literal blocks distance) lower or equal to this
parameters will always be kept.
|
SatParameters.ClauseOrdering |
getClauseCleanupOrdering()
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY]; |
int |
getClauseCleanupPeriod()
Trigger a cleanup when this number of "deletable" clauses is learned.
|
SatParameters.ClauseProtection |
getClauseCleanupProtection()
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE]; |
double |
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.
|
int |
getClauseCleanupTarget()
During a cleanup, we will always keep that number of "deletable" clauses.
|
boolean |
getConvertIntervals()
Temporary flag util the feature is more mature.
|
int |
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.
|
boolean |
getCountAssumptionLevelsInLbd()
Whether or not the assumption levels are taken into account during the LBD
computation.
|
boolean |
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.
|
boolean |
getCpModelPresolve()
Whether we presolve the cp_model before solving it.
|
int |
getCpModelProbingLevel()
How much effort do we spend on probing.
|
boolean |
getCpModelUseSatPresolve()
Whether we also use the sat presolve when cp_model_presolve is true.
|
double |
getCutActiveCountDecay()
optional double cut_active_count_decay = 156 [default = 0.8]; |
int |
getCutCleanupTarget()
Target number of constraints to remove during cleanup.
|
int |
getCutLevel()
Control the global cut effort.
|
double |
getCutMaxActiveCountValue()
These parameters are similar to sat clause management activity parameters.
|
boolean |
getDebugCrashOnBadHint()
Crash if we do not manage to complete the hint into a full solution.
|
int |
getDebugMaxNumPresolveOperations()
If positive, try to stop just after that many presolve rules have been
applied.
|
boolean |
getDebugPostsolveWithFullSolver()
We have two different postsolve code.
|
SatParameters |
getDefaultInstanceForType() |
java.lang.String |
getDefaultRestartAlgorithms()
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"]; |
com.google.protobuf.ByteString |
getDefaultRestartAlgorithmsBytes()
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"]; |
static com.google.protobuf.Descriptors.Descriptor |
getDescriptor() |
com.google.protobuf.Descriptors.Descriptor |
getDescriptorForType() |
boolean |
getDetectLinearizedProduct()
Infer products of Boolean or of Boolean time IntegerVariable from the
linear constrainst in the problem.
|
boolean |
getDetectTableWithCost()
If true, we detect variable that are unique to a table constraint and only
there to encode a cost on each tuple.
|
boolean |
getDisableConstraintExpansion()
If true, it disable all constraint expansion.
|
boolean |
getDiversifyLnsParams()
If true, registers more lns subsolvers with different parameters.
|
boolean |
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.
|
boolean |
getEnumerateAllSolutions()
Whether we enumerate all solutions of a problem without objective.
|
boolean |
getExpandAlldiffConstraints()
If true, expand all_different constraints that are not permutations.
|
boolean |
getExpandReservoirConstraints()
If true, expand the reservoir constraints by creating booleans for all
possible precedences between event and encoding the constraint.
|
boolean |
getExploitAllLpSolution()
If true and the Lp relaxation of the problem has a solution, try to exploit
it.
|
boolean |
getExploitAllPrecedences()
optional bool exploit_all_precedences = 220 [default = false]; |
boolean |
getExploitBestSolution()
When branching on a variable, follow the last best solution value.
|
boolean |
getExploitIntegerLpSolution()
If true and the Lp relaxation of the problem has an integer optimal
solution, try to exploit it.
|
boolean |
getExploitObjective()
When branching an a variable that directly affect the objective,
branch on the value that lead to the best objective first.
|
boolean |
getExploitRelaxationSolution()
When branching on a variable, follow the last best relaxation solution
value.
|
java.lang.String |
getExtraSubsolvers(int index)
A convenient way to add more workers types.
|
com.google.protobuf.ByteString |
getExtraSubsolversBytes(int index)
A convenient way to add more workers types.
|
int |
getExtraSubsolversCount()
A convenient way to add more workers types.
|
com.google.protobuf.ProtocolStringList |
getExtraSubsolversList()
A convenient way to add more workers types.
|
double |
getFeasibilityJumpDecay()
On each restart, we randomly choose if we use decay (with this parameter)
or no decay.
|
boolean |
getFeasibilityJumpEnableRestarts()
When stagnating, feasibility jump will either restart from a default
solution (with some possible randomization), or randomly pertubate the
current solution.
|
int |
getFeasibilityJumpLinearizationLevel()
How much do we linearize the problem in the local search code.
|
int |
getFeasibilityJumpMaxExpandedConstraintSize()
Maximum size of no_overlap or no_overlap_2d constraint for a quadratic
expansion.
|
int |
getFeasibilityJumpRestartFactor()
This is a factor that directly influence the work before each restart.
|
double |
getFeasibilityJumpVarPerburbationRangeRatio()
Max distance between the default value and the pertubated value relative to
the range of the domain of the variable.
|
double |
getFeasibilityJumpVarRandomizationProbability()
Probability for a variable to have a non default value upon restarts or
perturbations.
|
boolean |
getFillAdditionalSolutionsInResponse()
If true, the final response addition_solutions field will be filled with
all solutions from our solutions pool.
|
boolean |
getFillTightenedDomainsInResponse()
If true, add information about the derived variable domains to the
CpSolverResponse.
|
boolean |
getFindBigLinearOverlap()
Try to find large "rectangle" in the linear constraint matrix with
identical lines.
|
boolean |
getFindMultipleCores()
Whether we try to find more independent cores for a given set of
assumptions in the core based max-SAT algorithms.
|
boolean |
getFixVariablesToTheirHintedValue()
If true, variables appearing in the solution hints will be fixed to their
hinted value.
|
SatParameters.FPRoundingMethod |
getFpRounding()
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED]; |
double |
getGlucoseDecayIncrement()
optional double glucose_decay_increment = 23 [default = 0.01]; |
int |
getGlucoseDecayIncrementPeriod()
optional int32 glucose_decay_increment_period = 24 [default = 5000]; |
double |
getGlucoseMaxDecay()
The activity starts at 0.8 and increment by 0.01 every 5000 conflicts until
0.95.
|
int |
getHintConflictLimit()
Conflict limit used in the phase that exploit the solution hint.
|
boolean |
getIgnoreNames()
If true, we don't keep names in our internal copy of the user given model.
|
java.lang.String |
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.
|
com.google.protobuf.ByteString |
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.
|
int |
getIgnoreSubsolversCount()
Rather than fully specifying subsolvers, it is often convenient to just
remove the ones that are not useful on a given problem.
|
com.google.protobuf.ProtocolStringList |
getIgnoreSubsolversList()
Rather than fully specifying subsolvers, it is often convenient to just
remove the ones that are not useful on a given problem.
|
boolean |
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.
|
SatParameters.Polarity |
getInitialPolarity()
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE]; |
double |
getInitialVariablesActivity()
The initial value of the variables activity.
|
double |
getInprocessingDtimeRatio()
Proportion of deterministic time we should spend on inprocessing.
|
double |
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.
|
double |
getInprocessingProbingDtime()
The amount of dtime we should spend on probing for each inprocessing round.
|
boolean |
getInstantiateAllVariables()
If true, the solver will add a default integer branching strategy to the
already defined search strategy.
|
int |
getInterleaveBatchSize()
optional int32 interleave_batch_size = 134 [default = 0]; |
boolean |
getInterleaveSearch()
Experimental.
|
boolean |
getKeepAllFeasibleSolutionsInPresolve()
If true, we disable the presolve reductions that remove feasible solutions
from the search space.
|
int |
getLinearizationLevel()
A non-negative level indicating the type of constraints we consider in the
LP relaxation.
|
int |
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.
|
java.lang.String |
getLogPrefix()
Add a prefix to all logs.
|
com.google.protobuf.ByteString |
getLogPrefixBytes()
Add a prefix to all logs.
|
boolean |
getLogSearchProgress()
Whether the solver should log the search progress.
|
boolean |
getLogSubsolverStatistics()
Whether the solver should display per sub-solver search statistics.
|
boolean |
getLogToResponse()
Log to response proto.
|
boolean |
getLogToStdout()
Log to stdout.
|
double |
getLpDualTolerance()
optional double lp_dual_tolerance = 267 [default = 1e-07]; |
double |
getLpPrimalTolerance()
The internal LP tolerances used by CP-SAT.
|
int |
getMaxAllDiffCutSize()
Cut generator for all diffs can add too many cuts for large all_diff
constraints.
|
double |
getMaxClauseActivityValue()
optional double max_clause_activity_value = 18 [default = 1e+20]; |
int |
getMaxConsecutiveInactiveCount()
If a constraint/cut in LP is not active for that many consecutive OPTIMAL
solves, remove it from the LP.
|
int |
getMaxCutRoundsAtLevelZero()
Max number of time we perform cut generation and resolve the LP at level 0.
|
double |
getMaxDeterministicTime()
Maximum time allowed in deterministic time to solve a problem.
|
int |
getMaxDomainSizeWhenEncodingEqNeqConstraints()
When loading a*x + b*y ==/!= c when x and y are both fully encoded.
|
int |
getMaxIntegerRoundingScaling()
In the integer rounding procedure used for MIR and Gomory cut, the maximum
"scaling" we use (must be positive).
|
int |
getMaxLinMaxSizeForExpansion()
If the number of expressions in the lin_max is less that the max size
parameter, model expansion replaces target = max(xi) by linear constraint
with the introduction of new booleans bi such that bi => target == xi.
|
long |
getMaxMemoryInMb()
Maximum memory allowed for the whole thread containing the solver.
|
long |
getMaxNumberOfConflicts()
Maximum number of conflicts allowed to solve a problem.
|
int |
getMaxNumCuts()
The limit on the number of cuts in our cut pool.
|
int |
getMaxNumIntervalsForTimetableEdgeFinding()
Max number of intervals for the timetable_edge_finding algorithm to
propagate.
|
int |
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.
|
int |
getMaxPresolveIterations()
In case of large reduction in a presolve iteration, we perform multiple
presolve iterations.
|
SatParameters.MaxSatAssumptionOrder |
getMaxSatAssumptionOrder()
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER]; |
boolean |
getMaxSatReverseAssumptionOrder()
If true, adds the assumption in the reverse order of the one defined by
max_sat_assumption_order.
|
SatParameters.MaxSatStratificationAlgorithm |
getMaxSatStratification()
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT]; |
int |
getMaxSizeToCreatePrecedenceLiteralsInDisjunctive()
Create one literal for each disjunction of two pairs of tasks.
|
double |
getMaxTimeInSeconds()
Maximum time allowed in seconds to solve a problem.
|
double |
getMaxVariableActivityValue()
optional double max_variable_activity_value = 16 [default = 1e+100]; |
double |
getMergeAtMostOneWorkLimit()
optional double merge_at_most_one_work_limit = 146 [default = 100000000]; |
double |
getMergeNoOverlapWorkLimit()
During presolve, we use a maximum clique heuristic to merge together
no-overlap constraints or at most one constraints.
|
SatParameters.ConflictMinimizationAlgorithm |
getMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE]; |
boolean |
getMinimizeReductionDuringPbResolution()
A different algorithm during PB resolution.
|
int |
getMinNumLnsWorkers()
Obsolete parameter.
|
double |
getMinOrthogonalityForLpConstraints()
While adding constraints, skip the constraints which have orthogonality
less than 'min_orthogonality_for_lp_constraints' with already added
constraints during current call.
|
boolean |
getMipAutomaticallyScaleVariables()
If true, some continuous variable might be automatically scaled.
|
double |
getMipCheckPrecision()
As explained in mip_precision and mip_max_activity_exponent, we cannot
always reach the wanted precision during scaling.
|
boolean |
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.
|
double |
getMipDropTolerance()
Any value in the input mip with a magnitude lower than this will be set to
zero.
|
int |
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.
|
double |
getMipMaxBound()
We need to bound the maximum magnitude of the variables for CP-SAT, and
that is the bound we use.
|
double |
getMipMaxValidMagnitude()
Any finite values in the input MIP must be below this threshold, otherwise
the model will be reported invalid.
|
int |
getMipPresolveLevel()
When solving a MIP, we do some basic floating point presolving before
scaling the problem to integer to be handled by CP-SAT.
|
boolean |
getMipScaleLargeDomain()
If this is false, then mip_var_scaling is only applied to variables with
"small" domain.
|
boolean |
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.
|
double |
getMipVarScaling()
All continuous variable of the problem will be multiplied by this factor.
|
double |
getMipWantedPrecision()
When scaling constraint with double coefficients to integer coefficients,
we will multiply by a power of 2 and round the coefficients.
|
java.lang.String |
getName()
In some context, like in a portfolio of search, it makes sense to name a
given parameters set for logging purpose.
|
com.google.protobuf.ByteString |
getNameBytes()
In some context, like in a portfolio of search, it makes sense to name a
given parameters set for logging purpose.
|
int |
getNewConstraintsBatchSize()
Add that many lazy constraints (or cuts) at once in the LP.
|
boolean |
getNewLinearPropagation()
The new linear propagation code treat all constraints at once and use
an adaptation of Bellman-Ford-Tarjan to propagate constraint in a smarter
order and potentially detect propagation cycle earlier.
|
int |
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.
|
int |
getNumSearchWorkers()
optional int32 num_search_workers = 100 [default = 0]; |
int |
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.
|
int |
getNumWorkers()
Specify the number of parallel workers (i.e.
|
boolean |
getOnlyAddCutsAtLevelZero()
For the cut that can be generated at any level, this control if we only
try to generate them at the root node.
|
boolean |
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.
|
boolean |
getOptimizeWithCore()
The default optimization method is a simple "linear scan", each time trying
to find a better solution than the previous one.
|
boolean |
getOptimizeWithLbTreeSearch()
Do a more conventional tree search (by opposition to SAT based one) where
we keep all the explored node in a tree.
|
boolean |
getOptimizeWithMaxHs()
This has no effect if optimize_with_core is false.
|
int |
getPbCleanupIncrement()
Same as for the clauses, but for the learned pseudo-Boolean constraints.
|
double |
getPbCleanupRatio()
optional double pb_cleanup_ratio = 47 [default = 0.5]; |
boolean |
getPermutePresolveConstraintOrder()
optional bool permute_presolve_constraint_order = 179 [default = false]; |
boolean |
getPermuteVariableRandomly()
This is mainly here to test the solver variability.
|
int |
getPolarityRephaseIncrement()
If non-zero, then we change the polarity heuristic after that many number
of conflicts in an arithmetically increasing fashion.
|
boolean |
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.
|
SatParameters.VariableOrder |
getPreferredVariableOrder()
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER]; |
boolean |
getPresolveBlockedClause()
Whether we use an heuristic to detect some basic case of blocked clause
in the SAT presolve.
|
int |
getPresolveBvaThreshold()
Apply Bounded Variable Addition (BVA) if the number of clauses is reduced
by stricly more than this threshold.
|
int |
getPresolveBveClauseWeight()
During presolve, we apply BVE only if this weight times the number of
clauses plus the number of clause literals is not increased.
|
int |
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.
|
boolean |
getPresolveExtractIntegerEnforcement()
If true, we will extract from linear constraints, enforcement literals of
the form "integer variable at bound => simplified constraint".
|
long |
getPresolveInclusionWorkLimit()
A few presolve operations involve detecting constraints included in other
constraint.
|
double |
getPresolveProbingDeterministicTimeLimit()
optional double presolve_probing_deterministic_time_limit = 57 [default = 30]; |
int |
getPresolveSubstitutionLevel()
How much substitution (also called free variable aggregation in MIP
litterature) should we perform at presolve.
|
boolean |
getPresolveUseBva()
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
|
double |
getProbingDeterministicTimeLimit()
The maximum "deterministic" time limit to spend in probing.
|
int |
getProbingNumCombinationsLimit()
How many combinations of pairs or triplets of variables we want to scan.
|
double |
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.
|
long |
getPseudoCostReliabilityThreshold()
The solver ignores the pseudo costs of variables with number of recordings
less than this threshold.
|
boolean |
getPushAllTasksTowardStart()
Experimental code: specify if the objective pushes all tasks toward the
start of the schedule.
|
double |
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.
|
boolean |
getRandomizeSearch()
Randomize fixed search.
|
double |
getRandomPolarityRatio()
The proportion of polarity chosen at random.
|
int |
getRandomSeed()
At the beginning of each solve, the random number generator used in some
part of the solver is reinitialized to this seed.
|
double |
getRelativeGapLimit()
optional double relative_gap_limit = 160 [default = 0]; |
boolean |
getRepairHint()
If true, the solver tries to repair the solution given in the hint.
|
SatParameters.RestartAlgorithm |
getRestartAlgorithms(int index)
The restart strategies will change each time the strategy_counter is
increased.
|
int |
getRestartAlgorithmsCount()
The restart strategies will change each time the strategy_counter is
increased.
|
java.util.List<SatParameters.RestartAlgorithm> |
getRestartAlgorithmsList()
The restart strategies will change each time the strategy_counter is
increased.
|
double |
getRestartDlAverageRatio()
In the moving average restart algorithms, a restart is triggered if the
window average times this ratio is greater that the global average.
|
double |
getRestartLbdAverageRatio()
optional double restart_lbd_average_ratio = 71 [default = 1]; |
int |
getRestartPeriod()
Restart period for the FIXED_RESTART strategy.
|
int |
getRestartRunningWindowSize()
Size of the window for the moving average restarts.
|
int |
getRootLpIterations()
Even at the root node, we do not want to spend too much time on the LP if
it is "difficult".
|
SatParameters.SearchBranching |
getSearchBranching()
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH]; |
long |
getSearchRandomVariablePoolSize()
Search randomization will collect the top
'search_random_variable_pool_size' valued variables, and pick one randomly.
|
boolean |
getShareBinaryClauses()
Allows sharing of new learned binary clause between workers.
|
int |
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.
|
int |
getSharedTreeNumWorkers()
Enables experimental workstealing-like shared tree search.
|
double |
getSharedTreeOpenLeavesPerWorker()
How many open leaf nodes should the shared tree maintain per worker.
|
SatParameters.SharedTreeSplitStrategy |
getSharedTreeSplitStrategy()
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO]; |
int |
getSharedTreeWorkerMinRestartsPerSubtree()
Minimum number of restarts before a worker will replace a subtree
that looks "bad" based on the average LBD of learned clauses.
|
double |
getSharedTreeWorkerObjectiveSplitProbability()
After their assigned prefix, shared tree workers will branch on the
objective with this probability.
|
boolean |
getShareLevelZeroBounds()
Allows sharing of the bounds of modified variables at level 0.
|
boolean |
getShareObjectiveBounds()
Allows objective sharing between workers.
|
double |
getShavingSearchDeterministicTime()
Specifies the amount of deterministic time spent of each try at shaving a
bound in the shaving search.
|
int |
getSolutionPoolSize()
Size of the top-n different solutions kept by the solver.
|
boolean |
getStopAfterFirstSolution()
For an optimization problem, stop the solver as soon as we have a solution.
|
boolean |
getStopAfterPresolve()
Mainly used when improving the presolver.
|
boolean |
getStopAfterRootPropagation()
optional bool stop_after_root_propagation = 252 [default = false]; |
double |
getStrategyChangeIncreaseRatio()
The parameter num_conflicts_before_strategy_changes is increased by that
much after each strategy change.
|
SatParameters |
getSubsolverParams(int index)
It is possible to specify additional subsolver configuration.
|
SatParameters.Builder |
getSubsolverParamsBuilder(int index)
It is possible to specify additional subsolver configuration.
|
java.util.List<SatParameters.Builder> |
getSubsolverParamsBuilderList()
It is possible to specify additional subsolver configuration.
|
int |
getSubsolverParamsCount()
It is possible to specify additional subsolver configuration.
|
java.util.List<SatParameters> |
getSubsolverParamsList()
It is possible to specify additional subsolver configuration.
|
SatParametersOrBuilder |
getSubsolverParamsOrBuilder(int index)
It is possible to specify additional subsolver configuration.
|
java.util.List<? extends SatParametersOrBuilder> |
getSubsolverParamsOrBuilderList()
It is possible to specify additional subsolver configuration.
|
java.lang.String |
getSubsolvers(int index)
In multi-thread, the solver can be mainly seen as a portfolio of solvers
with different parameters.
|
com.google.protobuf.ByteString |
getSubsolversBytes(int index)
In multi-thread, the solver can be mainly seen as a portfolio of solvers
with different parameters.
|
int |
getSubsolversCount()
In multi-thread, the solver can be mainly seen as a portfolio of solvers
with different parameters.
|
com.google.protobuf.ProtocolStringList |
getSubsolversList()
In multi-thread, the solver can be mainly seen as a portfolio of solvers
with different parameters.
|
boolean |
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.
|
int |
getSymmetryLevel()
Whether we try to automatically detect the symmetries in a model and
exploit them.
|
int |
getTableCompressionLevel()
How much we try to "compress" a table constraint.
|
boolean |
getTestFeasibilityJump()
Disable every other type of subsolver, setting this turns CP-SAT into a
pure local-search solver.
|
boolean |
getUseAbslRandom()
optional bool use_absl_random = 180 [default = false]; |
boolean |
getUseAreaEnergeticReasoningInNoOverlap2D()
When this is true, the no_overlap_2d constraint is reinforced with
an energetic reasoning that uses an area-based energy.
|
boolean |
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.
|
boolean |
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.
|
boolean |
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.
|
boolean |
getUseDualSchedulingHeuristics()
When set, it activates a few scheduling parameters to improve the lower
bound of scheduling problems.
|
boolean |
getUseDynamicPrecedenceInCumulative()
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false]; |
boolean |
getUseDynamicPrecedenceInDisjunctive()
Whether we try to branch on decision "interval A before interval B" rather
than on intervals bounds.
|
boolean |
getUseEnergeticReasoningInNoOverlap2D()
When this is true, the no_overlap_2d constraint is reinforced with
energetic reasoning.
|
boolean |
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.
|
boolean |
getUseExactLpReason()
The solver usually exploit the LP relaxation of a model.
|
boolean |
getUseExtendedProbing()
Use extended probing (probe bool_or, at_most_one, exactly_one).
|
boolean |
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.
|
boolean |
getUseFeasibilityPump()
Adds a feasibility pump subsolver along with lns subsolvers.
|
boolean |
getUseHardPrecedencesInCumulative()
If true, detect and create constraint for integer variable that are "after"
a set of intervals in the same cumulative constraint.
|
boolean |
getUseImpliedBounds()
Stores and exploits "implied-bounds" in the solver.
|
boolean |
getUseLbRelaxLns()
Turns on neighborhood generator based on local branching LP.
|
boolean |
getUseLns()
Testing parameters used to disable all lns workers.
|
boolean |
getUseLnsOnly()
Experimental parameters to disable everything but lns.
|
boolean |
getUseObjectiveLbSearch()
If true, search will search in ascending max objective value (when
minimizing) starting from the lower bound of the objective.
|
boolean |
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.
|
boolean |
getUseOptimizationHints()
For an optimization problem, whether we follow some hints in order to find
a better first solution.
|
boolean |
getUseOptionalVariables()
If true, we automatically detect variables whose constraint are always
enforced by the same literal and we mark them as optional.
|
boolean |
getUseOverloadCheckerInCumulative()
When this is true, the cumulative constraint is reinforced with overload
checking, i.e., an additional level of reasoning based on energy.
|
boolean |
getUsePbResolution()
Whether to use pseudo-Boolean resolution to analyze a conflict.
|
boolean |
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().
|
boolean |
getUsePrecedencesInDisjunctiveConstraint()
When this is true, then a disjunctive constraint will try to use the
precedence relations between time intervals to propagate their bounds
further.
|
boolean |
getUseProbingSearch()
If true, search will continuously probe Boolean variables, and integer
variable bounds.
|
boolean |
getUseRinsLns()
Turns on relaxation induced neighborhood generator.
|
boolean |
getUseSatInprocessing()
Enable or disable "inprocessing" which is some SAT presolving done at
each restart to the root level.
|
boolean |
getUseSharedTreeSearch()
Set on shared subtree workers.
|
boolean |
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.
|
boolean |
getUseStrongPropagationInDisjunctive()
Enable stronger and more expensive propagation on no_overlap constraint.
|
boolean |
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.
|
boolean |
getUseTimetablingInNoOverlap2D()
When this is true, the no_overlap_2d constraint is reinforced with
propagators from the cumulative constraints.
|
double |
getVariableActivityDecay()
Each time a conflict is found, the activities of some variables are
increased by one.
|
double |
getViolationLsCompoundMoveProbability()
Probability of using compound move search each restart.
|
int |
getViolationLsPerturbationPeriod()
How long violation_ls should wait before perturbating a solution.
|
boolean |
hasAbsoluteGapLimit()
Stop the search when the gap between the best feasible objective (O) and
our best objective bound (B) is smaller than a limit.
|
boolean |
hasAddCgCuts()
Whether we generate and add Chvatal-Gomory cuts to the LP at root node.
|
boolean |
hasAddCliqueCuts()
Whether we generate clique cuts from the binary implication graph.
|
boolean |
hasAddLinMaxCuts()
For the lin max constraints, generates the cuts described in "Strong
mixed-integer programming formulations for trained neural networks" by Ross
Anderson et.
|
boolean |
hasAddLpConstraintsLazily()
If true, we start by an empty LP, and only add constraints not satisfied
by the current LP solution batch by batch.
|
boolean |
hasAddMirCuts()
Whether we generate MIR cuts at root node.
|
boolean |
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.
|
boolean |
hasAddRltCuts()
Whether we generate RLT cuts.
|
boolean |
hasAddZeroHalfCuts()
Whether we generate Zero-Half cuts at root node.
|
boolean |
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.
|
boolean |
hasAtMostOneMaxExpansionSize()
All at_most_one constraints with a size <= param will be replaced by a
quadratic number of binary implications.
|
boolean |
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.
|
boolean |
hasBinaryMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST]; |
boolean |
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.
|
boolean |
hasBlockingRestartMultiplier()
optional double blocking_restart_multiplier = 66 [default = 1.4]; |
boolean |
hasBlockingRestartWindowSize()
optional int32 blocking_restart_window_size = 65 [default = 5000]; |
boolean |
hasBooleanEncodingLevel()
A non-negative level indicating how much we should try to fully encode
Integer variables as Boolean.
|
boolean |
hasCatchSigintSignal()
Indicates if the CP-SAT layer should catch Control-C (SIGINT) signals
when calling solve.
|
boolean |
hasClauseActivityDecay()
Clause activity parameters (same effect as the one on the variables).
|
boolean |
hasClauseCleanupLbdBound()
All the clauses with a LBD (literal blocks distance) lower or equal to this
parameters will always be kept.
|
boolean |
hasClauseCleanupOrdering()
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY]; |
boolean |
hasClauseCleanupPeriod()
Trigger a cleanup when this number of "deletable" clauses is learned.
|
boolean |
hasClauseCleanupProtection()
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE]; |
boolean |
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.
|
boolean |
hasClauseCleanupTarget()
During a cleanup, we will always keep that number of "deletable" clauses.
|
boolean |
hasConvertIntervals()
Temporary flag util the feature is more mature.
|
boolean |
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.
|
boolean |
hasCountAssumptionLevelsInLbd()
Whether or not the assumption levels are taken into account during the LBD
computation.
|
boolean |
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.
|
boolean |
hasCpModelPresolve()
Whether we presolve the cp_model before solving it.
|
boolean |
hasCpModelProbingLevel()
How much effort do we spend on probing.
|
boolean |
hasCpModelUseSatPresolve()
Whether we also use the sat presolve when cp_model_presolve is true.
|
boolean |
hasCutActiveCountDecay()
optional double cut_active_count_decay = 156 [default = 0.8]; |
boolean |
hasCutCleanupTarget()
Target number of constraints to remove during cleanup.
|
boolean |
hasCutLevel()
Control the global cut effort.
|
boolean |
hasCutMaxActiveCountValue()
These parameters are similar to sat clause management activity parameters.
|
boolean |
hasDebugCrashOnBadHint()
Crash if we do not manage to complete the hint into a full solution.
|
boolean |
hasDebugMaxNumPresolveOperations()
If positive, try to stop just after that many presolve rules have been
applied.
|
boolean |
hasDebugPostsolveWithFullSolver()
We have two different postsolve code.
|
boolean |
hasDefaultRestartAlgorithms()
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"]; |
boolean |
hasDetectLinearizedProduct()
Infer products of Boolean or of Boolean time IntegerVariable from the
linear constrainst in the problem.
|
boolean |
hasDetectTableWithCost()
If true, we detect variable that are unique to a table constraint and only
there to encode a cost on each tuple.
|
boolean |
hasDisableConstraintExpansion()
If true, it disable all constraint expansion.
|
boolean |
hasDiversifyLnsParams()
If true, registers more lns subsolvers with different parameters.
|
boolean |
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.
|
boolean |
hasEnumerateAllSolutions()
Whether we enumerate all solutions of a problem without objective.
|
boolean |
hasExpandAlldiffConstraints()
If true, expand all_different constraints that are not permutations.
|
boolean |
hasExpandReservoirConstraints()
If true, expand the reservoir constraints by creating booleans for all
possible precedences between event and encoding the constraint.
|
boolean |
hasExploitAllLpSolution()
If true and the Lp relaxation of the problem has a solution, try to exploit
it.
|
boolean |
hasExploitAllPrecedences()
optional bool exploit_all_precedences = 220 [default = false]; |
boolean |
hasExploitBestSolution()
When branching on a variable, follow the last best solution value.
|
boolean |
hasExploitIntegerLpSolution()
If true and the Lp relaxation of the problem has an integer optimal
solution, try to exploit it.
|
boolean |
hasExploitObjective()
When branching an a variable that directly affect the objective,
branch on the value that lead to the best objective first.
|
boolean |
hasExploitRelaxationSolution()
When branching on a variable, follow the last best relaxation solution
value.
|
boolean |
hasFeasibilityJumpDecay()
On each restart, we randomly choose if we use decay (with this parameter)
or no decay.
|
boolean |
hasFeasibilityJumpEnableRestarts()
When stagnating, feasibility jump will either restart from a default
solution (with some possible randomization), or randomly pertubate the
current solution.
|
boolean |
hasFeasibilityJumpLinearizationLevel()
How much do we linearize the problem in the local search code.
|
boolean |
hasFeasibilityJumpMaxExpandedConstraintSize()
Maximum size of no_overlap or no_overlap_2d constraint for a quadratic
expansion.
|
boolean |
hasFeasibilityJumpRestartFactor()
This is a factor that directly influence the work before each restart.
|
boolean |
hasFeasibilityJumpVarPerburbationRangeRatio()
Max distance between the default value and the pertubated value relative to
the range of the domain of the variable.
|
boolean |
hasFeasibilityJumpVarRandomizationProbability()
Probability for a variable to have a non default value upon restarts or
perturbations.
|
boolean |
hasFillAdditionalSolutionsInResponse()
If true, the final response addition_solutions field will be filled with
all solutions from our solutions pool.
|
boolean |
hasFillTightenedDomainsInResponse()
If true, add information about the derived variable domains to the
CpSolverResponse.
|
boolean |
hasFindBigLinearOverlap()
Try to find large "rectangle" in the linear constraint matrix with
identical lines.
|
boolean |
hasFindMultipleCores()
Whether we try to find more independent cores for a given set of
assumptions in the core based max-SAT algorithms.
|
boolean |
hasFixVariablesToTheirHintedValue()
If true, variables appearing in the solution hints will be fixed to their
hinted value.
|
boolean |
hasFpRounding()
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED]; |
boolean |
hasGlucoseDecayIncrement()
optional double glucose_decay_increment = 23 [default = 0.01]; |
boolean |
hasGlucoseDecayIncrementPeriod()
optional int32 glucose_decay_increment_period = 24 [default = 5000]; |
boolean |
hasGlucoseMaxDecay()
The activity starts at 0.8 and increment by 0.01 every 5000 conflicts until
0.95.
|
boolean |
hasHintConflictLimit()
Conflict limit used in the phase that exploit the solution hint.
|
boolean |
hasIgnoreNames()
If true, we don't keep names in our internal copy of the user given model.
|
boolean |
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.
|
boolean |
hasInitialPolarity()
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE]; |
boolean |
hasInitialVariablesActivity()
The initial value of the variables activity.
|
boolean |
hasInprocessingDtimeRatio()
Proportion of deterministic time we should spend on inprocessing.
|
boolean |
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.
|
boolean |
hasInprocessingProbingDtime()
The amount of dtime we should spend on probing for each inprocessing round.
|
boolean |
hasInstantiateAllVariables()
If true, the solver will add a default integer branching strategy to the
already defined search strategy.
|
boolean |
hasInterleaveBatchSize()
optional int32 interleave_batch_size = 134 [default = 0]; |
boolean |
hasInterleaveSearch()
Experimental.
|
boolean |
hasKeepAllFeasibleSolutionsInPresolve()
If true, we disable the presolve reductions that remove feasible solutions
from the search space.
|
boolean |
hasLinearizationLevel()
A non-negative level indicating the type of constraints we consider in the
LP relaxation.
|
boolean |
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.
|
boolean |
hasLogPrefix()
Add a prefix to all logs.
|
boolean |
hasLogSearchProgress()
Whether the solver should log the search progress.
|
boolean |
hasLogSubsolverStatistics()
Whether the solver should display per sub-solver search statistics.
|
boolean |
hasLogToResponse()
Log to response proto.
|
boolean |
hasLogToStdout()
Log to stdout.
|
boolean |
hasLpDualTolerance()
optional double lp_dual_tolerance = 267 [default = 1e-07]; |
boolean |
hasLpPrimalTolerance()
The internal LP tolerances used by CP-SAT.
|
boolean |
hasMaxAllDiffCutSize()
Cut generator for all diffs can add too many cuts for large all_diff
constraints.
|
boolean |
hasMaxClauseActivityValue()
optional double max_clause_activity_value = 18 [default = 1e+20]; |
boolean |
hasMaxConsecutiveInactiveCount()
If a constraint/cut in LP is not active for that many consecutive OPTIMAL
solves, remove it from the LP.
|
boolean |
hasMaxCutRoundsAtLevelZero()
Max number of time we perform cut generation and resolve the LP at level 0.
|
boolean |
hasMaxDeterministicTime()
Maximum time allowed in deterministic time to solve a problem.
|
boolean |
hasMaxDomainSizeWhenEncodingEqNeqConstraints()
When loading a*x + b*y ==/!= c when x and y are both fully encoded.
|
boolean |
hasMaxIntegerRoundingScaling()
In the integer rounding procedure used for MIR and Gomory cut, the maximum
"scaling" we use (must be positive).
|
boolean |
hasMaxLinMaxSizeForExpansion()
If the number of expressions in the lin_max is less that the max size
parameter, model expansion replaces target = max(xi) by linear constraint
with the introduction of new booleans bi such that bi => target == xi.
|
boolean |
hasMaxMemoryInMb()
Maximum memory allowed for the whole thread containing the solver.
|
boolean |
hasMaxNumberOfConflicts()
Maximum number of conflicts allowed to solve a problem.
|
boolean |
hasMaxNumCuts()
The limit on the number of cuts in our cut pool.
|
boolean |
hasMaxNumIntervalsForTimetableEdgeFinding()
Max number of intervals for the timetable_edge_finding algorithm to
propagate.
|
boolean |
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.
|
boolean |
hasMaxPresolveIterations()
In case of large reduction in a presolve iteration, we perform multiple
presolve iterations.
|
boolean |
hasMaxSatAssumptionOrder()
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER]; |
boolean |
hasMaxSatReverseAssumptionOrder()
If true, adds the assumption in the reverse order of the one defined by
max_sat_assumption_order.
|
boolean |
hasMaxSatStratification()
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT]; |
boolean |
hasMaxSizeToCreatePrecedenceLiteralsInDisjunctive()
Create one literal for each disjunction of two pairs of tasks.
|
boolean |
hasMaxTimeInSeconds()
Maximum time allowed in seconds to solve a problem.
|
boolean |
hasMaxVariableActivityValue()
optional double max_variable_activity_value = 16 [default = 1e+100]; |
boolean |
hasMergeAtMostOneWorkLimit()
optional double merge_at_most_one_work_limit = 146 [default = 100000000]; |
boolean |
hasMergeNoOverlapWorkLimit()
During presolve, we use a maximum clique heuristic to merge together
no-overlap constraints or at most one constraints.
|
boolean |
hasMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE]; |
boolean |
hasMinimizeReductionDuringPbResolution()
A different algorithm during PB resolution.
|
boolean |
hasMinNumLnsWorkers()
Obsolete parameter.
|
boolean |
hasMinOrthogonalityForLpConstraints()
While adding constraints, skip the constraints which have orthogonality
less than 'min_orthogonality_for_lp_constraints' with already added
constraints during current call.
|
boolean |
hasMipAutomaticallyScaleVariables()
If true, some continuous variable might be automatically scaled.
|
boolean |
hasMipCheckPrecision()
As explained in mip_precision and mip_max_activity_exponent, we cannot
always reach the wanted precision during scaling.
|
boolean |
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.
|
boolean |
hasMipDropTolerance()
Any value in the input mip with a magnitude lower than this will be set to
zero.
|
boolean |
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.
|
boolean |
hasMipMaxBound()
We need to bound the maximum magnitude of the variables for CP-SAT, and
that is the bound we use.
|
boolean |
hasMipMaxValidMagnitude()
Any finite values in the input MIP must be below this threshold, otherwise
the model will be reported invalid.
|
boolean |
hasMipPresolveLevel()
When solving a MIP, we do some basic floating point presolving before
scaling the problem to integer to be handled by CP-SAT.
|
boolean |
hasMipScaleLargeDomain()
If this is false, then mip_var_scaling is only applied to variables with
"small" domain.
|
boolean |
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.
|
boolean |
hasMipVarScaling()
All continuous variable of the problem will be multiplied by this factor.
|
boolean |
hasMipWantedPrecision()
When scaling constraint with double coefficients to integer coefficients,
we will multiply by a power of 2 and round the coefficients.
|
boolean |
hasName()
In some context, like in a portfolio of search, it makes sense to name a
given parameters set for logging purpose.
|
boolean |
hasNewConstraintsBatchSize()
Add that many lazy constraints (or cuts) at once in the LP.
|
boolean |
hasNewLinearPropagation()
The new linear propagation code treat all constraints at once and use
an adaptation of Bellman-Ford-Tarjan to propagate constraint in a smarter
order and potentially detect propagation cycle earlier.
|
boolean |
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.
|
boolean |
hasNumSearchWorkers()
optional int32 num_search_workers = 100 [default = 0]; |
boolean |
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.
|
boolean |
hasNumWorkers()
Specify the number of parallel workers (i.e.
|
boolean |
hasOnlyAddCutsAtLevelZero()
For the cut that can be generated at any level, this control if we only
try to generate them at the root node.
|
boolean |
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.
|
boolean |
hasOptimizeWithCore()
The default optimization method is a simple "linear scan", each time trying
to find a better solution than the previous one.
|
boolean |
hasOptimizeWithLbTreeSearch()
Do a more conventional tree search (by opposition to SAT based one) where
we keep all the explored node in a tree.
|
boolean |
hasOptimizeWithMaxHs()
This has no effect if optimize_with_core is false.
|
boolean |
hasPbCleanupIncrement()
Same as for the clauses, but for the learned pseudo-Boolean constraints.
|
boolean |
hasPbCleanupRatio()
optional double pb_cleanup_ratio = 47 [default = 0.5]; |
boolean |
hasPermutePresolveConstraintOrder()
optional bool permute_presolve_constraint_order = 179 [default = false]; |
boolean |
hasPermuteVariableRandomly()
This is mainly here to test the solver variability.
|
boolean |
hasPolarityRephaseIncrement()
If non-zero, then we change the polarity heuristic after that many number
of conflicts in an arithmetically increasing fashion.
|
boolean |
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.
|
boolean |
hasPreferredVariableOrder()
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER]; |
boolean |
hasPresolveBlockedClause()
Whether we use an heuristic to detect some basic case of blocked clause
in the SAT presolve.
|
boolean |
hasPresolveBvaThreshold()
Apply Bounded Variable Addition (BVA) if the number of clauses is reduced
by stricly more than this threshold.
|
boolean |
hasPresolveBveClauseWeight()
During presolve, we apply BVE only if this weight times the number of
clauses plus the number of clause literals is not increased.
|
boolean |
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.
|
boolean |
hasPresolveExtractIntegerEnforcement()
If true, we will extract from linear constraints, enforcement literals of
the form "integer variable at bound => simplified constraint".
|
boolean |
hasPresolveInclusionWorkLimit()
A few presolve operations involve detecting constraints included in other
constraint.
|
boolean |
hasPresolveProbingDeterministicTimeLimit()
optional double presolve_probing_deterministic_time_limit = 57 [default = 30]; |
boolean |
hasPresolveSubstitutionLevel()
How much substitution (also called free variable aggregation in MIP
litterature) should we perform at presolve.
|
boolean |
hasPresolveUseBva()
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
|
boolean |
hasProbingDeterministicTimeLimit()
The maximum "deterministic" time limit to spend in probing.
|
boolean |
hasProbingNumCombinationsLimit()
How many combinations of pairs or triplets of variables we want to scan.
|
boolean |
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.
|
boolean |
hasPseudoCostReliabilityThreshold()
The solver ignores the pseudo costs of variables with number of recordings
less than this threshold.
|
boolean |
hasPushAllTasksTowardStart()
Experimental code: specify if the objective pushes all tasks toward the
start of the schedule.
|
boolean |
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.
|
boolean |
hasRandomizeSearch()
Randomize fixed search.
|
boolean |
hasRandomPolarityRatio()
The proportion of polarity chosen at random.
|
boolean |
hasRandomSeed()
At the beginning of each solve, the random number generator used in some
part of the solver is reinitialized to this seed.
|
boolean |
hasRelativeGapLimit()
optional double relative_gap_limit = 160 [default = 0]; |
boolean |
hasRepairHint()
If true, the solver tries to repair the solution given in the hint.
|
boolean |
hasRestartDlAverageRatio()
In the moving average restart algorithms, a restart is triggered if the
window average times this ratio is greater that the global average.
|
boolean |
hasRestartLbdAverageRatio()
optional double restart_lbd_average_ratio = 71 [default = 1]; |
boolean |
hasRestartPeriod()
Restart period for the FIXED_RESTART strategy.
|
boolean |
hasRestartRunningWindowSize()
Size of the window for the moving average restarts.
|
boolean |
hasRootLpIterations()
Even at the root node, we do not want to spend too much time on the LP if
it is "difficult".
|
boolean |
hasSearchBranching()
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH]; |
boolean |
hasSearchRandomVariablePoolSize()
Search randomization will collect the top
'search_random_variable_pool_size' valued variables, and pick one randomly.
|
boolean |
hasShareBinaryClauses()
Allows sharing of new learned binary clause between workers.
|
boolean |
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.
|
boolean |
hasSharedTreeNumWorkers()
Enables experimental workstealing-like shared tree search.
|
boolean |
hasSharedTreeOpenLeavesPerWorker()
How many open leaf nodes should the shared tree maintain per worker.
|
boolean |
hasSharedTreeSplitStrategy()
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO]; |
boolean |
hasSharedTreeWorkerMinRestartsPerSubtree()
Minimum number of restarts before a worker will replace a subtree
that looks "bad" based on the average LBD of learned clauses.
|
boolean |
hasSharedTreeWorkerObjectiveSplitProbability()
After their assigned prefix, shared tree workers will branch on the
objective with this probability.
|
boolean |
hasShareLevelZeroBounds()
Allows sharing of the bounds of modified variables at level 0.
|
boolean |
hasShareObjectiveBounds()
Allows objective sharing between workers.
|
boolean |
hasShavingSearchDeterministicTime()
Specifies the amount of deterministic time spent of each try at shaving a
bound in the shaving search.
|
boolean |
hasSolutionPoolSize()
Size of the top-n different solutions kept by the solver.
|
boolean |
hasStopAfterFirstSolution()
For an optimization problem, stop the solver as soon as we have a solution.
|
boolean |
hasStopAfterPresolve()
Mainly used when improving the presolver.
|
boolean |
hasStopAfterRootPropagation()
optional bool stop_after_root_propagation = 252 [default = false]; |
boolean |
hasStrategyChangeIncreaseRatio()
The parameter num_conflicts_before_strategy_changes is increased by that
much after each strategy change.
|
boolean |
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.
|
boolean |
hasSymmetryLevel()
Whether we try to automatically detect the symmetries in a model and
exploit them.
|
boolean |
hasTableCompressionLevel()
How much we try to "compress" a table constraint.
|
boolean |
hasTestFeasibilityJump()
Disable every other type of subsolver, setting this turns CP-SAT into a
pure local-search solver.
|
boolean |
hasUseAbslRandom()
optional bool use_absl_random = 180 [default = false]; |
boolean |
hasUseAreaEnergeticReasoningInNoOverlap2D()
When this is true, the no_overlap_2d constraint is reinforced with
an energetic reasoning that uses an area-based energy.
|
boolean |
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.
|
boolean |
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.
|
boolean |
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.
|
boolean |
hasUseDualSchedulingHeuristics()
When set, it activates a few scheduling parameters to improve the lower
bound of scheduling problems.
|
boolean |
hasUseDynamicPrecedenceInCumulative()
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false]; |
boolean |
hasUseDynamicPrecedenceInDisjunctive()
Whether we try to branch on decision "interval A before interval B" rather
than on intervals bounds.
|
boolean |
hasUseEnergeticReasoningInNoOverlap2D()
When this is true, the no_overlap_2d constraint is reinforced with
energetic reasoning.
|
boolean |
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.
|
boolean |
hasUseExactLpReason()
The solver usually exploit the LP relaxation of a model.
|
boolean |
hasUseExtendedProbing()
Use extended probing (probe bool_or, at_most_one, exactly_one).
|
boolean |
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.
|
boolean |
hasUseFeasibilityPump()
Adds a feasibility pump subsolver along with lns subsolvers.
|
boolean |
hasUseHardPrecedencesInCumulative()
If true, detect and create constraint for integer variable that are "after"
a set of intervals in the same cumulative constraint.
|
boolean |
hasUseImpliedBounds()
Stores and exploits "implied-bounds" in the solver.
|
boolean |
hasUseLbRelaxLns()
Turns on neighborhood generator based on local branching LP.
|
boolean |
hasUseLns()
Testing parameters used to disable all lns workers.
|
boolean |
hasUseLnsOnly()
Experimental parameters to disable everything but lns.
|
boolean |
hasUseObjectiveLbSearch()
If true, search will search in ascending max objective value (when
minimizing) starting from the lower bound of the objective.
|
boolean |
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.
|
boolean |
hasUseOptimizationHints()
For an optimization problem, whether we follow some hints in order to find
a better first solution.
|
boolean |
hasUseOptionalVariables()
If true, we automatically detect variables whose constraint are always
enforced by the same literal and we mark them as optional.
|
boolean |
hasUseOverloadCheckerInCumulative()
When this is true, the cumulative constraint is reinforced with overload
checking, i.e., an additional level of reasoning based on energy.
|
boolean |
hasUsePbResolution()
Whether to use pseudo-Boolean resolution to analyze a conflict.
|
boolean |
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().
|
boolean |
hasUsePrecedencesInDisjunctiveConstraint()
When this is true, then a disjunctive constraint will try to use the
precedence relations between time intervals to propagate their bounds
further.
|
boolean |
hasUseProbingSearch()
If true, search will continuously probe Boolean variables, and integer
variable bounds.
|
boolean |
hasUseRinsLns()
Turns on relaxation induced neighborhood generator.
|
boolean |
hasUseSatInprocessing()
Enable or disable "inprocessing" which is some SAT presolving done at
each restart to the root level.
|
boolean |
hasUseSharedTreeSearch()
Set on shared subtree workers.
|
boolean |
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.
|
boolean |
hasUseStrongPropagationInDisjunctive()
Enable stronger and more expensive propagation on no_overlap constraint.
|
boolean |
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.
|
boolean |
hasUseTimetablingInNoOverlap2D()
When this is true, the no_overlap_2d constraint is reinforced with
propagators from the cumulative constraints.
|
boolean |
hasVariableActivityDecay()
Each time a conflict is found, the activities of some variables are
increased by one.
|
boolean |
hasViolationLsCompoundMoveProbability()
Probability of using compound move search each restart.
|
boolean |
hasViolationLsPerturbationPeriod()
How long violation_ls should wait before perturbating a solution.
|
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable |
internalGetFieldAccessorTable() |
boolean |
isInitialized() |
SatParameters.Builder |
mergeFrom(com.google.protobuf.CodedInputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
SatParameters.Builder |
mergeFrom(com.google.protobuf.Message other) |
SatParameters.Builder |
mergeFrom(SatParameters other) |
SatParameters.Builder |
removeSubsolverParams(int index)
It is possible to specify additional subsolver configuration.
|
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.
|
SatParameters.Builder |
setAddCgCuts(boolean value)
Whether we generate and add Chvatal-Gomory cuts to the LP at root node.
|
SatParameters.Builder |
setAddCliqueCuts(boolean value)
Whether we generate clique cuts from the binary implication graph.
|
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.
|
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.
|
SatParameters.Builder |
setAddMirCuts(boolean value)
Whether we generate MIR cuts at root node.
|
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.
|
SatParameters.Builder |
setAddRltCuts(boolean value)
Whether we generate RLT cuts.
|
SatParameters.Builder |
setAddZeroHalfCuts(boolean value)
Whether we generate Zero-Half cuts at root node.
|
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.
|
SatParameters.Builder |
setAtMostOneMaxExpansionSize(int value)
All at_most_one constraints with a size <= param will be replaced by a
quadratic number of binary implications.
|
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.
|
SatParameters.Builder |
setBinaryMinimizationAlgorithm(SatParameters.BinaryMinizationAlgorithm value)
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST]; |
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.
|
SatParameters.Builder |
setBlockingRestartMultiplier(double value)
optional double blocking_restart_multiplier = 66 [default = 1.4]; |
SatParameters.Builder |
setBlockingRestartWindowSize(int value)
optional int32 blocking_restart_window_size = 65 [default = 5000]; |
SatParameters.Builder |
setBooleanEncodingLevel(int value)
A non-negative level indicating how much we should try to fully encode
Integer variables as Boolean.
|
SatParameters.Builder |
setCatchSigintSignal(boolean value)
Indicates if the CP-SAT layer should catch Control-C (SIGINT) signals
when calling solve.
|
SatParameters.Builder |
setClauseActivityDecay(double value)
Clause activity parameters (same effect as the one on the variables).
|
SatParameters.Builder |
setClauseCleanupLbdBound(int value)
All the clauses with a LBD (literal blocks distance) lower or equal to this
parameters will always be kept.
|
SatParameters.Builder |
setClauseCleanupOrdering(SatParameters.ClauseOrdering value)
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY]; |
SatParameters.Builder |
setClauseCleanupPeriod(int value)
Trigger a cleanup when this number of "deletable" clauses is learned.
|
SatParameters.Builder |
setClauseCleanupProtection(SatParameters.ClauseProtection value)
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE]; |
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.
|
SatParameters.Builder |
setClauseCleanupTarget(int value)
During a cleanup, we will always keep that number of "deletable" clauses.
|
SatParameters.Builder |
setConvertIntervals(boolean value)
Temporary flag util the feature is more mature.
|
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.
|
SatParameters.Builder |
setCountAssumptionLevelsInLbd(boolean value)
Whether or not the assumption levels are taken into account during the LBD
computation.
|
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.
|
SatParameters.Builder |
setCpModelPresolve(boolean value)
Whether we presolve the cp_model before solving it.
|
SatParameters.Builder |
setCpModelProbingLevel(int value)
How much effort do we spend on probing.
|
SatParameters.Builder |
setCpModelUseSatPresolve(boolean value)
Whether we also use the sat presolve when cp_model_presolve is true.
|
SatParameters.Builder |
setCutActiveCountDecay(double value)
optional double cut_active_count_decay = 156 [default = 0.8]; |
SatParameters.Builder |
setCutCleanupTarget(int value)
Target number of constraints to remove during cleanup.
|
SatParameters.Builder |
setCutLevel(int value)
Control the global cut effort.
|
SatParameters.Builder |
setCutMaxActiveCountValue(double value)
These parameters are similar to sat clause management activity parameters.
|
SatParameters.Builder |
setDebugCrashOnBadHint(boolean value)
Crash if we do not manage to complete the hint into a full solution.
|
SatParameters.Builder |
setDebugMaxNumPresolveOperations(int value)
If positive, try to stop just after that many presolve rules have been
applied.
|
SatParameters.Builder |
setDebugPostsolveWithFullSolver(boolean value)
We have two different postsolve code.
|
SatParameters.Builder |
setDefaultRestartAlgorithms(java.lang.String value)
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"]; |
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"]; |
SatParameters.Builder |
setDetectLinearizedProduct(boolean value)
Infer products of Boolean or of Boolean time IntegerVariable from the
linear constrainst in the problem.
|
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.
|
SatParameters.Builder |
setDisableConstraintExpansion(boolean value)
If true, it disable all constraint expansion.
|
SatParameters.Builder |
setDiversifyLnsParams(boolean value)
If true, registers more lns subsolvers with different parameters.
|
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.
|
SatParameters.Builder |
setEnumerateAllSolutions(boolean value)
Whether we enumerate all solutions of a problem without objective.
|
SatParameters.Builder |
setExpandAlldiffConstraints(boolean value)
If true, expand all_different constraints that are not permutations.
|
SatParameters.Builder |
setExpandReservoirConstraints(boolean value)
If true, expand the reservoir constraints by creating booleans for all
possible precedences between event and encoding the constraint.
|
SatParameters.Builder |
setExploitAllLpSolution(boolean value)
If true and the Lp relaxation of the problem has a solution, try to exploit
it.
|
SatParameters.Builder |
setExploitAllPrecedences(boolean value)
optional bool exploit_all_precedences = 220 [default = false]; |
SatParameters.Builder |
setExploitBestSolution(boolean value)
When branching on a variable, follow the last best solution value.
|
SatParameters.Builder |
setExploitIntegerLpSolution(boolean value)
If true and the Lp relaxation of the problem has an integer optimal
solution, try to exploit it.
|
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.
|
SatParameters.Builder |
setExploitRelaxationSolution(boolean value)
When branching on a variable, follow the last best relaxation solution
value.
|
SatParameters.Builder |
setExtraSubsolvers(int index,
java.lang.String value)
A convenient way to add more workers types.
|
SatParameters.Builder |
setFeasibilityJumpDecay(double value)
On each restart, we randomly choose if we use decay (with this parameter)
or no decay.
|
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.
|
SatParameters.Builder |
setFeasibilityJumpLinearizationLevel(int value)
How much do we linearize the problem in the local search code.
|
SatParameters.Builder |
setFeasibilityJumpMaxExpandedConstraintSize(int value)
Maximum size of no_overlap or no_overlap_2d constraint for a quadratic
expansion.
|
SatParameters.Builder |
setFeasibilityJumpRestartFactor(int value)
This is a factor that directly influence the work before each restart.
|
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.
|
SatParameters.Builder |
setFeasibilityJumpVarRandomizationProbability(double value)
Probability for a variable to have a non default value upon restarts or
perturbations.
|
SatParameters.Builder |
setFillAdditionalSolutionsInResponse(boolean value)
If true, the final response addition_solutions field will be filled with
all solutions from our solutions pool.
|
SatParameters.Builder |
setFillTightenedDomainsInResponse(boolean value)
If true, add information about the derived variable domains to the
CpSolverResponse.
|
SatParameters.Builder |
setFindBigLinearOverlap(boolean value)
Try to find large "rectangle" in the linear constraint matrix with
identical lines.
|
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.
|
SatParameters.Builder |
setFixVariablesToTheirHintedValue(boolean value)
If true, variables appearing in the solution hints will be fixed to their
hinted value.
|
SatParameters.Builder |
setFpRounding(SatParameters.FPRoundingMethod value)
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED]; |
SatParameters.Builder |
setGlucoseDecayIncrement(double value)
optional double glucose_decay_increment = 23 [default = 0.01]; |
SatParameters.Builder |
setGlucoseDecayIncrementPeriod(int value)
optional int32 glucose_decay_increment_period = 24 [default = 5000]; |
SatParameters.Builder |
setGlucoseMaxDecay(double value)
The activity starts at 0.8 and increment by 0.01 every 5000 conflicts until
0.95.
|
SatParameters.Builder |
setHintConflictLimit(int value)
Conflict limit used in the phase that exploit the solution hint.
|
SatParameters.Builder |
setIgnoreNames(boolean value)
If true, we don't keep names in our internal copy of the user given model.
|
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.
|
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.
|
SatParameters.Builder |
setInitialPolarity(SatParameters.Polarity value)
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE]; |
SatParameters.Builder |
setInitialVariablesActivity(double value)
The initial value of the variables activity.
|
SatParameters.Builder |
setInprocessingDtimeRatio(double value)
Proportion of deterministic time we should spend on inprocessing.
|
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.
|
SatParameters.Builder |
setInprocessingProbingDtime(double value)
The amount of dtime we should spend on probing for each inprocessing round.
|
SatParameters.Builder |
setInstantiateAllVariables(boolean value)
If true, the solver will add a default integer branching strategy to the
already defined search strategy.
|
SatParameters.Builder |
setInterleaveBatchSize(int value)
optional int32 interleave_batch_size = 134 [default = 0]; |
SatParameters.Builder |
setInterleaveSearch(boolean value)
Experimental.
|
SatParameters.Builder |
setKeepAllFeasibleSolutionsInPresolve(boolean value)
If true, we disable the presolve reductions that remove feasible solutions
from the search space.
|
SatParameters.Builder |
setLinearizationLevel(int value)
A non-negative level indicating the type of constraints we consider in the
LP relaxation.
|
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.
|
SatParameters.Builder |
setLogPrefix(java.lang.String value)
Add a prefix to all logs.
|
SatParameters.Builder |
setLogPrefixBytes(com.google.protobuf.ByteString value)
Add a prefix to all logs.
|
SatParameters.Builder |
setLogSearchProgress(boolean value)
Whether the solver should log the search progress.
|
SatParameters.Builder |
setLogSubsolverStatistics(boolean value)
Whether the solver should display per sub-solver search statistics.
|
SatParameters.Builder |
setLogToResponse(boolean value)
Log to response proto.
|
SatParameters.Builder |
setLogToStdout(boolean value)
Log to stdout.
|
SatParameters.Builder |
setLpDualTolerance(double value)
optional double lp_dual_tolerance = 267 [default = 1e-07]; |
SatParameters.Builder |
setLpPrimalTolerance(double value)
The internal LP tolerances used by CP-SAT.
|
SatParameters.Builder |
setMaxAllDiffCutSize(int value)
Cut generator for all diffs can add too many cuts for large all_diff
constraints.
|
SatParameters.Builder |
setMaxClauseActivityValue(double value)
optional double max_clause_activity_value = 18 [default = 1e+20]; |
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.
|
SatParameters.Builder |
setMaxCutRoundsAtLevelZero(int value)
Max number of time we perform cut generation and resolve the LP at level 0.
|
SatParameters.Builder |
setMaxDeterministicTime(double value)
Maximum time allowed in deterministic time to solve a problem.
|
SatParameters.Builder |
setMaxDomainSizeWhenEncodingEqNeqConstraints(int value)
When loading a*x + b*y ==/!= c when x and y are both fully encoded.
|
SatParameters.Builder |
setMaxIntegerRoundingScaling(int value)
In the integer rounding procedure used for MIR and Gomory cut, the maximum
"scaling" we use (must be positive).
|
SatParameters.Builder |
setMaxLinMaxSizeForExpansion(int value)
If the number of expressions in the lin_max is less that the max size
parameter, model expansion replaces target = max(xi) by linear constraint
with the introduction of new booleans bi such that bi => target == xi.
|
SatParameters.Builder |
setMaxMemoryInMb(long value)
Maximum memory allowed for the whole thread containing the solver.
|
SatParameters.Builder |
setMaxNumberOfConflicts(long value)
Maximum number of conflicts allowed to solve a problem.
|
SatParameters.Builder |
setMaxNumCuts(int value)
The limit on the number of cuts in our cut pool.
|
SatParameters.Builder |
setMaxNumIntervalsForTimetableEdgeFinding(int value)
Max number of intervals for the timetable_edge_finding algorithm to
propagate.
|
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.
|
SatParameters.Builder |
setMaxPresolveIterations(int value)
In case of large reduction in a presolve iteration, we perform multiple
presolve iterations.
|
SatParameters.Builder |
setMaxSatAssumptionOrder(SatParameters.MaxSatAssumptionOrder value)
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER]; |
SatParameters.Builder |
setMaxSatReverseAssumptionOrder(boolean value)
If true, adds the assumption in the reverse order of the one defined by
max_sat_assumption_order.
|
SatParameters.Builder |
setMaxSatStratification(SatParameters.MaxSatStratificationAlgorithm value)
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT]; |
SatParameters.Builder |
setMaxSizeToCreatePrecedenceLiteralsInDisjunctive(int value)
Create one literal for each disjunction of two pairs of tasks.
|
SatParameters.Builder |
setMaxTimeInSeconds(double value)
Maximum time allowed in seconds to solve a problem.
|
SatParameters.Builder |
setMaxVariableActivityValue(double value)
optional double max_variable_activity_value = 16 [default = 1e+100]; |
SatParameters.Builder |
setMergeAtMostOneWorkLimit(double value)
optional double merge_at_most_one_work_limit = 146 [default = 100000000]; |
SatParameters.Builder |
setMergeNoOverlapWorkLimit(double value)
During presolve, we use a maximum clique heuristic to merge together
no-overlap constraints or at most one constraints.
|
SatParameters.Builder |
setMinimizationAlgorithm(SatParameters.ConflictMinimizationAlgorithm value)
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE]; |
SatParameters.Builder |
setMinimizeReductionDuringPbResolution(boolean value)
A different algorithm during PB resolution.
|
SatParameters.Builder |
setMinNumLnsWorkers(int value)
Obsolete parameter.
|
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.
|
SatParameters.Builder |
setMipAutomaticallyScaleVariables(boolean value)
If true, some continuous variable might be automatically scaled.
|
SatParameters.Builder |
setMipCheckPrecision(double value)
As explained in mip_precision and mip_max_activity_exponent, we cannot
always reach the wanted precision during scaling.
|
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.
|
SatParameters.Builder |
setMipDropTolerance(double value)
Any value in the input mip with a magnitude lower than this will be set to
zero.
|
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.
|
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.
|
SatParameters.Builder |
setMipMaxValidMagnitude(double value)
Any finite values in the input MIP must be below this threshold, otherwise
the model will be reported invalid.
|
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.
|
SatParameters.Builder |
setMipScaleLargeDomain(boolean value)
If this is false, then mip_var_scaling is only applied to variables with
"small" domain.
|
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.
|
SatParameters.Builder |
setMipVarScaling(double value)
All continuous variable of the problem will be multiplied by this factor.
|
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.
|
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.
|
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.
|
SatParameters.Builder |
setNewConstraintsBatchSize(int value)
Add that many lazy constraints (or cuts) at once in the LP.
|
SatParameters.Builder |
setNewLinearPropagation(boolean value)
The new linear propagation code treat all constraints at once and use
an adaptation of Bellman-Ford-Tarjan to propagate constraint in a smarter
order and potentially detect propagation cycle earlier.
|
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.
|
SatParameters.Builder |
setNumSearchWorkers(int value)
optional int32 num_search_workers = 100 [default = 0]; |
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.
|
SatParameters.Builder |
setNumWorkers(int value)
Specify the number of parallel workers (i.e.
|
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.
|
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.
|
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.
|
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.
|
SatParameters.Builder |
setOptimizeWithMaxHs(boolean value)
This has no effect if optimize_with_core is false.
|
SatParameters.Builder |
setPbCleanupIncrement(int value)
Same as for the clauses, but for the learned pseudo-Boolean constraints.
|
SatParameters.Builder |
setPbCleanupRatio(double value)
optional double pb_cleanup_ratio = 47 [default = 0.5]; |
SatParameters.Builder |
setPermutePresolveConstraintOrder(boolean value)
optional bool permute_presolve_constraint_order = 179 [default = false]; |
SatParameters.Builder |
setPermuteVariableRandomly(boolean value)
This is mainly here to test the solver variability.
|
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.
|
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.
|
SatParameters.Builder |
setPreferredVariableOrder(SatParameters.VariableOrder value)
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER]; |
SatParameters.Builder |
setPresolveBlockedClause(boolean value)
Whether we use an heuristic to detect some basic case of blocked clause
in the SAT presolve.
|
SatParameters.Builder |
setPresolveBvaThreshold(int value)
Apply Bounded Variable Addition (BVA) if the number of clauses is reduced
by stricly more than this threshold.
|
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.
|
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.
|
SatParameters.Builder |
setPresolveExtractIntegerEnforcement(boolean value)
If true, we will extract from linear constraints, enforcement literals of
the form "integer variable at bound => simplified constraint".
|
SatParameters.Builder |
setPresolveInclusionWorkLimit(long value)
A few presolve operations involve detecting constraints included in other
constraint.
|
SatParameters.Builder |
setPresolveProbingDeterministicTimeLimit(double value)
optional double presolve_probing_deterministic_time_limit = 57 [default = 30]; |
SatParameters.Builder |
setPresolveSubstitutionLevel(int value)
How much substitution (also called free variable aggregation in MIP
litterature) should we perform at presolve.
|
SatParameters.Builder |
setPresolveUseBva(boolean value)
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
|
SatParameters.Builder |
setProbingDeterministicTimeLimit(double value)
The maximum "deterministic" time limit to spend in probing.
|
SatParameters.Builder |
setProbingNumCombinationsLimit(int value)
How many combinations of pairs or triplets of variables we want to scan.
|
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.
|
SatParameters.Builder |
setPseudoCostReliabilityThreshold(long value)
The solver ignores the pseudo costs of variables with number of recordings
less than this threshold.
|
SatParameters.Builder |
setPushAllTasksTowardStart(boolean value)
Experimental code: specify if the objective pushes all tasks toward the
start of the schedule.
|
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.
|
SatParameters.Builder |
setRandomizeSearch(boolean value)
Randomize fixed search.
|
SatParameters.Builder |
setRandomPolarityRatio(double value)
The proportion of polarity chosen at random.
|
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.
|
SatParameters.Builder |
setRelativeGapLimit(double value)
optional double relative_gap_limit = 160 [default = 0]; |
SatParameters.Builder |
setRepairHint(boolean value)
If true, the solver tries to repair the solution given in the hint.
|
SatParameters.Builder |
setRestartAlgorithms(int index,
SatParameters.RestartAlgorithm value)
The restart strategies will change each time the strategy_counter is
increased.
|
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.
|
SatParameters.Builder |
setRestartLbdAverageRatio(double value)
optional double restart_lbd_average_ratio = 71 [default = 1]; |
SatParameters.Builder |
setRestartPeriod(int value)
Restart period for the FIXED_RESTART strategy.
|
SatParameters.Builder |
setRestartRunningWindowSize(int value)
Size of the window for the moving average restarts.
|
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".
|
SatParameters.Builder |
setSearchBranching(SatParameters.SearchBranching value)
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH]; |
SatParameters.Builder |
setSearchRandomVariablePoolSize(long value)
Search randomization will collect the top
'search_random_variable_pool_size' valued variables, and pick one randomly.
|
SatParameters.Builder |
setShareBinaryClauses(boolean value)
Allows sharing of new learned binary clause between workers.
|
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.
|
SatParameters.Builder |
setSharedTreeNumWorkers(int value)
Enables experimental workstealing-like shared tree search.
|
SatParameters.Builder |
setSharedTreeOpenLeavesPerWorker(double value)
How many open leaf nodes should the shared tree maintain per worker.
|
SatParameters.Builder |
setSharedTreeSplitStrategy(SatParameters.SharedTreeSplitStrategy value)
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO]; |
SatParameters.Builder |
setSharedTreeWorkerMinRestartsPerSubtree(int value)
Minimum number of restarts before a worker will replace a subtree
that looks "bad" based on the average LBD of learned clauses.
|
SatParameters.Builder |
setSharedTreeWorkerObjectiveSplitProbability(double value)
After their assigned prefix, shared tree workers will branch on the
objective with this probability.
|
SatParameters.Builder |
setShareLevelZeroBounds(boolean value)
Allows sharing of the bounds of modified variables at level 0.
|
SatParameters.Builder |
setShareObjectiveBounds(boolean value)
Allows objective sharing between workers.
|
SatParameters.Builder |
setShavingSearchDeterministicTime(double value)
Specifies the amount of deterministic time spent of each try at shaving a
bound in the shaving search.
|
SatParameters.Builder |
setSolutionPoolSize(int value)
Size of the top-n different solutions kept by the solver.
|
SatParameters.Builder |
setStopAfterFirstSolution(boolean value)
For an optimization problem, stop the solver as soon as we have a solution.
|
SatParameters.Builder |
setStopAfterPresolve(boolean value)
Mainly used when improving the presolver.
|
SatParameters.Builder |
setStopAfterRootPropagation(boolean value)
optional bool stop_after_root_propagation = 252 [default = false]; |
SatParameters.Builder |
setStrategyChangeIncreaseRatio(double value)
The parameter num_conflicts_before_strategy_changes is increased by that
much after each strategy change.
|
SatParameters.Builder |
setSubsolverParams(int index,
SatParameters.Builder builderForValue)
It is possible to specify additional subsolver configuration.
|
SatParameters.Builder |
setSubsolverParams(int index,
SatParameters value)
It is possible to specify additional subsolver configuration.
|
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.
|
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.
|
SatParameters.Builder |
setSymmetryLevel(int value)
Whether we try to automatically detect the symmetries in a model and
exploit them.
|
SatParameters.Builder |
setTableCompressionLevel(int value)
How much we try to "compress" a table constraint.
|
SatParameters.Builder |
setTestFeasibilityJump(boolean value)
Disable every other type of subsolver, setting this turns CP-SAT into a
pure local-search solver.
|
SatParameters.Builder |
setUseAbslRandom(boolean value)
optional bool use_absl_random = 180 [default = false]; |
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.
|
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.
|
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.
|
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.
|
SatParameters.Builder |
setUseDualSchedulingHeuristics(boolean value)
When set, it activates a few scheduling parameters to improve the lower
bound of scheduling problems.
|
SatParameters.Builder |
setUseDynamicPrecedenceInCumulative(boolean value)
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false]; |
SatParameters.Builder |
setUseDynamicPrecedenceInDisjunctive(boolean value)
Whether we try to branch on decision "interval A before interval B" rather
than on intervals bounds.
|
SatParameters.Builder |
setUseEnergeticReasoningInNoOverlap2D(boolean value)
When this is true, the no_overlap_2d constraint is reinforced with
energetic reasoning.
|
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.
|
SatParameters.Builder |
setUseExactLpReason(boolean value)
The solver usually exploit the LP relaxation of a model.
|
SatParameters.Builder |
setUseExtendedProbing(boolean value)
Use extended probing (probe bool_or, at_most_one, exactly_one).
|
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.
|
SatParameters.Builder |
setUseFeasibilityPump(boolean value)
Adds a feasibility pump subsolver along with lns subsolvers.
|
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.
|
SatParameters.Builder |
setUseImpliedBounds(boolean value)
Stores and exploits "implied-bounds" in the solver.
|
SatParameters.Builder |
setUseLbRelaxLns(boolean value)
Turns on neighborhood generator based on local branching LP.
|
SatParameters.Builder |
setUseLns(boolean value)
Testing parameters used to disable all lns workers.
|
SatParameters.Builder |
setUseLnsOnly(boolean value)
Experimental parameters to disable everything but lns.
|
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.
|
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.
|
SatParameters.Builder |
setUseOptimizationHints(boolean value)
For an optimization problem, whether we follow some hints in order to find
a better first solution.
|
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.
|
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.
|
SatParameters.Builder |
setUsePbResolution(boolean value)
Whether to use pseudo-Boolean resolution to analyze a conflict.
|
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().
|
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.
|
SatParameters.Builder |
setUseProbingSearch(boolean value)
If true, search will continuously probe Boolean variables, and integer
variable bounds.
|
SatParameters.Builder |
setUseRinsLns(boolean value)
Turns on relaxation induced neighborhood generator.
|
SatParameters.Builder |
setUseSatInprocessing(boolean value)
Enable or disable "inprocessing" which is some SAT presolving done at
each restart to the root level.
|
SatParameters.Builder |
setUseSharedTreeSearch(boolean value)
Set on shared subtree workers.
|
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.
|
SatParameters.Builder |
setUseStrongPropagationInDisjunctive(boolean value)
Enable stronger and more expensive propagation on no_overlap constraint.
|
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.
|
SatParameters.Builder |
setUseTimetablingInNoOverlap2D(boolean value)
When this is true, the no_overlap_2d constraint is reinforced with
propagators from the cumulative constraints.
|
SatParameters.Builder |
setVariableActivityDecay(double value)
Each time a conflict is found, the activities of some variables are
increased by one.
|
SatParameters.Builder |
setViolationLsCompoundMoveProbability(double value)
Probability of using compound move search each restart.
|
SatParameters.Builder |
setViolationLsPerturbationPeriod(int value)
How long violation_ls should wait before perturbating a solution.
|
addRepeatedField, clearField, clearOneof, clone, getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMapFieldReflection, internalGetMutableMapField, internalGetMutableMapFieldReflection, isClean, markClean, mergeUnknownFields, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setField, setRepeatedField, setUnknownFields, setUnknownFieldSetBuilder, setUnknownFieldsProto3findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringaddAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, newUninitializedMessageExceptionequals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitpublic static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessage.Builder<SatParameters.Builder>public SatParameters.Builder clear()
clear in interface com.google.protobuf.Message.Builderclear in interface com.google.protobuf.MessageLite.Builderclear in class com.google.protobuf.GeneratedMessage.Builder<SatParameters.Builder>public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
getDescriptorForType in interface com.google.protobuf.Message.BuildergetDescriptorForType in interface com.google.protobuf.MessageOrBuildergetDescriptorForType in class com.google.protobuf.GeneratedMessage.Builder<SatParameters.Builder>public SatParameters getDefaultInstanceForType()
getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuildergetDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilderpublic SatParameters build()
build in interface com.google.protobuf.Message.Builderbuild in interface com.google.protobuf.MessageLite.Builderpublic SatParameters buildPartial()
buildPartial in interface com.google.protobuf.Message.BuilderbuildPartial in interface com.google.protobuf.MessageLite.Builderpublic SatParameters.Builder mergeFrom(com.google.protobuf.Message other)
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<SatParameters.Builder>public SatParameters.Builder mergeFrom(SatParameters other)
public final boolean isInitialized()
isInitialized in interface com.google.protobuf.MessageLiteOrBuilderisInitialized in class com.google.protobuf.GeneratedMessage.Builder<SatParameters.Builder>public SatParameters.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws java.io.IOException
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in interface com.google.protobuf.MessageLite.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<SatParameters.Builder>java.io.IOExceptionpublic boolean 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 = ""];hasName in interface SatParametersOrBuilderpublic java.lang.String 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 = ""];getName in interface SatParametersOrBuilderpublic com.google.protobuf.ByteString 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 = ""];getNameBytes in interface SatParametersOrBuilderpublic 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.public 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 = ""];public 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.public boolean hasPreferredVariableOrder()
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];hasPreferredVariableOrder in interface SatParametersOrBuilderpublic SatParameters.VariableOrder getPreferredVariableOrder()
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];getPreferredVariableOrder in interface SatParametersOrBuilderpublic SatParameters.Builder setPreferredVariableOrder(SatParameters.VariableOrder value)
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];value - The preferredVariableOrder to set.public SatParameters.Builder clearPreferredVariableOrder()
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];public boolean hasInitialPolarity()
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];hasInitialPolarity in interface SatParametersOrBuilderpublic SatParameters.Polarity getInitialPolarity()
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];getInitialPolarity in interface SatParametersOrBuilderpublic SatParameters.Builder setInitialPolarity(SatParameters.Polarity value)
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];value - The initialPolarity to set.public SatParameters.Builder clearInitialPolarity()
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];public boolean 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];hasUsePhaseSaving in interface SatParametersOrBuilderpublic boolean 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];getUsePhaseSaving in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasPolarityRephaseIncrement in interface SatParametersOrBuilderpublic int 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];getPolarityRephaseIncrement in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasRandomPolarityRatio in interface SatParametersOrBuilderpublic double 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];getRandomPolarityRatio in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasRandomBranchesRatio in interface SatParametersOrBuilderpublic double 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];getRandomBranchesRatio in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseErwaHeuristic in interface SatParametersOrBuilderpublic boolean 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];getUseErwaHeuristic in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasInitialVariablesActivity in interface SatParametersOrBuilderpublic double 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];getInitialVariablesActivity in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAlsoBumpVariablesInConflictReasons in interface SatParametersOrBuilderpublic boolean 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];getAlsoBumpVariablesInConflictReasons in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];hasMinimizationAlgorithm in interface SatParametersOrBuilderpublic SatParameters.ConflictMinimizationAlgorithm getMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];getMinimizationAlgorithm in interface SatParametersOrBuilderpublic SatParameters.Builder setMinimizationAlgorithm(SatParameters.ConflictMinimizationAlgorithm value)
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];value - The minimizationAlgorithm to set.public SatParameters.Builder clearMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];public boolean hasBinaryMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];hasBinaryMinimizationAlgorithm in interface SatParametersOrBuilderpublic SatParameters.BinaryMinizationAlgorithm getBinaryMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];getBinaryMinimizationAlgorithm in interface SatParametersOrBuilderpublic SatParameters.Builder setBinaryMinimizationAlgorithm(SatParameters.BinaryMinizationAlgorithm value)
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];value - The binaryMinimizationAlgorithm to set.public SatParameters.Builder clearBinaryMinimizationAlgorithm()
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];public boolean 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];hasSubsumptionDuringConflictAnalysis in interface SatParametersOrBuilderpublic boolean 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];getSubsumptionDuringConflictAnalysis in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasClauseCleanupPeriod()
Trigger a cleanup when this number of "deletable" clauses is learned.
optional int32 clause_cleanup_period = 11 [default = 10000];hasClauseCleanupPeriod in interface SatParametersOrBuilderpublic int getClauseCleanupPeriod()
Trigger a cleanup when this number of "deletable" clauses is learned.
optional int32 clause_cleanup_period = 11 [default = 10000];getClauseCleanupPeriod in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearClauseCleanupPeriod()
Trigger a cleanup when this number of "deletable" clauses is learned.
optional int32 clause_cleanup_period = 11 [default = 10000];public boolean 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];hasClauseCleanupTarget in interface SatParametersOrBuilderpublic int 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];getClauseCleanupTarget in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasClauseCleanupRatio in interface SatParametersOrBuilderpublic double 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];getClauseCleanupRatio in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasClauseCleanupProtection()
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];hasClauseCleanupProtection in interface SatParametersOrBuilderpublic SatParameters.ClauseProtection getClauseCleanupProtection()
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];getClauseCleanupProtection in interface SatParametersOrBuilderpublic SatParameters.Builder setClauseCleanupProtection(SatParameters.ClauseProtection value)
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];value - The clauseCleanupProtection to set.public SatParameters.Builder clearClauseCleanupProtection()
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];public boolean 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];hasClauseCleanupLbdBound in interface SatParametersOrBuilderpublic int 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];getClauseCleanupLbdBound in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasClauseCleanupOrdering()
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];hasClauseCleanupOrdering in interface SatParametersOrBuilderpublic SatParameters.ClauseOrdering getClauseCleanupOrdering()
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];getClauseCleanupOrdering in interface SatParametersOrBuilderpublic SatParameters.Builder setClauseCleanupOrdering(SatParameters.ClauseOrdering value)
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];value - The clauseCleanupOrdering to set.public SatParameters.Builder clearClauseCleanupOrdering()
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];public boolean hasPbCleanupIncrement()
Same as for the clauses, but for the learned pseudo-Boolean constraints.
optional int32 pb_cleanup_increment = 46 [default = 200];hasPbCleanupIncrement in interface SatParametersOrBuilderpublic int getPbCleanupIncrement()
Same as for the clauses, but for the learned pseudo-Boolean constraints.
optional int32 pb_cleanup_increment = 46 [default = 200];getPbCleanupIncrement in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearPbCleanupIncrement()
Same as for the clauses, but for the learned pseudo-Boolean constraints.
optional int32 pb_cleanup_increment = 46 [default = 200];public boolean hasPbCleanupRatio()
optional double pb_cleanup_ratio = 47 [default = 0.5];hasPbCleanupRatio in interface SatParametersOrBuilderpublic double getPbCleanupRatio()
optional double pb_cleanup_ratio = 47 [default = 0.5];getPbCleanupRatio in interface SatParametersOrBuilderpublic SatParameters.Builder setPbCleanupRatio(double value)
optional double pb_cleanup_ratio = 47 [default = 0.5];value - The pbCleanupRatio to set.public SatParameters.Builder clearPbCleanupRatio()
optional double pb_cleanup_ratio = 47 [default = 0.5];public boolean 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];hasVariableActivityDecay in interface SatParametersOrBuilderpublic double 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];getVariableActivityDecay in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasMaxVariableActivityValue()
optional double max_variable_activity_value = 16 [default = 1e+100];hasMaxVariableActivityValue in interface SatParametersOrBuilderpublic double getMaxVariableActivityValue()
optional double max_variable_activity_value = 16 [default = 1e+100];getMaxVariableActivityValue in interface SatParametersOrBuilderpublic SatParameters.Builder setMaxVariableActivityValue(double value)
optional double max_variable_activity_value = 16 [default = 1e+100];value - The maxVariableActivityValue to set.public SatParameters.Builder clearMaxVariableActivityValue()
optional double max_variable_activity_value = 16 [default = 1e+100];public boolean 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];hasGlucoseMaxDecay in interface SatParametersOrBuilderpublic double 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];getGlucoseMaxDecay in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasGlucoseDecayIncrement()
optional double glucose_decay_increment = 23 [default = 0.01];hasGlucoseDecayIncrement in interface SatParametersOrBuilderpublic double getGlucoseDecayIncrement()
optional double glucose_decay_increment = 23 [default = 0.01];getGlucoseDecayIncrement in interface SatParametersOrBuilderpublic SatParameters.Builder setGlucoseDecayIncrement(double value)
optional double glucose_decay_increment = 23 [default = 0.01];value - The glucoseDecayIncrement to set.public SatParameters.Builder clearGlucoseDecayIncrement()
optional double glucose_decay_increment = 23 [default = 0.01];public boolean hasGlucoseDecayIncrementPeriod()
optional int32 glucose_decay_increment_period = 24 [default = 5000];hasGlucoseDecayIncrementPeriod in interface SatParametersOrBuilderpublic int getGlucoseDecayIncrementPeriod()
optional int32 glucose_decay_increment_period = 24 [default = 5000];getGlucoseDecayIncrementPeriod in interface SatParametersOrBuilderpublic SatParameters.Builder setGlucoseDecayIncrementPeriod(int value)
optional int32 glucose_decay_increment_period = 24 [default = 5000];value - The glucoseDecayIncrementPeriod to set.public SatParameters.Builder clearGlucoseDecayIncrementPeriod()
optional int32 glucose_decay_increment_period = 24 [default = 5000];public boolean hasClauseActivityDecay()
Clause activity parameters (same effect as the one on the variables).
optional double clause_activity_decay = 17 [default = 0.999];hasClauseActivityDecay in interface SatParametersOrBuilderpublic double getClauseActivityDecay()
Clause activity parameters (same effect as the one on the variables).
optional double clause_activity_decay = 17 [default = 0.999];getClauseActivityDecay in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearClauseActivityDecay()
Clause activity parameters (same effect as the one on the variables).
optional double clause_activity_decay = 17 [default = 0.999];public boolean hasMaxClauseActivityValue()
optional double max_clause_activity_value = 18 [default = 1e+20];hasMaxClauseActivityValue in interface SatParametersOrBuilderpublic double getMaxClauseActivityValue()
optional double max_clause_activity_value = 18 [default = 1e+20];getMaxClauseActivityValue in interface SatParametersOrBuilderpublic SatParameters.Builder setMaxClauseActivityValue(double value)
optional double max_clause_activity_value = 18 [default = 1e+20];value - The maxClauseActivityValue to set.public SatParameters.Builder clearMaxClauseActivityValue()
optional double max_clause_activity_value = 18 [default = 1e+20];public java.util.List<SatParameters.RestartAlgorithm> 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;getRestartAlgorithmsList in interface SatParametersOrBuilderpublic int 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;getRestartAlgorithmsCount in interface SatParametersOrBuilderpublic SatParameters.RestartAlgorithm 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;getRestartAlgorithms in interface SatParametersOrBuilderindex - The index of the element to return.public SatParameters.Builder setRestartAlgorithms(int index, 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.public SatParameters.Builder addRestartAlgorithms(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.public SatParameters.Builder addAllRestartAlgorithms(java.lang.Iterable<? extends 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.public 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;public boolean hasDefaultRestartAlgorithms()
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];hasDefaultRestartAlgorithms in interface SatParametersOrBuilderpublic java.lang.String getDefaultRestartAlgorithms()
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];getDefaultRestartAlgorithms in interface SatParametersOrBuilderpublic com.google.protobuf.ByteString getDefaultRestartAlgorithmsBytes()
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];getDefaultRestartAlgorithmsBytes in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearDefaultRestartAlgorithms()
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];public 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.public boolean 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];hasRestartPeriod in interface SatParametersOrBuilderpublic int 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];getRestartPeriod in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasRestartRunningWindowSize()
Size of the window for the moving average restarts.
optional int32 restart_running_window_size = 62 [default = 50];hasRestartRunningWindowSize in interface SatParametersOrBuilderpublic int getRestartRunningWindowSize()
Size of the window for the moving average restarts.
optional int32 restart_running_window_size = 62 [default = 50];getRestartRunningWindowSize in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearRestartRunningWindowSize()
Size of the window for the moving average restarts.
optional int32 restart_running_window_size = 62 [default = 50];public boolean 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];hasRestartDlAverageRatio in interface SatParametersOrBuilderpublic double 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];getRestartDlAverageRatio in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasRestartLbdAverageRatio()
optional double restart_lbd_average_ratio = 71 [default = 1];hasRestartLbdAverageRatio in interface SatParametersOrBuilderpublic double getRestartLbdAverageRatio()
optional double restart_lbd_average_ratio = 71 [default = 1];getRestartLbdAverageRatio in interface SatParametersOrBuilderpublic SatParameters.Builder setRestartLbdAverageRatio(double value)
optional double restart_lbd_average_ratio = 71 [default = 1];value - The restartLbdAverageRatio to set.public SatParameters.Builder clearRestartLbdAverageRatio()
optional double restart_lbd_average_ratio = 71 [default = 1];public boolean 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];hasUseBlockingRestart in interface SatParametersOrBuilderpublic boolean 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];getUseBlockingRestart in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasBlockingRestartWindowSize()
optional int32 blocking_restart_window_size = 65 [default = 5000];hasBlockingRestartWindowSize in interface SatParametersOrBuilderpublic int getBlockingRestartWindowSize()
optional int32 blocking_restart_window_size = 65 [default = 5000];getBlockingRestartWindowSize in interface SatParametersOrBuilderpublic SatParameters.Builder setBlockingRestartWindowSize(int value)
optional int32 blocking_restart_window_size = 65 [default = 5000];value - The blockingRestartWindowSize to set.public SatParameters.Builder clearBlockingRestartWindowSize()
optional int32 blocking_restart_window_size = 65 [default = 5000];public boolean hasBlockingRestartMultiplier()
optional double blocking_restart_multiplier = 66 [default = 1.4];hasBlockingRestartMultiplier in interface SatParametersOrBuilderpublic double getBlockingRestartMultiplier()
optional double blocking_restart_multiplier = 66 [default = 1.4];getBlockingRestartMultiplier in interface SatParametersOrBuilderpublic SatParameters.Builder setBlockingRestartMultiplier(double value)
optional double blocking_restart_multiplier = 66 [default = 1.4];value - The blockingRestartMultiplier to set.public SatParameters.Builder clearBlockingRestartMultiplier()
optional double blocking_restart_multiplier = 66 [default = 1.4];public boolean 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];hasNumConflictsBeforeStrategyChanges in interface SatParametersOrBuilderpublic int 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];getNumConflictsBeforeStrategyChanges in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasStrategyChangeIncreaseRatio in interface SatParametersOrBuilderpublic double 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];getStrategyChangeIncreaseRatio in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxTimeInSeconds in interface SatParametersOrBuilderpublic double 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];getMaxTimeInSeconds in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxDeterministicTime in interface SatParametersOrBuilderpublic double 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];getMaxDeterministicTime in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxNumberOfConflicts in interface SatParametersOrBuilderpublic long 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];getMaxNumberOfConflicts in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxMemoryInMb in interface SatParametersOrBuilderpublic long 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];getMaxMemoryInMb in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAbsoluteGapLimit in interface SatParametersOrBuilderpublic double 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];getAbsoluteGapLimit in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasRelativeGapLimit()
optional double relative_gap_limit = 160 [default = 0];hasRelativeGapLimit in interface SatParametersOrBuilderpublic double getRelativeGapLimit()
optional double relative_gap_limit = 160 [default = 0];getRelativeGapLimit in interface SatParametersOrBuilderpublic SatParameters.Builder setRelativeGapLimit(double value)
optional double relative_gap_limit = 160 [default = 0];value - The relativeGapLimit to set.public SatParameters.Builder clearRelativeGapLimit()
optional double relative_gap_limit = 160 [default = 0];public boolean 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];hasRandomSeed in interface SatParametersOrBuilderpublic int 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];getRandomSeed in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasPermuteVariableRandomly in interface SatParametersOrBuilderpublic boolean 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];getPermuteVariableRandomly in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasPermutePresolveConstraintOrder()
optional bool permute_presolve_constraint_order = 179 [default = false];hasPermutePresolveConstraintOrder in interface SatParametersOrBuilderpublic boolean getPermutePresolveConstraintOrder()
optional bool permute_presolve_constraint_order = 179 [default = false];getPermutePresolveConstraintOrder in interface SatParametersOrBuilderpublic SatParameters.Builder setPermutePresolveConstraintOrder(boolean value)
optional bool permute_presolve_constraint_order = 179 [default = false];value - The permutePresolveConstraintOrder to set.public SatParameters.Builder clearPermutePresolveConstraintOrder()
optional bool permute_presolve_constraint_order = 179 [default = false];public boolean hasUseAbslRandom()
optional bool use_absl_random = 180 [default = false];hasUseAbslRandom in interface SatParametersOrBuilderpublic boolean getUseAbslRandom()
optional bool use_absl_random = 180 [default = false];getUseAbslRandom in interface SatParametersOrBuilderpublic SatParameters.Builder setUseAbslRandom(boolean value)
optional bool use_absl_random = 180 [default = false];value - The useAbslRandom to set.public SatParameters.Builder clearUseAbslRandom()
optional bool use_absl_random = 180 [default = false];public boolean 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];hasLogSearchProgress in interface SatParametersOrBuilderpublic boolean 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];getLogSearchProgress in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasLogSubsolverStatistics in interface SatParametersOrBuilderpublic boolean 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];getLogSubsolverStatistics in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasLogPrefix()
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];hasLogPrefix in interface SatParametersOrBuilderpublic java.lang.String getLogPrefix()
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];getLogPrefix in interface SatParametersOrBuilderpublic com.google.protobuf.ByteString getLogPrefixBytes()
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];getLogPrefixBytes in interface SatParametersOrBuilderpublic SatParameters.Builder setLogPrefix(java.lang.String value)
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];value - The logPrefix to set.public SatParameters.Builder clearLogPrefix()
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];public 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.public boolean hasLogToStdout()
Log to stdout.
optional bool log_to_stdout = 186 [default = true];hasLogToStdout in interface SatParametersOrBuilderpublic boolean getLogToStdout()
Log to stdout.
optional bool log_to_stdout = 186 [default = true];getLogToStdout in interface SatParametersOrBuilderpublic SatParameters.Builder setLogToStdout(boolean value)
Log to stdout.
optional bool log_to_stdout = 186 [default = true];value - The logToStdout to set.public SatParameters.Builder clearLogToStdout()
Log to stdout.
optional bool log_to_stdout = 186 [default = true];public boolean hasLogToResponse()
Log to response proto.
optional bool log_to_response = 187 [default = false];hasLogToResponse in interface SatParametersOrBuilderpublic boolean getLogToResponse()
Log to response proto.
optional bool log_to_response = 187 [default = false];getLogToResponse in interface SatParametersOrBuilderpublic SatParameters.Builder setLogToResponse(boolean value)
Log to response proto.
optional bool log_to_response = 187 [default = false];value - The logToResponse to set.public SatParameters.Builder clearLogToResponse()
Log to response proto.
optional bool log_to_response = 187 [default = false];public boolean 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];hasUsePbResolution in interface SatParametersOrBuilderpublic boolean 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];getUsePbResolution in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMinimizeReductionDuringPbResolution in interface SatParametersOrBuilderpublic boolean 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];getMinimizeReductionDuringPbResolution in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasCountAssumptionLevelsInLbd in interface SatParametersOrBuilderpublic boolean 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];getCountAssumptionLevelsInLbd in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasPresolveBveThreshold in interface SatParametersOrBuilderpublic int 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];getPresolveBveThreshold in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasPresolveBveClauseWeight in interface SatParametersOrBuilderpublic int 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];getPresolveBveClauseWeight in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasProbingDeterministicTimeLimit in interface SatParametersOrBuilderpublic double 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];getProbingDeterministicTimeLimit in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasPresolveProbingDeterministicTimeLimit()
optional double presolve_probing_deterministic_time_limit = 57 [default = 30];hasPresolveProbingDeterministicTimeLimit in interface SatParametersOrBuilderpublic double getPresolveProbingDeterministicTimeLimit()
optional double presolve_probing_deterministic_time_limit = 57 [default = 30];getPresolveProbingDeterministicTimeLimit in interface SatParametersOrBuilderpublic SatParameters.Builder setPresolveProbingDeterministicTimeLimit(double value)
optional double presolve_probing_deterministic_time_limit = 57 [default = 30];value - The presolveProbingDeterministicTimeLimit to set.public SatParameters.Builder clearPresolveProbingDeterministicTimeLimit()
optional double presolve_probing_deterministic_time_limit = 57 [default = 30];public boolean 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];hasPresolveBlockedClause in interface SatParametersOrBuilderpublic boolean 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];getPresolveBlockedClause in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasPresolveUseBva()
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
optional bool presolve_use_bva = 72 [default = true];hasPresolveUseBva in interface SatParametersOrBuilderpublic boolean getPresolveUseBva()
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
optional bool presolve_use_bva = 72 [default = true];getPresolveUseBva in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearPresolveUseBva()
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
optional bool presolve_use_bva = 72 [default = true];public boolean 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];hasPresolveBvaThreshold in interface SatParametersOrBuilderpublic int 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];getPresolveBvaThreshold in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxPresolveIterations in interface SatParametersOrBuilderpublic int 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];getMaxPresolveIterations in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasCpModelPresolve()
Whether we presolve the cp_model before solving it.
optional bool cp_model_presolve = 86 [default = true];hasCpModelPresolve in interface SatParametersOrBuilderpublic boolean getCpModelPresolve()
Whether we presolve the cp_model before solving it.
optional bool cp_model_presolve = 86 [default = true];getCpModelPresolve in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearCpModelPresolve()
Whether we presolve the cp_model before solving it.
optional bool cp_model_presolve = 86 [default = true];public boolean hasCpModelProbingLevel()
How much effort do we spend on probing. 0 disables it completely.
optional int32 cp_model_probing_level = 110 [default = 2];hasCpModelProbingLevel in interface SatParametersOrBuilderpublic int getCpModelProbingLevel()
How much effort do we spend on probing. 0 disables it completely.
optional int32 cp_model_probing_level = 110 [default = 2];getCpModelProbingLevel in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearCpModelProbingLevel()
How much effort do we spend on probing. 0 disables it completely.
optional int32 cp_model_probing_level = 110 [default = 2];public boolean hasCpModelUseSatPresolve()
Whether we also use the sat presolve when cp_model_presolve is true.
optional bool cp_model_use_sat_presolve = 93 [default = true];hasCpModelUseSatPresolve in interface SatParametersOrBuilderpublic boolean getCpModelUseSatPresolve()
Whether we also use the sat presolve when cp_model_presolve is true.
optional bool cp_model_use_sat_presolve = 93 [default = true];getCpModelUseSatPresolve in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasDetectTableWithCost in interface SatParametersOrBuilderpublic boolean 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];getDetectTableWithCost in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasTableCompressionLevel in interface SatParametersOrBuilderpublic int 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];getTableCompressionLevel in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasExpandAlldiffConstraints in interface SatParametersOrBuilderpublic boolean 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];getExpandAlldiffConstraints in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasExpandReservoirConstraints in interface SatParametersOrBuilderpublic boolean 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];getExpandReservoirConstraints in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasMaxLinMaxSizeForExpansion()
If the number of expressions in the lin_max is less that the max size parameter, model expansion replaces target = max(xi) by linear constraint with the introduction of new booleans bi such that bi => target == xi. This is mainly for experimenting compared to a custom lin_max propagator.
optional int32 max_lin_max_size_for_expansion = 280 [default = 0];hasMaxLinMaxSizeForExpansion in interface SatParametersOrBuilderpublic int getMaxLinMaxSizeForExpansion()
If the number of expressions in the lin_max is less that the max size parameter, model expansion replaces target = max(xi) by linear constraint with the introduction of new booleans bi such that bi => target == xi. This is mainly for experimenting compared to a custom lin_max propagator.
optional int32 max_lin_max_size_for_expansion = 280 [default = 0];getMaxLinMaxSizeForExpansion in interface SatParametersOrBuilderpublic SatParameters.Builder setMaxLinMaxSizeForExpansion(int value)
If the number of expressions in the lin_max is less that the max size parameter, model expansion replaces target = max(xi) by linear constraint with the introduction of new booleans bi such that bi => target == xi. This is mainly for experimenting compared to a custom lin_max propagator.
optional int32 max_lin_max_size_for_expansion = 280 [default = 0];value - The maxLinMaxSizeForExpansion to set.public SatParameters.Builder clearMaxLinMaxSizeForExpansion()
If the number of expressions in the lin_max is less that the max size parameter, model expansion replaces target = max(xi) by linear constraint with the introduction of new booleans bi such that bi => target == xi. This is mainly for experimenting compared to a custom lin_max propagator.
optional int32 max_lin_max_size_for_expansion = 280 [default = 0];public boolean 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];hasDisableConstraintExpansion in interface SatParametersOrBuilderpublic boolean 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];getDisableConstraintExpansion in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasEncodeComplexLinearConstraintWithInteger in interface SatParametersOrBuilderpublic boolean 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];getEncodeComplexLinearConstraintWithInteger in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMergeNoOverlapWorkLimit in interface SatParametersOrBuilderpublic double 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];getMergeNoOverlapWorkLimit in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasMergeAtMostOneWorkLimit()
optional double merge_at_most_one_work_limit = 146 [default = 100000000];hasMergeAtMostOneWorkLimit in interface SatParametersOrBuilderpublic double getMergeAtMostOneWorkLimit()
optional double merge_at_most_one_work_limit = 146 [default = 100000000];getMergeAtMostOneWorkLimit in interface SatParametersOrBuilderpublic SatParameters.Builder setMergeAtMostOneWorkLimit(double value)
optional double merge_at_most_one_work_limit = 146 [default = 100000000];value - The mergeAtMostOneWorkLimit to set.public SatParameters.Builder clearMergeAtMostOneWorkLimit()
optional double merge_at_most_one_work_limit = 146 [default = 100000000];public boolean 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];hasPresolveSubstitutionLevel in interface SatParametersOrBuilderpublic int 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];getPresolveSubstitutionLevel in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasPresolveExtractIntegerEnforcement in interface SatParametersOrBuilderpublic boolean 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];getPresolveExtractIntegerEnforcement in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasPresolveInclusionWorkLimit in interface SatParametersOrBuilderpublic long 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];getPresolveInclusionWorkLimit in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasIgnoreNames()
If true, we don't keep names in our internal copy of the user given model.
optional bool ignore_names = 202 [default = true];hasIgnoreNames in interface SatParametersOrBuilderpublic boolean getIgnoreNames()
If true, we don't keep names in our internal copy of the user given model.
optional bool ignore_names = 202 [default = true];getIgnoreNames in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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. This will also detect and add no_overlap constraints, if all the relations x != y have "offsets" between them. I.e. x > y + offset.
optional bool infer_all_diffs = 233 [default = true];hasInferAllDiffs in interface SatParametersOrBuilderpublic boolean 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. This will also detect and add no_overlap constraints, if all the relations x != y have "offsets" between them. I.e. x > y + offset.
optional bool infer_all_diffs = 233 [default = true];getInferAllDiffs in interface SatParametersOrBuilderpublic 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. This will also detect and add no_overlap constraints, if all the relations x != y have "offsets" between them. I.e. x > y + offset.
optional bool infer_all_diffs = 233 [default = true];value - The inferAllDiffs to set.public 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. This will also detect and add no_overlap constraints, if all the relations x != y have "offsets" between them. I.e. x > y + offset.
optional bool infer_all_diffs = 233 [default = true];public boolean 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];hasFindBigLinearOverlap in interface SatParametersOrBuilderpublic boolean 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];getFindBigLinearOverlap in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseSatInprocessing in interface SatParametersOrBuilderpublic boolean 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];getUseSatInprocessing in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasInprocessingDtimeRatio in interface SatParametersOrBuilderpublic double 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];getInprocessingDtimeRatio in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasInprocessingProbingDtime()
The amount of dtime we should spend on probing for each inprocessing round.
optional double inprocessing_probing_dtime = 274 [default = 1];hasInprocessingProbingDtime in interface SatParametersOrBuilderpublic double getInprocessingProbingDtime()
The amount of dtime we should spend on probing for each inprocessing round.
optional double inprocessing_probing_dtime = 274 [default = 1];getInprocessingProbingDtime in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearInprocessingProbingDtime()
The amount of dtime we should spend on probing for each inprocessing round.
optional double inprocessing_probing_dtime = 274 [default = 1];public boolean 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];hasInprocessingMinimizationDtime in interface SatParametersOrBuilderpublic double 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];getInprocessingMinimizationDtime in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasNumWorkers in interface SatParametersOrBuilderpublic int 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];getNumWorkers in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasNumSearchWorkers()
optional int32 num_search_workers = 100 [default = 0];hasNumSearchWorkers in interface SatParametersOrBuilderpublic int getNumSearchWorkers()
optional int32 num_search_workers = 100 [default = 0];getNumSearchWorkers in interface SatParametersOrBuilderpublic SatParameters.Builder setNumSearchWorkers(int value)
optional int32 num_search_workers = 100 [default = 0];value - The numSearchWorkers to set.public SatParameters.Builder clearNumSearchWorkers()
optional int32 num_search_workers = 100 [default = 0];public boolean hasMinNumLnsWorkers()
Obsolete parameter. No-op.
optional int32 min_num_lns_workers = 211 [default = 2];hasMinNumLnsWorkers in interface SatParametersOrBuilderpublic int getMinNumLnsWorkers()
Obsolete parameter. No-op.
optional int32 min_num_lns_workers = 211 [default = 2];getMinNumLnsWorkers in interface SatParametersOrBuilderpublic SatParameters.Builder setMinNumLnsWorkers(int value)
Obsolete parameter. No-op.
optional int32 min_num_lns_workers = 211 [default = 2];value - The minNumLnsWorkers to set.public SatParameters.Builder clearMinNumLnsWorkers()
Obsolete parameter. No-op.
optional int32 min_num_lns_workers = 211 [default = 2];public com.google.protobuf.ProtocolStringList 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;getSubsolversList in interface SatParametersOrBuilderpublic int 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;getSubsolversCount in interface SatParametersOrBuilderpublic java.lang.String 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;getSubsolvers in interface SatParametersOrBuilderindex - The index of the element to return.public com.google.protobuf.ByteString 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;getSubsolversBytes in interface SatParametersOrBuilderindex - The index of the value to return.public 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.public 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.public 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.public 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;public 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.public com.google.protobuf.ProtocolStringList getExtraSubsolversList()
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;getExtraSubsolversList in interface SatParametersOrBuilderpublic int getExtraSubsolversCount()
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;getExtraSubsolversCount in interface SatParametersOrBuilderpublic java.lang.String 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;getExtraSubsolvers in interface SatParametersOrBuilderindex - The index of the element to return.public com.google.protobuf.ByteString 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;getExtraSubsolversBytes in interface SatParametersOrBuilderindex - The index of the value to return.public 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.public 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.public 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.public 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;public 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.public com.google.protobuf.ProtocolStringList 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;getIgnoreSubsolversList in interface SatParametersOrBuilderpublic int 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;getIgnoreSubsolversCount in interface SatParametersOrBuilderpublic java.lang.String 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;getIgnoreSubsolvers in interface SatParametersOrBuilderindex - The index of the element to return.public com.google.protobuf.ByteString 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;getIgnoreSubsolversBytes in interface SatParametersOrBuilderindex - The index of the value to return.public 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.public 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.public 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.public 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;public 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.public java.util.List<SatParameters> 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;getSubsolverParamsList in interface SatParametersOrBuilderpublic int 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;getSubsolverParamsCount in interface SatParametersOrBuilderpublic SatParameters 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;getSubsolverParams in interface SatParametersOrBuilderpublic SatParameters.Builder setSubsolverParams(int index, 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;public SatParameters.Builder setSubsolverParams(int index, 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;public SatParameters.Builder addSubsolverParams(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;public SatParameters.Builder addSubsolverParams(int index, 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;public SatParameters.Builder addSubsolverParams(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;public SatParameters.Builder addSubsolverParams(int index, 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;public SatParameters.Builder addAllSubsolverParams(java.lang.Iterable<? extends 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;public 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;public 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;public 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;public SatParametersOrBuilder 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;getSubsolverParamsOrBuilder in interface SatParametersOrBuilderpublic java.util.List<? extends SatParametersOrBuilder> 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;getSubsolverParamsOrBuilderList in interface SatParametersOrBuilderpublic 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;public 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;public java.util.List<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;public boolean 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];hasInterleaveSearch in interface SatParametersOrBuilderpublic boolean 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];getInterleaveSearch in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasInterleaveBatchSize()
optional int32 interleave_batch_size = 134 [default = 0];hasInterleaveBatchSize in interface SatParametersOrBuilderpublic int getInterleaveBatchSize()
optional int32 interleave_batch_size = 134 [default = 0];getInterleaveBatchSize in interface SatParametersOrBuilderpublic SatParameters.Builder setInterleaveBatchSize(int value)
optional int32 interleave_batch_size = 134 [default = 0];value - The interleaveBatchSize to set.public SatParameters.Builder clearInterleaveBatchSize()
optional int32 interleave_batch_size = 134 [default = 0];public boolean hasShareObjectiveBounds()
Allows objective sharing between workers.
optional bool share_objective_bounds = 113 [default = true];hasShareObjectiveBounds in interface SatParametersOrBuilderpublic boolean getShareObjectiveBounds()
Allows objective sharing between workers.
optional bool share_objective_bounds = 113 [default = true];getShareObjectiveBounds in interface SatParametersOrBuilderpublic SatParameters.Builder setShareObjectiveBounds(boolean value)
Allows objective sharing between workers.
optional bool share_objective_bounds = 113 [default = true];value - The shareObjectiveBounds to set.public SatParameters.Builder clearShareObjectiveBounds()
Allows objective sharing between workers.
optional bool share_objective_bounds = 113 [default = true];public boolean hasShareLevelZeroBounds()
Allows sharing of the bounds of modified variables at level 0.
optional bool share_level_zero_bounds = 114 [default = true];hasShareLevelZeroBounds in interface SatParametersOrBuilderpublic boolean getShareLevelZeroBounds()
Allows sharing of the bounds of modified variables at level 0.
optional bool share_level_zero_bounds = 114 [default = true];getShareLevelZeroBounds in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearShareLevelZeroBounds()
Allows sharing of the bounds of modified variables at level 0.
optional bool share_level_zero_bounds = 114 [default = true];public boolean hasShareBinaryClauses()
Allows sharing of new learned binary clause between workers.
optional bool share_binary_clauses = 203 [default = true];hasShareBinaryClauses in interface SatParametersOrBuilderpublic boolean getShareBinaryClauses()
Allows sharing of new learned binary clause between workers.
optional bool share_binary_clauses = 203 [default = true];getShareBinaryClauses in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearShareBinaryClauses()
Allows sharing of new learned binary clause between workers.
optional bool share_binary_clauses = 203 [default = true];public boolean 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];hasDebugPostsolveWithFullSolver in interface SatParametersOrBuilderpublic boolean 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];getDebugPostsolveWithFullSolver in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasDebugMaxNumPresolveOperations in interface SatParametersOrBuilderpublic int 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];getDebugMaxNumPresolveOperations in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasDebugCrashOnBadHint in interface SatParametersOrBuilderpublic boolean 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];getDebugCrashOnBadHint in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseOptimizationHints in interface SatParametersOrBuilderpublic boolean 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];getUseOptimizationHints in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasCoreMinimizationLevel in interface SatParametersOrBuilderpublic int 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];getCoreMinimizationLevel in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasFindMultipleCores in interface SatParametersOrBuilderpublic boolean 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];getFindMultipleCores in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasCoverOptimization in interface SatParametersOrBuilderpublic boolean 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];getCoverOptimization in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasMaxSatAssumptionOrder()
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];hasMaxSatAssumptionOrder in interface SatParametersOrBuilderpublic SatParameters.MaxSatAssumptionOrder getMaxSatAssumptionOrder()
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];getMaxSatAssumptionOrder in interface SatParametersOrBuilderpublic SatParameters.Builder setMaxSatAssumptionOrder(SatParameters.MaxSatAssumptionOrder value)
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];value - The maxSatAssumptionOrder to set.public SatParameters.Builder clearMaxSatAssumptionOrder()
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];public boolean 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];hasMaxSatReverseAssumptionOrder in interface SatParametersOrBuilderpublic boolean 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];getMaxSatReverseAssumptionOrder in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasMaxSatStratification()
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];hasMaxSatStratification in interface SatParametersOrBuilderpublic SatParameters.MaxSatStratificationAlgorithm getMaxSatStratification()
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];getMaxSatStratification in interface SatParametersOrBuilderpublic SatParameters.Builder setMaxSatStratification(SatParameters.MaxSatStratificationAlgorithm value)
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];value - The maxSatStratification to set.public SatParameters.Builder clearMaxSatStratification()
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];public boolean 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];hasPropagationLoopDetectionFactor in interface SatParametersOrBuilderpublic double 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];getPropagationLoopDetectionFactor in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUsePrecedencesInDisjunctiveConstraint in interface SatParametersOrBuilderpublic boolean 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];getUsePrecedencesInDisjunctiveConstraint in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxSizeToCreatePrecedenceLiteralsInDisjunctive in interface SatParametersOrBuilderpublic int 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];getMaxSizeToCreatePrecedenceLiteralsInDisjunctive in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasUseStrongPropagationInDisjunctive()
Enable stronger and more expensive propagation on no_overlap constraint.
optional bool use_strong_propagation_in_disjunctive = 230 [default = false];hasUseStrongPropagationInDisjunctive in interface SatParametersOrBuilderpublic boolean getUseStrongPropagationInDisjunctive()
Enable stronger and more expensive propagation on no_overlap constraint.
optional bool use_strong_propagation_in_disjunctive = 230 [default = false];getUseStrongPropagationInDisjunctive in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearUseStrongPropagationInDisjunctive()
Enable stronger and more expensive propagation on no_overlap constraint.
optional bool use_strong_propagation_in_disjunctive = 230 [default = false];public boolean 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];hasUseDynamicPrecedenceInDisjunctive in interface SatParametersOrBuilderpublic boolean 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];getUseDynamicPrecedenceInDisjunctive in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasUseDynamicPrecedenceInCumulative()
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];hasUseDynamicPrecedenceInCumulative in interface SatParametersOrBuilderpublic boolean getUseDynamicPrecedenceInCumulative()
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];getUseDynamicPrecedenceInCumulative in interface SatParametersOrBuilderpublic SatParameters.Builder setUseDynamicPrecedenceInCumulative(boolean value)
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];value - The useDynamicPrecedenceInCumulative to set.public SatParameters.Builder clearUseDynamicPrecedenceInCumulative()
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];public boolean 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];hasUseOverloadCheckerInCumulative in interface SatParametersOrBuilderpublic boolean 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];getUseOverloadCheckerInCumulative in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseTimetableEdgeFindingInCumulative in interface SatParametersOrBuilderpublic boolean 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];getUseTimetableEdgeFindingInCumulative in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxNumIntervalsForTimetableEdgeFinding in interface SatParametersOrBuilderpublic int 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];getMaxNumIntervalsForTimetableEdgeFinding in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseHardPrecedencesInCumulative in interface SatParametersOrBuilderpublic boolean 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];getUseHardPrecedencesInCumulative in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasExploitAllPrecedences()
optional bool exploit_all_precedences = 220 [default = false];hasExploitAllPrecedences in interface SatParametersOrBuilderpublic boolean getExploitAllPrecedences()
optional bool exploit_all_precedences = 220 [default = false];getExploitAllPrecedences in interface SatParametersOrBuilderpublic SatParameters.Builder setExploitAllPrecedences(boolean value)
optional bool exploit_all_precedences = 220 [default = false];value - The exploitAllPrecedences to set.public SatParameters.Builder clearExploitAllPrecedences()
optional bool exploit_all_precedences = 220 [default = false];public boolean 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];hasUseDisjunctiveConstraintInCumulative in interface SatParametersOrBuilderpublic boolean 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];getUseDisjunctiveConstraintInCumulative in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseTimetablingInNoOverlap2D in interface SatParametersOrBuilderpublic boolean 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];getUseTimetablingInNoOverlap2D in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseEnergeticReasoningInNoOverlap2D in interface SatParametersOrBuilderpublic boolean 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];getUseEnergeticReasoningInNoOverlap2D in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseAreaEnergeticReasoningInNoOverlap2D in interface SatParametersOrBuilderpublic boolean 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];getUseAreaEnergeticReasoningInNoOverlap2D in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxPairsPairwiseReasoningInNoOverlap2D in interface SatParametersOrBuilderpublic int 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];getMaxPairsPairwiseReasoningInNoOverlap2D in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseDualSchedulingHeuristics in interface SatParametersOrBuilderpublic boolean 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];getUseDualSchedulingHeuristics in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasSearchBranching()
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];hasSearchBranching in interface SatParametersOrBuilderpublic SatParameters.SearchBranching getSearchBranching()
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];getSearchBranching in interface SatParametersOrBuilderpublic SatParameters.Builder setSearchBranching(SatParameters.SearchBranching value)
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];value - The searchBranching to set.public SatParameters.Builder clearSearchBranching()
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];public boolean hasHintConflictLimit()
Conflict limit used in the phase that exploit the solution hint.
optional int32 hint_conflict_limit = 153 [default = 10];hasHintConflictLimit in interface SatParametersOrBuilderpublic int getHintConflictLimit()
Conflict limit used in the phase that exploit the solution hint.
optional int32 hint_conflict_limit = 153 [default = 10];getHintConflictLimit in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearHintConflictLimit()
Conflict limit used in the phase that exploit the solution hint.
optional int32 hint_conflict_limit = 153 [default = 10];public boolean 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];hasRepairHint in interface SatParametersOrBuilderpublic boolean 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];getRepairHint in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasFixVariablesToTheirHintedValue in interface SatParametersOrBuilderpublic boolean 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];getFixVariablesToTheirHintedValue in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseProbingSearch in interface SatParametersOrBuilderpublic boolean 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];getUseProbingSearch in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasUseExtendedProbing()
Use extended probing (probe bool_or, at_most_one, exactly_one).
optional bool use_extended_probing = 269 [default = true];hasUseExtendedProbing in interface SatParametersOrBuilderpublic boolean getUseExtendedProbing()
Use extended probing (probe bool_or, at_most_one, exactly_one).
optional bool use_extended_probing = 269 [default = true];getUseExtendedProbing in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearUseExtendedProbing()
Use extended probing (probe bool_or, at_most_one, exactly_one).
optional bool use_extended_probing = 269 [default = true];public boolean hasProbingNumCombinationsLimit()
How many combinations of pairs or triplets of variables we want to scan.
optional int32 probing_num_combinations_limit = 272 [default = 20000];hasProbingNumCombinationsLimit in interface SatParametersOrBuilderpublic int getProbingNumCombinationsLimit()
How many combinations of pairs or triplets of variables we want to scan.
optional int32 probing_num_combinations_limit = 272 [default = 20000];getProbingNumCombinationsLimit in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseShavingInProbingSearch in interface SatParametersOrBuilderpublic boolean 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];getUseShavingInProbingSearch in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasShavingSearchDeterministicTime in interface SatParametersOrBuilderpublic double 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];getShavingSearchDeterministicTime in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseObjectiveLbSearch in interface SatParametersOrBuilderpublic boolean 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];getUseObjectiveLbSearch in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseObjectiveShavingSearch in interface SatParametersOrBuilderpublic boolean 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];getUseObjectiveShavingSearch in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasPseudoCostReliabilityThreshold in interface SatParametersOrBuilderpublic long 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];getPseudoCostReliabilityThreshold in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasOptimizeWithCore in interface SatParametersOrBuilderpublic boolean 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];getOptimizeWithCore in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasOptimizeWithLbTreeSearch in interface SatParametersOrBuilderpublic boolean 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];getOptimizeWithLbTreeSearch in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasBinarySearchNumConflicts in interface SatParametersOrBuilderpublic int 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];getBinarySearchNumConflicts in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasOptimizeWithMaxHs in interface SatParametersOrBuilderpublic boolean 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];getOptimizeWithMaxHs in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseFeasibilityJump in interface SatParametersOrBuilderpublic boolean 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];getUseFeasibilityJump in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasTestFeasibilityJump in interface SatParametersOrBuilderpublic boolean 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];getTestFeasibilityJump in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasFeasibilityJumpDecay in interface SatParametersOrBuilderpublic double 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];getFeasibilityJumpDecay in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasFeasibilityJumpLinearizationLevel()
How much do we linearize the problem in the local search code.
optional int32 feasibility_jump_linearization_level = 257 [default = 2];hasFeasibilityJumpLinearizationLevel in interface SatParametersOrBuilderpublic int getFeasibilityJumpLinearizationLevel()
How much do we linearize the problem in the local search code.
optional int32 feasibility_jump_linearization_level = 257 [default = 2];getFeasibilityJumpLinearizationLevel in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearFeasibilityJumpLinearizationLevel()
How much do we linearize the problem in the local search code.
optional int32 feasibility_jump_linearization_level = 257 [default = 2];public boolean 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];hasFeasibilityJumpRestartFactor in interface SatParametersOrBuilderpublic int 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];getFeasibilityJumpRestartFactor in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasFeasibilityJumpVarRandomizationProbability in interface SatParametersOrBuilderpublic double 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];getFeasibilityJumpVarRandomizationProbability in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasFeasibilityJumpVarPerburbationRangeRatio in interface SatParametersOrBuilderpublic double 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];getFeasibilityJumpVarPerburbationRangeRatio in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasFeasibilityJumpEnableRestarts in interface SatParametersOrBuilderpublic boolean 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];getFeasibilityJumpEnableRestarts in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasFeasibilityJumpMaxExpandedConstraintSize in interface SatParametersOrBuilderpublic int 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];getFeasibilityJumpMaxExpandedConstraintSize in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasNumViolationLs in interface SatParametersOrBuilderpublic int 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];getNumViolationLs in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasViolationLsPerturbationPeriod()
How long violation_ls should wait before perturbating a solution.
optional int32 violation_ls_perturbation_period = 249 [default = 100];hasViolationLsPerturbationPeriod in interface SatParametersOrBuilderpublic int getViolationLsPerturbationPeriod()
How long violation_ls should wait before perturbating a solution.
optional int32 violation_ls_perturbation_period = 249 [default = 100];getViolationLsPerturbationPeriod in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearViolationLsPerturbationPeriod()
How long violation_ls should wait before perturbating a solution.
optional int32 violation_ls_perturbation_period = 249 [default = 100];public boolean 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];hasViolationLsCompoundMoveProbability in interface SatParametersOrBuilderpublic double 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];getViolationLsCompoundMoveProbability in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasSharedTreeNumWorkers in interface SatParametersOrBuilderpublic int 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];getSharedTreeNumWorkers in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasUseSharedTreeSearch()
Set on shared subtree workers. Users should not set this directly.
optional bool use_shared_tree_search = 236 [default = false];hasUseSharedTreeSearch in interface SatParametersOrBuilderpublic boolean getUseSharedTreeSearch()
Set on shared subtree workers. Users should not set this directly.
optional bool use_shared_tree_search = 236 [default = false];getUseSharedTreeSearch in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearUseSharedTreeSearch()
Set on shared subtree workers. Users should not set this directly.
optional bool use_shared_tree_search = 236 [default = false];public boolean 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];hasSharedTreeWorkerObjectiveSplitProbability in interface SatParametersOrBuilderpublic double 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];getSharedTreeWorkerObjectiveSplitProbability in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasSharedTreeWorkerMinRestartsPerSubtree()
Minimum number of restarts before a worker will replace a subtree that looks "bad" based on the average LBD of learned clauses.
optional int32 shared_tree_worker_min_restarts_per_subtree = 282 [default = 32];hasSharedTreeWorkerMinRestartsPerSubtree in interface SatParametersOrBuilderpublic int getSharedTreeWorkerMinRestartsPerSubtree()
Minimum number of restarts before a worker will replace a subtree that looks "bad" based on the average LBD of learned clauses.
optional int32 shared_tree_worker_min_restarts_per_subtree = 282 [default = 32];getSharedTreeWorkerMinRestartsPerSubtree in interface SatParametersOrBuilderpublic SatParameters.Builder setSharedTreeWorkerMinRestartsPerSubtree(int value)
Minimum number of restarts before a worker will replace a subtree that looks "bad" based on the average LBD of learned clauses.
optional int32 shared_tree_worker_min_restarts_per_subtree = 282 [default = 32];value - The sharedTreeWorkerMinRestartsPerSubtree to set.public SatParameters.Builder clearSharedTreeWorkerMinRestartsPerSubtree()
Minimum number of restarts before a worker will replace a subtree that looks "bad" based on the average LBD of learned clauses.
optional int32 shared_tree_worker_min_restarts_per_subtree = 282 [default = 32];public boolean hasSharedTreeOpenLeavesPerWorker()
How many open leaf nodes should the shared tree maintain per worker.
optional double shared_tree_open_leaves_per_worker = 281 [default = 2];hasSharedTreeOpenLeavesPerWorker in interface SatParametersOrBuilderpublic double getSharedTreeOpenLeavesPerWorker()
How many open leaf nodes should the shared tree maintain per worker.
optional double shared_tree_open_leaves_per_worker = 281 [default = 2];getSharedTreeOpenLeavesPerWorker in interface SatParametersOrBuilderpublic SatParameters.Builder setSharedTreeOpenLeavesPerWorker(double value)
How many open leaf nodes should the shared tree maintain per worker.
optional double shared_tree_open_leaves_per_worker = 281 [default = 2];value - The sharedTreeOpenLeavesPerWorker to set.public SatParameters.Builder clearSharedTreeOpenLeavesPerWorker()
How many open leaf nodes should the shared tree maintain per worker.
optional double shared_tree_open_leaves_per_worker = 281 [default = 2];public boolean 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];hasSharedTreeMaxNodesPerWorker in interface SatParametersOrBuilderpublic int 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];getSharedTreeMaxNodesPerWorker in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasSharedTreeSplitStrategy()
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];hasSharedTreeSplitStrategy in interface SatParametersOrBuilderpublic SatParameters.SharedTreeSplitStrategy getSharedTreeSplitStrategy()
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];getSharedTreeSplitStrategy in interface SatParametersOrBuilderpublic SatParameters.Builder setSharedTreeSplitStrategy(SatParameters.SharedTreeSplitStrategy value)
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];value - The sharedTreeSplitStrategy to set.public SatParameters.Builder clearSharedTreeSplitStrategy()
optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];public boolean 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];hasEnumerateAllSolutions in interface SatParametersOrBuilderpublic boolean 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];getEnumerateAllSolutions in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasKeepAllFeasibleSolutionsInPresolve in interface SatParametersOrBuilderpublic boolean 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];getKeepAllFeasibleSolutionsInPresolve in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasFillTightenedDomainsInResponse in interface SatParametersOrBuilderpublic boolean 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];getFillTightenedDomainsInResponse in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasFillAdditionalSolutionsInResponse in interface SatParametersOrBuilderpublic boolean 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];getFillAdditionalSolutionsInResponse in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasInstantiateAllVariables in interface SatParametersOrBuilderpublic boolean 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];getInstantiateAllVariables in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAutoDetectGreaterThanAtLeastOneOf in interface SatParametersOrBuilderpublic boolean 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];getAutoDetectGreaterThanAtLeastOneOf in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasStopAfterFirstSolution()
For an optimization problem, stop the solver as soon as we have a solution.
optional bool stop_after_first_solution = 98 [default = false];hasStopAfterFirstSolution in interface SatParametersOrBuilderpublic boolean getStopAfterFirstSolution()
For an optimization problem, stop the solver as soon as we have a solution.
optional bool stop_after_first_solution = 98 [default = false];getStopAfterFirstSolution in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasStopAfterPresolve in interface SatParametersOrBuilderpublic boolean 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];getStopAfterPresolve in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasStopAfterRootPropagation()
optional bool stop_after_root_propagation = 252 [default = false];hasStopAfterRootPropagation in interface SatParametersOrBuilderpublic boolean getStopAfterRootPropagation()
optional bool stop_after_root_propagation = 252 [default = false];getStopAfterRootPropagation in interface SatParametersOrBuilderpublic SatParameters.Builder setStopAfterRootPropagation(boolean value)
optional bool stop_after_root_propagation = 252 [default = false];value - The stopAfterRootPropagation to set.public SatParameters.Builder clearStopAfterRootPropagation()
optional bool stop_after_root_propagation = 252 [default = false];public boolean hasUseLns()
Testing parameters used to disable all lns workers.
optional bool use_lns = 283 [default = true];hasUseLns in interface SatParametersOrBuilderpublic boolean getUseLns()
Testing parameters used to disable all lns workers.
optional bool use_lns = 283 [default = true];getUseLns in interface SatParametersOrBuilderpublic SatParameters.Builder setUseLns(boolean value)
Testing parameters used to disable all lns workers.
optional bool use_lns = 283 [default = true];value - The useLns to set.public SatParameters.Builder clearUseLns()
Testing parameters used to disable all lns workers.
optional bool use_lns = 283 [default = true];public boolean hasUseLnsOnly()
Experimental parameters to disable everything but lns.
optional bool use_lns_only = 101 [default = false];hasUseLnsOnly in interface SatParametersOrBuilderpublic boolean getUseLnsOnly()
Experimental parameters to disable everything but lns.
optional bool use_lns_only = 101 [default = false];getUseLnsOnly in interface SatParametersOrBuilderpublic SatParameters.Builder setUseLnsOnly(boolean value)
Experimental parameters to disable everything but lns.
optional bool use_lns_only = 101 [default = false];value - The useLnsOnly to set.public SatParameters.Builder clearUseLnsOnly()
Experimental parameters to disable everything but lns.
optional bool use_lns_only = 101 [default = false];public boolean 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];hasSolutionPoolSize in interface SatParametersOrBuilderpublic int 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];getSolutionPoolSize in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasUseRinsLns()
Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];hasUseRinsLns in interface SatParametersOrBuilderpublic boolean getUseRinsLns()
Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];getUseRinsLns in interface SatParametersOrBuilderpublic SatParameters.Builder setUseRinsLns(boolean value)
Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];value - The useRinsLns to set.public SatParameters.Builder clearUseRinsLns()
Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];public boolean hasUseFeasibilityPump()
Adds a feasibility pump subsolver along with lns subsolvers.
optional bool use_feasibility_pump = 164 [default = true];hasUseFeasibilityPump in interface SatParametersOrBuilderpublic boolean getUseFeasibilityPump()
Adds a feasibility pump subsolver along with lns subsolvers.
optional bool use_feasibility_pump = 164 [default = true];getUseFeasibilityPump in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearUseFeasibilityPump()
Adds a feasibility pump subsolver along with lns subsolvers.
optional bool use_feasibility_pump = 164 [default = true];public boolean 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];hasUseLbRelaxLns in interface SatParametersOrBuilderpublic boolean 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];getUseLbRelaxLns in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasFpRounding()
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];hasFpRounding in interface SatParametersOrBuilderpublic SatParameters.FPRoundingMethod getFpRounding()
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];getFpRounding in interface SatParametersOrBuilderpublic SatParameters.Builder setFpRounding(SatParameters.FPRoundingMethod value)
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];value - The fpRounding to set.public SatParameters.Builder clearFpRounding()
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];public boolean hasDiversifyLnsParams()
If true, registers more lns subsolvers with different parameters.
optional bool diversify_lns_params = 137 [default = false];hasDiversifyLnsParams in interface SatParametersOrBuilderpublic boolean getDiversifyLnsParams()
If true, registers more lns subsolvers with different parameters.
optional bool diversify_lns_params = 137 [default = false];getDiversifyLnsParams in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearDiversifyLnsParams()
If true, registers more lns subsolvers with different parameters.
optional bool diversify_lns_params = 137 [default = false];public boolean hasRandomizeSearch()
Randomize fixed search.
optional bool randomize_search = 103 [default = false];hasRandomizeSearch in interface SatParametersOrBuilderpublic boolean getRandomizeSearch()
Randomize fixed search.
optional bool randomize_search = 103 [default = false];getRandomizeSearch in interface SatParametersOrBuilderpublic SatParameters.Builder setRandomizeSearch(boolean value)
Randomize fixed search.
optional bool randomize_search = 103 [default = false];value - The randomizeSearch to set.public SatParameters.Builder clearRandomizeSearch()
Randomize fixed search.
optional bool randomize_search = 103 [default = false];public boolean 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];hasSearchRandomVariablePoolSize in interface SatParametersOrBuilderpublic long 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];getSearchRandomVariablePoolSize in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasPushAllTasksTowardStart in interface SatParametersOrBuilderpublic boolean 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];getPushAllTasksTowardStart in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseOptionalVariables in interface SatParametersOrBuilderpublic boolean 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];getUseOptionalVariables in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseExactLpReason in interface SatParametersOrBuilderpublic boolean 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];getUseExactLpReason in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseCombinedNoOverlap in interface SatParametersOrBuilderpublic boolean 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];getUseCombinedNoOverlap in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAtMostOneMaxExpansionSize in interface SatParametersOrBuilderpublic int 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];getAtMostOneMaxExpansionSize in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasCatchSigintSignal in interface SatParametersOrBuilderpublic boolean 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];getCatchSigintSignal in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasUseImpliedBounds in interface SatParametersOrBuilderpublic boolean 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];getUseImpliedBounds in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasPolishLpSolution in interface SatParametersOrBuilderpublic boolean 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];getPolishLpSolution in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasLpPrimalTolerance in interface SatParametersOrBuilderpublic double 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];getLpPrimalTolerance in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasLpDualTolerance()
optional double lp_dual_tolerance = 267 [default = 1e-07];hasLpDualTolerance in interface SatParametersOrBuilderpublic double getLpDualTolerance()
optional double lp_dual_tolerance = 267 [default = 1e-07];getLpDualTolerance in interface SatParametersOrBuilderpublic SatParameters.Builder setLpDualTolerance(double value)
optional double lp_dual_tolerance = 267 [default = 1e-07];value - The lpDualTolerance to set.public SatParameters.Builder clearLpDualTolerance()
optional double lp_dual_tolerance = 267 [default = 1e-07];public boolean 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];hasConvertIntervals in interface SatParametersOrBuilderpublic boolean 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];getConvertIntervals in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasSymmetryLevel in interface SatParametersOrBuilderpublic int 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];getSymmetryLevel in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasNewLinearPropagation()
The new linear propagation code treat all constraints at once and use an adaptation of Bellman-Ford-Tarjan to propagate constraint in a smarter order and potentially detect propagation cycle earlier.
optional bool new_linear_propagation = 224 [default = true];hasNewLinearPropagation in interface SatParametersOrBuilderpublic boolean getNewLinearPropagation()
The new linear propagation code treat all constraints at once and use an adaptation of Bellman-Ford-Tarjan to propagate constraint in a smarter order and potentially detect propagation cycle earlier.
optional bool new_linear_propagation = 224 [default = true];getNewLinearPropagation in interface SatParametersOrBuilderpublic SatParameters.Builder setNewLinearPropagation(boolean value)
The new linear propagation code treat all constraints at once and use an adaptation of Bellman-Ford-Tarjan to propagate constraint in a smarter order and potentially detect propagation cycle earlier.
optional bool new_linear_propagation = 224 [default = true];value - The newLinearPropagation to set.public SatParameters.Builder clearNewLinearPropagation()
The new linear propagation code treat all constraints at once and use an adaptation of Bellman-Ford-Tarjan to propagate constraint in a smarter order and potentially detect propagation cycle earlier.
optional bool new_linear_propagation = 224 [default = true];public boolean 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];hasLinearSplitSize in interface SatParametersOrBuilderpublic int 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];getLinearSplitSize in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasLinearizationLevel in interface SatParametersOrBuilderpublic int 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];getLinearizationLevel in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasBooleanEncodingLevel in interface SatParametersOrBuilderpublic int 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];getBooleanEncodingLevel in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxDomainSizeWhenEncodingEqNeqConstraints in interface SatParametersOrBuilderpublic int 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];getMaxDomainSizeWhenEncodingEqNeqConstraints in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxNumCuts in interface SatParametersOrBuilderpublic int 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];getMaxNumCuts in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasCutLevel in interface SatParametersOrBuilderpublic int 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];getCutLevel in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasOnlyAddCutsAtLevelZero in interface SatParametersOrBuilderpublic boolean 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];getOnlyAddCutsAtLevelZero in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAddObjectiveCut in interface SatParametersOrBuilderpublic boolean 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];getAddObjectiveCut in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAddCgCuts in interface SatParametersOrBuilderpublic boolean 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];getAddCgCuts in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAddMirCuts in interface SatParametersOrBuilderpublic boolean 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];getAddMirCuts in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAddZeroHalfCuts in interface SatParametersOrBuilderpublic boolean 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];getAddZeroHalfCuts in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAddCliqueCuts in interface SatParametersOrBuilderpublic boolean 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];getAddCliqueCuts in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAddRltCuts in interface SatParametersOrBuilderpublic boolean 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];getAddRltCuts in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxAllDiffCutSize in interface SatParametersOrBuilderpublic int 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];getMaxAllDiffCutSize in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAddLinMaxCuts in interface SatParametersOrBuilderpublic boolean 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];getAddLinMaxCuts in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxIntegerRoundingScaling in interface SatParametersOrBuilderpublic int 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];getMaxIntegerRoundingScaling in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasAddLpConstraintsLazily in interface SatParametersOrBuilderpublic boolean 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];getAddLpConstraintsLazily in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasRootLpIterations in interface SatParametersOrBuilderpublic int 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];getRootLpIterations in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMinOrthogonalityForLpConstraints in interface SatParametersOrBuilderpublic double 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];getMinOrthogonalityForLpConstraints in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxCutRoundsAtLevelZero in interface SatParametersOrBuilderpublic int 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];getMaxCutRoundsAtLevelZero in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMaxConsecutiveInactiveCount in interface SatParametersOrBuilderpublic int 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];getMaxConsecutiveInactiveCount in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasCutMaxActiveCountValue in interface SatParametersOrBuilderpublic double 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];getCutMaxActiveCountValue in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasCutActiveCountDecay()
optional double cut_active_count_decay = 156 [default = 0.8];hasCutActiveCountDecay in interface SatParametersOrBuilderpublic double getCutActiveCountDecay()
optional double cut_active_count_decay = 156 [default = 0.8];getCutActiveCountDecay in interface SatParametersOrBuilderpublic SatParameters.Builder setCutActiveCountDecay(double value)
optional double cut_active_count_decay = 156 [default = 0.8];value - The cutActiveCountDecay to set.public SatParameters.Builder clearCutActiveCountDecay()
optional double cut_active_count_decay = 156 [default = 0.8];public boolean hasCutCleanupTarget()
Target number of constraints to remove during cleanup.
optional int32 cut_cleanup_target = 157 [default = 1000];hasCutCleanupTarget in interface SatParametersOrBuilderpublic int getCutCleanupTarget()
Target number of constraints to remove during cleanup.
optional int32 cut_cleanup_target = 157 [default = 1000];getCutCleanupTarget in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearCutCleanupTarget()
Target number of constraints to remove during cleanup.
optional int32 cut_cleanup_target = 157 [default = 1000];public boolean 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];hasNewConstraintsBatchSize in interface SatParametersOrBuilderpublic int 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];getNewConstraintsBatchSize in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasExploitIntegerLpSolution in interface SatParametersOrBuilderpublic boolean 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];getExploitIntegerLpSolution in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasExploitAllLpSolution in interface SatParametersOrBuilderpublic boolean 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];getExploitAllLpSolution in interface SatParametersOrBuilderpublic 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.public 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];public boolean hasExploitBestSolution()
When branching on a variable, follow the last best solution value.
optional bool exploit_best_solution = 130 [default = false];hasExploitBestSolution in interface SatParametersOrBuilderpublic boolean getExploitBestSolution()
When branching on a variable, follow the last best solution value.
optional bool exploit_best_solution = 130 [default = false];getExploitBestSolution in interface SatParametersOrBuilderpublic 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.public SatParameters.Builder clearExploitBestSolution()
When branching on a variable, follow the last best solution value.
optional bool exploit_best_solution = 130 [default = false];public boolean 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];hasExploitRelaxationSolution in interface SatParametersOrBuilderpublic boolean 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];getExploitRelaxationSolution in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasExploitObjective in interface SatParametersOrBuilderpublic boolean 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];getExploitObjective in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasDetectLinearizedProduct in interface SatParametersOrBuilderpublic boolean 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];getDetectLinearizedProduct in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipMaxBound in interface SatParametersOrBuilderpublic double 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];getMipMaxBound in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipVarScaling in interface SatParametersOrBuilderpublic double 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];getMipVarScaling in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipScaleLargeDomain in interface SatParametersOrBuilderpublic boolean 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];getMipScaleLargeDomain in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipAutomaticallyScaleVariables in interface SatParametersOrBuilderpublic boolean 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];getMipAutomaticallyScaleVariables in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasOnlySolveIp in interface SatParametersOrBuilderpublic boolean 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];getOnlySolveIp in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipWantedPrecision in interface SatParametersOrBuilderpublic double 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];getMipWantedPrecision in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipMaxActivityExponent in interface SatParametersOrBuilderpublic int 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];getMipMaxActivityExponent in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipCheckPrecision in interface SatParametersOrBuilderpublic double 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];getMipCheckPrecision in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipComputeTrueObjectiveBound in interface SatParametersOrBuilderpublic boolean 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];getMipComputeTrueObjectiveBound in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipMaxValidMagnitude in interface SatParametersOrBuilderpublic double 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];getMipMaxValidMagnitude in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipTreatHighMagnitudeBoundsAsInfinity in interface SatParametersOrBuilderpublic boolean 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];getMipTreatHighMagnitudeBoundsAsInfinity in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipDropTolerance in interface SatParametersOrBuilderpublic double 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];getMipDropTolerance in interface SatParametersOrBuilderpublic 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.public 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];public boolean 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];hasMipPresolveLevel in interface SatParametersOrBuilderpublic int 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];getMipPresolveLevel in interface SatParametersOrBuilderpublic 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.public 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];Copyright © 2024. All rights reserved.