Class SatParameters.Builder
java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<SatParameters.Builder>
com.google.protobuf.GeneratedMessage.Builder<SatParameters.Builder>
com.google.ortools.sat.SatParameters.Builder
- All Implemented Interfaces:
SatParametersOrBuilder,com.google.protobuf.Message.Builder,com.google.protobuf.MessageLite.Builder,com.google.protobuf.MessageLiteOrBuilder,com.google.protobuf.MessageOrBuilder,Cloneable
- Enclosing class:
SatParameters
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: 325Protobuf type
operations_research.sat.SatParameters-
Method Summary
Modifier and TypeMethodDescriptionaddAllExtraSubsolvers(Iterable<String> values) A convenient way to add more workers types.addAllFilterSubsolvers(Iterable<String> values) repeated string filter_subsolvers = 293;addAllIgnoreSubsolvers(Iterable<String> values) Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing.addAllRestartAlgorithms(Iterable<? extends SatParameters.RestartAlgorithm> values) The restart strategies will change each time the strategy_counter is increased.addAllSubsolverParams(Iterable<? extends SatParameters> values) It is possible to specify additional subsolver configuration.addAllSubsolvers(Iterable<String> values) In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters.addExtraSubsolvers(String value) A convenient way to add more workers types.addExtraSubsolversBytes(com.google.protobuf.ByteString value) A convenient way to add more workers types.addFilterSubsolvers(String value) repeated string filter_subsolvers = 293;addFilterSubsolversBytes(com.google.protobuf.ByteString value) repeated string filter_subsolvers = 293;addIgnoreSubsolvers(String value) Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing.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 or only keep specific ones for testing.The restart strategies will change each time the strategy_counter is increased.addSubsolverParams(int index, SatParameters value) It is possible to specify additional subsolver configuration.addSubsolverParams(int index, SatParameters.Builder builderForValue) It is possible to specify additional subsolver configuration.addSubsolverParams(SatParameters value) It is possible to specify additional subsolver configuration.addSubsolverParams(SatParameters.Builder builderForValue) It is possible to specify additional subsolver configuration.It is possible to specify additional subsolver configuration.addSubsolverParamsBuilder(int index) It is possible to specify additional subsolver configuration.addSubsolvers(String value) In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters.addSubsolversBytes(com.google.protobuf.ByteString value) In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters.build()clear()Stop the search when the gap between the best feasible objective (O) and our best objective bound (B) is smaller than a limit.Whether we generate and add Chvatal-Gomory cuts to the LP at root node.Whether we generate clique cuts from the binary implication graph.For the lin max constraints, generates the cuts described in "Strong mixed-integer programming formulations for trained neural networks" by Ross Anderson et.If true, we start by an empty LP, and only add constraints not satisfied by the current LP solution batch by batch.Whether we generate MIR cuts at root node.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?Whether we generate RLT cuts.Whether we generate Zero-Half cuts at root node.When this is true, then the variables that appear in any of the reason of the variables in a conflict have their activity bumped.All at_most_one constraints with a size <= param will be replaced by a quadratic number of binary implications.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.optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];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.optional double blocking_restart_multiplier = 66 [default = 1.4];optional int32 blocking_restart_window_size = 65 [default = 5000];A non-negative level indicating how much we should try to fully encode Integer variables as Boolean.Indicates if the CP-SAT layer should catch Control-C (SIGINT) signals when calling solve.Clause activity parameters (same effect as the one on the variables).All the clauses with a LBD (literal blocks distance) lower or equal to this parameters will always be kept.optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];Trigger a cleanup when this number of "deletable" clauses is learned.optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];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.During a cleanup, we will always keep that number of "deletable" clauses.Temporary flag util the feature is more mature.If positive, we spend some effort on each core: - At level 1, we use a simple heuristic to try to minimize an UNSAT coreWhether or not the assumption levels are taken into account during the LBD computation.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.Whether we presolve the cp_model before solving it.How much effort do we spend on probing. 0 disables it completely.Whether we also use the sat presolve when cp_model_presolve is true.optional double cut_active_count_decay = 156 [default = 0.8];Target number of constraints to remove during cleanup.Control the global cut effort.These parameters are similar to sat clause management activity parameters.Crash if presolve breaks a feasible hint.Crash if we do not manage to complete the hint into a full solution.If positive, try to stop just after that many presolve rules have been applied.We have two different postsolve code.optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];Infer products of Boolean or of Boolean time IntegerVariable from the linear constrainst in the problem.If true, we detect variable that are unique to a table constraint and only there to encode a cost on each tuple.If true, it disable all constraint expansion.If true, registers more lns subsolvers with different parameters.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.Encore cumulative with fixed demands and capacity as a reservoir constraint.Whether we enumerate all solutions of a problem without objective.If true, expand all_different constraints that are not permutations.If true, expand the reservoir constraints by creating booleans for all possible precedences between event and encoding the constraint.Mainly useful for testing.If true and the Lp relaxation of the problem has a solution, try to exploit it.optional bool exploit_all_precedences = 220 [default = false];When branching on a variable, follow the last best solution value.If true and the Lp relaxation of the problem has an integer optimal solution, try to exploit it.When branching an a variable that directly affect the objective, branch on the value that lead to the best objective first.When branching on a variable, follow the last best relaxation solution value.A convenient way to add more workers types.How much dtime for each LS batch.On each restart, we randomly choose if we use decay (with this parameter) or no decay.When stagnating, feasibility jump will either restart from a default solution (with some possible randomization), or randomly pertubate the current solution.How much do we linearize the problem in the local search code.Maximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion.This is a factor that directly influence the work before each restart.Max distance between the default value and the pertubated value relative to the range of the domain of the variable.Probability for a variable to have a non default value upon restarts or perturbations.If true, the final response addition_solutions field will be filled with all solutions from our solutions pool.If true, add information about the derived variable domains to the CpSolverResponse.Internal parameter.repeated string filter_subsolvers = 293;Try to find large "rectangle" in the linear constraint matrix with identical lines.Whether we try to find more independent cores for a given set of assumptions in the core based max-SAT algorithms.If true, variables appearing in the solution hints will be fixed to their hinted value.optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];optional double glucose_decay_increment = 23 [default = 0.01];optional int32 glucose_decay_increment_period = 24 [default = 5000];The activity starts at 0.8 and increment by 0.01 every 5000 conflicts until 0.95.Conflict limit used in the phase that exploit the solution hint.If true, we don't keep names in our internal copy of the user given model.Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing.Run a max-clique code amongst all the x !optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];The initial value of the variables activity.Proportion of deterministic time we should spend on inprocessing.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.optional bool inprocessing_minimization_use_all_orderings = 298 [default = false];optional bool inprocessing_minimization_use_conflict_analysis = 297 [default = true];The amount of dtime we should spend on probing for each inprocessing round.If true, the solver will add a default integer branching strategy to the already defined search strategy.optional int32 interleave_batch_size = 134 [default = 0];Experimental.If true, we disable the presolve reductions that remove feasible solutions from the search space.Experimental.Only use lb-relax if we have at least that many workers.A non-negative level indicating the type of constraints we consider in the LP relaxation.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 double lns_initial_deterministic_limit = 308 [default = 0.1];Initial parameters for neighborhood generation.Add a prefix to all logs.Whether the solver should log the search progress.Whether the solver should display per sub-solver search statistics.Log to response proto.Log to stdout.optional double lp_dual_tolerance = 267 [default = 1e-07];The internal LP tolerances used by CP-SAT.Cut generator for all diffs can add too many cuts for large all_diff constraints.Max domain size for all_different constraints to be expanded.optional double max_clause_activity_value = 18 [default = 1e+20];If a constraint/cut in LP is not active for that many consecutive OPTIMAL solves, remove it from the LP.Max number of time we perform cut generation and resolve the LP at level 0.Maximum time allowed in deterministic time to solve a problem.When loading a*x + b*y ==/!Detects when the space where items of a no_overlap_2d constraint can placed is disjoint (ie., fixed boxes split the domain).In the integer rounding procedure used for MIR and Gomory cut, the maximum "scaling" we use (must be positive).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.Maximum memory allowed for the whole thread containing the solver.Maximum number of conflicts allowed to solve a problem.The limit on the number of cuts in our cut pool.Stops after that number of batches has been scheduled.Max number of intervals for the timetable_edge_finding algorithm to propagate.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.In case of large reduction in a presolve iteration, we perform multiple presolve iterations.optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];If true, adds the assumption in the reverse order of the one defined by max_sat_assumption_order.optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];Create one literal for each disjunction of two pairs of tasks.Maximum time allowed in seconds to solve a problem.optional double max_variable_activity_value = 16 [default = 1e+100];optional double merge_at_most_one_work_limit = 146 [default = 100000000];During presolve, we use a maximum clique heuristic to merge together no-overlap constraints or at most one constraints.optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];A different algorithm during PB resolution.Minimize and detect subsumption of shared clauses immediately after they are imported.While adding constraints, skip the constraints which have orthogonality less than 'min_orthogonality_for_lp_constraints' with already added constraints during current call.If true, some continuous variable might be automatically scaled.As explained in mip_precision and mip_max_activity_exponent, we cannot always reach the wanted precision during scaling.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.Any value in the input mip with a magnitude lower than this will be set to zero.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.We need to bound the maximum magnitude of the variables for CP-SAT, and that is the bound we use.Any finite values in the input MIP must be below this threshold, otherwise the model will be reported invalid.When solving a MIP, we do some basic floating point presolving before scaling the problem to integer to be handled by CP-SAT.If this is false, then mip_var_scaling is only applied to variables with "small" domain.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.All continuous variable of the problem will be multiplied by this factor.When scaling constraint with double coefficients to integer coefficients, we will multiply by a power of 2 and round the coefficients.In some context, like in a portfolio of search, it makes sense to name a given parameters set for logging purpose.Add that many lazy constraints (or cuts) at once in the LP.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.If less than this number of boxes are present in a no-overlap 2d, we create 4 Booleans per pair of boxes: - Box 2 is after Box 1 on xAfter 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.We distinguish subsolvers that consume a full thread, and the ones that are always interleaved.optional int32 num_search_workers = 100 [default = 0];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.Specify the number of parallel workers (i.e. threads) to use during search.For the cut that can be generated at any level, this control if we only try to generate them at the root node.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.The default optimization method is a simple "linear scan", each time trying to find a better solution than the previous one.Do a more conventional tree search (by opposition to SAT based one) where we keep all the explored node in a tree.This has no effect if optimize_with_core is false.Same as for the clauses, but for the learned pseudo-Boolean constraints.optional double pb_cleanup_ratio = 47 [default = 0.5];optional bool permute_presolve_constraint_order = 179 [default = false];This is mainly here to test the solver variability.If true and we have first solution LS workers, tries in some phase to follow a LS solutions that violates has litle constraints as possible.If non-zero, then we change the polarity heuristic after that many number of conflicts in an arithmetically increasing fashion.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.optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];Whether we use an heuristic to detect some basic case of blocked clause in the SAT presolve.Apply Bounded Variable Addition (BVA) if the number of clauses is reduced by stricly more than this threshold.During presolve, we apply BVE only if this weight times the number of clauses plus the number of clause literals is not increased.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.If true, we will extract from linear constraints, enforcement literals of the form "integer variable at bound => simplified constraint".A few presolve operations involve detecting constraints included in other constraint.optional double presolve_probing_deterministic_time_limit = 57 [default = 30];How much substitution (also called free variable aggregation in MIP litterature) should we perform at presolve.Whether or not we use Bounded Variable Addition (BVA) in the presolve.The maximum "deterministic" time limit to spend in probing.How many combinations of pairs or triplets of variables we want to scan.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.The solver ignores the pseudo costs of variables with number of recordings less than this threshold.Experimental code: specify if the objective pushes all tasks toward the start of the schedule.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.Randomize fixed search.The proportion of polarity chosen at random.At the beginning of each solve, the random number generator used in some part of the solver is reinitialized to this seed.optional double relative_gap_limit = 160 [default = 0];If cp_model_presolve is true and there is a large proportion of fixed variable after the first model copy, remap all the model to a dense set of variable before the full presolve even starts.If true, the solver tries to repair the solution given in the hint.The restart strategies will change each time the strategy_counter is increased.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_lbd_average_ratio = 71 [default = 1];Restart period for the FIXED_RESTART strategy.Size of the window for the moving average restarts.Even at the root node, we do not want to spend too much time on the LP if it is "difficult".The amount of "effort" to spend in dynamic programming for computing routing cuts.If the length of an infeasible path is less than this value, a cut will be added to exclude it.If the size of a subset of nodes of a RoutesConstraint is less than this value, use linear constraints of size 1 and 2 (such as capacity and time window constraints) enforced by the arc literals to compute cuts for this subset (unless the subset size is less than routing_cut_subset_size_for_tight_binary_relation_bound, in which case the corresponding algorithm is used instead).Similar to above, but with an even stronger algorithm in O(n!).Similar to routing_cut_subset_size_for_exact_binary_relation_bound but use a bound based on shortest path distances (which respect triangular inequality).Similar to above, but with a different algorithm producing better cuts, at the price of a higher O(2^n) complexity, where n is the subset size.Experimental.optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];Search randomization will collect the top 'search_random_variable_pool_size' valued variables, and pick one randomly.Allows sharing of new learned binary clause between workers.How much deeper compared to the ideal max depth of the tree is considered "balanced" enough to still accept a split.In order to limit total shared memory and communication overhead, limit the total number of nodes that may be generated in the shared tree.Enables shared tree search.How many open leaf nodes should the shared tree maintain per worker.optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];If true, shared tree workers share their target phase when returning an assigned subtree for the next worker to use.If true, workers share more of the information from their local trail.Minimum restarts before a worker will replace a subtree that looks "bad" based on the average LBD of learned clauses.Allows sharing of short glue clauses between workers.The amount of dtime between each export of shared glue clauses.Allows sharing of the bounds of modified variables at level 0.Allows objective sharing between workers.Add a shaving phase (where the solver tries to prove that the lower or upper bound of a variable are infeasible) to the probing searchSpecifies the amount of deterministic time spent of each try at shaving a bound in the shaving search.Specifies the threshold between two modes in the shaving procedure.Size of the top-n different solutions kept by the solver.For an optimization problem, stop the solver as soon as we have a solution.Mainly used when improving the presolver.optional bool stop_after_root_propagation = 252 [default = false];The parameter num_conflicts_before_strategy_changes is increased by that much after each strategy change.It is possible to specify additional subsolver configuration.In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters.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.Deterministic time limit for symmetry detection.Whether we try to automatically detect the symmetries in a model and exploit them.How much we try to "compress" a table constraint.optional bool use_absl_random = 180 [default = false];Turn on extra propagation for the circuit constraint.When this is true, the no_overlap_2d constraint is reinforced with an energetic reasoning that uses an area-based energy.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.This can be beneficial if there is a lot of no-overlap constraints but a relatively low number of different intervals in the problem.Enable a heuristic to solve cumulative constraints using a modified energy constraint.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.When set, it activates a few scheduling parameters to improve the lower bound of scheduling problems.optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];Whether we try to branch on decision "interval A before interval B" rather than on intervals bounds.When this is true, the no_overlap_2d constraint is reinforced with energetic reasoning.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.The solver usually exploit the LP relaxation of a model.Use extended probing (probe bool_or, at_most_one, exactly_one).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.Adds a feasibility pump subsolver along with lns subsolvers.If true, detect and create constraint for integer variable that are "after" a set of intervals in the same cumulative constraint.Stores and exploits "implied-bounds" in the solver.Turns on neighborhood generator based on local branching LP.When set, this activates a propagator for the no_overlap_2d constraint that uses any eventual linear constraints of the model in the form `{start interval 1} - {end interval 2} + c*w <= ub` to detect that two intervals must overlap in one dimension for some values of `w`.Testing parameters used to disable all lns workers.Experimental parameters to disable everything but lns.Disable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.If true, search will search in ascending max objective value (when minimizing) starting from the lower bound of the objective.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.For an optimization problem, whether we follow some hints in order to find a better first solution.If true, we automatically detect variables whose constraint are always enforced by the same literal and we mark them as optional.When this is true, the cumulative constraint is reinforced with overload checking, i.e., an additional level of reasoning based on energy.Whether to use pseudo-Boolean resolution to analyze a conflict.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().When this is true, then a disjunctive constraint will try to use the precedence relations between time intervals to propagate their bounds further.If true, search will continuously probe Boolean variables, and integer variable bounds.Turns on relaxation induced neighborhood generator.Enable or disable "inprocessing" which is some SAT presolving done at each restart to the root level.Set on shared subtree workers.Enable stronger and more expensive propagation on no_overlap constraint.When we have symmetry, it is possible to "fold" all variables from the same orbit into a single variable, while having the same power of LP relaxation.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.When this is true, the no_overlap_2d constraint is reinforced with propagators from the cumulative constraints.optional bool use_try_edge_reasoning_in_no_overlap_2d = 299 [default = false];Each time a conflict is found, the activities of some variables are increased by one.This search takes all Boolean or integer variables, and maximize or minimize them in order to reduce their domain. -1 is automatic, otherwise value 0 disables it, and 1, 2, or 3 changes something.Probability of using compound move search each restart.How long violation_ls should wait before perturbating a solution.doubleStop the search when the gap between the best feasible objective (O) and our best objective bound (B) is smaller than a limit.booleanWhether we generate and add Chvatal-Gomory cuts to the LP at root node.booleanWhether we generate clique cuts from the binary implication graph.booleanFor the lin max constraints, generates the cuts described in "Strong mixed-integer programming formulations for trained neural networks" by Ross Anderson et.booleanIf true, we start by an empty LP, and only add constraints not satisfied by the current LP solution batch by batch.booleanWhether we generate MIR cuts at root node.booleanWhen 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?booleanWhether we generate RLT cuts.booleanWhether we generate Zero-Half cuts at root node.booleanWhen this is true, then the variables that appear in any of the reason of the variables in a conflict have their activity bumped.intAll at_most_one constraints with a size <= param will be replaced by a quadratic number of binary implications.booleanIf 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.optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];intIf 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.doubleoptional double blocking_restart_multiplier = 66 [default = 1.4];intoptional int32 blocking_restart_window_size = 65 [default = 5000];intA non-negative level indicating how much we should try to fully encode Integer variables as Boolean.booleanIndicates if the CP-SAT layer should catch Control-C (SIGINT) signals when calling solve.doubleClause activity parameters (same effect as the one on the variables).intAll the clauses with a LBD (literal blocks distance) lower or equal to this parameters will always be kept.optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];intTrigger a cleanup when this number of "deletable" clauses is learned.optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];doubleDuring 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.intDuring a cleanup, we will always keep that number of "deletable" clauses.booleanTemporary flag util the feature is more mature.intIf positive, we spend some effort on each core: - At level 1, we use a simple heuristic to try to minimize an UNSAT corebooleanWhether or not the assumption levels are taken into account during the LBD computation.booleanIf 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.booleanWhether we presolve the cp_model before solving it.intHow much effort do we spend on probing. 0 disables it completely.booleanWhether we also use the sat presolve when cp_model_presolve is true.doubleoptional double cut_active_count_decay = 156 [default = 0.8];intTarget number of constraints to remove during cleanup.intControl the global cut effort.doubleThese parameters are similar to sat clause management activity parameters.booleanCrash if presolve breaks a feasible hint.booleanCrash if we do not manage to complete the hint into a full solution.intIf positive, try to stop just after that many presolve rules have been applied.booleanWe have two different postsolve code.optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];com.google.protobuf.ByteStringoptional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];static final com.google.protobuf.Descriptors.Descriptorcom.google.protobuf.Descriptors.DescriptorbooleanInfer products of Boolean or of Boolean time IntegerVariable from the linear constrainst in the problem.booleanIf true, we detect variable that are unique to a table constraint and only there to encode a cost on each tuple.booleanIf true, it disable all constraint expansion.booleanIf true, registers more lns subsolvers with different parameters.booleanLinear 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.booleanEncore cumulative with fixed demands and capacity as a reservoir constraint.booleanWhether we enumerate all solutions of a problem without objective.booleanIf true, expand all_different constraints that are not permutations.booleanIf true, expand the reservoir constraints by creating booleans for all possible precedences between event and encoding the constraint.booleanMainly useful for testing.booleanIf true and the Lp relaxation of the problem has a solution, try to exploit it.booleanoptional bool exploit_all_precedences = 220 [default = false];booleanWhen branching on a variable, follow the last best solution value.booleanIf true and the Lp relaxation of the problem has an integer optimal solution, try to exploit it.booleanWhen branching an a variable that directly affect the objective, branch on the value that lead to the best objective first.booleanWhen branching on a variable, follow the last best relaxation solution value.getExtraSubsolvers(int index) A convenient way to add more workers types.com.google.protobuf.ByteStringgetExtraSubsolversBytes(int index) A convenient way to add more workers types.intA convenient way to add more workers types.com.google.protobuf.ProtocolStringListA convenient way to add more workers types.doubleHow much dtime for each LS batch.doubleOn each restart, we randomly choose if we use decay (with this parameter) or no decay.booleanWhen stagnating, feasibility jump will either restart from a default solution (with some possible randomization), or randomly pertubate the current solution.intHow much do we linearize the problem in the local search code.intMaximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion.intThis is a factor that directly influence the work before each restart.doubleMax distance between the default value and the pertubated value relative to the range of the domain of the variable.doubleProbability for a variable to have a non default value upon restarts or perturbations.booleanIf true, the final response addition_solutions field will be filled with all solutions from our solutions pool.booleanIf true, add information about the derived variable domains to the CpSolverResponse.booleanInternal parameter.getFilterSubsolvers(int index) repeated string filter_subsolvers = 293;com.google.protobuf.ByteStringgetFilterSubsolversBytes(int index) repeated string filter_subsolvers = 293;intrepeated string filter_subsolvers = 293;com.google.protobuf.ProtocolStringListrepeated string filter_subsolvers = 293;booleanTry to find large "rectangle" in the linear constraint matrix with identical lines.booleanWhether we try to find more independent cores for a given set of assumptions in the core based max-SAT algorithms.booleanIf true, variables appearing in the solution hints will be fixed to their hinted value.optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];doubleoptional double glucose_decay_increment = 23 [default = 0.01];intoptional int32 glucose_decay_increment_period = 24 [default = 5000];doubleThe activity starts at 0.8 and increment by 0.01 every 5000 conflicts until 0.95.intConflict limit used in the phase that exploit the solution hint.booleanIf true, we don't keep names in our internal copy of the user given model.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 or only keep specific ones for testing.com.google.protobuf.ByteStringgetIgnoreSubsolversBytes(int index) Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing.intRather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing.com.google.protobuf.ProtocolStringListRather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing.booleanRun a max-clique code amongst all the x !optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];doubleThe initial value of the variables activity.doubleProportion of deterministic time we should spend on inprocessing.doubleParameters 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.booleanoptional bool inprocessing_minimization_use_all_orderings = 298 [default = false];booleanoptional bool inprocessing_minimization_use_conflict_analysis = 297 [default = true];doubleThe amount of dtime we should spend on probing for each inprocessing round.booleanIf true, the solver will add a default integer branching strategy to the already defined search strategy.intoptional int32 interleave_batch_size = 134 [default = 0];booleanExperimental.booleanIf true, we disable the presolve reductions that remove feasible solutions from the search space.booleanExperimental.intOnly use lb-relax if we have at least that many workers.intA non-negative level indicating the type of constraints we consider in the LP relaxation.intLinear 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.doubleoptional double lns_initial_deterministic_limit = 308 [default = 0.1];doubleInitial parameters for neighborhood generation.Add a prefix to all logs.com.google.protobuf.ByteStringAdd a prefix to all logs.booleanWhether the solver should log the search progress.booleanWhether the solver should display per sub-solver search statistics.booleanLog to response proto.booleanLog to stdout.doubleoptional double lp_dual_tolerance = 267 [default = 1e-07];doubleThe internal LP tolerances used by CP-SAT.intCut generator for all diffs can add too many cuts for large all_diff constraints.intMax domain size for all_different constraints to be expanded.doubleoptional double max_clause_activity_value = 18 [default = 1e+20];intIf a constraint/cut in LP is not active for that many consecutive OPTIMAL solves, remove it from the LP.intMax number of time we perform cut generation and resolve the LP at level 0.doubleMaximum time allowed in deterministic time to solve a problem.intWhen loading a*x + b*y ==/!intDetects when the space where items of a no_overlap_2d constraint can placed is disjoint (ie., fixed boxes split the domain).intIn the integer rounding procedure used for MIR and Gomory cut, the maximum "scaling" we use (must be positive).intIf 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.longMaximum memory allowed for the whole thread containing the solver.longMaximum number of conflicts allowed to solve a problem.intThe limit on the number of cuts in our cut pool.intStops after that number of batches has been scheduled.intMax number of intervals for the timetable_edge_finding algorithm to propagate.intIf 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.intIn case of large reduction in a presolve iteration, we perform multiple presolve iterations.optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];booleanIf true, adds the assumption in the reverse order of the one defined by max_sat_assumption_order.optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];intCreate one literal for each disjunction of two pairs of tasks.doubleMaximum time allowed in seconds to solve a problem.doubleoptional double max_variable_activity_value = 16 [default = 1e+100];doubleoptional double merge_at_most_one_work_limit = 146 [default = 100000000];doubleDuring presolve, we use a maximum clique heuristic to merge together no-overlap constraints or at most one constraints.optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];booleanA different algorithm during PB resolution.booleanMinimize and detect subsumption of shared clauses immediately after they are imported.doubleWhile adding constraints, skip the constraints which have orthogonality less than 'min_orthogonality_for_lp_constraints' with already added constraints during current call.booleanIf true, some continuous variable might be automatically scaled.doubleAs explained in mip_precision and mip_max_activity_exponent, we cannot always reach the wanted precision during scaling.booleanEven 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.doubleAny value in the input mip with a magnitude lower than this will be set to zero.intTo 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.doubleWe need to bound the maximum magnitude of the variables for CP-SAT, and that is the bound we use.doubleAny finite values in the input MIP must be below this threshold, otherwise the model will be reported invalid.intWhen solving a MIP, we do some basic floating point presolving before scaling the problem to integer to be handled by CP-SAT.booleanIf this is false, then mip_var_scaling is only applied to variables with "small" domain.booleanBy 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.doubleAll continuous variable of the problem will be multiplied by this factor.doubleWhen scaling constraint with double coefficients to integer coefficients, we will multiply by a power of 2 and round the coefficients.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.ByteStringIn some context, like in a portfolio of search, it makes sense to name a given parameters set for logging purpose.intAdd that many lazy constraints (or cuts) at once in the LP.booleanThe 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.intIf less than this number of boxes are present in a no-overlap 2d, we create 4 Booleans per pair of boxes: - Box 2 is after Box 1 on xintAfter 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.intWe distinguish subsolvers that consume a full thread, and the ones that are always interleaved.intoptional int32 num_search_workers = 100 [default = 0];intThis 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.intSpecify the number of parallel workers (i.e. threads) to use during search.booleanFor the cut that can be generated at any level, this control if we only try to generate them at the root node.booleanIf 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.booleanThe default optimization method is a simple "linear scan", each time trying to find a better solution than the previous one.booleanDo a more conventional tree search (by opposition to SAT based one) where we keep all the explored node in a tree.booleanThis has no effect if optimize_with_core is false.intSame as for the clauses, but for the learned pseudo-Boolean constraints.doubleoptional double pb_cleanup_ratio = 47 [default = 0.5];booleanoptional bool permute_presolve_constraint_order = 179 [default = false];booleanThis is mainly here to test the solver variability.booleanIf true and we have first solution LS workers, tries in some phase to follow a LS solutions that violates has litle constraints as possible.intIf non-zero, then we change the polarity heuristic after that many number of conflicts in an arithmetically increasing fashion.booleanWhether 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.optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];booleanWhether we use an heuristic to detect some basic case of blocked clause in the SAT presolve.intApply Bounded Variable Addition (BVA) if the number of clauses is reduced by stricly more than this threshold.intDuring presolve, we apply BVE only if this weight times the number of clauses plus the number of clause literals is not increased.intDuring 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.booleanIf true, we will extract from linear constraints, enforcement literals of the form "integer variable at bound => simplified constraint".longA few presolve operations involve detecting constraints included in other constraint.doubleoptional double presolve_probing_deterministic_time_limit = 57 [default = 30];intHow much substitution (also called free variable aggregation in MIP litterature) should we perform at presolve.booleanWhether or not we use Bounded Variable Addition (BVA) in the presolve.doubleThe maximum "deterministic" time limit to spend in probing.intHow many combinations of pairs or triplets of variables we want to scan.doubleSome 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.longThe solver ignores the pseudo costs of variables with number of recordings less than this threshold.booleanExperimental code: specify if the objective pushes all tasks toward the start of the schedule.doubleA 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.booleanRandomize fixed search.doubleThe proportion of polarity chosen at random.intAt the beginning of each solve, the random number generator used in some part of the solver is reinitialized to this seed.doubleoptional double relative_gap_limit = 160 [default = 0];booleanIf cp_model_presolve is true and there is a large proportion of fixed variable after the first model copy, remap all the model to a dense set of variable before the full presolve even starts.booleanIf true, the solver tries to repair the solution given in the hint.getRestartAlgorithms(int index) The restart strategies will change each time the strategy_counter is increased.intThe restart strategies will change each time the strategy_counter is increased.The restart strategies will change each time the strategy_counter is increased.doubleIn the moving average restart algorithms, a restart is triggered if the window average times this ratio is greater that the global average.doubleoptional double restart_lbd_average_ratio = 71 [default = 1];intRestart period for the FIXED_RESTART strategy.intSize of the window for the moving average restarts.intEven at the root node, we do not want to spend too much time on the LP if it is "difficult".doubleThe amount of "effort" to spend in dynamic programming for computing routing cuts.intIf the length of an infeasible path is less than this value, a cut will be added to exclude it.intIf the size of a subset of nodes of a RoutesConstraint is less than this value, use linear constraints of size 1 and 2 (such as capacity and time window constraints) enforced by the arc literals to compute cuts for this subset (unless the subset size is less than routing_cut_subset_size_for_tight_binary_relation_bound, in which case the corresponding algorithm is used instead).intSimilar to above, but with an even stronger algorithm in O(n!).intSimilar to routing_cut_subset_size_for_exact_binary_relation_bound but use a bound based on shortest path distances (which respect triangular inequality).intSimilar to above, but with a different algorithm producing better cuts, at the price of a higher O(2^n) complexity, where n is the subset size.booleanExperimental.optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];longSearch randomization will collect the top 'search_random_variable_pool_size' valued variables, and pick one randomly.booleanAllows sharing of new learned binary clause between workers.intHow much deeper compared to the ideal max depth of the tree is considered "balanced" enough to still accept a split.intIn order to limit total shared memory and communication overhead, limit the total number of nodes that may be generated in the shared tree.intEnables shared tree search.doubleHow many open leaf nodes should the shared tree maintain per worker.optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];booleanIf true, shared tree workers share their target phase when returning an assigned subtree for the next worker to use.booleanIf true, workers share more of the information from their local trail.intMinimum restarts before a worker will replace a subtree that looks "bad" based on the average LBD of learned clauses.booleanAllows sharing of short glue clauses between workers.doubleThe amount of dtime between each export of shared glue clauses.booleanAllows sharing of the bounds of modified variables at level 0.booleanAllows objective sharing between workers.doubleAdd a shaving phase (where the solver tries to prove that the lower or upper bound of a variable are infeasible) to the probing searchdoubleSpecifies the amount of deterministic time spent of each try at shaving a bound in the shaving search.longSpecifies the threshold between two modes in the shaving procedure.intSize of the top-n different solutions kept by the solver.booleanFor an optimization problem, stop the solver as soon as we have a solution.booleanMainly used when improving the presolver.booleanoptional bool stop_after_root_propagation = 252 [default = false];doubleThe parameter num_conflicts_before_strategy_changes is increased by that much after each strategy change.getSubsolverParams(int index) It is possible to specify additional subsolver configuration.getSubsolverParamsBuilder(int index) It is possible to specify additional subsolver configuration.It is possible to specify additional subsolver configuration.intIt is possible to specify additional subsolver configuration.It is possible to specify additional subsolver configuration.getSubsolverParamsOrBuilder(int index) It is possible to specify additional subsolver configuration.List<? extends SatParametersOrBuilder> It is possible to specify additional subsolver configuration.getSubsolvers(int index) In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters.com.google.protobuf.ByteStringgetSubsolversBytes(int index) In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters.intIn multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters.com.google.protobuf.ProtocolStringListIn multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters.booleanAt 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.doubleDeterministic time limit for symmetry detection.intWhether we try to automatically detect the symmetries in a model and exploit them.intHow much we try to "compress" a table constraint.booleanoptional bool use_absl_random = 180 [default = false];booleanTurn on extra propagation for the circuit constraint.booleanWhen this is true, the no_overlap_2d constraint is reinforced with an energetic reasoning that uses an area-based energy.booleanBlock 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.booleanThis can be beneficial if there is a lot of no-overlap constraints but a relatively low number of different intervals in the problem.booleanEnable a heuristic to solve cumulative constraints using a modified energy constraint.booleanWhen 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.booleanWhen set, it activates a few scheduling parameters to improve the lower bound of scheduling problems.booleanoptional bool use_dynamic_precedence_in_cumulative = 268 [default = false];booleanWhether we try to branch on decision "interval A before interval B" rather than on intervals bounds.booleanWhen this is true, the no_overlap_2d constraint is reinforced with energetic reasoning.booleanWhether we use the ERWA (Exponential Recency Weighted Average) heuristic as described in "Learning Rate Based Branching Heuristic for SAT solvers", J.H.Liang, V.booleanThe solver usually exploit the LP relaxation of a model.booleanUse extended probing (probe bool_or, at_most_one, exactly_one).booleanParameters 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.booleanAdds a feasibility pump subsolver along with lns subsolvers.booleanIf true, detect and create constraint for integer variable that are "after" a set of intervals in the same cumulative constraint.booleanStores and exploits "implied-bounds" in the solver.booleanTurns on neighborhood generator based on local branching LP.booleanWhen set, this activates a propagator for the no_overlap_2d constraint that uses any eventual linear constraints of the model in the form `{start interval 1} - {end interval 2} + c*w <= ub` to detect that two intervals must overlap in one dimension for some values of `w`.booleanTesting parameters used to disable all lns workers.booleanExperimental parameters to disable everything but lns.booleanDisable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.booleanIf true, search will search in ascending max objective value (when minimizing) starting from the lower bound of the objective.booleanThis 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.booleanFor an optimization problem, whether we follow some hints in order to find a better first solution.booleanIf true, we automatically detect variables whose constraint are always enforced by the same literal and we mark them as optional.booleanWhen this is true, the cumulative constraint is reinforced with overload checking, i.e., an additional level of reasoning based on energy.booleanWhether to use pseudo-Boolean resolution to analyze a conflict.booleanIf 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().booleanWhen this is true, then a disjunctive constraint will try to use the precedence relations between time intervals to propagate their bounds further.booleanIf true, search will continuously probe Boolean variables, and integer variable bounds.booleanTurns on relaxation induced neighborhood generator.booleanEnable or disable "inprocessing" which is some SAT presolving done at each restart to the root level.booleanSet on shared subtree workers.booleanEnable stronger and more expensive propagation on no_overlap constraint.booleanWhen we have symmetry, it is possible to "fold" all variables from the same orbit into a single variable, while having the same power of LP relaxation.booleanWhen 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.booleanWhen this is true, the no_overlap_2d constraint is reinforced with propagators from the cumulative constraints.booleanoptional bool use_try_edge_reasoning_in_no_overlap_2d = 299 [default = false];doubleEach time a conflict is found, the activities of some variables are increased by one.intThis search takes all Boolean or integer variables, and maximize or minimize them in order to reduce their domain. -1 is automatic, otherwise value 0 disables it, and 1, 2, or 3 changes something.doubleProbability of using compound move search each restart.intHow long violation_ls should wait before perturbating a solution.booleanStop the search when the gap between the best feasible objective (O) and our best objective bound (B) is smaller than a limit.booleanWhether we generate and add Chvatal-Gomory cuts to the LP at root node.booleanWhether we generate clique cuts from the binary implication graph.booleanFor the lin max constraints, generates the cuts described in "Strong mixed-integer programming formulations for trained neural networks" by Ross Anderson et.booleanIf true, we start by an empty LP, and only add constraints not satisfied by the current LP solution batch by batch.booleanWhether we generate MIR cuts at root node.booleanWhen 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?booleanWhether we generate RLT cuts.booleanWhether we generate Zero-Half cuts at root node.booleanWhen this is true, then the variables that appear in any of the reason of the variables in a conflict have their activity bumped.booleanAll at_most_one constraints with a size <= param will be replaced by a quadratic number of binary implications.booleanIf 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.booleanoptional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];booleanIf 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.booleanoptional double blocking_restart_multiplier = 66 [default = 1.4];booleanoptional int32 blocking_restart_window_size = 65 [default = 5000];booleanA non-negative level indicating how much we should try to fully encode Integer variables as Boolean.booleanIndicates if the CP-SAT layer should catch Control-C (SIGINT) signals when calling solve.booleanClause activity parameters (same effect as the one on the variables).booleanAll the clauses with a LBD (literal blocks distance) lower or equal to this parameters will always be kept.booleanoptional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];booleanTrigger a cleanup when this number of "deletable" clauses is learned.booleanoptional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];booleanDuring 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.booleanDuring a cleanup, we will always keep that number of "deletable" clauses.booleanTemporary flag util the feature is more mature.booleanIf positive, we spend some effort on each core: - At level 1, we use a simple heuristic to try to minimize an UNSAT corebooleanWhether or not the assumption levels are taken into account during the LBD computation.booleanIf 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.booleanWhether we presolve the cp_model before solving it.booleanHow much effort do we spend on probing. 0 disables it completely.booleanWhether we also use the sat presolve when cp_model_presolve is true.booleanoptional double cut_active_count_decay = 156 [default = 0.8];booleanTarget number of constraints to remove during cleanup.booleanControl the global cut effort.booleanThese parameters are similar to sat clause management activity parameters.booleanCrash if presolve breaks a feasible hint.booleanCrash if we do not manage to complete the hint into a full solution.booleanIf positive, try to stop just after that many presolve rules have been applied.booleanWe have two different postsolve code.booleanoptional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];booleanInfer products of Boolean or of Boolean time IntegerVariable from the linear constrainst in the problem.booleanIf true, we detect variable that are unique to a table constraint and only there to encode a cost on each tuple.booleanIf true, it disable all constraint expansion.booleanIf true, registers more lns subsolvers with different parameters.booleanLinear 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.booleanEncore cumulative with fixed demands and capacity as a reservoir constraint.booleanWhether we enumerate all solutions of a problem without objective.booleanIf true, expand all_different constraints that are not permutations.booleanIf true, expand the reservoir constraints by creating booleans for all possible precedences between event and encoding the constraint.booleanMainly useful for testing.booleanIf true and the Lp relaxation of the problem has a solution, try to exploit it.booleanoptional bool exploit_all_precedences = 220 [default = false];booleanWhen branching on a variable, follow the last best solution value.booleanIf true and the Lp relaxation of the problem has an integer optimal solution, try to exploit it.booleanWhen branching an a variable that directly affect the objective, branch on the value that lead to the best objective first.booleanWhen branching on a variable, follow the last best relaxation solution value.booleanHow much dtime for each LS batch.booleanOn each restart, we randomly choose if we use decay (with this parameter) or no decay.booleanWhen stagnating, feasibility jump will either restart from a default solution (with some possible randomization), or randomly pertubate the current solution.booleanHow much do we linearize the problem in the local search code.booleanMaximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion.booleanThis is a factor that directly influence the work before each restart.booleanMax distance between the default value and the pertubated value relative to the range of the domain of the variable.booleanProbability for a variable to have a non default value upon restarts or perturbations.booleanIf true, the final response addition_solutions field will be filled with all solutions from our solutions pool.booleanIf true, add information about the derived variable domains to the CpSolverResponse.booleanInternal parameter.booleanTry to find large "rectangle" in the linear constraint matrix with identical lines.booleanWhether we try to find more independent cores for a given set of assumptions in the core based max-SAT algorithms.booleanIf true, variables appearing in the solution hints will be fixed to their hinted value.booleanoptional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];booleanoptional double glucose_decay_increment = 23 [default = 0.01];booleanoptional int32 glucose_decay_increment_period = 24 [default = 5000];booleanThe activity starts at 0.8 and increment by 0.01 every 5000 conflicts until 0.95.booleanConflict limit used in the phase that exploit the solution hint.booleanIf true, we don't keep names in our internal copy of the user given model.booleanRun a max-clique code amongst all the x !booleanoptional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];booleanThe initial value of the variables activity.booleanProportion of deterministic time we should spend on inprocessing.booleanParameters 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.booleanoptional bool inprocessing_minimization_use_all_orderings = 298 [default = false];booleanoptional bool inprocessing_minimization_use_conflict_analysis = 297 [default = true];booleanThe amount of dtime we should spend on probing for each inprocessing round.booleanIf true, the solver will add a default integer branching strategy to the already defined search strategy.booleanoptional int32 interleave_batch_size = 134 [default = 0];booleanExperimental.booleanIf true, we disable the presolve reductions that remove feasible solutions from the search space.booleanExperimental.booleanOnly use lb-relax if we have at least that many workers.booleanA non-negative level indicating the type of constraints we consider in the LP relaxation.booleanLinear 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.booleanoptional double lns_initial_deterministic_limit = 308 [default = 0.1];booleanInitial parameters for neighborhood generation.booleanAdd a prefix to all logs.booleanWhether the solver should log the search progress.booleanWhether the solver should display per sub-solver search statistics.booleanLog to response proto.booleanLog to stdout.booleanoptional double lp_dual_tolerance = 267 [default = 1e-07];booleanThe internal LP tolerances used by CP-SAT.booleanCut generator for all diffs can add too many cuts for large all_diff constraints.booleanMax domain size for all_different constraints to be expanded.booleanoptional double max_clause_activity_value = 18 [default = 1e+20];booleanIf a constraint/cut in LP is not active for that many consecutive OPTIMAL solves, remove it from the LP.booleanMax number of time we perform cut generation and resolve the LP at level 0.booleanMaximum time allowed in deterministic time to solve a problem.booleanWhen loading a*x + b*y ==/!booleanDetects when the space where items of a no_overlap_2d constraint can placed is disjoint (ie., fixed boxes split the domain).booleanIn the integer rounding procedure used for MIR and Gomory cut, the maximum "scaling" we use (must be positive).booleanIf 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.booleanMaximum memory allowed for the whole thread containing the solver.booleanMaximum number of conflicts allowed to solve a problem.booleanThe limit on the number of cuts in our cut pool.booleanStops after that number of batches has been scheduled.booleanMax number of intervals for the timetable_edge_finding algorithm to propagate.booleanIf 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.booleanIn case of large reduction in a presolve iteration, we perform multiple presolve iterations.booleanoptional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];booleanIf true, adds the assumption in the reverse order of the one defined by max_sat_assumption_order.booleanoptional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];booleanCreate one literal for each disjunction of two pairs of tasks.booleanMaximum time allowed in seconds to solve a problem.booleanoptional double max_variable_activity_value = 16 [default = 1e+100];booleanoptional double merge_at_most_one_work_limit = 146 [default = 100000000];booleanDuring presolve, we use a maximum clique heuristic to merge together no-overlap constraints or at most one constraints.booleanoptional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];booleanA different algorithm during PB resolution.booleanMinimize and detect subsumption of shared clauses immediately after they are imported.booleanWhile adding constraints, skip the constraints which have orthogonality less than 'min_orthogonality_for_lp_constraints' with already added constraints during current call.booleanIf true, some continuous variable might be automatically scaled.booleanAs explained in mip_precision and mip_max_activity_exponent, we cannot always reach the wanted precision during scaling.booleanEven 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.booleanAny value in the input mip with a magnitude lower than this will be set to zero.booleanTo 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.booleanWe need to bound the maximum magnitude of the variables for CP-SAT, and that is the bound we use.booleanAny finite values in the input MIP must be below this threshold, otherwise the model will be reported invalid.booleanWhen solving a MIP, we do some basic floating point presolving before scaling the problem to integer to be handled by CP-SAT.booleanIf this is false, then mip_var_scaling is only applied to variables with "small" domain.booleanBy 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.booleanAll continuous variable of the problem will be multiplied by this factor.booleanWhen scaling constraint with double coefficients to integer coefficients, we will multiply by a power of 2 and round the coefficients.booleanhasName()In some context, like in a portfolio of search, it makes sense to name a given parameters set for logging purpose.booleanAdd that many lazy constraints (or cuts) at once in the LP.booleanThe 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.booleanIf less than this number of boxes are present in a no-overlap 2d, we create 4 Booleans per pair of boxes: - Box 2 is after Box 1 on xbooleanAfter 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.booleanWe distinguish subsolvers that consume a full thread, and the ones that are always interleaved.booleanoptional int32 num_search_workers = 100 [default = 0];booleanThis 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.booleanSpecify the number of parallel workers (i.e. threads) to use during search.booleanFor the cut that can be generated at any level, this control if we only try to generate them at the root node.booleanIf 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.booleanThe default optimization method is a simple "linear scan", each time trying to find a better solution than the previous one.booleanDo a more conventional tree search (by opposition to SAT based one) where we keep all the explored node in a tree.booleanThis has no effect if optimize_with_core is false.booleanSame as for the clauses, but for the learned pseudo-Boolean constraints.booleanoptional double pb_cleanup_ratio = 47 [default = 0.5];booleanoptional bool permute_presolve_constraint_order = 179 [default = false];booleanThis is mainly here to test the solver variability.booleanIf true and we have first solution LS workers, tries in some phase to follow a LS solutions that violates has litle constraints as possible.booleanIf non-zero, then we change the polarity heuristic after that many number of conflicts in an arithmetically increasing fashion.booleanWhether 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.booleanoptional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];booleanWhether we use an heuristic to detect some basic case of blocked clause in the SAT presolve.booleanApply Bounded Variable Addition (BVA) if the number of clauses is reduced by stricly more than this threshold.booleanDuring presolve, we apply BVE only if this weight times the number of clauses plus the number of clause literals is not increased.booleanDuring 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.booleanIf true, we will extract from linear constraints, enforcement literals of the form "integer variable at bound => simplified constraint".booleanA few presolve operations involve detecting constraints included in other constraint.booleanoptional double presolve_probing_deterministic_time_limit = 57 [default = 30];booleanHow much substitution (also called free variable aggregation in MIP litterature) should we perform at presolve.booleanWhether or not we use Bounded Variable Addition (BVA) in the presolve.booleanThe maximum "deterministic" time limit to spend in probing.booleanHow many combinations of pairs or triplets of variables we want to scan.booleanSome 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.booleanThe solver ignores the pseudo costs of variables with number of recordings less than this threshold.booleanExperimental code: specify if the objective pushes all tasks toward the start of the schedule.booleanA 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.booleanRandomize fixed search.booleanThe proportion of polarity chosen at random.booleanAt the beginning of each solve, the random number generator used in some part of the solver is reinitialized to this seed.booleanoptional double relative_gap_limit = 160 [default = 0];booleanIf cp_model_presolve is true and there is a large proportion of fixed variable after the first model copy, remap all the model to a dense set of variable before the full presolve even starts.booleanIf true, the solver tries to repair the solution given in the hint.booleanIn the moving average restart algorithms, a restart is triggered if the window average times this ratio is greater that the global average.booleanoptional double restart_lbd_average_ratio = 71 [default = 1];booleanRestart period for the FIXED_RESTART strategy.booleanSize of the window for the moving average restarts.booleanEven at the root node, we do not want to spend too much time on the LP if it is "difficult".booleanThe amount of "effort" to spend in dynamic programming for computing routing cuts.booleanIf the length of an infeasible path is less than this value, a cut will be added to exclude it.booleanIf the size of a subset of nodes of a RoutesConstraint is less than this value, use linear constraints of size 1 and 2 (such as capacity and time window constraints) enforced by the arc literals to compute cuts for this subset (unless the subset size is less than routing_cut_subset_size_for_tight_binary_relation_bound, in which case the corresponding algorithm is used instead).booleanSimilar to above, but with an even stronger algorithm in O(n!).booleanSimilar to routing_cut_subset_size_for_exact_binary_relation_bound but use a bound based on shortest path distances (which respect triangular inequality).booleanSimilar to above, but with a different algorithm producing better cuts, at the price of a higher O(2^n) complexity, where n is the subset size.booleanExperimental.booleanoptional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];booleanSearch randomization will collect the top 'search_random_variable_pool_size' valued variables, and pick one randomly.booleanAllows sharing of new learned binary clause between workers.booleanHow much deeper compared to the ideal max depth of the tree is considered "balanced" enough to still accept a split.booleanIn order to limit total shared memory and communication overhead, limit the total number of nodes that may be generated in the shared tree.booleanEnables shared tree search.booleanHow many open leaf nodes should the shared tree maintain per worker.booleanoptional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];booleanIf true, shared tree workers share their target phase when returning an assigned subtree for the next worker to use.booleanIf true, workers share more of the information from their local trail.booleanMinimum restarts before a worker will replace a subtree that looks "bad" based on the average LBD of learned clauses.booleanAllows sharing of short glue clauses between workers.booleanThe amount of dtime between each export of shared glue clauses.booleanAllows sharing of the bounds of modified variables at level 0.booleanAllows objective sharing between workers.booleanAdd a shaving phase (where the solver tries to prove that the lower or upper bound of a variable are infeasible) to the probing searchbooleanSpecifies the amount of deterministic time spent of each try at shaving a bound in the shaving search.booleanSpecifies the threshold between two modes in the shaving procedure.booleanSize of the top-n different solutions kept by the solver.booleanFor an optimization problem, stop the solver as soon as we have a solution.booleanMainly used when improving the presolver.booleanoptional bool stop_after_root_propagation = 252 [default = false];booleanThe parameter num_conflicts_before_strategy_changes is increased by that much after each strategy change.booleanAt 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.booleanDeterministic time limit for symmetry detection.booleanWhether we try to automatically detect the symmetries in a model and exploit them.booleanHow much we try to "compress" a table constraint.booleanoptional bool use_absl_random = 180 [default = false];booleanTurn on extra propagation for the circuit constraint.booleanWhen this is true, the no_overlap_2d constraint is reinforced with an energetic reasoning that uses an area-based energy.booleanBlock 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.booleanThis can be beneficial if there is a lot of no-overlap constraints but a relatively low number of different intervals in the problem.booleanEnable a heuristic to solve cumulative constraints using a modified energy constraint.booleanWhen 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.booleanWhen set, it activates a few scheduling parameters to improve the lower bound of scheduling problems.booleanoptional bool use_dynamic_precedence_in_cumulative = 268 [default = false];booleanWhether we try to branch on decision "interval A before interval B" rather than on intervals bounds.booleanWhen this is true, the no_overlap_2d constraint is reinforced with energetic reasoning.booleanWhether we use the ERWA (Exponential Recency Weighted Average) heuristic as described in "Learning Rate Based Branching Heuristic for SAT solvers", J.H.Liang, V.booleanThe solver usually exploit the LP relaxation of a model.booleanUse extended probing (probe bool_or, at_most_one, exactly_one).booleanParameters 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.booleanAdds a feasibility pump subsolver along with lns subsolvers.booleanIf true, detect and create constraint for integer variable that are "after" a set of intervals in the same cumulative constraint.booleanStores and exploits "implied-bounds" in the solver.booleanTurns on neighborhood generator based on local branching LP.booleanWhen set, this activates a propagator for the no_overlap_2d constraint that uses any eventual linear constraints of the model in the form `{start interval 1} - {end interval 2} + c*w <= ub` to detect that two intervals must overlap in one dimension for some values of `w`.booleanTesting parameters used to disable all lns workers.booleanExperimental parameters to disable everything but lns.booleanDisable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.booleanIf true, search will search in ascending max objective value (when minimizing) starting from the lower bound of the objective.booleanThis 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.booleanFor an optimization problem, whether we follow some hints in order to find a better first solution.booleanIf true, we automatically detect variables whose constraint are always enforced by the same literal and we mark them as optional.booleanWhen this is true, the cumulative constraint is reinforced with overload checking, i.e., an additional level of reasoning based on energy.booleanWhether to use pseudo-Boolean resolution to analyze a conflict.booleanIf 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().booleanWhen this is true, then a disjunctive constraint will try to use the precedence relations between time intervals to propagate their bounds further.booleanIf true, search will continuously probe Boolean variables, and integer variable bounds.booleanTurns on relaxation induced neighborhood generator.booleanEnable or disable "inprocessing" which is some SAT presolving done at each restart to the root level.booleanSet on shared subtree workers.booleanEnable stronger and more expensive propagation on no_overlap constraint.booleanWhen we have symmetry, it is possible to "fold" all variables from the same orbit into a single variable, while having the same power of LP relaxation.booleanWhen 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.booleanWhen this is true, the no_overlap_2d constraint is reinforced with propagators from the cumulative constraints.booleanoptional bool use_try_edge_reasoning_in_no_overlap_2d = 299 [default = false];booleanEach time a conflict is found, the activities of some variables are increased by one.booleanThis search takes all Boolean or integer variables, and maximize or minimize them in order to reduce their domain. -1 is automatic, otherwise value 0 disables it, and 1, 2, or 3 changes something.booleanProbability of using compound move search each restart.booleanHow long violation_ls should wait before perturbating a solution.protected com.google.protobuf.GeneratedMessage.FieldAccessorTablefinal booleanmergeFrom(SatParameters other) mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) mergeFrom(com.google.protobuf.Message other) removeSubsolverParams(int index) It is possible to specify additional subsolver configuration.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.setAddCgCuts(boolean value) Whether we generate and add Chvatal-Gomory cuts to the LP at root node.setAddCliqueCuts(boolean value) Whether we generate clique cuts from the binary implication graph.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.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.setAddMirCuts(boolean value) Whether we generate MIR cuts at root node.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?setAddRltCuts(boolean value) Whether we generate RLT cuts.setAddZeroHalfCuts(boolean value) Whether we generate Zero-Half cuts at root node.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.setAtMostOneMaxExpansionSize(int value) All at_most_one constraints with a size <= param will be replaced by a quadratic number of binary implications.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.optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];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.setBlockingRestartMultiplier(double value) optional double blocking_restart_multiplier = 66 [default = 1.4];setBlockingRestartWindowSize(int value) optional int32 blocking_restart_window_size = 65 [default = 5000];setBooleanEncodingLevel(int value) A non-negative level indicating how much we should try to fully encode Integer variables as Boolean.setCatchSigintSignal(boolean value) Indicates if the CP-SAT layer should catch Control-C (SIGINT) signals when calling solve.setClauseActivityDecay(double value) Clause activity parameters (same effect as the one on the variables).setClauseCleanupLbdBound(int value) All the clauses with a LBD (literal blocks distance) lower or equal to this parameters will always be kept.optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];setClauseCleanupPeriod(int value) Trigger a cleanup when this number of "deletable" clauses is learned.optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];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.setClauseCleanupTarget(int value) During a cleanup, we will always keep that number of "deletable" clauses.setConvertIntervals(boolean value) Temporary flag util the feature is more mature.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 coresetCountAssumptionLevelsInLbd(boolean value) Whether or not the assumption levels are taken into account during the LBD computation.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.setCpModelPresolve(boolean value) Whether we presolve the cp_model before solving it.setCpModelProbingLevel(int value) How much effort do we spend on probing. 0 disables it completely.setCpModelUseSatPresolve(boolean value) Whether we also use the sat presolve when cp_model_presolve is true.setCutActiveCountDecay(double value) optional double cut_active_count_decay = 156 [default = 0.8];setCutCleanupTarget(int value) Target number of constraints to remove during cleanup.setCutLevel(int value) Control the global cut effort.setCutMaxActiveCountValue(double value) These parameters are similar to sat clause management activity parameters.setDebugCrashIfPresolveBreaksHint(boolean value) Crash if presolve breaks a feasible hint.setDebugCrashOnBadHint(boolean value) Crash if we do not manage to complete the hint into a full solution.setDebugMaxNumPresolveOperations(int value) If positive, try to stop just after that many presolve rules have been applied.setDebugPostsolveWithFullSolver(boolean value) We have two different postsolve code.optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];setDefaultRestartAlgorithmsBytes(com.google.protobuf.ByteString value) optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];setDetectLinearizedProduct(boolean value) Infer products of Boolean or of Boolean time IntegerVariable from the linear constrainst in the problem.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.setDisableConstraintExpansion(boolean value) If true, it disable all constraint expansion.setDiversifyLnsParams(boolean value) If true, registers more lns subsolvers with different parameters.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.setEncodeCumulativeAsReservoir(boolean value) Encore cumulative with fixed demands and capacity as a reservoir constraint.setEnumerateAllSolutions(boolean value) Whether we enumerate all solutions of a problem without objective.setExpandAlldiffConstraints(boolean value) If true, expand all_different constraints that are not permutations.setExpandReservoirConstraints(boolean value) If true, expand the reservoir constraints by creating booleans for all possible precedences between event and encoding the constraint.setExpandReservoirUsingCircuit(boolean value) Mainly useful for testing.setExploitAllLpSolution(boolean value) If true and the Lp relaxation of the problem has a solution, try to exploit it.setExploitAllPrecedences(boolean value) optional bool exploit_all_precedences = 220 [default = false];setExploitBestSolution(boolean value) When branching on a variable, follow the last best solution value.setExploitIntegerLpSolution(boolean value) If true and the Lp relaxation of the problem has an integer optimal solution, try to exploit it.setExploitObjective(boolean value) When branching an a variable that directly affect the objective, branch on the value that lead to the best objective first.setExploitRelaxationSolution(boolean value) When branching on a variable, follow the last best relaxation solution value.setExtraSubsolvers(int index, String value) A convenient way to add more workers types.setFeasibilityJumpBatchDtime(double value) How much dtime for each LS batch.setFeasibilityJumpDecay(double value) On each restart, we randomly choose if we use decay (with this parameter) or no decay.setFeasibilityJumpEnableRestarts(boolean value) When stagnating, feasibility jump will either restart from a default solution (with some possible randomization), or randomly pertubate the current solution.setFeasibilityJumpLinearizationLevel(int value) How much do we linearize the problem in the local search code.setFeasibilityJumpMaxExpandedConstraintSize(int value) Maximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion.setFeasibilityJumpRestartFactor(int value) This is a factor that directly influence the work before each restart.setFeasibilityJumpVarPerburbationRangeRatio(double value) Max distance between the default value and the pertubated value relative to the range of the domain of the variable.setFeasibilityJumpVarRandomizationProbability(double value) Probability for a variable to have a non default value upon restarts or perturbations.setFillAdditionalSolutionsInResponse(boolean value) If true, the final response addition_solutions field will be filled with all solutions from our solutions pool.setFillTightenedDomainsInResponse(boolean value) If true, add information about the derived variable domains to the CpSolverResponse.setFilterSatPostsolveClauses(boolean value) Internal parameter.setFilterSubsolvers(int index, String value) repeated string filter_subsolvers = 293;setFindBigLinearOverlap(boolean value) Try to find large "rectangle" in the linear constraint matrix with identical lines.setFindMultipleCores(boolean value) Whether we try to find more independent cores for a given set of assumptions in the core based max-SAT algorithms.setFixVariablesToTheirHintedValue(boolean value) If true, variables appearing in the solution hints will be fixed to their hinted value.optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];setGlucoseDecayIncrement(double value) optional double glucose_decay_increment = 23 [default = 0.01];setGlucoseDecayIncrementPeriod(int value) optional int32 glucose_decay_increment_period = 24 [default = 5000];setGlucoseMaxDecay(double value) The activity starts at 0.8 and increment by 0.01 every 5000 conflicts until 0.95.setHintConflictLimit(int value) Conflict limit used in the phase that exploit the solution hint.setIgnoreNames(boolean value) If true, we don't keep names in our internal copy of the user given model.setIgnoreSubsolvers(int index, String value) Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing.setInferAllDiffs(boolean value) Run a max-clique code amongst all the x !optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];setInitialVariablesActivity(double value) The initial value of the variables activity.setInprocessingDtimeRatio(double value) Proportion of deterministic time we should spend on inprocessing.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.setInprocessingMinimizationUseAllOrderings(boolean value) optional bool inprocessing_minimization_use_all_orderings = 298 [default = false];setInprocessingMinimizationUseConflictAnalysis(boolean value) optional bool inprocessing_minimization_use_conflict_analysis = 297 [default = true];setInprocessingProbingDtime(double value) The amount of dtime we should spend on probing for each inprocessing round.setInstantiateAllVariables(boolean value) If true, the solver will add a default integer branching strategy to the already defined search strategy.setInterleaveBatchSize(int value) optional int32 interleave_batch_size = 134 [default = 0];setInterleaveSearch(boolean value) Experimental.setKeepAllFeasibleSolutionsInPresolve(boolean value) If true, we disable the presolve reductions that remove feasible solutions from the search space.setKeepSymmetryInPresolve(boolean value) Experimental.setLbRelaxNumWorkersThreshold(int value) Only use lb-relax if we have at least that many workers.setLinearizationLevel(int value) A non-negative level indicating the type of constraints we consider in the LP relaxation.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.setLnsInitialDeterministicLimit(double value) optional double lns_initial_deterministic_limit = 308 [default = 0.1];setLnsInitialDifficulty(double value) Initial parameters for neighborhood generation.setLogPrefix(String value) Add a prefix to all logs.setLogPrefixBytes(com.google.protobuf.ByteString value) Add a prefix to all logs.setLogSearchProgress(boolean value) Whether the solver should log the search progress.setLogSubsolverStatistics(boolean value) Whether the solver should display per sub-solver search statistics.setLogToResponse(boolean value) Log to response proto.setLogToStdout(boolean value) Log to stdout.setLpDualTolerance(double value) optional double lp_dual_tolerance = 267 [default = 1e-07];setLpPrimalTolerance(double value) The internal LP tolerances used by CP-SAT.setMaxAllDiffCutSize(int value) Cut generator for all diffs can add too many cuts for large all_diff constraints.setMaxAlldiffDomainSize(int value) Max domain size for all_different constraints to be expanded.setMaxClauseActivityValue(double value) optional double max_clause_activity_value = 18 [default = 1e+20];setMaxConsecutiveInactiveCount(int value) If a constraint/cut in LP is not active for that many consecutive OPTIMAL solves, remove it from the LP.setMaxCutRoundsAtLevelZero(int value) Max number of time we perform cut generation and resolve the LP at level 0.setMaxDeterministicTime(double value) Maximum time allowed in deterministic time to solve a problem.setMaxDomainSizeWhenEncodingEqNeqConstraints(int value) When loading a*x + b*y ==/!Detects when the space where items of a no_overlap_2d constraint can placed is disjoint (ie., fixed boxes split the domain).setMaxIntegerRoundingScaling(int value) In the integer rounding procedure used for MIR and Gomory cut, the maximum "scaling" we use (must be positive).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.setMaxMemoryInMb(long value) Maximum memory allowed for the whole thread containing the solver.setMaxNumberOfConflicts(long value) Maximum number of conflicts allowed to solve a problem.setMaxNumCuts(int value) The limit on the number of cuts in our cut pool.setMaxNumDeterministicBatches(int value) Stops after that number of batches has been scheduled.setMaxNumIntervalsForTimetableEdgeFinding(int value) Max number of intervals for the timetable_edge_finding algorithm to propagate.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.setMaxPresolveIterations(int value) In case of large reduction in a presolve iteration, we perform multiple presolve iterations.optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];setMaxSatReverseAssumptionOrder(boolean value) If true, adds the assumption in the reverse order of the one defined by max_sat_assumption_order.optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];Create one literal for each disjunction of two pairs of tasks.setMaxTimeInSeconds(double value) Maximum time allowed in seconds to solve a problem.setMaxVariableActivityValue(double value) optional double max_variable_activity_value = 16 [default = 1e+100];setMergeAtMostOneWorkLimit(double value) optional double merge_at_most_one_work_limit = 146 [default = 100000000];setMergeNoOverlapWorkLimit(double value) During presolve, we use a maximum clique heuristic to merge together no-overlap constraints or at most one constraints.optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];setMinimizeReductionDuringPbResolution(boolean value) A different algorithm during PB resolution.setMinimizeSharedClauses(boolean value) Minimize and detect subsumption of shared clauses immediately after they are imported.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.setMipAutomaticallyScaleVariables(boolean value) If true, some continuous variable might be automatically scaled.setMipCheckPrecision(double value) As explained in mip_precision and mip_max_activity_exponent, we cannot always reach the wanted precision during scaling.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.setMipDropTolerance(double value) Any value in the input mip with a magnitude lower than this will be set to zero.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.setMipMaxBound(double value) We need to bound the maximum magnitude of the variables for CP-SAT, and that is the bound we use.setMipMaxValidMagnitude(double value) Any finite values in the input MIP must be below this threshold, otherwise the model will be reported invalid.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.setMipScaleLargeDomain(boolean value) If this is false, then mip_var_scaling is only applied to variables with "small" domain.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.setMipVarScaling(double value) All continuous variable of the problem will be multiplied by this factor.setMipWantedPrecision(double value) When scaling constraint with double coefficients to integer coefficients, we will multiply by a power of 2 and round the coefficients.In some context, like in a portfolio of search, it makes sense to name a given parameters set for logging purpose.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.setNewConstraintsBatchSize(int value) Add that many lazy constraints (or cuts) at once in the LP.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.setNoOverlap2DBooleanRelationsLimit(int value) If less than this number of boxes are present in a no-overlap 2d, we create 4 Booleans per pair of boxes: - Box 2 is after Box 1 on xsetNumConflictsBeforeStrategyChanges(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.setNumFullSubsolvers(int value) We distinguish subsolvers that consume a full thread, and the ones that are always interleaved.setNumSearchWorkers(int value) optional int32 num_search_workers = 100 [default = 0];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.setNumWorkers(int value) Specify the number of parallel workers (i.e. threads) to use during search.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.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.setOptimizeWithCore(boolean value) The default optimization method is a simple "linear scan", each time trying to find a better solution than the previous one.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.setOptimizeWithMaxHs(boolean value) This has no effect if optimize_with_core is false.setPbCleanupIncrement(int value) Same as for the clauses, but for the learned pseudo-Boolean constraints.setPbCleanupRatio(double value) optional double pb_cleanup_ratio = 47 [default = 0.5];setPermutePresolveConstraintOrder(boolean value) optional bool permute_presolve_constraint_order = 179 [default = false];setPermuteVariableRandomly(boolean value) This is mainly here to test the solver variability.setPolarityExploitLsHints(boolean value) If true and we have first solution LS workers, tries in some phase to follow a LS solutions that violates has litle constraints as possible.setPolarityRephaseIncrement(int value) If non-zero, then we change the polarity heuristic after that many number of conflicts in an arithmetically increasing fashion.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.optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];setPresolveBlockedClause(boolean value) Whether we use an heuristic to detect some basic case of blocked clause in the SAT presolve.setPresolveBvaThreshold(int value) Apply Bounded Variable Addition (BVA) if the number of clauses is reduced by stricly more than this threshold.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.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.setPresolveExtractIntegerEnforcement(boolean value) If true, we will extract from linear constraints, enforcement literals of the form "integer variable at bound => simplified constraint".setPresolveInclusionWorkLimit(long value) A few presolve operations involve detecting constraints included in other constraint.setPresolveProbingDeterministicTimeLimit(double value) optional double presolve_probing_deterministic_time_limit = 57 [default = 30];setPresolveSubstitutionLevel(int value) How much substitution (also called free variable aggregation in MIP litterature) should we perform at presolve.setPresolveUseBva(boolean value) Whether or not we use Bounded Variable Addition (BVA) in the presolve.setProbingDeterministicTimeLimit(double value) The maximum "deterministic" time limit to spend in probing.setProbingNumCombinationsLimit(int value) How many combinations of pairs or triplets of variables we want to scan.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.setPseudoCostReliabilityThreshold(long value) The solver ignores the pseudo costs of variables with number of recordings less than this threshold.setPushAllTasksTowardStart(boolean value) Experimental code: specify if the objective pushes all tasks toward the start of the schedule.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.setRandomizeSearch(boolean value) Randomize fixed search.setRandomPolarityRatio(double value) The proportion of polarity chosen at random.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.setRelativeGapLimit(double value) optional double relative_gap_limit = 160 [default = 0];setRemoveFixedVariablesEarly(boolean value) If cp_model_presolve is true and there is a large proportion of fixed variable after the first model copy, remap all the model to a dense set of variable before the full presolve even starts.setRepairHint(boolean value) If true, the solver tries to repair the solution given in the hint.setRestartAlgorithms(int index, SatParameters.RestartAlgorithm value) The restart strategies will change each time the strategy_counter is increased.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.setRestartLbdAverageRatio(double value) optional double restart_lbd_average_ratio = 71 [default = 1];setRestartPeriod(int value) Restart period for the FIXED_RESTART strategy.setRestartRunningWindowSize(int value) Size of the window for the moving average restarts.setRootLpIterations(int value) Even at the root node, we do not want to spend too much time on the LP if it is "difficult".setRoutingCutDpEffort(double value) The amount of "effort" to spend in dynamic programming for computing routing cuts.setRoutingCutMaxInfeasiblePathLength(int value) If the length of an infeasible path is less than this value, a cut will be added to exclude it.If the size of a subset of nodes of a RoutesConstraint is less than this value, use linear constraints of size 1 and 2 (such as capacity and time window constraints) enforced by the arc literals to compute cuts for this subset (unless the subset size is less than routing_cut_subset_size_for_tight_binary_relation_bound, in which case the corresponding algorithm is used instead).Similar to above, but with an even stronger algorithm in O(n!).setRoutingCutSubsetSizeForShortestPathsBound(int value) Similar to routing_cut_subset_size_for_exact_binary_relation_bound but use a bound based on shortest path distances (which respect triangular inequality).Similar to above, but with a different algorithm producing better cuts, at the price of a higher O(2^n) complexity, where n is the subset size.setSaveLpBasisInLbTreeSearch(boolean value) Experimental.optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];setSearchRandomVariablePoolSize(long value) Search randomization will collect the top 'search_random_variable_pool_size' valued variables, and pick one randomly.setShareBinaryClauses(boolean value) Allows sharing of new learned binary clause between workers.setSharedTreeBalanceTolerance(int value) How much deeper compared to the ideal max depth of the tree is considered "balanced" enough to still accept a split.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.setSharedTreeNumWorkers(int value) Enables shared tree search.setSharedTreeOpenLeavesPerWorker(double value) How many open leaf nodes should the shared tree maintain per worker.optional .operations_research.sat.SatParameters.SharedTreeSplitStrategy shared_tree_split_strategy = 239 [default = SPLIT_STRATEGY_AUTO];setSharedTreeWorkerEnablePhaseSharing(boolean value) If true, shared tree workers share their target phase when returning an assigned subtree for the next worker to use.setSharedTreeWorkerEnableTrailSharing(boolean value) If true, workers share more of the information from their local trail.setSharedTreeWorkerMinRestartsPerSubtree(int value) Minimum restarts before a worker will replace a subtree that looks "bad" based on the average LBD of learned clauses.setShareGlueClauses(boolean value) Allows sharing of short glue clauses between workers.setShareGlueClausesDtime(double value) The amount of dtime between each export of shared glue clauses.setShareLevelZeroBounds(boolean value) Allows sharing of the bounds of modified variables at level 0.setShareObjectiveBounds(boolean value) Allows objective sharing between workers.setShavingDeterministicTimeInProbingSearch(double 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 searchsetShavingSearchDeterministicTime(double value) Specifies the amount of deterministic time spent of each try at shaving a bound in the shaving search.setShavingSearchThreshold(long value) Specifies the threshold between two modes in the shaving procedure.setSolutionPoolSize(int value) Size of the top-n different solutions kept by the solver.setStopAfterFirstSolution(boolean value) For an optimization problem, stop the solver as soon as we have a solution.setStopAfterPresolve(boolean value) Mainly used when improving the presolver.setStopAfterRootPropagation(boolean value) optional bool stop_after_root_propagation = 252 [default = false];setStrategyChangeIncreaseRatio(double value) The parameter num_conflicts_before_strategy_changes is increased by that much after each strategy change.setSubsolverParams(int index, SatParameters value) It is possible to specify additional subsolver configuration.setSubsolverParams(int index, SatParameters.Builder builderForValue) It is possible to specify additional subsolver configuration.setSubsolvers(int index, String value) In multi-thread, the solver can be mainly seen as a portfolio of solvers with different parameters.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.setSymmetryDetectionDeterministicTimeLimit(double value) Deterministic time limit for symmetry detection.setSymmetryLevel(int value) Whether we try to automatically detect the symmetries in a model and exploit them.setTableCompressionLevel(int value) How much we try to "compress" a table constraint.setUseAbslRandom(boolean value) optional bool use_absl_random = 180 [default = false];setUseAllDifferentForCircuit(boolean value) Turn on extra propagation for the circuit constraint.setUseAreaEnergeticReasoningInNoOverlap2D(boolean value) When this is true, the no_overlap_2d constraint is reinforced with an energetic reasoning that uses an area-based energy.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.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.setUseConservativeScaleOverloadChecker(boolean value) Enable a heuristic to solve cumulative constraints using a modified energy constraint.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.setUseDualSchedulingHeuristics(boolean value) When set, it activates a few scheduling parameters to improve the lower bound of scheduling problems.setUseDynamicPrecedenceInCumulative(boolean value) optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];setUseDynamicPrecedenceInDisjunctive(boolean value) Whether we try to branch on decision "interval A before interval B" rather than on intervals bounds.setUseEnergeticReasoningInNoOverlap2D(boolean value) When this is true, the no_overlap_2d constraint is reinforced with energetic reasoning.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.setUseExactLpReason(boolean value) The solver usually exploit the LP relaxation of a model.setUseExtendedProbing(boolean value) Use extended probing (probe bool_or, at_most_one, exactly_one).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.setUseFeasibilityPump(boolean value) Adds a feasibility pump subsolver along with lns subsolvers.setUseHardPrecedencesInCumulative(boolean value) If true, detect and create constraint for integer variable that are "after" a set of intervals in the same cumulative constraint.setUseImpliedBounds(boolean value) Stores and exploits "implied-bounds" in the solver.setUseLbRelaxLns(boolean value) Turns on neighborhood generator based on local branching LP.setUseLinear3ForNoOverlap2DPrecedences(boolean value) When set, this activates a propagator for the no_overlap_2d constraint that uses any eventual linear constraints of the model in the form `{start interval 1} - {end interval 2} + c*w <= ub` to detect that two intervals must overlap in one dimension for some values of `w`.setUseLns(boolean value) Testing parameters used to disable all lns workers.setUseLnsOnly(boolean value) Experimental parameters to disable everything but lns.setUseLsOnly(boolean value) Disable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.setUseObjectiveLbSearch(boolean value) If true, search will search in ascending max objective value (when minimizing) starting from the lower bound of the objective.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.setUseOptimizationHints(boolean value) For an optimization problem, whether we follow some hints in order to find a better first solution.setUseOptionalVariables(boolean value) If true, we automatically detect variables whose constraint are always enforced by the same literal and we mark them as optional.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.setUsePbResolution(boolean value) Whether to use pseudo-Boolean resolution to analyze a conflict.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().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.setUseProbingSearch(boolean value) If true, search will continuously probe Boolean variables, and integer variable bounds.setUseRinsLns(boolean value) Turns on relaxation induced neighborhood generator.setUseSatInprocessing(boolean value) Enable or disable "inprocessing" which is some SAT presolving done at each restart to the root level.setUseSharedTreeSearch(boolean value) Set on shared subtree workers.setUseStrongPropagationInDisjunctive(boolean value) Enable stronger and more expensive propagation on no_overlap constraint.setUseSymmetryInLp(boolean value) When we have symmetry, it is possible to "fold" all variables from the same orbit into a single variable, while having the same power of LP relaxation.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.setUseTimetablingInNoOverlap2D(boolean value) When this is true, the no_overlap_2d constraint is reinforced with propagators from the cumulative constraints.setUseTryEdgeReasoningInNoOverlap2D(boolean value) optional bool use_try_edge_reasoning_in_no_overlap_2d = 299 [default = false];setVariableActivityDecay(double value) Each time a conflict is found, the activities of some variables are increased by one.setVariablesShavingLevel(int value) This search takes all Boolean or integer variables, and maximize or minimize them in order to reduce their domain. -1 is automatic, otherwise value 0 disables it, and 1, 2, or 3 changes something.setViolationLsCompoundMoveProbability(double value) Probability of using compound move search each restart.setViolationLsPerturbationPeriod(int value) How long violation_ls should wait before perturbating a solution.Methods inherited from class com.google.protobuf.GeneratedMessage.Builder
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, setUnknownFieldsProto3Methods inherited from class com.google.protobuf.AbstractMessage.Builder
findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringMethods inherited from class com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageExceptionMethods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitMethods inherited from interface com.google.protobuf.Message.Builder
mergeDelimitedFrom, mergeDelimitedFromMethods inherited from interface com.google.protobuf.MessageLite.Builder
mergeFromMethods inherited from interface com.google.protobuf.MessageOrBuilder
findInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
-
Method Details
-
getDescriptor
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor() -
internalGetFieldAccessorTable
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()- Specified by:
internalGetFieldAccessorTablein classcom.google.protobuf.GeneratedMessage.Builder<SatParameters.Builder>
-
clear
- Specified by:
clearin interfacecom.google.protobuf.Message.Builder- Specified by:
clearin interfacecom.google.protobuf.MessageLite.Builder- Overrides:
clearin classcom.google.protobuf.GeneratedMessage.Builder<SatParameters.Builder>
-
getDescriptorForType
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()- Specified by:
getDescriptorForTypein interfacecom.google.protobuf.Message.Builder- Specified by:
getDescriptorForTypein interfacecom.google.protobuf.MessageOrBuilder- Overrides:
getDescriptorForTypein classcom.google.protobuf.GeneratedMessage.Builder<SatParameters.Builder>
-
getDefaultInstanceForType
- Specified by:
getDefaultInstanceForTypein interfacecom.google.protobuf.MessageLiteOrBuilder- Specified by:
getDefaultInstanceForTypein interfacecom.google.protobuf.MessageOrBuilder
-
build
- Specified by:
buildin interfacecom.google.protobuf.Message.Builder- Specified by:
buildin interfacecom.google.protobuf.MessageLite.Builder
-
buildPartial
- Specified by:
buildPartialin interfacecom.google.protobuf.Message.Builder- Specified by:
buildPartialin interfacecom.google.protobuf.MessageLite.Builder
-
mergeFrom
- Specified by:
mergeFromin interfacecom.google.protobuf.Message.Builder- Overrides:
mergeFromin classcom.google.protobuf.AbstractMessage.Builder<SatParameters.Builder>
-
mergeFrom
-
isInitialized
public final boolean isInitialized()- Specified by:
isInitializedin interfacecom.google.protobuf.MessageLiteOrBuilder- Overrides:
isInitializedin classcom.google.protobuf.GeneratedMessage.Builder<SatParameters.Builder>
-
mergeFrom
public SatParameters.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException - Specified by:
mergeFromin interfacecom.google.protobuf.Message.Builder- Specified by:
mergeFromin interfacecom.google.protobuf.MessageLite.Builder- Overrides:
mergeFromin classcom.google.protobuf.AbstractMessage.Builder<SatParameters.Builder>- Throws:
IOException
-
hasName
public 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 = ""];- Specified by:
hasNamein interfaceSatParametersOrBuilder- Returns:
- Whether the name field is set.
-
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 = ""];- Specified by:
getNamein interfaceSatParametersOrBuilder- Returns:
- The name.
-
getNameBytes
public 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 = ""];- Specified by:
getNameBytesin interfaceSatParametersOrBuilder- Returns:
- The bytes for name.
-
setName
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 = ""];- Parameters:
value- The name to set.- Returns:
- This builder for chaining.
-
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 = ""];- Returns:
- This builder for chaining.
-
setNameBytes
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 = ""];- Parameters:
value- The bytes for name to set.- Returns:
- This builder for chaining.
-
hasPreferredVariableOrder
public boolean hasPreferredVariableOrder()optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];- Specified by:
hasPreferredVariableOrderin interfaceSatParametersOrBuilder- Returns:
- Whether the preferredVariableOrder field is set.
-
getPreferredVariableOrder
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];- Specified by:
getPreferredVariableOrderin interfaceSatParametersOrBuilder- Returns:
- The preferredVariableOrder.
-
setPreferredVariableOrder
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];- Parameters:
value- The preferredVariableOrder to set.- Returns:
- This builder for chaining.
-
clearPreferredVariableOrder
optional .operations_research.sat.SatParameters.VariableOrder preferred_variable_order = 1 [default = IN_ORDER];- Returns:
- This builder for chaining.
-
hasInitialPolarity
public boolean hasInitialPolarity()optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];- Specified by:
hasInitialPolarityin interfaceSatParametersOrBuilder- Returns:
- Whether the initialPolarity field is set.
-
getInitialPolarity
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];- Specified by:
getInitialPolarityin interfaceSatParametersOrBuilder- Returns:
- The initialPolarity.
-
setInitialPolarity
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];- Parameters:
value- The initialPolarity to set.- Returns:
- This builder for chaining.
-
clearInitialPolarity
optional .operations_research.sat.SatParameters.Polarity initial_polarity = 2 [default = POLARITY_FALSE];- Returns:
- This builder for chaining.
-
hasUsePhaseSaving
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];- Specified by:
hasUsePhaseSavingin interfaceSatParametersOrBuilder- Returns:
- Whether the usePhaseSaving field is set.
-
getUsePhaseSaving
public 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];- Specified by:
getUsePhaseSavingin interfaceSatParametersOrBuilder- Returns:
- The usePhaseSaving.
-
setUsePhaseSaving
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];- Parameters:
value- The usePhaseSaving to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasPolarityRephaseIncrement
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];- Specified by:
hasPolarityRephaseIncrementin interfaceSatParametersOrBuilder- Returns:
- Whether the polarityRephaseIncrement field is set.
-
getPolarityRephaseIncrement
public 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];- Specified by:
getPolarityRephaseIncrementin interfaceSatParametersOrBuilder- Returns:
- The polarityRephaseIncrement.
-
setPolarityRephaseIncrement
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];- Parameters:
value- The polarityRephaseIncrement to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasPolarityExploitLsHints
public boolean hasPolarityExploitLsHints()If true and we have first solution LS workers, tries in some phase to follow a LS solutions that violates has litle constraints as possible.
optional bool polarity_exploit_ls_hints = 309 [default = false];- Specified by:
hasPolarityExploitLsHintsin interfaceSatParametersOrBuilder- Returns:
- Whether the polarityExploitLsHints field is set.
-
getPolarityExploitLsHints
public boolean getPolarityExploitLsHints()If true and we have first solution LS workers, tries in some phase to follow a LS solutions that violates has litle constraints as possible.
optional bool polarity_exploit_ls_hints = 309 [default = false];- Specified by:
getPolarityExploitLsHintsin interfaceSatParametersOrBuilder- Returns:
- The polarityExploitLsHints.
-
setPolarityExploitLsHints
If true and we have first solution LS workers, tries in some phase to follow a LS solutions that violates has litle constraints as possible.
optional bool polarity_exploit_ls_hints = 309 [default = false];- Parameters:
value- The polarityExploitLsHints to set.- Returns:
- This builder for chaining.
-
clearPolarityExploitLsHints
If true and we have first solution LS workers, tries in some phase to follow a LS solutions that violates has litle constraints as possible.
optional bool polarity_exploit_ls_hints = 309 [default = false];- Returns:
- This builder for chaining.
-
hasRandomPolarityRatio
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];- Specified by:
hasRandomPolarityRatioin interfaceSatParametersOrBuilder- Returns:
- Whether the randomPolarityRatio field is set.
-
getRandomPolarityRatio
public 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];- Specified by:
getRandomPolarityRatioin interfaceSatParametersOrBuilder- Returns:
- The randomPolarityRatio.
-
setRandomPolarityRatio
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];- Parameters:
value- The randomPolarityRatio to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasRandomBranchesRatio
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];- Specified by:
hasRandomBranchesRatioin interfaceSatParametersOrBuilder- Returns:
- Whether the randomBranchesRatio field is set.
-
getRandomBranchesRatio
public 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];- Specified by:
getRandomBranchesRatioin interfaceSatParametersOrBuilder- Returns:
- The randomBranchesRatio.
-
setRandomBranchesRatio
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];- Parameters:
value- The randomBranchesRatio to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseErwaHeuristic
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];- Specified by:
hasUseErwaHeuristicin interfaceSatParametersOrBuilder- Returns:
- Whether the useErwaHeuristic field is set.
-
getUseErwaHeuristic
public 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];- Specified by:
getUseErwaHeuristicin interfaceSatParametersOrBuilder- Returns:
- The useErwaHeuristic.
-
setUseErwaHeuristic
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];- Parameters:
value- The useErwaHeuristic to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasInitialVariablesActivity
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];- Specified by:
hasInitialVariablesActivityin interfaceSatParametersOrBuilder- Returns:
- Whether the initialVariablesActivity field is set.
-
getInitialVariablesActivity
public 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];- Specified by:
getInitialVariablesActivityin interfaceSatParametersOrBuilder- Returns:
- The initialVariablesActivity.
-
setInitialVariablesActivity
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];- Parameters:
value- The initialVariablesActivity to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAlsoBumpVariablesInConflictReasons
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];- Specified by:
hasAlsoBumpVariablesInConflictReasonsin interfaceSatParametersOrBuilder- Returns:
- Whether the alsoBumpVariablesInConflictReasons field is set.
-
getAlsoBumpVariablesInConflictReasons
public 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];- Specified by:
getAlsoBumpVariablesInConflictReasonsin interfaceSatParametersOrBuilder- Returns:
- The alsoBumpVariablesInConflictReasons.
-
setAlsoBumpVariablesInConflictReasons
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];- Parameters:
value- The alsoBumpVariablesInConflictReasons to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMinimizationAlgorithm
public boolean hasMinimizationAlgorithm()optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];- Specified by:
hasMinimizationAlgorithmin interfaceSatParametersOrBuilder- Returns:
- Whether the minimizationAlgorithm field is set.
-
getMinimizationAlgorithm
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];- Specified by:
getMinimizationAlgorithmin interfaceSatParametersOrBuilder- Returns:
- The minimizationAlgorithm.
-
setMinimizationAlgorithm
public SatParameters.Builder setMinimizationAlgorithm(SatParameters.ConflictMinimizationAlgorithm value) optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];- Parameters:
value- The minimizationAlgorithm to set.- Returns:
- This builder for chaining.
-
clearMinimizationAlgorithm
optional .operations_research.sat.SatParameters.ConflictMinimizationAlgorithm minimization_algorithm = 4 [default = RECURSIVE];- Returns:
- This builder for chaining.
-
hasBinaryMinimizationAlgorithm
public boolean hasBinaryMinimizationAlgorithm()optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];- Specified by:
hasBinaryMinimizationAlgorithmin interfaceSatParametersOrBuilder- Returns:
- Whether the binaryMinimizationAlgorithm field is set.
-
getBinaryMinimizationAlgorithm
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];- Specified by:
getBinaryMinimizationAlgorithmin interfaceSatParametersOrBuilder- Returns:
- The binaryMinimizationAlgorithm.
-
setBinaryMinimizationAlgorithm
public SatParameters.Builder setBinaryMinimizationAlgorithm(SatParameters.BinaryMinizationAlgorithm value) optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];- Parameters:
value- The binaryMinimizationAlgorithm to set.- Returns:
- This builder for chaining.
-
clearBinaryMinimizationAlgorithm
optional .operations_research.sat.SatParameters.BinaryMinizationAlgorithm binary_minimization_algorithm = 34 [default = BINARY_MINIMIZATION_FIRST];- Returns:
- This builder for chaining.
-
hasSubsumptionDuringConflictAnalysis
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];- Specified by:
hasSubsumptionDuringConflictAnalysisin interfaceSatParametersOrBuilder- Returns:
- Whether the subsumptionDuringConflictAnalysis field is set.
-
getSubsumptionDuringConflictAnalysis
public 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];- Specified by:
getSubsumptionDuringConflictAnalysisin interfaceSatParametersOrBuilder- Returns:
- The subsumptionDuringConflictAnalysis.
-
setSubsumptionDuringConflictAnalysis
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];- Parameters:
value- The subsumptionDuringConflictAnalysis to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasClauseCleanupPeriod
public boolean hasClauseCleanupPeriod()Trigger a cleanup when this number of "deletable" clauses is learned.
optional int32 clause_cleanup_period = 11 [default = 10000];- Specified by:
hasClauseCleanupPeriodin interfaceSatParametersOrBuilder- Returns:
- Whether the clauseCleanupPeriod field is set.
-
getClauseCleanupPeriod
public int getClauseCleanupPeriod()Trigger a cleanup when this number of "deletable" clauses is learned.
optional int32 clause_cleanup_period = 11 [default = 10000];- Specified by:
getClauseCleanupPeriodin interfaceSatParametersOrBuilder- Returns:
- The clauseCleanupPeriod.
-
setClauseCleanupPeriod
Trigger a cleanup when this number of "deletable" clauses is learned.
optional int32 clause_cleanup_period = 11 [default = 10000];- Parameters:
value- The clauseCleanupPeriod to set.- Returns:
- This builder for chaining.
-
clearClauseCleanupPeriod
Trigger a cleanup when this number of "deletable" clauses is learned.
optional int32 clause_cleanup_period = 11 [default = 10000];- Returns:
- This builder for chaining.
-
hasClauseCleanupTarget
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];- Specified by:
hasClauseCleanupTargetin interfaceSatParametersOrBuilder- Returns:
- Whether the clauseCleanupTarget field is set.
-
getClauseCleanupTarget
public 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];- Specified by:
getClauseCleanupTargetin interfaceSatParametersOrBuilder- Returns:
- The clauseCleanupTarget.
-
setClauseCleanupTarget
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];- Parameters:
value- The clauseCleanupTarget to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasClauseCleanupRatio
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];- Specified by:
hasClauseCleanupRatioin interfaceSatParametersOrBuilder- Returns:
- Whether the clauseCleanupRatio field is set.
-
getClauseCleanupRatio
public 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];- Specified by:
getClauseCleanupRatioin interfaceSatParametersOrBuilder- Returns:
- The clauseCleanupRatio.
-
setClauseCleanupRatio
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];- Parameters:
value- The clauseCleanupRatio to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasClauseCleanupProtection
public boolean hasClauseCleanupProtection()optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];- Specified by:
hasClauseCleanupProtectionin interfaceSatParametersOrBuilder- Returns:
- Whether the clauseCleanupProtection field is set.
-
getClauseCleanupProtection
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];- Specified by:
getClauseCleanupProtectionin interfaceSatParametersOrBuilder- Returns:
- The clauseCleanupProtection.
-
setClauseCleanupProtection
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];- Parameters:
value- The clauseCleanupProtection to set.- Returns:
- This builder for chaining.
-
clearClauseCleanupProtection
optional .operations_research.sat.SatParameters.ClauseProtection clause_cleanup_protection = 58 [default = PROTECTION_NONE];- Returns:
- This builder for chaining.
-
hasClauseCleanupLbdBound
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];- Specified by:
hasClauseCleanupLbdBoundin interfaceSatParametersOrBuilder- Returns:
- Whether the clauseCleanupLbdBound field is set.
-
getClauseCleanupLbdBound
public 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];- Specified by:
getClauseCleanupLbdBoundin interfaceSatParametersOrBuilder- Returns:
- The clauseCleanupLbdBound.
-
setClauseCleanupLbdBound
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];- Parameters:
value- The clauseCleanupLbdBound to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasClauseCleanupOrdering
public boolean hasClauseCleanupOrdering()optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];- Specified by:
hasClauseCleanupOrderingin interfaceSatParametersOrBuilder- Returns:
- Whether the clauseCleanupOrdering field is set.
-
getClauseCleanupOrdering
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];- Specified by:
getClauseCleanupOrderingin interfaceSatParametersOrBuilder- Returns:
- The clauseCleanupOrdering.
-
setClauseCleanupOrdering
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];- Parameters:
value- The clauseCleanupOrdering to set.- Returns:
- This builder for chaining.
-
clearClauseCleanupOrdering
optional .operations_research.sat.SatParameters.ClauseOrdering clause_cleanup_ordering = 60 [default = CLAUSE_ACTIVITY];- Returns:
- This builder for chaining.
-
hasPbCleanupIncrement
public boolean hasPbCleanupIncrement()Same as for the clauses, but for the learned pseudo-Boolean constraints.
optional int32 pb_cleanup_increment = 46 [default = 200];- Specified by:
hasPbCleanupIncrementin interfaceSatParametersOrBuilder- Returns:
- Whether the pbCleanupIncrement field is set.
-
getPbCleanupIncrement
public int getPbCleanupIncrement()Same as for the clauses, but for the learned pseudo-Boolean constraints.
optional int32 pb_cleanup_increment = 46 [default = 200];- Specified by:
getPbCleanupIncrementin interfaceSatParametersOrBuilder- Returns:
- The pbCleanupIncrement.
-
setPbCleanupIncrement
Same as for the clauses, but for the learned pseudo-Boolean constraints.
optional int32 pb_cleanup_increment = 46 [default = 200];- Parameters:
value- The pbCleanupIncrement to set.- Returns:
- This builder for chaining.
-
clearPbCleanupIncrement
Same as for the clauses, but for the learned pseudo-Boolean constraints.
optional int32 pb_cleanup_increment = 46 [default = 200];- Returns:
- This builder for chaining.
-
hasPbCleanupRatio
public boolean hasPbCleanupRatio()optional double pb_cleanup_ratio = 47 [default = 0.5];- Specified by:
hasPbCleanupRatioin interfaceSatParametersOrBuilder- Returns:
- Whether the pbCleanupRatio field is set.
-
getPbCleanupRatio
public double getPbCleanupRatio()optional double pb_cleanup_ratio = 47 [default = 0.5];- Specified by:
getPbCleanupRatioin interfaceSatParametersOrBuilder- Returns:
- The pbCleanupRatio.
-
setPbCleanupRatio
optional double pb_cleanup_ratio = 47 [default = 0.5];- Parameters:
value- The pbCleanupRatio to set.- Returns:
- This builder for chaining.
-
clearPbCleanupRatio
optional double pb_cleanup_ratio = 47 [default = 0.5];- Returns:
- This builder for chaining.
-
hasVariableActivityDecay
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];- Specified by:
hasVariableActivityDecayin interfaceSatParametersOrBuilder- Returns:
- Whether the variableActivityDecay field is set.
-
getVariableActivityDecay
public 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];- Specified by:
getVariableActivityDecayin interfaceSatParametersOrBuilder- Returns:
- The variableActivityDecay.
-
setVariableActivityDecay
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];- Parameters:
value- The variableActivityDecay to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxVariableActivityValue
public boolean hasMaxVariableActivityValue()optional double max_variable_activity_value = 16 [default = 1e+100];- Specified by:
hasMaxVariableActivityValuein interfaceSatParametersOrBuilder- Returns:
- Whether the maxVariableActivityValue field is set.
-
getMaxVariableActivityValue
public double getMaxVariableActivityValue()optional double max_variable_activity_value = 16 [default = 1e+100];- Specified by:
getMaxVariableActivityValuein interfaceSatParametersOrBuilder- Returns:
- The maxVariableActivityValue.
-
setMaxVariableActivityValue
optional double max_variable_activity_value = 16 [default = 1e+100];- Parameters:
value- The maxVariableActivityValue to set.- Returns:
- This builder for chaining.
-
clearMaxVariableActivityValue
optional double max_variable_activity_value = 16 [default = 1e+100];- Returns:
- This builder for chaining.
-
hasGlucoseMaxDecay
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];- Specified by:
hasGlucoseMaxDecayin interfaceSatParametersOrBuilder- Returns:
- Whether the glucoseMaxDecay field is set.
-
getGlucoseMaxDecay
public 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];- Specified by:
getGlucoseMaxDecayin interfaceSatParametersOrBuilder- Returns:
- The glucoseMaxDecay.
-
setGlucoseMaxDecay
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];- Parameters:
value- The glucoseMaxDecay to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasGlucoseDecayIncrement
public boolean hasGlucoseDecayIncrement()optional double glucose_decay_increment = 23 [default = 0.01];- Specified by:
hasGlucoseDecayIncrementin interfaceSatParametersOrBuilder- Returns:
- Whether the glucoseDecayIncrement field is set.
-
getGlucoseDecayIncrement
public double getGlucoseDecayIncrement()optional double glucose_decay_increment = 23 [default = 0.01];- Specified by:
getGlucoseDecayIncrementin interfaceSatParametersOrBuilder- Returns:
- The glucoseDecayIncrement.
-
setGlucoseDecayIncrement
optional double glucose_decay_increment = 23 [default = 0.01];- Parameters:
value- The glucoseDecayIncrement to set.- Returns:
- This builder for chaining.
-
clearGlucoseDecayIncrement
optional double glucose_decay_increment = 23 [default = 0.01];- Returns:
- This builder for chaining.
-
hasGlucoseDecayIncrementPeriod
public boolean hasGlucoseDecayIncrementPeriod()optional int32 glucose_decay_increment_period = 24 [default = 5000];- Specified by:
hasGlucoseDecayIncrementPeriodin interfaceSatParametersOrBuilder- Returns:
- Whether the glucoseDecayIncrementPeriod field is set.
-
getGlucoseDecayIncrementPeriod
public int getGlucoseDecayIncrementPeriod()optional int32 glucose_decay_increment_period = 24 [default = 5000];- Specified by:
getGlucoseDecayIncrementPeriodin interfaceSatParametersOrBuilder- Returns:
- The glucoseDecayIncrementPeriod.
-
setGlucoseDecayIncrementPeriod
optional int32 glucose_decay_increment_period = 24 [default = 5000];- Parameters:
value- The glucoseDecayIncrementPeriod to set.- Returns:
- This builder for chaining.
-
clearGlucoseDecayIncrementPeriod
optional int32 glucose_decay_increment_period = 24 [default = 5000];- Returns:
- This builder for chaining.
-
hasClauseActivityDecay
public boolean hasClauseActivityDecay()Clause activity parameters (same effect as the one on the variables).
optional double clause_activity_decay = 17 [default = 0.999];- Specified by:
hasClauseActivityDecayin interfaceSatParametersOrBuilder- Returns:
- Whether the clauseActivityDecay field is set.
-
getClauseActivityDecay
public double getClauseActivityDecay()Clause activity parameters (same effect as the one on the variables).
optional double clause_activity_decay = 17 [default = 0.999];- Specified by:
getClauseActivityDecayin interfaceSatParametersOrBuilder- Returns:
- The clauseActivityDecay.
-
setClauseActivityDecay
Clause activity parameters (same effect as the one on the variables).
optional double clause_activity_decay = 17 [default = 0.999];- Parameters:
value- The clauseActivityDecay to set.- Returns:
- This builder for chaining.
-
clearClauseActivityDecay
Clause activity parameters (same effect as the one on the variables).
optional double clause_activity_decay = 17 [default = 0.999];- Returns:
- This builder for chaining.
-
hasMaxClauseActivityValue
public boolean hasMaxClauseActivityValue()optional double max_clause_activity_value = 18 [default = 1e+20];- Specified by:
hasMaxClauseActivityValuein interfaceSatParametersOrBuilder- Returns:
- Whether the maxClauseActivityValue field is set.
-
getMaxClauseActivityValue
public double getMaxClauseActivityValue()optional double max_clause_activity_value = 18 [default = 1e+20];- Specified by:
getMaxClauseActivityValuein interfaceSatParametersOrBuilder- Returns:
- The maxClauseActivityValue.
-
setMaxClauseActivityValue
optional double max_clause_activity_value = 18 [default = 1e+20];- Parameters:
value- The maxClauseActivityValue to set.- Returns:
- This builder for chaining.
-
clearMaxClauseActivityValue
optional double max_clause_activity_value = 18 [default = 1e+20];- Returns:
- This builder for chaining.
-
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;- Specified by:
getRestartAlgorithmsListin interfaceSatParametersOrBuilder- Returns:
- A list containing the restartAlgorithms.
-
getRestartAlgorithmsCount
public 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;- Specified by:
getRestartAlgorithmsCountin interfaceSatParametersOrBuilder- Returns:
- The count of restartAlgorithms.
-
getRestartAlgorithms
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;- Specified by:
getRestartAlgorithmsin interfaceSatParametersOrBuilder- Parameters:
index- The index of the element to return.- Returns:
- The restartAlgorithms at the given index.
-
setRestartAlgorithms
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;- Parameters:
index- The index to set the value at.value- The restartAlgorithms to set.- Returns:
- This builder for chaining.
-
addRestartAlgorithms
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;- Parameters:
value- The restartAlgorithms to add.- Returns:
- This builder for chaining.
-
addAllRestartAlgorithms
public SatParameters.Builder addAllRestartAlgorithms(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;- Parameters:
values- The restartAlgorithms to add.- Returns:
- This builder for chaining.
-
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;- Returns:
- This builder for chaining.
-
hasDefaultRestartAlgorithms
public boolean hasDefaultRestartAlgorithms()optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];- Specified by:
hasDefaultRestartAlgorithmsin interfaceSatParametersOrBuilder- Returns:
- Whether the defaultRestartAlgorithms field is set.
-
getDefaultRestartAlgorithms
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];- Specified by:
getDefaultRestartAlgorithmsin interfaceSatParametersOrBuilder- Returns:
- The defaultRestartAlgorithms.
-
getDefaultRestartAlgorithmsBytes
public com.google.protobuf.ByteString getDefaultRestartAlgorithmsBytes()optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];- Specified by:
getDefaultRestartAlgorithmsBytesin interfaceSatParametersOrBuilder- Returns:
- The bytes for defaultRestartAlgorithms.
-
setDefaultRestartAlgorithms
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];- Parameters:
value- The defaultRestartAlgorithms to set.- Returns:
- This builder for chaining.
-
clearDefaultRestartAlgorithms
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];- Returns:
- This builder for chaining.
-
setDefaultRestartAlgorithmsBytes
optional string default_restart_algorithms = 70 [default = "LUBY_RESTART,LBD_MOVING_AVERAGE_RESTART,DL_MOVING_AVERAGE_RESTART"];- Parameters:
value- The bytes for defaultRestartAlgorithms to set.- Returns:
- This builder for chaining.
-
hasRestartPeriod
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];- Specified by:
hasRestartPeriodin interfaceSatParametersOrBuilder- Returns:
- Whether the restartPeriod field is set.
-
getRestartPeriod
public 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];- Specified by:
getRestartPeriodin interfaceSatParametersOrBuilder- Returns:
- The restartPeriod.
-
setRestartPeriod
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];- Parameters:
value- The restartPeriod to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasRestartRunningWindowSize
public boolean hasRestartRunningWindowSize()Size of the window for the moving average restarts.
optional int32 restart_running_window_size = 62 [default = 50];- Specified by:
hasRestartRunningWindowSizein interfaceSatParametersOrBuilder- Returns:
- Whether the restartRunningWindowSize field is set.
-
getRestartRunningWindowSize
public int getRestartRunningWindowSize()Size of the window for the moving average restarts.
optional int32 restart_running_window_size = 62 [default = 50];- Specified by:
getRestartRunningWindowSizein interfaceSatParametersOrBuilder- Returns:
- The restartRunningWindowSize.
-
setRestartRunningWindowSize
Size of the window for the moving average restarts.
optional int32 restart_running_window_size = 62 [default = 50];- Parameters:
value- The restartRunningWindowSize to set.- Returns:
- This builder for chaining.
-
clearRestartRunningWindowSize
Size of the window for the moving average restarts.
optional int32 restart_running_window_size = 62 [default = 50];- Returns:
- This builder for chaining.
-
hasRestartDlAverageRatio
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];- Specified by:
hasRestartDlAverageRatioin interfaceSatParametersOrBuilder- Returns:
- Whether the restartDlAverageRatio field is set.
-
getRestartDlAverageRatio
public 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];- Specified by:
getRestartDlAverageRatioin interfaceSatParametersOrBuilder- Returns:
- The restartDlAverageRatio.
-
setRestartDlAverageRatio
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];- Parameters:
value- The restartDlAverageRatio to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasRestartLbdAverageRatio
public boolean hasRestartLbdAverageRatio()optional double restart_lbd_average_ratio = 71 [default = 1];- Specified by:
hasRestartLbdAverageRatioin interfaceSatParametersOrBuilder- Returns:
- Whether the restartLbdAverageRatio field is set.
-
getRestartLbdAverageRatio
public double getRestartLbdAverageRatio()optional double restart_lbd_average_ratio = 71 [default = 1];- Specified by:
getRestartLbdAverageRatioin interfaceSatParametersOrBuilder- Returns:
- The restartLbdAverageRatio.
-
setRestartLbdAverageRatio
optional double restart_lbd_average_ratio = 71 [default = 1];- Parameters:
value- The restartLbdAverageRatio to set.- Returns:
- This builder for chaining.
-
clearRestartLbdAverageRatio
optional double restart_lbd_average_ratio = 71 [default = 1];- Returns:
- This builder for chaining.
-
hasUseBlockingRestart
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];- Specified by:
hasUseBlockingRestartin interfaceSatParametersOrBuilder- Returns:
- Whether the useBlockingRestart field is set.
-
getUseBlockingRestart
public 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];- Specified by:
getUseBlockingRestartin interfaceSatParametersOrBuilder- Returns:
- The useBlockingRestart.
-
setUseBlockingRestart
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];- Parameters:
value- The useBlockingRestart to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasBlockingRestartWindowSize
public boolean hasBlockingRestartWindowSize()optional int32 blocking_restart_window_size = 65 [default = 5000];- Specified by:
hasBlockingRestartWindowSizein interfaceSatParametersOrBuilder- Returns:
- Whether the blockingRestartWindowSize field is set.
-
getBlockingRestartWindowSize
public int getBlockingRestartWindowSize()optional int32 blocking_restart_window_size = 65 [default = 5000];- Specified by:
getBlockingRestartWindowSizein interfaceSatParametersOrBuilder- Returns:
- The blockingRestartWindowSize.
-
setBlockingRestartWindowSize
optional int32 blocking_restart_window_size = 65 [default = 5000];- Parameters:
value- The blockingRestartWindowSize to set.- Returns:
- This builder for chaining.
-
clearBlockingRestartWindowSize
optional int32 blocking_restart_window_size = 65 [default = 5000];- Returns:
- This builder for chaining.
-
hasBlockingRestartMultiplier
public boolean hasBlockingRestartMultiplier()optional double blocking_restart_multiplier = 66 [default = 1.4];- Specified by:
hasBlockingRestartMultiplierin interfaceSatParametersOrBuilder- Returns:
- Whether the blockingRestartMultiplier field is set.
-
getBlockingRestartMultiplier
public double getBlockingRestartMultiplier()optional double blocking_restart_multiplier = 66 [default = 1.4];- Specified by:
getBlockingRestartMultiplierin interfaceSatParametersOrBuilder- Returns:
- The blockingRestartMultiplier.
-
setBlockingRestartMultiplier
optional double blocking_restart_multiplier = 66 [default = 1.4];- Parameters:
value- The blockingRestartMultiplier to set.- Returns:
- This builder for chaining.
-
clearBlockingRestartMultiplier
optional double blocking_restart_multiplier = 66 [default = 1.4];- Returns:
- This builder for chaining.
-
hasNumConflictsBeforeStrategyChanges
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];- Specified by:
hasNumConflictsBeforeStrategyChangesin interfaceSatParametersOrBuilder- Returns:
- Whether the numConflictsBeforeStrategyChanges field is set.
-
getNumConflictsBeforeStrategyChanges
public 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];- Specified by:
getNumConflictsBeforeStrategyChangesin interfaceSatParametersOrBuilder- Returns:
- The numConflictsBeforeStrategyChanges.
-
setNumConflictsBeforeStrategyChanges
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];- Parameters:
value- The numConflictsBeforeStrategyChanges to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasStrategyChangeIncreaseRatio
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];- Specified by:
hasStrategyChangeIncreaseRatioin interfaceSatParametersOrBuilder- Returns:
- Whether the strategyChangeIncreaseRatio field is set.
-
getStrategyChangeIncreaseRatio
public 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];- Specified by:
getStrategyChangeIncreaseRatioin interfaceSatParametersOrBuilder- Returns:
- The strategyChangeIncreaseRatio.
-
setStrategyChangeIncreaseRatio
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];- Parameters:
value- The strategyChangeIncreaseRatio to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxTimeInSeconds
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];- Specified by:
hasMaxTimeInSecondsin interfaceSatParametersOrBuilder- Returns:
- Whether the maxTimeInSeconds field is set.
-
getMaxTimeInSeconds
public 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];- Specified by:
getMaxTimeInSecondsin interfaceSatParametersOrBuilder- Returns:
- The maxTimeInSeconds.
-
setMaxTimeInSeconds
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];- Parameters:
value- The maxTimeInSeconds to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxDeterministicTime
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];- Specified by:
hasMaxDeterministicTimein interfaceSatParametersOrBuilder- Returns:
- Whether the maxDeterministicTime field is set.
-
getMaxDeterministicTime
public 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];- Specified by:
getMaxDeterministicTimein interfaceSatParametersOrBuilder- Returns:
- The maxDeterministicTime.
-
setMaxDeterministicTime
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];- Parameters:
value- The maxDeterministicTime to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxNumDeterministicBatches
public boolean hasMaxNumDeterministicBatches()Stops after that number of batches has been scheduled. This only make sense when interleave_search is true.
optional int32 max_num_deterministic_batches = 291 [default = 0];- Specified by:
hasMaxNumDeterministicBatchesin interfaceSatParametersOrBuilder- Returns:
- Whether the maxNumDeterministicBatches field is set.
-
getMaxNumDeterministicBatches
public int getMaxNumDeterministicBatches()Stops after that number of batches has been scheduled. This only make sense when interleave_search is true.
optional int32 max_num_deterministic_batches = 291 [default = 0];- Specified by:
getMaxNumDeterministicBatchesin interfaceSatParametersOrBuilder- Returns:
- The maxNumDeterministicBatches.
-
setMaxNumDeterministicBatches
Stops after that number of batches has been scheduled. This only make sense when interleave_search is true.
optional int32 max_num_deterministic_batches = 291 [default = 0];- Parameters:
value- The maxNumDeterministicBatches to set.- Returns:
- This builder for chaining.
-
clearMaxNumDeterministicBatches
Stops after that number of batches has been scheduled. This only make sense when interleave_search is true.
optional int32 max_num_deterministic_batches = 291 [default = 0];- Returns:
- This builder for chaining.
-
hasMaxNumberOfConflicts
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];- Specified by:
hasMaxNumberOfConflictsin interfaceSatParametersOrBuilder- Returns:
- Whether the maxNumberOfConflicts field is set.
-
getMaxNumberOfConflicts
public 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];- Specified by:
getMaxNumberOfConflictsin interfaceSatParametersOrBuilder- Returns:
- The maxNumberOfConflicts.
-
setMaxNumberOfConflicts
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];- Parameters:
value- The maxNumberOfConflicts to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxMemoryInMb
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];- Specified by:
hasMaxMemoryInMbin interfaceSatParametersOrBuilder- Returns:
- Whether the maxMemoryInMb field is set.
-
getMaxMemoryInMb
public 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];- Specified by:
getMaxMemoryInMbin interfaceSatParametersOrBuilder- Returns:
- The maxMemoryInMb.
-
setMaxMemoryInMb
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];- Parameters:
value- The maxMemoryInMb to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAbsoluteGapLimit
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];- Specified by:
hasAbsoluteGapLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the absoluteGapLimit field is set.
-
getAbsoluteGapLimit
public 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];- Specified by:
getAbsoluteGapLimitin interfaceSatParametersOrBuilder- Returns:
- The absoluteGapLimit.
-
setAbsoluteGapLimit
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];- Parameters:
value- The absoluteGapLimit to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasRelativeGapLimit
public boolean hasRelativeGapLimit()optional double relative_gap_limit = 160 [default = 0];- Specified by:
hasRelativeGapLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the relativeGapLimit field is set.
-
getRelativeGapLimit
public double getRelativeGapLimit()optional double relative_gap_limit = 160 [default = 0];- Specified by:
getRelativeGapLimitin interfaceSatParametersOrBuilder- Returns:
- The relativeGapLimit.
-
setRelativeGapLimit
optional double relative_gap_limit = 160 [default = 0];- Parameters:
value- The relativeGapLimit to set.- Returns:
- This builder for chaining.
-
clearRelativeGapLimit
optional double relative_gap_limit = 160 [default = 0];- Returns:
- This builder for chaining.
-
hasRandomSeed
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];- Specified by:
hasRandomSeedin interfaceSatParametersOrBuilder- Returns:
- Whether the randomSeed field is set.
-
getRandomSeed
public 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];- Specified by:
getRandomSeedin interfaceSatParametersOrBuilder- Returns:
- The randomSeed.
-
setRandomSeed
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];- Parameters:
value- The randomSeed to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasPermuteVariableRandomly
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];- Specified by:
hasPermuteVariableRandomlyin interfaceSatParametersOrBuilder- Returns:
- Whether the permuteVariableRandomly field is set.
-
getPermuteVariableRandomly
public 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];- Specified by:
getPermuteVariableRandomlyin interfaceSatParametersOrBuilder- Returns:
- The permuteVariableRandomly.
-
setPermuteVariableRandomly
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];- Parameters:
value- The permuteVariableRandomly to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasPermutePresolveConstraintOrder
public boolean hasPermutePresolveConstraintOrder()optional bool permute_presolve_constraint_order = 179 [default = false];- Specified by:
hasPermutePresolveConstraintOrderin interfaceSatParametersOrBuilder- Returns:
- Whether the permutePresolveConstraintOrder field is set.
-
getPermutePresolveConstraintOrder
public boolean getPermutePresolveConstraintOrder()optional bool permute_presolve_constraint_order = 179 [default = false];- Specified by:
getPermutePresolveConstraintOrderin interfaceSatParametersOrBuilder- Returns:
- The permutePresolveConstraintOrder.
-
setPermutePresolveConstraintOrder
optional bool permute_presolve_constraint_order = 179 [default = false];- Parameters:
value- The permutePresolveConstraintOrder to set.- Returns:
- This builder for chaining.
-
clearPermutePresolveConstraintOrder
optional bool permute_presolve_constraint_order = 179 [default = false];- Returns:
- This builder for chaining.
-
hasUseAbslRandom
public boolean hasUseAbslRandom()optional bool use_absl_random = 180 [default = false];- Specified by:
hasUseAbslRandomin interfaceSatParametersOrBuilder- Returns:
- Whether the useAbslRandom field is set.
-
getUseAbslRandom
public boolean getUseAbslRandom()optional bool use_absl_random = 180 [default = false];- Specified by:
getUseAbslRandomin interfaceSatParametersOrBuilder- Returns:
- The useAbslRandom.
-
setUseAbslRandom
optional bool use_absl_random = 180 [default = false];- Parameters:
value- The useAbslRandom to set.- Returns:
- This builder for chaining.
-
clearUseAbslRandom
optional bool use_absl_random = 180 [default = false];- Returns:
- This builder for chaining.
-
hasLogSearchProgress
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];- Specified by:
hasLogSearchProgressin interfaceSatParametersOrBuilder- Returns:
- Whether the logSearchProgress field is set.
-
getLogSearchProgress
public 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];- Specified by:
getLogSearchProgressin interfaceSatParametersOrBuilder- Returns:
- The logSearchProgress.
-
setLogSearchProgress
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];- Parameters:
value- The logSearchProgress to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasLogSubsolverStatistics
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];- Specified by:
hasLogSubsolverStatisticsin interfaceSatParametersOrBuilder- Returns:
- Whether the logSubsolverStatistics field is set.
-
getLogSubsolverStatistics
public 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];- Specified by:
getLogSubsolverStatisticsin interfaceSatParametersOrBuilder- Returns:
- The logSubsolverStatistics.
-
setLogSubsolverStatistics
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];- Parameters:
value- The logSubsolverStatistics to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasLogPrefix
public boolean hasLogPrefix()Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];- Specified by:
hasLogPrefixin interfaceSatParametersOrBuilder- Returns:
- Whether the logPrefix field is set.
-
getLogPrefix
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];- Specified by:
getLogPrefixin interfaceSatParametersOrBuilder- Returns:
- The logPrefix.
-
getLogPrefixBytes
public com.google.protobuf.ByteString getLogPrefixBytes()Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];- Specified by:
getLogPrefixBytesin interfaceSatParametersOrBuilder- Returns:
- The bytes for logPrefix.
-
setLogPrefix
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];- Parameters:
value- The logPrefix to set.- Returns:
- This builder for chaining.
-
clearLogPrefix
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];- Returns:
- This builder for chaining.
-
setLogPrefixBytes
Add a prefix to all logs.
optional string log_prefix = 185 [default = ""];- Parameters:
value- The bytes for logPrefix to set.- Returns:
- This builder for chaining.
-
hasLogToStdout
public boolean hasLogToStdout()Log to stdout.
optional bool log_to_stdout = 186 [default = true];- Specified by:
hasLogToStdoutin interfaceSatParametersOrBuilder- Returns:
- Whether the logToStdout field is set.
-
getLogToStdout
public boolean getLogToStdout()Log to stdout.
optional bool log_to_stdout = 186 [default = true];- Specified by:
getLogToStdoutin interfaceSatParametersOrBuilder- Returns:
- The logToStdout.
-
setLogToStdout
Log to stdout.
optional bool log_to_stdout = 186 [default = true];- Parameters:
value- The logToStdout to set.- Returns:
- This builder for chaining.
-
clearLogToStdout
Log to stdout.
optional bool log_to_stdout = 186 [default = true];- Returns:
- This builder for chaining.
-
hasLogToResponse
public boolean hasLogToResponse()Log to response proto.
optional bool log_to_response = 187 [default = false];- Specified by:
hasLogToResponsein interfaceSatParametersOrBuilder- Returns:
- Whether the logToResponse field is set.
-
getLogToResponse
public boolean getLogToResponse()Log to response proto.
optional bool log_to_response = 187 [default = false];- Specified by:
getLogToResponsein interfaceSatParametersOrBuilder- Returns:
- The logToResponse.
-
setLogToResponse
Log to response proto.
optional bool log_to_response = 187 [default = false];- Parameters:
value- The logToResponse to set.- Returns:
- This builder for chaining.
-
clearLogToResponse
Log to response proto.
optional bool log_to_response = 187 [default = false];- Returns:
- This builder for chaining.
-
hasUsePbResolution
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];- Specified by:
hasUsePbResolutionin interfaceSatParametersOrBuilder- Returns:
- Whether the usePbResolution field is set.
-
getUsePbResolution
public 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];- Specified by:
getUsePbResolutionin interfaceSatParametersOrBuilder- Returns:
- The usePbResolution.
-
setUsePbResolution
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];- Parameters:
value- The usePbResolution to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMinimizeReductionDuringPbResolution
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];- Specified by:
hasMinimizeReductionDuringPbResolutionin interfaceSatParametersOrBuilder- Returns:
- Whether the minimizeReductionDuringPbResolution field is set.
-
getMinimizeReductionDuringPbResolution
public 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];- Specified by:
getMinimizeReductionDuringPbResolutionin interfaceSatParametersOrBuilder- Returns:
- The minimizeReductionDuringPbResolution.
-
setMinimizeReductionDuringPbResolution
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];- Parameters:
value- The minimizeReductionDuringPbResolution to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasCountAssumptionLevelsInLbd
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];- Specified by:
hasCountAssumptionLevelsInLbdin interfaceSatParametersOrBuilder- Returns:
- Whether the countAssumptionLevelsInLbd field is set.
-
getCountAssumptionLevelsInLbd
public 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];- Specified by:
getCountAssumptionLevelsInLbdin interfaceSatParametersOrBuilder- Returns:
- The countAssumptionLevelsInLbd.
-
setCountAssumptionLevelsInLbd
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];- Parameters:
value- The countAssumptionLevelsInLbd to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasPresolveBveThreshold
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];- Specified by:
hasPresolveBveThresholdin interfaceSatParametersOrBuilder- Returns:
- Whether the presolveBveThreshold field is set.
-
getPresolveBveThreshold
public 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];- Specified by:
getPresolveBveThresholdin interfaceSatParametersOrBuilder- Returns:
- The presolveBveThreshold.
-
setPresolveBveThreshold
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];- Parameters:
value- The presolveBveThreshold to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasFilterSatPostsolveClauses
public boolean hasFilterSatPostsolveClauses()Internal parameter. During BVE, if we eliminate a variable x, by default we will push all clauses containing x and all clauses containing not(x) to the postsolve. However, it is possible to write the postsolve code so that only one such set is needed. The idea is that, if we push the set containing a literal l, is to set l to false except if it is needed to satisfy one of the clause in the set. This is always beneficial, but for historical reason, not all our postsolve algorithm support this.
optional bool filter_sat_postsolve_clauses = 324 [default = false];- Specified by:
hasFilterSatPostsolveClausesin interfaceSatParametersOrBuilder- Returns:
- Whether the filterSatPostsolveClauses field is set.
-
getFilterSatPostsolveClauses
public boolean getFilterSatPostsolveClauses()Internal parameter. During BVE, if we eliminate a variable x, by default we will push all clauses containing x and all clauses containing not(x) to the postsolve. However, it is possible to write the postsolve code so that only one such set is needed. The idea is that, if we push the set containing a literal l, is to set l to false except if it is needed to satisfy one of the clause in the set. This is always beneficial, but for historical reason, not all our postsolve algorithm support this.
optional bool filter_sat_postsolve_clauses = 324 [default = false];- Specified by:
getFilterSatPostsolveClausesin interfaceSatParametersOrBuilder- Returns:
- The filterSatPostsolveClauses.
-
setFilterSatPostsolveClauses
Internal parameter. During BVE, if we eliminate a variable x, by default we will push all clauses containing x and all clauses containing not(x) to the postsolve. However, it is possible to write the postsolve code so that only one such set is needed. The idea is that, if we push the set containing a literal l, is to set l to false except if it is needed to satisfy one of the clause in the set. This is always beneficial, but for historical reason, not all our postsolve algorithm support this.
optional bool filter_sat_postsolve_clauses = 324 [default = false];- Parameters:
value- The filterSatPostsolveClauses to set.- Returns:
- This builder for chaining.
-
clearFilterSatPostsolveClauses
Internal parameter. During BVE, if we eliminate a variable x, by default we will push all clauses containing x and all clauses containing not(x) to the postsolve. However, it is possible to write the postsolve code so that only one such set is needed. The idea is that, if we push the set containing a literal l, is to set l to false except if it is needed to satisfy one of the clause in the set. This is always beneficial, but for historical reason, not all our postsolve algorithm support this.
optional bool filter_sat_postsolve_clauses = 324 [default = false];- Returns:
- This builder for chaining.
-
hasPresolveBveClauseWeight
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];- Specified by:
hasPresolveBveClauseWeightin interfaceSatParametersOrBuilder- Returns:
- Whether the presolveBveClauseWeight field is set.
-
getPresolveBveClauseWeight
public 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];- Specified by:
getPresolveBveClauseWeightin interfaceSatParametersOrBuilder- Returns:
- The presolveBveClauseWeight.
-
setPresolveBveClauseWeight
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];- Parameters:
value- The presolveBveClauseWeight to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasProbingDeterministicTimeLimit
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];- Specified by:
hasProbingDeterministicTimeLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the probingDeterministicTimeLimit field is set.
-
getProbingDeterministicTimeLimit
public 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];- Specified by:
getProbingDeterministicTimeLimitin interfaceSatParametersOrBuilder- Returns:
- The probingDeterministicTimeLimit.
-
setProbingDeterministicTimeLimit
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];- Parameters:
value- The probingDeterministicTimeLimit to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasPresolveProbingDeterministicTimeLimit
public boolean hasPresolveProbingDeterministicTimeLimit()optional double presolve_probing_deterministic_time_limit = 57 [default = 30];- Specified by:
hasPresolveProbingDeterministicTimeLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the presolveProbingDeterministicTimeLimit field is set.
-
getPresolveProbingDeterministicTimeLimit
public double getPresolveProbingDeterministicTimeLimit()optional double presolve_probing_deterministic_time_limit = 57 [default = 30];- Specified by:
getPresolveProbingDeterministicTimeLimitin interfaceSatParametersOrBuilder- Returns:
- The presolveProbingDeterministicTimeLimit.
-
setPresolveProbingDeterministicTimeLimit
optional double presolve_probing_deterministic_time_limit = 57 [default = 30];- Parameters:
value- The presolveProbingDeterministicTimeLimit to set.- Returns:
- This builder for chaining.
-
clearPresolveProbingDeterministicTimeLimit
optional double presolve_probing_deterministic_time_limit = 57 [default = 30];- Returns:
- This builder for chaining.
-
hasPresolveBlockedClause
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];- Specified by:
hasPresolveBlockedClausein interfaceSatParametersOrBuilder- Returns:
- Whether the presolveBlockedClause field is set.
-
getPresolveBlockedClause
public 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];- Specified by:
getPresolveBlockedClausein interfaceSatParametersOrBuilder- Returns:
- The presolveBlockedClause.
-
setPresolveBlockedClause
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];- Parameters:
value- The presolveBlockedClause to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasPresolveUseBva
public boolean hasPresolveUseBva()Whether or not we use Bounded Variable Addition (BVA) in the presolve.
optional bool presolve_use_bva = 72 [default = true];- Specified by:
hasPresolveUseBvain interfaceSatParametersOrBuilder- Returns:
- Whether the presolveUseBva field is set.
-
getPresolveUseBva
public boolean getPresolveUseBva()Whether or not we use Bounded Variable Addition (BVA) in the presolve.
optional bool presolve_use_bva = 72 [default = true];- Specified by:
getPresolveUseBvain interfaceSatParametersOrBuilder- Returns:
- The presolveUseBva.
-
setPresolveUseBva
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
optional bool presolve_use_bva = 72 [default = true];- Parameters:
value- The presolveUseBva to set.- Returns:
- This builder for chaining.
-
clearPresolveUseBva
Whether or not we use Bounded Variable Addition (BVA) in the presolve.
optional bool presolve_use_bva = 72 [default = true];- Returns:
- This builder for chaining.
-
hasPresolveBvaThreshold
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];- Specified by:
hasPresolveBvaThresholdin interfaceSatParametersOrBuilder- Returns:
- Whether the presolveBvaThreshold field is set.
-
getPresolveBvaThreshold
public 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];- Specified by:
getPresolveBvaThresholdin interfaceSatParametersOrBuilder- Returns:
- The presolveBvaThreshold.
-
setPresolveBvaThreshold
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];- Parameters:
value- The presolveBvaThreshold to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxPresolveIterations
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];- Specified by:
hasMaxPresolveIterationsin interfaceSatParametersOrBuilder- Returns:
- Whether the maxPresolveIterations field is set.
-
getMaxPresolveIterations
public 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];- Specified by:
getMaxPresolveIterationsin interfaceSatParametersOrBuilder- Returns:
- The maxPresolveIterations.
-
setMaxPresolveIterations
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];- Parameters:
value- The maxPresolveIterations to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasCpModelPresolve
public boolean hasCpModelPresolve()Whether we presolve the cp_model before solving it.
optional bool cp_model_presolve = 86 [default = true];- Specified by:
hasCpModelPresolvein interfaceSatParametersOrBuilder- Returns:
- Whether the cpModelPresolve field is set.
-
getCpModelPresolve
public boolean getCpModelPresolve()Whether we presolve the cp_model before solving it.
optional bool cp_model_presolve = 86 [default = true];- Specified by:
getCpModelPresolvein interfaceSatParametersOrBuilder- Returns:
- The cpModelPresolve.
-
setCpModelPresolve
Whether we presolve the cp_model before solving it.
optional bool cp_model_presolve = 86 [default = true];- Parameters:
value- The cpModelPresolve to set.- Returns:
- This builder for chaining.
-
clearCpModelPresolve
Whether we presolve the cp_model before solving it.
optional bool cp_model_presolve = 86 [default = true];- Returns:
- This builder for chaining.
-
hasCpModelProbingLevel
public boolean hasCpModelProbingLevel()How much effort do we spend on probing. 0 disables it completely.
optional int32 cp_model_probing_level = 110 [default = 2];- Specified by:
hasCpModelProbingLevelin interfaceSatParametersOrBuilder- Returns:
- Whether the cpModelProbingLevel field is set.
-
getCpModelProbingLevel
public int getCpModelProbingLevel()How much effort do we spend on probing. 0 disables it completely.
optional int32 cp_model_probing_level = 110 [default = 2];- Specified by:
getCpModelProbingLevelin interfaceSatParametersOrBuilder- Returns:
- The cpModelProbingLevel.
-
setCpModelProbingLevel
How much effort do we spend on probing. 0 disables it completely.
optional int32 cp_model_probing_level = 110 [default = 2];- Parameters:
value- The cpModelProbingLevel to set.- Returns:
- This builder for chaining.
-
clearCpModelProbingLevel
How much effort do we spend on probing. 0 disables it completely.
optional int32 cp_model_probing_level = 110 [default = 2];- Returns:
- This builder for chaining.
-
hasCpModelUseSatPresolve
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];- Specified by:
hasCpModelUseSatPresolvein interfaceSatParametersOrBuilder- Returns:
- Whether the cpModelUseSatPresolve field is set.
-
getCpModelUseSatPresolve
public 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];- Specified by:
getCpModelUseSatPresolvein interfaceSatParametersOrBuilder- Returns:
- The cpModelUseSatPresolve.
-
setCpModelUseSatPresolve
Whether we also use the sat presolve when cp_model_presolve is true.
optional bool cp_model_use_sat_presolve = 93 [default = true];- Parameters:
value- The cpModelUseSatPresolve to set.- Returns:
- This builder for chaining.
-
clearCpModelUseSatPresolve
Whether we also use the sat presolve when cp_model_presolve is true.
optional bool cp_model_use_sat_presolve = 93 [default = true];- Returns:
- This builder for chaining.
-
hasRemoveFixedVariablesEarly
public boolean hasRemoveFixedVariablesEarly()If cp_model_presolve is true and there is a large proportion of fixed variable after the first model copy, remap all the model to a dense set of variable before the full presolve even starts. This should help for LNS on large models.
optional bool remove_fixed_variables_early = 310 [default = true];- Specified by:
hasRemoveFixedVariablesEarlyin interfaceSatParametersOrBuilder- Returns:
- Whether the removeFixedVariablesEarly field is set.
-
getRemoveFixedVariablesEarly
public boolean getRemoveFixedVariablesEarly()If cp_model_presolve is true and there is a large proportion of fixed variable after the first model copy, remap all the model to a dense set of variable before the full presolve even starts. This should help for LNS on large models.
optional bool remove_fixed_variables_early = 310 [default = true];- Specified by:
getRemoveFixedVariablesEarlyin interfaceSatParametersOrBuilder- Returns:
- The removeFixedVariablesEarly.
-
setRemoveFixedVariablesEarly
If cp_model_presolve is true and there is a large proportion of fixed variable after the first model copy, remap all the model to a dense set of variable before the full presolve even starts. This should help for LNS on large models.
optional bool remove_fixed_variables_early = 310 [default = true];- Parameters:
value- The removeFixedVariablesEarly to set.- Returns:
- This builder for chaining.
-
clearRemoveFixedVariablesEarly
If cp_model_presolve is true and there is a large proportion of fixed variable after the first model copy, remap all the model to a dense set of variable before the full presolve even starts. This should help for LNS on large models.
optional bool remove_fixed_variables_early = 310 [default = true];- Returns:
- This builder for chaining.
-
hasDetectTableWithCost
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];- Specified by:
hasDetectTableWithCostin interfaceSatParametersOrBuilder- Returns:
- Whether the detectTableWithCost field is set.
-
getDetectTableWithCost
public 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];- Specified by:
getDetectTableWithCostin interfaceSatParametersOrBuilder- Returns:
- The detectTableWithCost.
-
setDetectTableWithCost
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];- Parameters:
value- The detectTableWithCost to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasTableCompressionLevel
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];- Specified by:
hasTableCompressionLevelin interfaceSatParametersOrBuilder- Returns:
- Whether the tableCompressionLevel field is set.
-
getTableCompressionLevel
public 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];- Specified by:
getTableCompressionLevelin interfaceSatParametersOrBuilder- Returns:
- The tableCompressionLevel.
-
setTableCompressionLevel
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];- Parameters:
value- The tableCompressionLevel to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasExpandAlldiffConstraints
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];- Specified by:
hasExpandAlldiffConstraintsin interfaceSatParametersOrBuilder- Returns:
- Whether the expandAlldiffConstraints field is set.
-
getExpandAlldiffConstraints
public 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];- Specified by:
getExpandAlldiffConstraintsin interfaceSatParametersOrBuilder- Returns:
- The expandAlldiffConstraints.
-
setExpandAlldiffConstraints
If true, expand all_different constraints that are not permutations. Permutations (#Variables = #Values) are always expanded.
optional bool expand_alldiff_constraints = 170 [default = false];- Parameters:
value- The expandAlldiffConstraints to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxAlldiffDomainSize
public boolean hasMaxAlldiffDomainSize()Max domain size for all_different constraints to be expanded.
optional int32 max_alldiff_domain_size = 320 [default = 256];- Specified by:
hasMaxAlldiffDomainSizein interfaceSatParametersOrBuilder- Returns:
- Whether the maxAlldiffDomainSize field is set.
-
getMaxAlldiffDomainSize
public int getMaxAlldiffDomainSize()Max domain size for all_different constraints to be expanded.
optional int32 max_alldiff_domain_size = 320 [default = 256];- Specified by:
getMaxAlldiffDomainSizein interfaceSatParametersOrBuilder- Returns:
- The maxAlldiffDomainSize.
-
setMaxAlldiffDomainSize
Max domain size for all_different constraints to be expanded.
optional int32 max_alldiff_domain_size = 320 [default = 256];- Parameters:
value- The maxAlldiffDomainSize to set.- Returns:
- This builder for chaining.
-
clearMaxAlldiffDomainSize
Max domain size for all_different constraints to be expanded.
optional int32 max_alldiff_domain_size = 320 [default = 256];- Returns:
- This builder for chaining.
-
hasExpandReservoirConstraints
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];- Specified by:
hasExpandReservoirConstraintsin interfaceSatParametersOrBuilder- Returns:
- Whether the expandReservoirConstraints field is set.
-
getExpandReservoirConstraints
public 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];- Specified by:
getExpandReservoirConstraintsin interfaceSatParametersOrBuilder- Returns:
- The expandReservoirConstraints.
-
setExpandReservoirConstraints
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];- Parameters:
value- The expandReservoirConstraints to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasExpandReservoirUsingCircuit
public boolean hasExpandReservoirUsingCircuit()Mainly useful for testing. If this and expand_reservoir_constraints is true, we use a different encoding of the reservoir constraint using circuit instead of precedences. Note that this is usually slower, but can exercise different part of the solver. Note that contrary to the precedence encoding, this easily support variable demands. WARNING: with this encoding, the constraint takes a slightly different meaning. There must exist a permutation of the events occurring at the same time such that the level is within the reservoir after each of these events (in this permuted order). So we cannot have +100 and -100 at the same time if the level must be between 0 and 10 (as authorized by the reservoir constraint).
optional bool expand_reservoir_using_circuit = 288 [default = false];- Specified by:
hasExpandReservoirUsingCircuitin interfaceSatParametersOrBuilder- Returns:
- Whether the expandReservoirUsingCircuit field is set.
-
getExpandReservoirUsingCircuit
public boolean getExpandReservoirUsingCircuit()Mainly useful for testing. If this and expand_reservoir_constraints is true, we use a different encoding of the reservoir constraint using circuit instead of precedences. Note that this is usually slower, but can exercise different part of the solver. Note that contrary to the precedence encoding, this easily support variable demands. WARNING: with this encoding, the constraint takes a slightly different meaning. There must exist a permutation of the events occurring at the same time such that the level is within the reservoir after each of these events (in this permuted order). So we cannot have +100 and -100 at the same time if the level must be between 0 and 10 (as authorized by the reservoir constraint).
optional bool expand_reservoir_using_circuit = 288 [default = false];- Specified by:
getExpandReservoirUsingCircuitin interfaceSatParametersOrBuilder- Returns:
- The expandReservoirUsingCircuit.
-
setExpandReservoirUsingCircuit
Mainly useful for testing. If this and expand_reservoir_constraints is true, we use a different encoding of the reservoir constraint using circuit instead of precedences. Note that this is usually slower, but can exercise different part of the solver. Note that contrary to the precedence encoding, this easily support variable demands. WARNING: with this encoding, the constraint takes a slightly different meaning. There must exist a permutation of the events occurring at the same time such that the level is within the reservoir after each of these events (in this permuted order). So we cannot have +100 and -100 at the same time if the level must be between 0 and 10 (as authorized by the reservoir constraint).
optional bool expand_reservoir_using_circuit = 288 [default = false];- Parameters:
value- The expandReservoirUsingCircuit to set.- Returns:
- This builder for chaining.
-
clearExpandReservoirUsingCircuit
Mainly useful for testing. If this and expand_reservoir_constraints is true, we use a different encoding of the reservoir constraint using circuit instead of precedences. Note that this is usually slower, but can exercise different part of the solver. Note that contrary to the precedence encoding, this easily support variable demands. WARNING: with this encoding, the constraint takes a slightly different meaning. There must exist a permutation of the events occurring at the same time such that the level is within the reservoir after each of these events (in this permuted order). So we cannot have +100 and -100 at the same time if the level must be between 0 and 10 (as authorized by the reservoir constraint).
optional bool expand_reservoir_using_circuit = 288 [default = false];- Returns:
- This builder for chaining.
-
hasEncodeCumulativeAsReservoir
public boolean hasEncodeCumulativeAsReservoir()Encore cumulative with fixed demands and capacity as a reservoir constraint. The only reason you might want to do that is to test the reservoir propagation code!
optional bool encode_cumulative_as_reservoir = 287 [default = false];- Specified by:
hasEncodeCumulativeAsReservoirin interfaceSatParametersOrBuilder- Returns:
- Whether the encodeCumulativeAsReservoir field is set.
-
getEncodeCumulativeAsReservoir
public boolean getEncodeCumulativeAsReservoir()Encore cumulative with fixed demands and capacity as a reservoir constraint. The only reason you might want to do that is to test the reservoir propagation code!
optional bool encode_cumulative_as_reservoir = 287 [default = false];- Specified by:
getEncodeCumulativeAsReservoirin interfaceSatParametersOrBuilder- Returns:
- The encodeCumulativeAsReservoir.
-
setEncodeCumulativeAsReservoir
Encore cumulative with fixed demands and capacity as a reservoir constraint. The only reason you might want to do that is to test the reservoir propagation code!
optional bool encode_cumulative_as_reservoir = 287 [default = false];- Parameters:
value- The encodeCumulativeAsReservoir to set.- Returns:
- This builder for chaining.
-
clearEncodeCumulativeAsReservoir
Encore cumulative with fixed demands and capacity as a reservoir constraint. The only reason you might want to do that is to test the reservoir propagation code!
optional bool encode_cumulative_as_reservoir = 287 [default = false];- Returns:
- This builder for chaining.
-
hasMaxLinMaxSizeForExpansion
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];- Specified by:
hasMaxLinMaxSizeForExpansionin interfaceSatParametersOrBuilder- Returns:
- Whether the maxLinMaxSizeForExpansion field is set.
-
getMaxLinMaxSizeForExpansion
public 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];- Specified by:
getMaxLinMaxSizeForExpansionin interfaceSatParametersOrBuilder- Returns:
- The maxLinMaxSizeForExpansion.
-
setMaxLinMaxSizeForExpansion
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];- Parameters:
value- The maxLinMaxSizeForExpansion to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasDisableConstraintExpansion
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];- Specified by:
hasDisableConstraintExpansionin interfaceSatParametersOrBuilder- Returns:
- Whether the disableConstraintExpansion field is set.
-
getDisableConstraintExpansion
public 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];- Specified by:
getDisableConstraintExpansionin interfaceSatParametersOrBuilder- Returns:
- The disableConstraintExpansion.
-
setDisableConstraintExpansion
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];- Parameters:
value- The disableConstraintExpansion to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasEncodeComplexLinearConstraintWithInteger
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];- Specified by:
hasEncodeComplexLinearConstraintWithIntegerin interfaceSatParametersOrBuilder- Returns:
- Whether the encodeComplexLinearConstraintWithInteger field is set.
-
getEncodeComplexLinearConstraintWithInteger
public 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];- Specified by:
getEncodeComplexLinearConstraintWithIntegerin interfaceSatParametersOrBuilder- Returns:
- The encodeComplexLinearConstraintWithInteger.
-
setEncodeComplexLinearConstraintWithInteger
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];- Parameters:
value- The encodeComplexLinearConstraintWithInteger to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMergeNoOverlapWorkLimit
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];- Specified by:
hasMergeNoOverlapWorkLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the mergeNoOverlapWorkLimit field is set.
-
getMergeNoOverlapWorkLimit
public 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];- Specified by:
getMergeNoOverlapWorkLimitin interfaceSatParametersOrBuilder- Returns:
- The mergeNoOverlapWorkLimit.
-
setMergeNoOverlapWorkLimit
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];- Parameters:
value- The mergeNoOverlapWorkLimit to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMergeAtMostOneWorkLimit
public boolean hasMergeAtMostOneWorkLimit()optional double merge_at_most_one_work_limit = 146 [default = 100000000];- Specified by:
hasMergeAtMostOneWorkLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the mergeAtMostOneWorkLimit field is set.
-
getMergeAtMostOneWorkLimit
public double getMergeAtMostOneWorkLimit()optional double merge_at_most_one_work_limit = 146 [default = 100000000];- Specified by:
getMergeAtMostOneWorkLimitin interfaceSatParametersOrBuilder- Returns:
- The mergeAtMostOneWorkLimit.
-
setMergeAtMostOneWorkLimit
optional double merge_at_most_one_work_limit = 146 [default = 100000000];- Parameters:
value- The mergeAtMostOneWorkLimit to set.- Returns:
- This builder for chaining.
-
clearMergeAtMostOneWorkLimit
optional double merge_at_most_one_work_limit = 146 [default = 100000000];- Returns:
- This builder for chaining.
-
hasPresolveSubstitutionLevel
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];- Specified by:
hasPresolveSubstitutionLevelin interfaceSatParametersOrBuilder- Returns:
- Whether the presolveSubstitutionLevel field is set.
-
getPresolveSubstitutionLevel
public 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];- Specified by:
getPresolveSubstitutionLevelin interfaceSatParametersOrBuilder- Returns:
- The presolveSubstitutionLevel.
-
setPresolveSubstitutionLevel
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];- Parameters:
value- The presolveSubstitutionLevel to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasPresolveExtractIntegerEnforcement
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];- Specified by:
hasPresolveExtractIntegerEnforcementin interfaceSatParametersOrBuilder- Returns:
- Whether the presolveExtractIntegerEnforcement field is set.
-
getPresolveExtractIntegerEnforcement
public 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];- Specified by:
getPresolveExtractIntegerEnforcementin interfaceSatParametersOrBuilder- Returns:
- The presolveExtractIntegerEnforcement.
-
setPresolveExtractIntegerEnforcement
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];- Parameters:
value- The presolveExtractIntegerEnforcement to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasPresolveInclusionWorkLimit
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];- Specified by:
hasPresolveInclusionWorkLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the presolveInclusionWorkLimit field is set.
-
getPresolveInclusionWorkLimit
public 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];- Specified by:
getPresolveInclusionWorkLimitin interfaceSatParametersOrBuilder- Returns:
- The presolveInclusionWorkLimit.
-
setPresolveInclusionWorkLimit
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];- Parameters:
value- The presolveInclusionWorkLimit to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasIgnoreNames
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];- Specified by:
hasIgnoreNamesin interfaceSatParametersOrBuilder- Returns:
- Whether the ignoreNames field is set.
-
getIgnoreNames
public 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];- Specified by:
getIgnoreNamesin interfaceSatParametersOrBuilder- Returns:
- The ignoreNames.
-
setIgnoreNames
If true, we don't keep names in our internal copy of the user given model.
optional bool ignore_names = 202 [default = true];- Parameters:
value- The ignoreNames to set.- Returns:
- This builder for chaining.
-
clearIgnoreNames
If true, we don't keep names in our internal copy of the user given model.
optional bool ignore_names = 202 [default = true];- Returns:
- This builder for chaining.
-
hasInferAllDiffs
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];- Specified by:
hasInferAllDiffsin interfaceSatParametersOrBuilder- Returns:
- Whether the inferAllDiffs field is set.
-
getInferAllDiffs
public 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];- Specified by:
getInferAllDiffsin interfaceSatParametersOrBuilder- Returns:
- The inferAllDiffs.
-
setInferAllDiffs
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];- Parameters:
value- The inferAllDiffs to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasFindBigLinearOverlap
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];- Specified by:
hasFindBigLinearOverlapin interfaceSatParametersOrBuilder- Returns:
- Whether the findBigLinearOverlap field is set.
-
getFindBigLinearOverlap
public 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];- Specified by:
getFindBigLinearOverlapin interfaceSatParametersOrBuilder- Returns:
- The findBigLinearOverlap.
-
setFindBigLinearOverlap
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];- Parameters:
value- The findBigLinearOverlap to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseSatInprocessing
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];- Specified by:
hasUseSatInprocessingin interfaceSatParametersOrBuilder- Returns:
- Whether the useSatInprocessing field is set.
-
getUseSatInprocessing
public 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];- Specified by:
getUseSatInprocessingin interfaceSatParametersOrBuilder- Returns:
- The useSatInprocessing.
-
setUseSatInprocessing
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];- Parameters:
value- The useSatInprocessing to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasInprocessingDtimeRatio
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];- Specified by:
hasInprocessingDtimeRatioin interfaceSatParametersOrBuilder- Returns:
- Whether the inprocessingDtimeRatio field is set.
-
getInprocessingDtimeRatio
public 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];- Specified by:
getInprocessingDtimeRatioin interfaceSatParametersOrBuilder- Returns:
- The inprocessingDtimeRatio.
-
setInprocessingDtimeRatio
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];- Parameters:
value- The inprocessingDtimeRatio to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasInprocessingProbingDtime
public boolean hasInprocessingProbingDtime()The amount of dtime we should spend on probing for each inprocessing round.
optional double inprocessing_probing_dtime = 274 [default = 1];- Specified by:
hasInprocessingProbingDtimein interfaceSatParametersOrBuilder- Returns:
- Whether the inprocessingProbingDtime field is set.
-
getInprocessingProbingDtime
public double getInprocessingProbingDtime()The amount of dtime we should spend on probing for each inprocessing round.
optional double inprocessing_probing_dtime = 274 [default = 1];- Specified by:
getInprocessingProbingDtimein interfaceSatParametersOrBuilder- Returns:
- The inprocessingProbingDtime.
-
setInprocessingProbingDtime
The amount of dtime we should spend on probing for each inprocessing round.
optional double inprocessing_probing_dtime = 274 [default = 1];- Parameters:
value- The inprocessingProbingDtime to set.- Returns:
- This builder for chaining.
-
clearInprocessingProbingDtime
The amount of dtime we should spend on probing for each inprocessing round.
optional double inprocessing_probing_dtime = 274 [default = 1];- Returns:
- This builder for chaining.
-
hasInprocessingMinimizationDtime
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];- Specified by:
hasInprocessingMinimizationDtimein interfaceSatParametersOrBuilder- Returns:
- Whether the inprocessingMinimizationDtime field is set.
-
getInprocessingMinimizationDtime
public 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];- Specified by:
getInprocessingMinimizationDtimein interfaceSatParametersOrBuilder- Returns:
- The inprocessingMinimizationDtime.
-
setInprocessingMinimizationDtime
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];- Parameters:
value- The inprocessingMinimizationDtime to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasInprocessingMinimizationUseConflictAnalysis
public boolean hasInprocessingMinimizationUseConflictAnalysis()optional bool inprocessing_minimization_use_conflict_analysis = 297 [default = true];- Specified by:
hasInprocessingMinimizationUseConflictAnalysisin interfaceSatParametersOrBuilder- Returns:
- Whether the inprocessingMinimizationUseConflictAnalysis field is set.
-
getInprocessingMinimizationUseConflictAnalysis
public boolean getInprocessingMinimizationUseConflictAnalysis()optional bool inprocessing_minimization_use_conflict_analysis = 297 [default = true];- Specified by:
getInprocessingMinimizationUseConflictAnalysisin interfaceSatParametersOrBuilder- Returns:
- The inprocessingMinimizationUseConflictAnalysis.
-
setInprocessingMinimizationUseConflictAnalysis
optional bool inprocessing_minimization_use_conflict_analysis = 297 [default = true];- Parameters:
value- The inprocessingMinimizationUseConflictAnalysis to set.- Returns:
- This builder for chaining.
-
clearInprocessingMinimizationUseConflictAnalysis
optional bool inprocessing_minimization_use_conflict_analysis = 297 [default = true];- Returns:
- This builder for chaining.
-
hasInprocessingMinimizationUseAllOrderings
public boolean hasInprocessingMinimizationUseAllOrderings()optional bool inprocessing_minimization_use_all_orderings = 298 [default = false];- Specified by:
hasInprocessingMinimizationUseAllOrderingsin interfaceSatParametersOrBuilder- Returns:
- Whether the inprocessingMinimizationUseAllOrderings field is set.
-
getInprocessingMinimizationUseAllOrderings
public boolean getInprocessingMinimizationUseAllOrderings()optional bool inprocessing_minimization_use_all_orderings = 298 [default = false];- Specified by:
getInprocessingMinimizationUseAllOrderingsin interfaceSatParametersOrBuilder- Returns:
- The inprocessingMinimizationUseAllOrderings.
-
setInprocessingMinimizationUseAllOrderings
optional bool inprocessing_minimization_use_all_orderings = 298 [default = false];- Parameters:
value- The inprocessingMinimizationUseAllOrderings to set.- Returns:
- This builder for chaining.
-
clearInprocessingMinimizationUseAllOrderings
optional bool inprocessing_minimization_use_all_orderings = 298 [default = false];- Returns:
- This builder for chaining.
-
hasNumWorkers
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_workers'. 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];- Specified by:
hasNumWorkersin interfaceSatParametersOrBuilder- Returns:
- Whether the numWorkers field is set.
-
getNumWorkers
public 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_workers'. 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];- Specified by:
getNumWorkersin interfaceSatParametersOrBuilder- Returns:
- The numWorkers.
-
setNumWorkers
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_workers'. 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];- Parameters:
value- The numWorkers to set.- Returns:
- This builder for chaining.
-
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_workers'. 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];- Returns:
- This builder for chaining.
-
hasNumSearchWorkers
public boolean hasNumSearchWorkers()optional int32 num_search_workers = 100 [default = 0];- Specified by:
hasNumSearchWorkersin interfaceSatParametersOrBuilder- Returns:
- Whether the numSearchWorkers field is set.
-
getNumSearchWorkers
public int getNumSearchWorkers()optional int32 num_search_workers = 100 [default = 0];- Specified by:
getNumSearchWorkersin interfaceSatParametersOrBuilder- Returns:
- The numSearchWorkers.
-
setNumSearchWorkers
optional int32 num_search_workers = 100 [default = 0];- Parameters:
value- The numSearchWorkers to set.- Returns:
- This builder for chaining.
-
clearNumSearchWorkers
optional int32 num_search_workers = 100 [default = 0];- Returns:
- This builder for chaining.
-
hasNumFullSubsolvers
public boolean hasNumFullSubsolvers()We distinguish subsolvers that consume a full thread, and the ones that are always interleaved. If left at zero, we will fix this with a default formula that depends on num_workers. But if you start modifying what runs, you might want to fix that to a given value depending on the num_workers you use.
optional int32 num_full_subsolvers = 294 [default = 0];- Specified by:
hasNumFullSubsolversin interfaceSatParametersOrBuilder- Returns:
- Whether the numFullSubsolvers field is set.
-
getNumFullSubsolvers
public int getNumFullSubsolvers()We distinguish subsolvers that consume a full thread, and the ones that are always interleaved. If left at zero, we will fix this with a default formula that depends on num_workers. But if you start modifying what runs, you might want to fix that to a given value depending on the num_workers you use.
optional int32 num_full_subsolvers = 294 [default = 0];- Specified by:
getNumFullSubsolversin interfaceSatParametersOrBuilder- Returns:
- The numFullSubsolvers.
-
setNumFullSubsolvers
We distinguish subsolvers that consume a full thread, and the ones that are always interleaved. If left at zero, we will fix this with a default formula that depends on num_workers. But if you start modifying what runs, you might want to fix that to a given value depending on the num_workers you use.
optional int32 num_full_subsolvers = 294 [default = 0];- Parameters:
value- The numFullSubsolvers to set.- Returns:
- This builder for chaining.
-
clearNumFullSubsolvers
We distinguish subsolvers that consume a full thread, and the ones that are always interleaved. If left at zero, we will fix this with a default formula that depends on num_workers. But if you start modifying what runs, you might want to fix that to a given value depending on the num_workers you use.
optional int32 num_full_subsolvers = 294 [default = 0];- Returns:
- This builder for chaining.
-
getSubsolversList
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. This only applies to "full" subsolvers. 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 num_full_subsolvers will be scheduled. You can see in the log which one are selected for a given run.
repeated string subsolvers = 207;- Specified by:
getSubsolversListin interfaceSatParametersOrBuilder- Returns:
- A list containing the subsolvers.
-
getSubsolversCount
public 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. This only applies to "full" subsolvers. 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 num_full_subsolvers will be scheduled. You can see in the log which one are selected for a given run.
repeated string subsolvers = 207;- Specified by:
getSubsolversCountin interfaceSatParametersOrBuilder- Returns:
- The count of subsolvers.
-
getSubsolvers
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. This only applies to "full" subsolvers. 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 num_full_subsolvers will be scheduled. You can see in the log which one are selected for a given run.
repeated string subsolvers = 207;- Specified by:
getSubsolversin interfaceSatParametersOrBuilder- Parameters:
index- The index of the element to return.- Returns:
- The subsolvers at the given index.
-
getSubsolversBytes
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. This only applies to "full" subsolvers. 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 num_full_subsolvers will be scheduled. You can see in the log which one are selected for a given run.
repeated string subsolvers = 207;- Specified by:
getSubsolversBytesin interfaceSatParametersOrBuilder- Parameters:
index- The index of the value to return.- Returns:
- The bytes of the subsolvers at the given index.
-
setSubsolvers
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. This only applies to "full" subsolvers. 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 num_full_subsolvers will be scheduled. You can see in the log which one are selected for a given run.
repeated string subsolvers = 207;- Parameters:
index- The index to set the value at.value- The subsolvers to set.- Returns:
- This builder for chaining.
-
addSubsolvers
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. This only applies to "full" subsolvers. 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 num_full_subsolvers will be scheduled. You can see in the log which one are selected for a given run.
repeated string subsolvers = 207;- Parameters:
value- The subsolvers to add.- Returns:
- This builder for chaining.
-
addAllSubsolvers
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. This only applies to "full" subsolvers. 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 num_full_subsolvers will be scheduled. You can see in the log which one are selected for a given run.
repeated string subsolvers = 207;- Parameters:
values- The subsolvers to add.- Returns:
- This builder for chaining.
-
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. This only applies to "full" subsolvers. 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 num_full_subsolvers will be scheduled. You can see in the log which one are selected for a given run.
repeated string subsolvers = 207;- Returns:
- This builder for chaining.
-
addSubsolversBytes
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. This only applies to "full" subsolvers. 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 num_full_subsolvers will be scheduled. You can see in the log which one are selected for a given run.
repeated string subsolvers = 207;- Parameters:
value- The bytes of the subsolvers to add.- Returns:
- This builder for chaining.
-
getExtraSubsolversList
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;- Specified by:
getExtraSubsolversListin interfaceSatParametersOrBuilder- Returns:
- A list containing the extraSubsolvers.
-
getExtraSubsolversCount
public 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;- Specified by:
getExtraSubsolversCountin interfaceSatParametersOrBuilder- Returns:
- The count of extraSubsolvers.
-
getExtraSubsolvers
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;- Specified by:
getExtraSubsolversin interfaceSatParametersOrBuilder- Parameters:
index- The index of the element to return.- Returns:
- The extraSubsolvers at the given index.
-
getExtraSubsolversBytes
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;- Specified by:
getExtraSubsolversBytesin interfaceSatParametersOrBuilder- Parameters:
index- The index of the value to return.- Returns:
- The bytes of the extraSubsolvers at the given index.
-
setExtraSubsolvers
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;- Parameters:
index- The index to set the value at.value- The extraSubsolvers to set.- Returns:
- This builder for chaining.
-
addExtraSubsolvers
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;- Parameters:
value- The extraSubsolvers to add.- Returns:
- This builder for chaining.
-
addAllExtraSubsolvers
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;- Parameters:
values- The extraSubsolvers to add.- Returns:
- This builder for chaining.
-
clearExtraSubsolvers
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;- Returns:
- This builder for chaining.
-
addExtraSubsolversBytes
A convenient way to add more workers types. These will be added at the beginning of the list.
repeated string extra_subsolvers = 219;- Parameters:
value- The bytes of the extraSubsolvers to add.- Returns:
- This builder for chaining.
-
getIgnoreSubsolversList
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 or only keep specific ones for testing. Each string is interpreted as a "glob", so we support '*' and '?'. The way this work is that we will only accept a name that match a filter pattern (if non-empty) and do not match an ignore pattern. Note also that these fields work on LNS or LS names even if these are currently not specified via the subsolvers field.
repeated string ignore_subsolvers = 209;- Specified by:
getIgnoreSubsolversListin interfaceSatParametersOrBuilder- Returns:
- A list containing the ignoreSubsolvers.
-
getIgnoreSubsolversCount
public int getIgnoreSubsolversCount()Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing. Each string is interpreted as a "glob", so we support '*' and '?'. The way this work is that we will only accept a name that match a filter pattern (if non-empty) and do not match an ignore pattern. Note also that these fields work on LNS or LS names even if these are currently not specified via the subsolvers field.
repeated string ignore_subsolvers = 209;- Specified by:
getIgnoreSubsolversCountin interfaceSatParametersOrBuilder- Returns:
- The count of ignoreSubsolvers.
-
getIgnoreSubsolvers
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing. Each string is interpreted as a "glob", so we support '*' and '?'. The way this work is that we will only accept a name that match a filter pattern (if non-empty) and do not match an ignore pattern. Note also that these fields work on LNS or LS names even if these are currently not specified via the subsolvers field.
repeated string ignore_subsolvers = 209;- Specified by:
getIgnoreSubsolversin interfaceSatParametersOrBuilder- Parameters:
index- The index of the element to return.- Returns:
- The ignoreSubsolvers at the given index.
-
getIgnoreSubsolversBytes
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 or only keep specific ones for testing. Each string is interpreted as a "glob", so we support '*' and '?'. The way this work is that we will only accept a name that match a filter pattern (if non-empty) and do not match an ignore pattern. Note also that these fields work on LNS or LS names even if these are currently not specified via the subsolvers field.
repeated string ignore_subsolvers = 209;- Specified by:
getIgnoreSubsolversBytesin interfaceSatParametersOrBuilder- Parameters:
index- The index of the value to return.- Returns:
- The bytes of the ignoreSubsolvers at the given index.
-
setIgnoreSubsolvers
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing. Each string is interpreted as a "glob", so we support '*' and '?'. The way this work is that we will only accept a name that match a filter pattern (if non-empty) and do not match an ignore pattern. Note also that these fields work on LNS or LS names even if these are currently not specified via the subsolvers field.
repeated string ignore_subsolvers = 209;- Parameters:
index- The index to set the value at.value- The ignoreSubsolvers to set.- Returns:
- This builder for chaining.
-
addIgnoreSubsolvers
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing. Each string is interpreted as a "glob", so we support '*' and '?'. The way this work is that we will only accept a name that match a filter pattern (if non-empty) and do not match an ignore pattern. Note also that these fields work on LNS or LS names even if these are currently not specified via the subsolvers field.
repeated string ignore_subsolvers = 209;- Parameters:
value- The ignoreSubsolvers to add.- Returns:
- This builder for chaining.
-
addAllIgnoreSubsolvers
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing. Each string is interpreted as a "glob", so we support '*' and '?'. The way this work is that we will only accept a name that match a filter pattern (if non-empty) and do not match an ignore pattern. Note also that these fields work on LNS or LS names even if these are currently not specified via the subsolvers field.
repeated string ignore_subsolvers = 209;- Parameters:
values- The ignoreSubsolvers to add.- Returns:
- This builder for chaining.
-
clearIgnoreSubsolvers
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing. Each string is interpreted as a "glob", so we support '*' and '?'. The way this work is that we will only accept a name that match a filter pattern (if non-empty) and do not match an ignore pattern. Note also that these fields work on LNS or LS names even if these are currently not specified via the subsolvers field.
repeated string ignore_subsolvers = 209;- Returns:
- This builder for chaining.
-
addIgnoreSubsolversBytes
Rather than fully specifying subsolvers, it is often convenient to just remove the ones that are not useful on a given problem or only keep specific ones for testing. Each string is interpreted as a "glob", so we support '*' and '?'. The way this work is that we will only accept a name that match a filter pattern (if non-empty) and do not match an ignore pattern. Note also that these fields work on LNS or LS names even if these are currently not specified via the subsolvers field.
repeated string ignore_subsolvers = 209;- Parameters:
value- The bytes of the ignoreSubsolvers to add.- Returns:
- This builder for chaining.
-
getFilterSubsolversList
public com.google.protobuf.ProtocolStringList getFilterSubsolversList()repeated string filter_subsolvers = 293;- Specified by:
getFilterSubsolversListin interfaceSatParametersOrBuilder- Returns:
- A list containing the filterSubsolvers.
-
getFilterSubsolversCount
public int getFilterSubsolversCount()repeated string filter_subsolvers = 293;- Specified by:
getFilterSubsolversCountin interfaceSatParametersOrBuilder- Returns:
- The count of filterSubsolvers.
-
getFilterSubsolvers
repeated string filter_subsolvers = 293;- Specified by:
getFilterSubsolversin interfaceSatParametersOrBuilder- Parameters:
index- The index of the element to return.- Returns:
- The filterSubsolvers at the given index.
-
getFilterSubsolversBytes
public com.google.protobuf.ByteString getFilterSubsolversBytes(int index) repeated string filter_subsolvers = 293;- Specified by:
getFilterSubsolversBytesin interfaceSatParametersOrBuilder- Parameters:
index- The index of the value to return.- Returns:
- The bytes of the filterSubsolvers at the given index.
-
setFilterSubsolvers
repeated string filter_subsolvers = 293;- Parameters:
index- The index to set the value at.value- The filterSubsolvers to set.- Returns:
- This builder for chaining.
-
addFilterSubsolvers
repeated string filter_subsolvers = 293;- Parameters:
value- The filterSubsolvers to add.- Returns:
- This builder for chaining.
-
addAllFilterSubsolvers
repeated string filter_subsolvers = 293;- Parameters:
values- The filterSubsolvers to add.- Returns:
- This builder for chaining.
-
clearFilterSubsolvers
repeated string filter_subsolvers = 293;- Returns:
- This builder for chaining.
-
addFilterSubsolversBytes
repeated string filter_subsolvers = 293;- Parameters:
value- The bytes of the filterSubsolvers to add.- Returns:
- This builder for chaining.
-
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;- Specified by:
getSubsolverParamsListin interfaceSatParametersOrBuilder
-
getSubsolverParamsCount
public 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;- Specified by:
getSubsolverParamsCountin interfaceSatParametersOrBuilder
-
getSubsolverParams
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;- Specified by:
getSubsolverParamsin interfaceSatParametersOrBuilder
-
setSubsolverParams
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; -
setSubsolverParams
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; -
addSubsolverParams
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; -
addSubsolverParams
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; -
addSubsolverParams
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; -
addSubsolverParams
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; -
addAllSubsolverParams
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; -
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; -
removeSubsolverParams
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; -
getSubsolverParamsBuilder
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
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;- Specified by:
getSubsolverParamsOrBuilderin interfaceSatParametersOrBuilder
-
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;- Specified by:
getSubsolverParamsOrBuilderListin interfaceSatParametersOrBuilder
-
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; -
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; -
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; -
hasInterleaveSearch
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];- Specified by:
hasInterleaveSearchin interfaceSatParametersOrBuilder- Returns:
- Whether the interleaveSearch field is set.
-
getInterleaveSearch
public 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];- Specified by:
getInterleaveSearchin interfaceSatParametersOrBuilder- Returns:
- The interleaveSearch.
-
setInterleaveSearch
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];- Parameters:
value- The interleaveSearch to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasInterleaveBatchSize
public boolean hasInterleaveBatchSize()optional int32 interleave_batch_size = 134 [default = 0];- Specified by:
hasInterleaveBatchSizein interfaceSatParametersOrBuilder- Returns:
- Whether the interleaveBatchSize field is set.
-
getInterleaveBatchSize
public int getInterleaveBatchSize()optional int32 interleave_batch_size = 134 [default = 0];- Specified by:
getInterleaveBatchSizein interfaceSatParametersOrBuilder- Returns:
- The interleaveBatchSize.
-
setInterleaveBatchSize
optional int32 interleave_batch_size = 134 [default = 0];- Parameters:
value- The interleaveBatchSize to set.- Returns:
- This builder for chaining.
-
clearInterleaveBatchSize
optional int32 interleave_batch_size = 134 [default = 0];- Returns:
- This builder for chaining.
-
hasDebugPostsolveWithFullSolver
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];- Specified by:
hasDebugPostsolveWithFullSolverin interfaceSatParametersOrBuilder- Returns:
- Whether the debugPostsolveWithFullSolver field is set.
-
getDebugPostsolveWithFullSolver
public 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];- Specified by:
getDebugPostsolveWithFullSolverin interfaceSatParametersOrBuilder- Returns:
- The debugPostsolveWithFullSolver.
-
setDebugPostsolveWithFullSolver
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];- Parameters:
value- The debugPostsolveWithFullSolver to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasDebugMaxNumPresolveOperations
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];- Specified by:
hasDebugMaxNumPresolveOperationsin interfaceSatParametersOrBuilder- Returns:
- Whether the debugMaxNumPresolveOperations field is set.
-
getDebugMaxNumPresolveOperations
public 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];- Specified by:
getDebugMaxNumPresolveOperationsin interfaceSatParametersOrBuilder- Returns:
- The debugMaxNumPresolveOperations.
-
setDebugMaxNumPresolveOperations
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];- Parameters:
value- The debugMaxNumPresolveOperations to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasDebugCrashOnBadHint
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];- Specified by:
hasDebugCrashOnBadHintin interfaceSatParametersOrBuilder- Returns:
- Whether the debugCrashOnBadHint field is set.
-
getDebugCrashOnBadHint
public 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];- Specified by:
getDebugCrashOnBadHintin interfaceSatParametersOrBuilder- Returns:
- The debugCrashOnBadHint.
-
setDebugCrashOnBadHint
Crash if we do not manage to complete the hint into a full solution.
optional bool debug_crash_on_bad_hint = 195 [default = false];- Parameters:
value- The debugCrashOnBadHint to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasDebugCrashIfPresolveBreaksHint
public boolean hasDebugCrashIfPresolveBreaksHint()Crash if presolve breaks a feasible hint.
optional bool debug_crash_if_presolve_breaks_hint = 306 [default = false];- Specified by:
hasDebugCrashIfPresolveBreaksHintin interfaceSatParametersOrBuilder- Returns:
- Whether the debugCrashIfPresolveBreaksHint field is set.
-
getDebugCrashIfPresolveBreaksHint
public boolean getDebugCrashIfPresolveBreaksHint()Crash if presolve breaks a feasible hint.
optional bool debug_crash_if_presolve_breaks_hint = 306 [default = false];- Specified by:
getDebugCrashIfPresolveBreaksHintin interfaceSatParametersOrBuilder- Returns:
- The debugCrashIfPresolveBreaksHint.
-
setDebugCrashIfPresolveBreaksHint
Crash if presolve breaks a feasible hint.
optional bool debug_crash_if_presolve_breaks_hint = 306 [default = false];- Parameters:
value- The debugCrashIfPresolveBreaksHint to set.- Returns:
- This builder for chaining.
-
clearDebugCrashIfPresolveBreaksHint
Crash if presolve breaks a feasible hint.
optional bool debug_crash_if_presolve_breaks_hint = 306 [default = false];- Returns:
- This builder for chaining.
-
hasUseOptimizationHints
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];- Specified by:
hasUseOptimizationHintsin interfaceSatParametersOrBuilder- Returns:
- Whether the useOptimizationHints field is set.
-
getUseOptimizationHints
public 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];- Specified by:
getUseOptimizationHintsin interfaceSatParametersOrBuilder- Returns:
- The useOptimizationHints.
-
setUseOptimizationHints
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];- Parameters:
value- The useOptimizationHints to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasCoreMinimizationLevel
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];- Specified by:
hasCoreMinimizationLevelin interfaceSatParametersOrBuilder- Returns:
- Whether the coreMinimizationLevel field is set.
-
getCoreMinimizationLevel
public 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];- Specified by:
getCoreMinimizationLevelin interfaceSatParametersOrBuilder- Returns:
- The coreMinimizationLevel.
-
setCoreMinimizationLevel
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];- Parameters:
value- The coreMinimizationLevel to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasFindMultipleCores
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];- Specified by:
hasFindMultipleCoresin interfaceSatParametersOrBuilder- Returns:
- Whether the findMultipleCores field is set.
-
getFindMultipleCores
public 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];- Specified by:
getFindMultipleCoresin interfaceSatParametersOrBuilder- Returns:
- The findMultipleCores.
-
setFindMultipleCores
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];- Parameters:
value- The findMultipleCores to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasCoverOptimization
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];- Specified by:
hasCoverOptimizationin interfaceSatParametersOrBuilder- Returns:
- Whether the coverOptimization field is set.
-
getCoverOptimization
public 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];- Specified by:
getCoverOptimizationin interfaceSatParametersOrBuilder- Returns:
- The coverOptimization.
-
setCoverOptimization
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];- Parameters:
value- The coverOptimization to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxSatAssumptionOrder
public boolean hasMaxSatAssumptionOrder()optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];- Specified by:
hasMaxSatAssumptionOrderin interfaceSatParametersOrBuilder- Returns:
- Whether the maxSatAssumptionOrder field is set.
-
getMaxSatAssumptionOrder
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];- Specified by:
getMaxSatAssumptionOrderin interfaceSatParametersOrBuilder- Returns:
- The maxSatAssumptionOrder.
-
setMaxSatAssumptionOrder
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];- Parameters:
value- The maxSatAssumptionOrder to set.- Returns:
- This builder for chaining.
-
clearMaxSatAssumptionOrder
optional .operations_research.sat.SatParameters.MaxSatAssumptionOrder max_sat_assumption_order = 51 [default = DEFAULT_ASSUMPTION_ORDER];- Returns:
- This builder for chaining.
-
hasMaxSatReverseAssumptionOrder
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];- Specified by:
hasMaxSatReverseAssumptionOrderin interfaceSatParametersOrBuilder- Returns:
- Whether the maxSatReverseAssumptionOrder field is set.
-
getMaxSatReverseAssumptionOrder
public 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];- Specified by:
getMaxSatReverseAssumptionOrderin interfaceSatParametersOrBuilder- Returns:
- The maxSatReverseAssumptionOrder.
-
setMaxSatReverseAssumptionOrder
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];- Parameters:
value- The maxSatReverseAssumptionOrder to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxSatStratification
public boolean hasMaxSatStratification()optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];- Specified by:
hasMaxSatStratificationin interfaceSatParametersOrBuilder- Returns:
- Whether the maxSatStratification field is set.
-
getMaxSatStratification
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];- Specified by:
getMaxSatStratificationin interfaceSatParametersOrBuilder- Returns:
- The maxSatStratification.
-
setMaxSatStratification
public SatParameters.Builder setMaxSatStratification(SatParameters.MaxSatStratificationAlgorithm value) optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];- Parameters:
value- The maxSatStratification to set.- Returns:
- This builder for chaining.
-
clearMaxSatStratification
optional .operations_research.sat.SatParameters.MaxSatStratificationAlgorithm max_sat_stratification = 53 [default = STRATIFICATION_DESCENT];- Returns:
- This builder for chaining.
-
hasPropagationLoopDetectionFactor
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];- Specified by:
hasPropagationLoopDetectionFactorin interfaceSatParametersOrBuilder- Returns:
- Whether the propagationLoopDetectionFactor field is set.
-
getPropagationLoopDetectionFactor
public 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];- Specified by:
getPropagationLoopDetectionFactorin interfaceSatParametersOrBuilder- Returns:
- The propagationLoopDetectionFactor.
-
setPropagationLoopDetectionFactor
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];- Parameters:
value- The propagationLoopDetectionFactor to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUsePrecedencesInDisjunctiveConstraint
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];- Specified by:
hasUsePrecedencesInDisjunctiveConstraintin interfaceSatParametersOrBuilder- Returns:
- Whether the usePrecedencesInDisjunctiveConstraint field is set.
-
getUsePrecedencesInDisjunctiveConstraint
public 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];- Specified by:
getUsePrecedencesInDisjunctiveConstraintin interfaceSatParametersOrBuilder- Returns:
- The usePrecedencesInDisjunctiveConstraint.
-
setUsePrecedencesInDisjunctiveConstraint
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];- Parameters:
value- The usePrecedencesInDisjunctiveConstraint to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxSizeToCreatePrecedenceLiteralsInDisjunctive
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];- Specified by:
hasMaxSizeToCreatePrecedenceLiteralsInDisjunctivein interfaceSatParametersOrBuilder- Returns:
- Whether the maxSizeToCreatePrecedenceLiteralsInDisjunctive field is set.
-
getMaxSizeToCreatePrecedenceLiteralsInDisjunctive
public 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];- Specified by:
getMaxSizeToCreatePrecedenceLiteralsInDisjunctivein interfaceSatParametersOrBuilder- Returns:
- The maxSizeToCreatePrecedenceLiteralsInDisjunctive.
-
setMaxSizeToCreatePrecedenceLiteralsInDisjunctive
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];- Parameters:
value- The maxSizeToCreatePrecedenceLiteralsInDisjunctive to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseStrongPropagationInDisjunctive
public boolean hasUseStrongPropagationInDisjunctive()Enable stronger and more expensive propagation on no_overlap constraint.
optional bool use_strong_propagation_in_disjunctive = 230 [default = false];- Specified by:
hasUseStrongPropagationInDisjunctivein interfaceSatParametersOrBuilder- Returns:
- Whether the useStrongPropagationInDisjunctive field is set.
-
getUseStrongPropagationInDisjunctive
public boolean getUseStrongPropagationInDisjunctive()Enable stronger and more expensive propagation on no_overlap constraint.
optional bool use_strong_propagation_in_disjunctive = 230 [default = false];- Specified by:
getUseStrongPropagationInDisjunctivein interfaceSatParametersOrBuilder- Returns:
- The useStrongPropagationInDisjunctive.
-
setUseStrongPropagationInDisjunctive
Enable stronger and more expensive propagation on no_overlap constraint.
optional bool use_strong_propagation_in_disjunctive = 230 [default = false];- Parameters:
value- The useStrongPropagationInDisjunctive to set.- Returns:
- This builder for chaining.
-
clearUseStrongPropagationInDisjunctive
Enable stronger and more expensive propagation on no_overlap constraint.
optional bool use_strong_propagation_in_disjunctive = 230 [default = false];- Returns:
- This builder for chaining.
-
hasUseDynamicPrecedenceInDisjunctive
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];- Specified by:
hasUseDynamicPrecedenceInDisjunctivein interfaceSatParametersOrBuilder- Returns:
- Whether the useDynamicPrecedenceInDisjunctive field is set.
-
getUseDynamicPrecedenceInDisjunctive
public 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];- Specified by:
getUseDynamicPrecedenceInDisjunctivein interfaceSatParametersOrBuilder- Returns:
- The useDynamicPrecedenceInDisjunctive.
-
setUseDynamicPrecedenceInDisjunctive
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];- Parameters:
value- The useDynamicPrecedenceInDisjunctive to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseDynamicPrecedenceInCumulative
public boolean hasUseDynamicPrecedenceInCumulative()optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];- Specified by:
hasUseDynamicPrecedenceInCumulativein interfaceSatParametersOrBuilder- Returns:
- Whether the useDynamicPrecedenceInCumulative field is set.
-
getUseDynamicPrecedenceInCumulative
public boolean getUseDynamicPrecedenceInCumulative()optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];- Specified by:
getUseDynamicPrecedenceInCumulativein interfaceSatParametersOrBuilder- Returns:
- The useDynamicPrecedenceInCumulative.
-
setUseDynamicPrecedenceInCumulative
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];- Parameters:
value- The useDynamicPrecedenceInCumulative to set.- Returns:
- This builder for chaining.
-
clearUseDynamicPrecedenceInCumulative
optional bool use_dynamic_precedence_in_cumulative = 268 [default = false];- Returns:
- This builder for chaining.
-
hasUseOverloadCheckerInCumulative
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];- Specified by:
hasUseOverloadCheckerInCumulativein interfaceSatParametersOrBuilder- Returns:
- Whether the useOverloadCheckerInCumulative field is set.
-
getUseOverloadCheckerInCumulative
public 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];- Specified by:
getUseOverloadCheckerInCumulativein interfaceSatParametersOrBuilder- Returns:
- The useOverloadCheckerInCumulative.
-
setUseOverloadCheckerInCumulative
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];- Parameters:
value- The useOverloadCheckerInCumulative to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseConservativeScaleOverloadChecker
public boolean hasUseConservativeScaleOverloadChecker()Enable a heuristic to solve cumulative constraints using a modified energy constraint. We modify the usual energy definition by applying a super-additive function (also called "conservative scale" or "dual-feasible function") to the demand and the durations of the tasks. This heuristic is fast but for most problems it does not help much to find a solution.
optional bool use_conservative_scale_overload_checker = 286 [default = false];- Specified by:
hasUseConservativeScaleOverloadCheckerin interfaceSatParametersOrBuilder- Returns:
- Whether the useConservativeScaleOverloadChecker field is set.
-
getUseConservativeScaleOverloadChecker
public boolean getUseConservativeScaleOverloadChecker()Enable a heuristic to solve cumulative constraints using a modified energy constraint. We modify the usual energy definition by applying a super-additive function (also called "conservative scale" or "dual-feasible function") to the demand and the durations of the tasks. This heuristic is fast but for most problems it does not help much to find a solution.
optional bool use_conservative_scale_overload_checker = 286 [default = false];- Specified by:
getUseConservativeScaleOverloadCheckerin interfaceSatParametersOrBuilder- Returns:
- The useConservativeScaleOverloadChecker.
-
setUseConservativeScaleOverloadChecker
Enable a heuristic to solve cumulative constraints using a modified energy constraint. We modify the usual energy definition by applying a super-additive function (also called "conservative scale" or "dual-feasible function") to the demand and the durations of the tasks. This heuristic is fast but for most problems it does not help much to find a solution.
optional bool use_conservative_scale_overload_checker = 286 [default = false];- Parameters:
value- The useConservativeScaleOverloadChecker to set.- Returns:
- This builder for chaining.
-
clearUseConservativeScaleOverloadChecker
Enable a heuristic to solve cumulative constraints using a modified energy constraint. We modify the usual energy definition by applying a super-additive function (also called "conservative scale" or "dual-feasible function") to the demand and the durations of the tasks. This heuristic is fast but for most problems it does not help much to find a solution.
optional bool use_conservative_scale_overload_checker = 286 [default = false];- Returns:
- This builder for chaining.
-
hasUseTimetableEdgeFindingInCumulative
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];- Specified by:
hasUseTimetableEdgeFindingInCumulativein interfaceSatParametersOrBuilder- Returns:
- Whether the useTimetableEdgeFindingInCumulative field is set.
-
getUseTimetableEdgeFindingInCumulative
public 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];- Specified by:
getUseTimetableEdgeFindingInCumulativein interfaceSatParametersOrBuilder- Returns:
- The useTimetableEdgeFindingInCumulative.
-
setUseTimetableEdgeFindingInCumulative
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];- Parameters:
value- The useTimetableEdgeFindingInCumulative to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxNumIntervalsForTimetableEdgeFinding
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];- Specified by:
hasMaxNumIntervalsForTimetableEdgeFindingin interfaceSatParametersOrBuilder- Returns:
- Whether the maxNumIntervalsForTimetableEdgeFinding field is set.
-
getMaxNumIntervalsForTimetableEdgeFinding
public 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];- Specified by:
getMaxNumIntervalsForTimetableEdgeFindingin interfaceSatParametersOrBuilder- Returns:
- The maxNumIntervalsForTimetableEdgeFinding.
-
setMaxNumIntervalsForTimetableEdgeFinding
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];- Parameters:
value- The maxNumIntervalsForTimetableEdgeFinding to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseHardPrecedencesInCumulative
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];- Specified by:
hasUseHardPrecedencesInCumulativein interfaceSatParametersOrBuilder- Returns:
- Whether the useHardPrecedencesInCumulative field is set.
-
getUseHardPrecedencesInCumulative
public 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];- Specified by:
getUseHardPrecedencesInCumulativein interfaceSatParametersOrBuilder- Returns:
- The useHardPrecedencesInCumulative.
-
setUseHardPrecedencesInCumulative
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];- Parameters:
value- The useHardPrecedencesInCumulative to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasExploitAllPrecedences
public boolean hasExploitAllPrecedences()optional bool exploit_all_precedences = 220 [default = false];- Specified by:
hasExploitAllPrecedencesin interfaceSatParametersOrBuilder- Returns:
- Whether the exploitAllPrecedences field is set.
-
getExploitAllPrecedences
public boolean getExploitAllPrecedences()optional bool exploit_all_precedences = 220 [default = false];- Specified by:
getExploitAllPrecedencesin interfaceSatParametersOrBuilder- Returns:
- The exploitAllPrecedences.
-
setExploitAllPrecedences
optional bool exploit_all_precedences = 220 [default = false];- Parameters:
value- The exploitAllPrecedences to set.- Returns:
- This builder for chaining.
-
clearExploitAllPrecedences
optional bool exploit_all_precedences = 220 [default = false];- Returns:
- This builder for chaining.
-
hasUseDisjunctiveConstraintInCumulative
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];- Specified by:
hasUseDisjunctiveConstraintInCumulativein interfaceSatParametersOrBuilder- Returns:
- Whether the useDisjunctiveConstraintInCumulative field is set.
-
getUseDisjunctiveConstraintInCumulative
public 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];- Specified by:
getUseDisjunctiveConstraintInCumulativein interfaceSatParametersOrBuilder- Returns:
- The useDisjunctiveConstraintInCumulative.
-
setUseDisjunctiveConstraintInCumulative
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];- Parameters:
value- The useDisjunctiveConstraintInCumulative to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasNoOverlap2DBooleanRelationsLimit
public boolean hasNoOverlap2DBooleanRelationsLimit()If less than this number of boxes are present in a no-overlap 2d, we create 4 Booleans per pair of boxes: - Box 2 is after Box 1 on x. - Box 1 is after Box 2 on x. - Box 2 is after Box 1 on y. - Box 1 is after Box 2 on y. Note that at least one of them must be true, and at most one on x and one on y can be true. This can significantly help in closing small problem. The SAT reasoning can be a lot more powerful when we take decision on such positional relations.
optional int32 no_overlap_2d_boolean_relations_limit = 321 [default = 10];- Specified by:
hasNoOverlap2DBooleanRelationsLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the noOverlap2dBooleanRelationsLimit field is set.
-
getNoOverlap2DBooleanRelationsLimit
public int getNoOverlap2DBooleanRelationsLimit()If less than this number of boxes are present in a no-overlap 2d, we create 4 Booleans per pair of boxes: - Box 2 is after Box 1 on x. - Box 1 is after Box 2 on x. - Box 2 is after Box 1 on y. - Box 1 is after Box 2 on y. Note that at least one of them must be true, and at most one on x and one on y can be true. This can significantly help in closing small problem. The SAT reasoning can be a lot more powerful when we take decision on such positional relations.
optional int32 no_overlap_2d_boolean_relations_limit = 321 [default = 10];- Specified by:
getNoOverlap2DBooleanRelationsLimitin interfaceSatParametersOrBuilder- Returns:
- The noOverlap2dBooleanRelationsLimit.
-
setNoOverlap2DBooleanRelationsLimit
If less than this number of boxes are present in a no-overlap 2d, we create 4 Booleans per pair of boxes: - Box 2 is after Box 1 on x. - Box 1 is after Box 2 on x. - Box 2 is after Box 1 on y. - Box 1 is after Box 2 on y. Note that at least one of them must be true, and at most one on x and one on y can be true. This can significantly help in closing small problem. The SAT reasoning can be a lot more powerful when we take decision on such positional relations.
optional int32 no_overlap_2d_boolean_relations_limit = 321 [default = 10];- Parameters:
value- The noOverlap2dBooleanRelationsLimit to set.- Returns:
- This builder for chaining.
-
clearNoOverlap2DBooleanRelationsLimit
If less than this number of boxes are present in a no-overlap 2d, we create 4 Booleans per pair of boxes: - Box 2 is after Box 1 on x. - Box 1 is after Box 2 on x. - Box 2 is after Box 1 on y. - Box 1 is after Box 2 on y. Note that at least one of them must be true, and at most one on x and one on y can be true. This can significantly help in closing small problem. The SAT reasoning can be a lot more powerful when we take decision on such positional relations.
optional int32 no_overlap_2d_boolean_relations_limit = 321 [default = 10];- Returns:
- This builder for chaining.
-
hasUseTimetablingInNoOverlap2D
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];- Specified by:
hasUseTimetablingInNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- Whether the useTimetablingInNoOverlap2d field is set.
-
getUseTimetablingInNoOverlap2D
public 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];- Specified by:
getUseTimetablingInNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- The useTimetablingInNoOverlap2d.
-
setUseTimetablingInNoOverlap2D
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];- Parameters:
value- The useTimetablingInNoOverlap2d to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseEnergeticReasoningInNoOverlap2D
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];- Specified by:
hasUseEnergeticReasoningInNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- Whether the useEnergeticReasoningInNoOverlap2d field is set.
-
getUseEnergeticReasoningInNoOverlap2D
public 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];- Specified by:
getUseEnergeticReasoningInNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- The useEnergeticReasoningInNoOverlap2d.
-
setUseEnergeticReasoningInNoOverlap2D
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];- Parameters:
value- The useEnergeticReasoningInNoOverlap2d to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseAreaEnergeticReasoningInNoOverlap2D
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];- Specified by:
hasUseAreaEnergeticReasoningInNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- Whether the useAreaEnergeticReasoningInNoOverlap2d field is set.
-
getUseAreaEnergeticReasoningInNoOverlap2D
public 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];- Specified by:
getUseAreaEnergeticReasoningInNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- The useAreaEnergeticReasoningInNoOverlap2d.
-
setUseAreaEnergeticReasoningInNoOverlap2D
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];- Parameters:
value- The useAreaEnergeticReasoningInNoOverlap2d to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseTryEdgeReasoningInNoOverlap2D
public boolean hasUseTryEdgeReasoningInNoOverlap2D()optional bool use_try_edge_reasoning_in_no_overlap_2d = 299 [default = false];- Specified by:
hasUseTryEdgeReasoningInNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- Whether the useTryEdgeReasoningInNoOverlap2d field is set.
-
getUseTryEdgeReasoningInNoOverlap2D
public boolean getUseTryEdgeReasoningInNoOverlap2D()optional bool use_try_edge_reasoning_in_no_overlap_2d = 299 [default = false];- Specified by:
getUseTryEdgeReasoningInNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- The useTryEdgeReasoningInNoOverlap2d.
-
setUseTryEdgeReasoningInNoOverlap2D
optional bool use_try_edge_reasoning_in_no_overlap_2d = 299 [default = false];- Parameters:
value- The useTryEdgeReasoningInNoOverlap2d to set.- Returns:
- This builder for chaining.
-
clearUseTryEdgeReasoningInNoOverlap2D
optional bool use_try_edge_reasoning_in_no_overlap_2d = 299 [default = false];- Returns:
- This builder for chaining.
-
hasMaxPairsPairwiseReasoningInNoOverlap2D
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];- Specified by:
hasMaxPairsPairwiseReasoningInNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- Whether the maxPairsPairwiseReasoningInNoOverlap2d field is set.
-
getMaxPairsPairwiseReasoningInNoOverlap2D
public 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];- Specified by:
getMaxPairsPairwiseReasoningInNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- The maxPairsPairwiseReasoningInNoOverlap2d.
-
setMaxPairsPairwiseReasoningInNoOverlap2D
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];- Parameters:
value- The maxPairsPairwiseReasoningInNoOverlap2d to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaximumRegionsToSplitInDisconnectedNoOverlap2D
public boolean hasMaximumRegionsToSplitInDisconnectedNoOverlap2D()Detects when the space where items of a no_overlap_2d constraint can placed is disjoint (ie., fixed boxes split the domain). When it is the case, we can introduce a boolean for each pair <item, component> encoding whether the item is in the component or not. Then we replace the original no_overlap_2d constraint by one no_overlap_2d constraint for each component, with the new booleans as the enforcement_literal of the intervals. This is equivalent to expanding the original no_overlap_2d constraint into a bin packing problem with each connected component being a bin. This heuristic is only done when the number of regions to split is less than this parameter and <= 1 disables it.
optional int32 maximum_regions_to_split_in_disconnected_no_overlap_2d = 315 [default = 0];- Specified by:
hasMaximumRegionsToSplitInDisconnectedNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- Whether the maximumRegionsToSplitInDisconnectedNoOverlap2d field is set.
-
getMaximumRegionsToSplitInDisconnectedNoOverlap2D
public int getMaximumRegionsToSplitInDisconnectedNoOverlap2D()Detects when the space where items of a no_overlap_2d constraint can placed is disjoint (ie., fixed boxes split the domain). When it is the case, we can introduce a boolean for each pair <item, component> encoding whether the item is in the component or not. Then we replace the original no_overlap_2d constraint by one no_overlap_2d constraint for each component, with the new booleans as the enforcement_literal of the intervals. This is equivalent to expanding the original no_overlap_2d constraint into a bin packing problem with each connected component being a bin. This heuristic is only done when the number of regions to split is less than this parameter and <= 1 disables it.
optional int32 maximum_regions_to_split_in_disconnected_no_overlap_2d = 315 [default = 0];- Specified by:
getMaximumRegionsToSplitInDisconnectedNoOverlap2Din interfaceSatParametersOrBuilder- Returns:
- The maximumRegionsToSplitInDisconnectedNoOverlap2d.
-
setMaximumRegionsToSplitInDisconnectedNoOverlap2D
Detects when the space where items of a no_overlap_2d constraint can placed is disjoint (ie., fixed boxes split the domain). When it is the case, we can introduce a boolean for each pair <item, component> encoding whether the item is in the component or not. Then we replace the original no_overlap_2d constraint by one no_overlap_2d constraint for each component, with the new booleans as the enforcement_literal of the intervals. This is equivalent to expanding the original no_overlap_2d constraint into a bin packing problem with each connected component being a bin. This heuristic is only done when the number of regions to split is less than this parameter and <= 1 disables it.
optional int32 maximum_regions_to_split_in_disconnected_no_overlap_2d = 315 [default = 0];- Parameters:
value- The maximumRegionsToSplitInDisconnectedNoOverlap2d to set.- Returns:
- This builder for chaining.
-
clearMaximumRegionsToSplitInDisconnectedNoOverlap2D
Detects when the space where items of a no_overlap_2d constraint can placed is disjoint (ie., fixed boxes split the domain). When it is the case, we can introduce a boolean for each pair <item, component> encoding whether the item is in the component or not. Then we replace the original no_overlap_2d constraint by one no_overlap_2d constraint for each component, with the new booleans as the enforcement_literal of the intervals. This is equivalent to expanding the original no_overlap_2d constraint into a bin packing problem with each connected component being a bin. This heuristic is only done when the number of regions to split is less than this parameter and <= 1 disables it.
optional int32 maximum_regions_to_split_in_disconnected_no_overlap_2d = 315 [default = 0];- Returns:
- This builder for chaining.
-
hasUseLinear3ForNoOverlap2DPrecedences
public boolean hasUseLinear3ForNoOverlap2DPrecedences()When set, this activates a propagator for the no_overlap_2d constraint that uses any eventual linear constraints of the model in the form `{start interval 1} - {end interval 2} + c*w <= ub` to detect that two intervals must overlap in one dimension for some values of `w`. This is particularly useful for problems where the distance between two boxes is part of the model.optional bool use_linear3_for_no_overlap_2d_precedences = 323 [default = true];- Specified by:
hasUseLinear3ForNoOverlap2DPrecedencesin interfaceSatParametersOrBuilder- Returns:
- Whether the useLinear3ForNoOverlap2dPrecedences field is set.
-
getUseLinear3ForNoOverlap2DPrecedences
public boolean getUseLinear3ForNoOverlap2DPrecedences()When set, this activates a propagator for the no_overlap_2d constraint that uses any eventual linear constraints of the model in the form `{start interval 1} - {end interval 2} + c*w <= ub` to detect that two intervals must overlap in one dimension for some values of `w`. This is particularly useful for problems where the distance between two boxes is part of the model.optional bool use_linear3_for_no_overlap_2d_precedences = 323 [default = true];- Specified by:
getUseLinear3ForNoOverlap2DPrecedencesin interfaceSatParametersOrBuilder- Returns:
- The useLinear3ForNoOverlap2dPrecedences.
-
setUseLinear3ForNoOverlap2DPrecedences
When set, this activates a propagator for the no_overlap_2d constraint that uses any eventual linear constraints of the model in the form `{start interval 1} - {end interval 2} + c*w <= ub` to detect that two intervals must overlap in one dimension for some values of `w`. This is particularly useful for problems where the distance between two boxes is part of the model.optional bool use_linear3_for_no_overlap_2d_precedences = 323 [default = true];- Parameters:
value- The useLinear3ForNoOverlap2dPrecedences to set.- Returns:
- This builder for chaining.
-
clearUseLinear3ForNoOverlap2DPrecedences
When set, this activates a propagator for the no_overlap_2d constraint that uses any eventual linear constraints of the model in the form `{start interval 1} - {end interval 2} + c*w <= ub` to detect that two intervals must overlap in one dimension for some values of `w`. This is particularly useful for problems where the distance between two boxes is part of the model.optional bool use_linear3_for_no_overlap_2d_precedences = 323 [default = true];- Returns:
- This builder for chaining.
-
hasUseDualSchedulingHeuristics
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];- Specified by:
hasUseDualSchedulingHeuristicsin interfaceSatParametersOrBuilder- Returns:
- Whether the useDualSchedulingHeuristics field is set.
-
getUseDualSchedulingHeuristics
public 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];- Specified by:
getUseDualSchedulingHeuristicsin interfaceSatParametersOrBuilder- Returns:
- The useDualSchedulingHeuristics.
-
setUseDualSchedulingHeuristics
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];- Parameters:
value- The useDualSchedulingHeuristics to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseAllDifferentForCircuit
public boolean hasUseAllDifferentForCircuit()Turn on extra propagation for the circuit constraint. This can be quite slow.
optional bool use_all_different_for_circuit = 311 [default = false];- Specified by:
hasUseAllDifferentForCircuitin interfaceSatParametersOrBuilder- Returns:
- Whether the useAllDifferentForCircuit field is set.
-
getUseAllDifferentForCircuit
public boolean getUseAllDifferentForCircuit()Turn on extra propagation for the circuit constraint. This can be quite slow.
optional bool use_all_different_for_circuit = 311 [default = false];- Specified by:
getUseAllDifferentForCircuitin interfaceSatParametersOrBuilder- Returns:
- The useAllDifferentForCircuit.
-
setUseAllDifferentForCircuit
Turn on extra propagation for the circuit constraint. This can be quite slow.
optional bool use_all_different_for_circuit = 311 [default = false];- Parameters:
value- The useAllDifferentForCircuit to set.- Returns:
- This builder for chaining.
-
clearUseAllDifferentForCircuit
Turn on extra propagation for the circuit constraint. This can be quite slow.
optional bool use_all_different_for_circuit = 311 [default = false];- Returns:
- This builder for chaining.
-
hasRoutingCutSubsetSizeForBinaryRelationBound
public boolean hasRoutingCutSubsetSizeForBinaryRelationBound()If the size of a subset of nodes of a RoutesConstraint is less than this value, use linear constraints of size 1 and 2 (such as capacity and time window constraints) enforced by the arc literals to compute cuts for this subset (unless the subset size is less than routing_cut_subset_size_for_tight_binary_relation_bound, in which case the corresponding algorithm is used instead). The algorithm for these cuts has a O(n^3) complexity, where n is the subset size. Hence the value of this parameter should not be too large (e.g. 10 or 20).
optional int32 routing_cut_subset_size_for_binary_relation_bound = 312 [default = 0];- Specified by:
hasRoutingCutSubsetSizeForBinaryRelationBoundin interfaceSatParametersOrBuilder- Returns:
- Whether the routingCutSubsetSizeForBinaryRelationBound field is set.
-
getRoutingCutSubsetSizeForBinaryRelationBound
public int getRoutingCutSubsetSizeForBinaryRelationBound()If the size of a subset of nodes of a RoutesConstraint is less than this value, use linear constraints of size 1 and 2 (such as capacity and time window constraints) enforced by the arc literals to compute cuts for this subset (unless the subset size is less than routing_cut_subset_size_for_tight_binary_relation_bound, in which case the corresponding algorithm is used instead). The algorithm for these cuts has a O(n^3) complexity, where n is the subset size. Hence the value of this parameter should not be too large (e.g. 10 or 20).
optional int32 routing_cut_subset_size_for_binary_relation_bound = 312 [default = 0];- Specified by:
getRoutingCutSubsetSizeForBinaryRelationBoundin interfaceSatParametersOrBuilder- Returns:
- The routingCutSubsetSizeForBinaryRelationBound.
-
setRoutingCutSubsetSizeForBinaryRelationBound
If the size of a subset of nodes of a RoutesConstraint is less than this value, use linear constraints of size 1 and 2 (such as capacity and time window constraints) enforced by the arc literals to compute cuts for this subset (unless the subset size is less than routing_cut_subset_size_for_tight_binary_relation_bound, in which case the corresponding algorithm is used instead). The algorithm for these cuts has a O(n^3) complexity, where n is the subset size. Hence the value of this parameter should not be too large (e.g. 10 or 20).
optional int32 routing_cut_subset_size_for_binary_relation_bound = 312 [default = 0];- Parameters:
value- The routingCutSubsetSizeForBinaryRelationBound to set.- Returns:
- This builder for chaining.
-
clearRoutingCutSubsetSizeForBinaryRelationBound
If the size of a subset of nodes of a RoutesConstraint is less than this value, use linear constraints of size 1 and 2 (such as capacity and time window constraints) enforced by the arc literals to compute cuts for this subset (unless the subset size is less than routing_cut_subset_size_for_tight_binary_relation_bound, in which case the corresponding algorithm is used instead). The algorithm for these cuts has a O(n^3) complexity, where n is the subset size. Hence the value of this parameter should not be too large (e.g. 10 or 20).
optional int32 routing_cut_subset_size_for_binary_relation_bound = 312 [default = 0];- Returns:
- This builder for chaining.
-
hasRoutingCutSubsetSizeForTightBinaryRelationBound
public boolean hasRoutingCutSubsetSizeForTightBinaryRelationBound()Similar to above, but with a different algorithm producing better cuts, at the price of a higher O(2^n) complexity, where n is the subset size. Hence the value of this parameter should be small (e.g. less than 10).
optional int32 routing_cut_subset_size_for_tight_binary_relation_bound = 313 [default = 0];- Specified by:
hasRoutingCutSubsetSizeForTightBinaryRelationBoundin interfaceSatParametersOrBuilder- Returns:
- Whether the routingCutSubsetSizeForTightBinaryRelationBound field is set.
-
getRoutingCutSubsetSizeForTightBinaryRelationBound
public int getRoutingCutSubsetSizeForTightBinaryRelationBound()Similar to above, but with a different algorithm producing better cuts, at the price of a higher O(2^n) complexity, where n is the subset size. Hence the value of this parameter should be small (e.g. less than 10).
optional int32 routing_cut_subset_size_for_tight_binary_relation_bound = 313 [default = 0];- Specified by:
getRoutingCutSubsetSizeForTightBinaryRelationBoundin interfaceSatParametersOrBuilder- Returns:
- The routingCutSubsetSizeForTightBinaryRelationBound.
-
setRoutingCutSubsetSizeForTightBinaryRelationBound
Similar to above, but with a different algorithm producing better cuts, at the price of a higher O(2^n) complexity, where n is the subset size. Hence the value of this parameter should be small (e.g. less than 10).
optional int32 routing_cut_subset_size_for_tight_binary_relation_bound = 313 [default = 0];- Parameters:
value- The routingCutSubsetSizeForTightBinaryRelationBound to set.- Returns:
- This builder for chaining.
-
clearRoutingCutSubsetSizeForTightBinaryRelationBound
Similar to above, but with a different algorithm producing better cuts, at the price of a higher O(2^n) complexity, where n is the subset size. Hence the value of this parameter should be small (e.g. less than 10).
optional int32 routing_cut_subset_size_for_tight_binary_relation_bound = 313 [default = 0];- Returns:
- This builder for chaining.
-
hasRoutingCutSubsetSizeForExactBinaryRelationBound
public boolean hasRoutingCutSubsetSizeForExactBinaryRelationBound()Similar to above, but with an even stronger algorithm in O(n!). We try to be defensive and abort early or not run that often. Still the value of that parameter shouldn't really be much more than 10.
optional int32 routing_cut_subset_size_for_exact_binary_relation_bound = 316 [default = 8];- Specified by:
hasRoutingCutSubsetSizeForExactBinaryRelationBoundin interfaceSatParametersOrBuilder- Returns:
- Whether the routingCutSubsetSizeForExactBinaryRelationBound field is set.
-
getRoutingCutSubsetSizeForExactBinaryRelationBound
public int getRoutingCutSubsetSizeForExactBinaryRelationBound()Similar to above, but with an even stronger algorithm in O(n!). We try to be defensive and abort early or not run that often. Still the value of that parameter shouldn't really be much more than 10.
optional int32 routing_cut_subset_size_for_exact_binary_relation_bound = 316 [default = 8];- Specified by:
getRoutingCutSubsetSizeForExactBinaryRelationBoundin interfaceSatParametersOrBuilder- Returns:
- The routingCutSubsetSizeForExactBinaryRelationBound.
-
setRoutingCutSubsetSizeForExactBinaryRelationBound
Similar to above, but with an even stronger algorithm in O(n!). We try to be defensive and abort early or not run that often. Still the value of that parameter shouldn't really be much more than 10.
optional int32 routing_cut_subset_size_for_exact_binary_relation_bound = 316 [default = 8];- Parameters:
value- The routingCutSubsetSizeForExactBinaryRelationBound to set.- Returns:
- This builder for chaining.
-
clearRoutingCutSubsetSizeForExactBinaryRelationBound
Similar to above, but with an even stronger algorithm in O(n!). We try to be defensive and abort early or not run that often. Still the value of that parameter shouldn't really be much more than 10.
optional int32 routing_cut_subset_size_for_exact_binary_relation_bound = 316 [default = 8];- Returns:
- This builder for chaining.
-
hasRoutingCutSubsetSizeForShortestPathsBound
public boolean hasRoutingCutSubsetSizeForShortestPathsBound()Similar to routing_cut_subset_size_for_exact_binary_relation_bound but use a bound based on shortest path distances (which respect triangular inequality). This allows to derive bounds that are valid for any superset of a given subset. This is slow, so it shouldn't really be larger than 10.
optional int32 routing_cut_subset_size_for_shortest_paths_bound = 318 [default = 8];- Specified by:
hasRoutingCutSubsetSizeForShortestPathsBoundin interfaceSatParametersOrBuilder- Returns:
- Whether the routingCutSubsetSizeForShortestPathsBound field is set.
-
getRoutingCutSubsetSizeForShortestPathsBound
public int getRoutingCutSubsetSizeForShortestPathsBound()Similar to routing_cut_subset_size_for_exact_binary_relation_bound but use a bound based on shortest path distances (which respect triangular inequality). This allows to derive bounds that are valid for any superset of a given subset. This is slow, so it shouldn't really be larger than 10.
optional int32 routing_cut_subset_size_for_shortest_paths_bound = 318 [default = 8];- Specified by:
getRoutingCutSubsetSizeForShortestPathsBoundin interfaceSatParametersOrBuilder- Returns:
- The routingCutSubsetSizeForShortestPathsBound.
-
setRoutingCutSubsetSizeForShortestPathsBound
Similar to routing_cut_subset_size_for_exact_binary_relation_bound but use a bound based on shortest path distances (which respect triangular inequality). This allows to derive bounds that are valid for any superset of a given subset. This is slow, so it shouldn't really be larger than 10.
optional int32 routing_cut_subset_size_for_shortest_paths_bound = 318 [default = 8];- Parameters:
value- The routingCutSubsetSizeForShortestPathsBound to set.- Returns:
- This builder for chaining.
-
clearRoutingCutSubsetSizeForShortestPathsBound
Similar to routing_cut_subset_size_for_exact_binary_relation_bound but use a bound based on shortest path distances (which respect triangular inequality). This allows to derive bounds that are valid for any superset of a given subset. This is slow, so it shouldn't really be larger than 10.
optional int32 routing_cut_subset_size_for_shortest_paths_bound = 318 [default = 8];- Returns:
- This builder for chaining.
-
hasRoutingCutDpEffort
public boolean hasRoutingCutDpEffort()The amount of "effort" to spend in dynamic programming for computing routing cuts. This is in term of basic operations needed by the algorithm in the worst case, so a value like 1e8 should take less than a second to compute.
optional double routing_cut_dp_effort = 314 [default = 10000000];- Specified by:
hasRoutingCutDpEffortin interfaceSatParametersOrBuilder- Returns:
- Whether the routingCutDpEffort field is set.
-
getRoutingCutDpEffort
public double getRoutingCutDpEffort()The amount of "effort" to spend in dynamic programming for computing routing cuts. This is in term of basic operations needed by the algorithm in the worst case, so a value like 1e8 should take less than a second to compute.
optional double routing_cut_dp_effort = 314 [default = 10000000];- Specified by:
getRoutingCutDpEffortin interfaceSatParametersOrBuilder- Returns:
- The routingCutDpEffort.
-
setRoutingCutDpEffort
The amount of "effort" to spend in dynamic programming for computing routing cuts. This is in term of basic operations needed by the algorithm in the worst case, so a value like 1e8 should take less than a second to compute.
optional double routing_cut_dp_effort = 314 [default = 10000000];- Parameters:
value- The routingCutDpEffort to set.- Returns:
- This builder for chaining.
-
clearRoutingCutDpEffort
The amount of "effort" to spend in dynamic programming for computing routing cuts. This is in term of basic operations needed by the algorithm in the worst case, so a value like 1e8 should take less than a second to compute.
optional double routing_cut_dp_effort = 314 [default = 10000000];- Returns:
- This builder for chaining.
-
hasRoutingCutMaxInfeasiblePathLength
public boolean hasRoutingCutMaxInfeasiblePathLength()If the length of an infeasible path is less than this value, a cut will be added to exclude it.
optional int32 routing_cut_max_infeasible_path_length = 317 [default = 6];- Specified by:
hasRoutingCutMaxInfeasiblePathLengthin interfaceSatParametersOrBuilder- Returns:
- Whether the routingCutMaxInfeasiblePathLength field is set.
-
getRoutingCutMaxInfeasiblePathLength
public int getRoutingCutMaxInfeasiblePathLength()If the length of an infeasible path is less than this value, a cut will be added to exclude it.
optional int32 routing_cut_max_infeasible_path_length = 317 [default = 6];- Specified by:
getRoutingCutMaxInfeasiblePathLengthin interfaceSatParametersOrBuilder- Returns:
- The routingCutMaxInfeasiblePathLength.
-
setRoutingCutMaxInfeasiblePathLength
If the length of an infeasible path is less than this value, a cut will be added to exclude it.
optional int32 routing_cut_max_infeasible_path_length = 317 [default = 6];- Parameters:
value- The routingCutMaxInfeasiblePathLength to set.- Returns:
- This builder for chaining.
-
clearRoutingCutMaxInfeasiblePathLength
If the length of an infeasible path is less than this value, a cut will be added to exclude it.
optional int32 routing_cut_max_infeasible_path_length = 317 [default = 6];- Returns:
- This builder for chaining.
-
hasSearchBranching
public boolean hasSearchBranching()optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];- Specified by:
hasSearchBranchingin interfaceSatParametersOrBuilder- Returns:
- Whether the searchBranching field is set.
-
getSearchBranching
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];- Specified by:
getSearchBranchingin interfaceSatParametersOrBuilder- Returns:
- The searchBranching.
-
setSearchBranching
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];- Parameters:
value- The searchBranching to set.- Returns:
- This builder for chaining.
-
clearSearchBranching
optional .operations_research.sat.SatParameters.SearchBranching search_branching = 82 [default = AUTOMATIC_SEARCH];- Returns:
- This builder for chaining.
-
hasHintConflictLimit
public boolean hasHintConflictLimit()Conflict limit used in the phase that exploit the solution hint.
optional int32 hint_conflict_limit = 153 [default = 10];- Specified by:
hasHintConflictLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the hintConflictLimit field is set.
-
getHintConflictLimit
public int getHintConflictLimit()Conflict limit used in the phase that exploit the solution hint.
optional int32 hint_conflict_limit = 153 [default = 10];- Specified by:
getHintConflictLimitin interfaceSatParametersOrBuilder- Returns:
- The hintConflictLimit.
-
setHintConflictLimit
Conflict limit used in the phase that exploit the solution hint.
optional int32 hint_conflict_limit = 153 [default = 10];- Parameters:
value- The hintConflictLimit to set.- Returns:
- This builder for chaining.
-
clearHintConflictLimit
Conflict limit used in the phase that exploit the solution hint.
optional int32 hint_conflict_limit = 153 [default = 10];- Returns:
- This builder for chaining.
-
hasRepairHint
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];- Specified by:
hasRepairHintin interfaceSatParametersOrBuilder- Returns:
- Whether the repairHint field is set.
-
getRepairHint
public 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];- Specified by:
getRepairHintin interfaceSatParametersOrBuilder- Returns:
- The repairHint.
-
setRepairHint
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];- Parameters:
value- The repairHint to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasFixVariablesToTheirHintedValue
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];- Specified by:
hasFixVariablesToTheirHintedValuein interfaceSatParametersOrBuilder- Returns:
- Whether the fixVariablesToTheirHintedValue field is set.
-
getFixVariablesToTheirHintedValue
public 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];- Specified by:
getFixVariablesToTheirHintedValuein interfaceSatParametersOrBuilder- Returns:
- The fixVariablesToTheirHintedValue.
-
setFixVariablesToTheirHintedValue
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];- Parameters:
value- The fixVariablesToTheirHintedValue to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseProbingSearch
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];- Specified by:
hasUseProbingSearchin interfaceSatParametersOrBuilder- Returns:
- Whether the useProbingSearch field is set.
-
getUseProbingSearch
public 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];- Specified by:
getUseProbingSearchin interfaceSatParametersOrBuilder- Returns:
- The useProbingSearch.
-
setUseProbingSearch
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];- Parameters:
value- The useProbingSearch to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseExtendedProbing
public boolean hasUseExtendedProbing()Use extended probing (probe bool_or, at_most_one, exactly_one).
optional bool use_extended_probing = 269 [default = true];- Specified by:
hasUseExtendedProbingin interfaceSatParametersOrBuilder- Returns:
- Whether the useExtendedProbing field is set.
-
getUseExtendedProbing
public boolean getUseExtendedProbing()Use extended probing (probe bool_or, at_most_one, exactly_one).
optional bool use_extended_probing = 269 [default = true];- Specified by:
getUseExtendedProbingin interfaceSatParametersOrBuilder- Returns:
- The useExtendedProbing.
-
setUseExtendedProbing
Use extended probing (probe bool_or, at_most_one, exactly_one).
optional bool use_extended_probing = 269 [default = true];- Parameters:
value- The useExtendedProbing to set.- Returns:
- This builder for chaining.
-
clearUseExtendedProbing
Use extended probing (probe bool_or, at_most_one, exactly_one).
optional bool use_extended_probing = 269 [default = true];- Returns:
- This builder for chaining.
-
hasProbingNumCombinationsLimit
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];- Specified by:
hasProbingNumCombinationsLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the probingNumCombinationsLimit field is set.
-
getProbingNumCombinationsLimit
public int getProbingNumCombinationsLimit()How many combinations of pairs or triplets of variables we want to scan.
optional int32 probing_num_combinations_limit = 272 [default = 20000];- Specified by:
getProbingNumCombinationsLimitin interfaceSatParametersOrBuilder- Returns:
- The probingNumCombinationsLimit.
-
setProbingNumCombinationsLimit
How many combinations of pairs or triplets of variables we want to scan.
optional int32 probing_num_combinations_limit = 272 [default = 20000];- Parameters:
value- The probingNumCombinationsLimit to set.- Returns:
- This builder for chaining.
-
clearProbingNumCombinationsLimit
How many combinations of pairs or triplets of variables we want to scan.
optional int32 probing_num_combinations_limit = 272 [default = 20000];- Returns:
- This builder for chaining.
-
hasShavingDeterministicTimeInProbingSearch
public boolean hasShavingDeterministicTimeInProbingSearch()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. (<= 0 disables it).
optional double shaving_deterministic_time_in_probing_search = 204 [default = 0.001];- Specified by:
hasShavingDeterministicTimeInProbingSearchin interfaceSatParametersOrBuilder- Returns:
- Whether the shavingDeterministicTimeInProbingSearch field is set.
-
getShavingDeterministicTimeInProbingSearch
public double getShavingDeterministicTimeInProbingSearch()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. (<= 0 disables it).
optional double shaving_deterministic_time_in_probing_search = 204 [default = 0.001];- Specified by:
getShavingDeterministicTimeInProbingSearchin interfaceSatParametersOrBuilder- Returns:
- The shavingDeterministicTimeInProbingSearch.
-
setShavingDeterministicTimeInProbingSearch
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. (<= 0 disables it).
optional double shaving_deterministic_time_in_probing_search = 204 [default = 0.001];- Parameters:
value- The shavingDeterministicTimeInProbingSearch to set.- Returns:
- This builder for chaining.
-
clearShavingDeterministicTimeInProbingSearch
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. (<= 0 disables it).
optional double shaving_deterministic_time_in_probing_search = 204 [default = 0.001];- Returns:
- This builder for chaining.
-
hasShavingSearchDeterministicTime
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.1];- Specified by:
hasShavingSearchDeterministicTimein interfaceSatParametersOrBuilder- Returns:
- Whether the shavingSearchDeterministicTime field is set.
-
getShavingSearchDeterministicTime
public 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.1];- Specified by:
getShavingSearchDeterministicTimein interfaceSatParametersOrBuilder- Returns:
- The shavingSearchDeterministicTime.
-
setShavingSearchDeterministicTime
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.1];- Parameters:
value- The shavingSearchDeterministicTime to set.- Returns:
- This builder for chaining.
-
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.1];- Returns:
- This builder for chaining.
-
hasShavingSearchThreshold
public boolean hasShavingSearchThreshold()Specifies the threshold between two modes in the shaving procedure. If the range of the variable/objective is less than this threshold, then the shaving procedure will try to remove values one by one. Otherwise, it will try to remove one range at a time.
optional int64 shaving_search_threshold = 290 [default = 64];- Specified by:
hasShavingSearchThresholdin interfaceSatParametersOrBuilder- Returns:
- Whether the shavingSearchThreshold field is set.
-
getShavingSearchThreshold
public long getShavingSearchThreshold()Specifies the threshold between two modes in the shaving procedure. If the range of the variable/objective is less than this threshold, then the shaving procedure will try to remove values one by one. Otherwise, it will try to remove one range at a time.
optional int64 shaving_search_threshold = 290 [default = 64];- Specified by:
getShavingSearchThresholdin interfaceSatParametersOrBuilder- Returns:
- The shavingSearchThreshold.
-
setShavingSearchThreshold
Specifies the threshold between two modes in the shaving procedure. If the range of the variable/objective is less than this threshold, then the shaving procedure will try to remove values one by one. Otherwise, it will try to remove one range at a time.
optional int64 shaving_search_threshold = 290 [default = 64];- Parameters:
value- The shavingSearchThreshold to set.- Returns:
- This builder for chaining.
-
clearShavingSearchThreshold
Specifies the threshold between two modes in the shaving procedure. If the range of the variable/objective is less than this threshold, then the shaving procedure will try to remove values one by one. Otherwise, it will try to remove one range at a time.
optional int64 shaving_search_threshold = 290 [default = 64];- Returns:
- This builder for chaining.
-
hasUseObjectiveLbSearch
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];- Specified by:
hasUseObjectiveLbSearchin interfaceSatParametersOrBuilder- Returns:
- Whether the useObjectiveLbSearch field is set.
-
getUseObjectiveLbSearch
public 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];- Specified by:
getUseObjectiveLbSearchin interfaceSatParametersOrBuilder- Returns:
- The useObjectiveLbSearch.
-
setUseObjectiveLbSearch
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];- Parameters:
value- The useObjectiveLbSearch to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseObjectiveShavingSearch
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];- Specified by:
hasUseObjectiveShavingSearchin interfaceSatParametersOrBuilder- Returns:
- Whether the useObjectiveShavingSearch field is set.
-
getUseObjectiveShavingSearch
public 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];- Specified by:
getUseObjectiveShavingSearchin interfaceSatParametersOrBuilder- Returns:
- The useObjectiveShavingSearch.
-
setUseObjectiveShavingSearch
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];- Parameters:
value- The useObjectiveShavingSearch to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasVariablesShavingLevel
public boolean hasVariablesShavingLevel()This search takes all Boolean or integer variables, and maximize or minimize them in order to reduce their domain. -1 is automatic, otherwise value 0 disables it, and 1, 2, or 3 changes something.
optional int32 variables_shaving_level = 289 [default = -1];- Specified by:
hasVariablesShavingLevelin interfaceSatParametersOrBuilder- Returns:
- Whether the variablesShavingLevel field is set.
-
getVariablesShavingLevel
public int getVariablesShavingLevel()This search takes all Boolean or integer variables, and maximize or minimize them in order to reduce their domain. -1 is automatic, otherwise value 0 disables it, and 1, 2, or 3 changes something.
optional int32 variables_shaving_level = 289 [default = -1];- Specified by:
getVariablesShavingLevelin interfaceSatParametersOrBuilder- Returns:
- The variablesShavingLevel.
-
setVariablesShavingLevel
This search takes all Boolean or integer variables, and maximize or minimize them in order to reduce their domain. -1 is automatic, otherwise value 0 disables it, and 1, 2, or 3 changes something.
optional int32 variables_shaving_level = 289 [default = -1];- Parameters:
value- The variablesShavingLevel to set.- Returns:
- This builder for chaining.
-
clearVariablesShavingLevel
This search takes all Boolean or integer variables, and maximize or minimize them in order to reduce their domain. -1 is automatic, otherwise value 0 disables it, and 1, 2, or 3 changes something.
optional int32 variables_shaving_level = 289 [default = -1];- Returns:
- This builder for chaining.
-
hasPseudoCostReliabilityThreshold
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];- Specified by:
hasPseudoCostReliabilityThresholdin interfaceSatParametersOrBuilder- Returns:
- Whether the pseudoCostReliabilityThreshold field is set.
-
getPseudoCostReliabilityThreshold
public 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];- Specified by:
getPseudoCostReliabilityThresholdin interfaceSatParametersOrBuilder- Returns:
- The pseudoCostReliabilityThreshold.
-
setPseudoCostReliabilityThreshold
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];- Parameters:
value- The pseudoCostReliabilityThreshold to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasOptimizeWithCore
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];- Specified by:
hasOptimizeWithCorein interfaceSatParametersOrBuilder- Returns:
- Whether the optimizeWithCore field is set.
-
getOptimizeWithCore
public 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];- Specified by:
getOptimizeWithCorein interfaceSatParametersOrBuilder- Returns:
- The optimizeWithCore.
-
setOptimizeWithCore
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];- Parameters:
value- The optimizeWithCore to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasOptimizeWithLbTreeSearch
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];- Specified by:
hasOptimizeWithLbTreeSearchin interfaceSatParametersOrBuilder- Returns:
- Whether the optimizeWithLbTreeSearch field is set.
-
getOptimizeWithLbTreeSearch
public 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];- Specified by:
getOptimizeWithLbTreeSearchin interfaceSatParametersOrBuilder- Returns:
- The optimizeWithLbTreeSearch.
-
setOptimizeWithLbTreeSearch
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];- Parameters:
value- The optimizeWithLbTreeSearch to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasSaveLpBasisInLbTreeSearch
public boolean hasSaveLpBasisInLbTreeSearch()Experimental. Save the current LP basis at each node of the search tree so that when we jump around, we can load it and reduce the number of LP iterations needed. It currently works okay if we do not change the lp with cuts or simplification... More work is needed to make it robust in all cases.
optional bool save_lp_basis_in_lb_tree_search = 284 [default = false];- Specified by:
hasSaveLpBasisInLbTreeSearchin interfaceSatParametersOrBuilder- Returns:
- Whether the saveLpBasisInLbTreeSearch field is set.
-
getSaveLpBasisInLbTreeSearch
public boolean getSaveLpBasisInLbTreeSearch()Experimental. Save the current LP basis at each node of the search tree so that when we jump around, we can load it and reduce the number of LP iterations needed. It currently works okay if we do not change the lp with cuts or simplification... More work is needed to make it robust in all cases.
optional bool save_lp_basis_in_lb_tree_search = 284 [default = false];- Specified by:
getSaveLpBasisInLbTreeSearchin interfaceSatParametersOrBuilder- Returns:
- The saveLpBasisInLbTreeSearch.
-
setSaveLpBasisInLbTreeSearch
Experimental. Save the current LP basis at each node of the search tree so that when we jump around, we can load it and reduce the number of LP iterations needed. It currently works okay if we do not change the lp with cuts or simplification... More work is needed to make it robust in all cases.
optional bool save_lp_basis_in_lb_tree_search = 284 [default = false];- Parameters:
value- The saveLpBasisInLbTreeSearch to set.- Returns:
- This builder for chaining.
-
clearSaveLpBasisInLbTreeSearch
Experimental. Save the current LP basis at each node of the search tree so that when we jump around, we can load it and reduce the number of LP iterations needed. It currently works okay if we do not change the lp with cuts or simplification... More work is needed to make it robust in all cases.
optional bool save_lp_basis_in_lb_tree_search = 284 [default = false];- Returns:
- This builder for chaining.
-
hasBinarySearchNumConflicts
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];- Specified by:
hasBinarySearchNumConflictsin interfaceSatParametersOrBuilder- Returns:
- Whether the binarySearchNumConflicts field is set.
-
getBinarySearchNumConflicts
public 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];- Specified by:
getBinarySearchNumConflictsin interfaceSatParametersOrBuilder- Returns:
- The binarySearchNumConflicts.
-
setBinarySearchNumConflicts
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];- Parameters:
value- The binarySearchNumConflicts to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasOptimizeWithMaxHs
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];- Specified by:
hasOptimizeWithMaxHsin interfaceSatParametersOrBuilder- Returns:
- Whether the optimizeWithMaxHs field is set.
-
getOptimizeWithMaxHs
public 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];- Specified by:
getOptimizeWithMaxHsin interfaceSatParametersOrBuilder- Returns:
- The optimizeWithMaxHs.
-
setOptimizeWithMaxHs
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];- Parameters:
value- The optimizeWithMaxHs to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseFeasibilityJump
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];- Specified by:
hasUseFeasibilityJumpin interfaceSatParametersOrBuilder- Returns:
- Whether the useFeasibilityJump field is set.
-
getUseFeasibilityJump
public 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];- Specified by:
getUseFeasibilityJumpin interfaceSatParametersOrBuilder- Returns:
- The useFeasibilityJump.
-
setUseFeasibilityJump
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];- Parameters:
value- The useFeasibilityJump to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseLsOnly
public boolean hasUseLsOnly()Disable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.
optional bool use_ls_only = 240 [default = false];- Specified by:
hasUseLsOnlyin interfaceSatParametersOrBuilder- Returns:
- Whether the useLsOnly field is set.
-
getUseLsOnly
public boolean getUseLsOnly()Disable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.
optional bool use_ls_only = 240 [default = false];- Specified by:
getUseLsOnlyin interfaceSatParametersOrBuilder- Returns:
- The useLsOnly.
-
setUseLsOnly
Disable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.
optional bool use_ls_only = 240 [default = false];- Parameters:
value- The useLsOnly to set.- Returns:
- This builder for chaining.
-
clearUseLsOnly
Disable every other type of subsolver, setting this turns CP-SAT into a pure local-search solver.
optional bool use_ls_only = 240 [default = false];- Returns:
- This builder for chaining.
-
hasFeasibilityJumpDecay
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];- Specified by:
hasFeasibilityJumpDecayin interfaceSatParametersOrBuilder- Returns:
- Whether the feasibilityJumpDecay field is set.
-
getFeasibilityJumpDecay
public 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];- Specified by:
getFeasibilityJumpDecayin interfaceSatParametersOrBuilder- Returns:
- The feasibilityJumpDecay.
-
setFeasibilityJumpDecay
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];- Parameters:
value- The feasibilityJumpDecay to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasFeasibilityJumpLinearizationLevel
public boolean hasFeasibilityJumpLinearizationLevel()How much do we linearize the problem in the local search code.
optional int32 feasibility_jump_linearization_level = 257 [default = 2];- Specified by:
hasFeasibilityJumpLinearizationLevelin interfaceSatParametersOrBuilder- Returns:
- Whether the feasibilityJumpLinearizationLevel field is set.
-
getFeasibilityJumpLinearizationLevel
public int getFeasibilityJumpLinearizationLevel()How much do we linearize the problem in the local search code.
optional int32 feasibility_jump_linearization_level = 257 [default = 2];- Specified by:
getFeasibilityJumpLinearizationLevelin interfaceSatParametersOrBuilder- Returns:
- The feasibilityJumpLinearizationLevel.
-
setFeasibilityJumpLinearizationLevel
How much do we linearize the problem in the local search code.
optional int32 feasibility_jump_linearization_level = 257 [default = 2];- Parameters:
value- The feasibilityJumpLinearizationLevel to set.- Returns:
- This builder for chaining.
-
clearFeasibilityJumpLinearizationLevel
How much do we linearize the problem in the local search code.
optional int32 feasibility_jump_linearization_level = 257 [default = 2];- Returns:
- This builder for chaining.
-
hasFeasibilityJumpRestartFactor
public boolean hasFeasibilityJumpRestartFactor()This is a factor that directly influence the work before each restart. Increasing it leads to longer restart.
optional int32 feasibility_jump_restart_factor = 258 [default = 1];- Specified by:
hasFeasibilityJumpRestartFactorin interfaceSatParametersOrBuilder- Returns:
- Whether the feasibilityJumpRestartFactor field is set.
-
getFeasibilityJumpRestartFactor
public int getFeasibilityJumpRestartFactor()This is a factor that directly influence the work before each restart. Increasing it leads to longer restart.
optional int32 feasibility_jump_restart_factor = 258 [default = 1];- Specified by:
getFeasibilityJumpRestartFactorin interfaceSatParametersOrBuilder- Returns:
- The feasibilityJumpRestartFactor.
-
setFeasibilityJumpRestartFactor
This is a factor that directly influence the work before each restart. Increasing it leads to longer restart.
optional int32 feasibility_jump_restart_factor = 258 [default = 1];- Parameters:
value- The feasibilityJumpRestartFactor to set.- Returns:
- This builder for chaining.
-
clearFeasibilityJumpRestartFactor
This is a factor that directly influence the work before each restart. Increasing it leads to longer restart.
optional int32 feasibility_jump_restart_factor = 258 [default = 1];- Returns:
- This builder for chaining.
-
hasFeasibilityJumpBatchDtime
public boolean hasFeasibilityJumpBatchDtime()How much dtime for each LS batch.
optional double feasibility_jump_batch_dtime = 292 [default = 0.1];- Specified by:
hasFeasibilityJumpBatchDtimein interfaceSatParametersOrBuilder- Returns:
- Whether the feasibilityJumpBatchDtime field is set.
-
getFeasibilityJumpBatchDtime
public double getFeasibilityJumpBatchDtime()How much dtime for each LS batch.
optional double feasibility_jump_batch_dtime = 292 [default = 0.1];- Specified by:
getFeasibilityJumpBatchDtimein interfaceSatParametersOrBuilder- Returns:
- The feasibilityJumpBatchDtime.
-
setFeasibilityJumpBatchDtime
How much dtime for each LS batch.
optional double feasibility_jump_batch_dtime = 292 [default = 0.1];- Parameters:
value- The feasibilityJumpBatchDtime to set.- Returns:
- This builder for chaining.
-
clearFeasibilityJumpBatchDtime
How much dtime for each LS batch.
optional double feasibility_jump_batch_dtime = 292 [default = 0.1];- Returns:
- This builder for chaining.
-
hasFeasibilityJumpVarRandomizationProbability
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.05];- Specified by:
hasFeasibilityJumpVarRandomizationProbabilityin interfaceSatParametersOrBuilder- Returns:
- Whether the feasibilityJumpVarRandomizationProbability field is set.
-
getFeasibilityJumpVarRandomizationProbability
public 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.05];- Specified by:
getFeasibilityJumpVarRandomizationProbabilityin interfaceSatParametersOrBuilder- Returns:
- The feasibilityJumpVarRandomizationProbability.
-
setFeasibilityJumpVarRandomizationProbability
Probability for a variable to have a non default value upon restarts or perturbations.
optional double feasibility_jump_var_randomization_probability = 247 [default = 0.05];- Parameters:
value- The feasibilityJumpVarRandomizationProbability to set.- Returns:
- This builder for chaining.
-
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.05];- Returns:
- This builder for chaining.
-
hasFeasibilityJumpVarPerburbationRangeRatio
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];- Specified by:
hasFeasibilityJumpVarPerburbationRangeRatioin interfaceSatParametersOrBuilder- Returns:
- Whether the feasibilityJumpVarPerburbationRangeRatio field is set.
-
getFeasibilityJumpVarPerburbationRangeRatio
public 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];- Specified by:
getFeasibilityJumpVarPerburbationRangeRatioin interfaceSatParametersOrBuilder- Returns:
- The feasibilityJumpVarPerburbationRangeRatio.
-
setFeasibilityJumpVarPerburbationRangeRatio
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];- Parameters:
value- The feasibilityJumpVarPerburbationRangeRatio to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasFeasibilityJumpEnableRestarts
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];- Specified by:
hasFeasibilityJumpEnableRestartsin interfaceSatParametersOrBuilder- Returns:
- Whether the feasibilityJumpEnableRestarts field is set.
-
getFeasibilityJumpEnableRestarts
public 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];- Specified by:
getFeasibilityJumpEnableRestartsin interfaceSatParametersOrBuilder- Returns:
- The feasibilityJumpEnableRestarts.
-
setFeasibilityJumpEnableRestarts
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];- Parameters:
value- The feasibilityJumpEnableRestarts to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasFeasibilityJumpMaxExpandedConstraintSize
public boolean hasFeasibilityJumpMaxExpandedConstraintSize()Maximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion. This might look a lot, but by expanding such constraint, we get a linear time evaluation per single variable moves instead of a slow O(n log n) one.
optional int32 feasibility_jump_max_expanded_constraint_size = 264 [default = 500];- Specified by:
hasFeasibilityJumpMaxExpandedConstraintSizein interfaceSatParametersOrBuilder- Returns:
- Whether the feasibilityJumpMaxExpandedConstraintSize field is set.
-
getFeasibilityJumpMaxExpandedConstraintSize
public int getFeasibilityJumpMaxExpandedConstraintSize()Maximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion. This might look a lot, but by expanding such constraint, we get a linear time evaluation per single variable moves instead of a slow O(n log n) one.
optional int32 feasibility_jump_max_expanded_constraint_size = 264 [default = 500];- Specified by:
getFeasibilityJumpMaxExpandedConstraintSizein interfaceSatParametersOrBuilder- Returns:
- The feasibilityJumpMaxExpandedConstraintSize.
-
setFeasibilityJumpMaxExpandedConstraintSize
Maximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion. This might look a lot, but by expanding such constraint, we get a linear time evaluation per single variable moves instead of a slow O(n log n) one.
optional int32 feasibility_jump_max_expanded_constraint_size = 264 [default = 500];- Parameters:
value- The feasibilityJumpMaxExpandedConstraintSize to set.- Returns:
- This builder for chaining.
-
clearFeasibilityJumpMaxExpandedConstraintSize
Maximum size of no_overlap or no_overlap_2d constraint for a quadratic expansion. This might look a lot, but by expanding such constraint, we get a linear time evaluation per single variable moves instead of a slow O(n log n) one.
optional int32 feasibility_jump_max_expanded_constraint_size = 264 [default = 500];- Returns:
- This builder for chaining.
-
hasNumViolationLs
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];- Specified by:
hasNumViolationLsin interfaceSatParametersOrBuilder- Returns:
- Whether the numViolationLs field is set.
-
getNumViolationLs
public 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];- Specified by:
getNumViolationLsin interfaceSatParametersOrBuilder- Returns:
- The numViolationLs.
-
setNumViolationLs
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];- Parameters:
value- The numViolationLs to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasViolationLsPerturbationPeriod
public boolean hasViolationLsPerturbationPeriod()How long violation_ls should wait before perturbating a solution.
optional int32 violation_ls_perturbation_period = 249 [default = 100];- Specified by:
hasViolationLsPerturbationPeriodin interfaceSatParametersOrBuilder- Returns:
- Whether the violationLsPerturbationPeriod field is set.
-
getViolationLsPerturbationPeriod
public int getViolationLsPerturbationPeriod()How long violation_ls should wait before perturbating a solution.
optional int32 violation_ls_perturbation_period = 249 [default = 100];- Specified by:
getViolationLsPerturbationPeriodin interfaceSatParametersOrBuilder- Returns:
- The violationLsPerturbationPeriod.
-
setViolationLsPerturbationPeriod
How long violation_ls should wait before perturbating a solution.
optional int32 violation_ls_perturbation_period = 249 [default = 100];- Parameters:
value- The violationLsPerturbationPeriod to set.- Returns:
- This builder for chaining.
-
clearViolationLsPerturbationPeriod
How long violation_ls should wait before perturbating a solution.
optional int32 violation_ls_perturbation_period = 249 [default = 100];- Returns:
- This builder for chaining.
-
hasViolationLsCompoundMoveProbability
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];- Specified by:
hasViolationLsCompoundMoveProbabilityin interfaceSatParametersOrBuilder- Returns:
- Whether the violationLsCompoundMoveProbability field is set.
-
getViolationLsCompoundMoveProbability
public 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];- Specified by:
getViolationLsCompoundMoveProbabilityin interfaceSatParametersOrBuilder- Returns:
- The violationLsCompoundMoveProbability.
-
setViolationLsCompoundMoveProbability
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];- Parameters:
value- The violationLsCompoundMoveProbability to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasEnumerateAllSolutions
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];- Specified by:
hasEnumerateAllSolutionsin interfaceSatParametersOrBuilder- Returns:
- Whether the enumerateAllSolutions field is set.
-
getEnumerateAllSolutions
public 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];- Specified by:
getEnumerateAllSolutionsin interfaceSatParametersOrBuilder- Returns:
- The enumerateAllSolutions.
-
setEnumerateAllSolutions
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];- Parameters:
value- The enumerateAllSolutions to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasKeepAllFeasibleSolutionsInPresolve
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];- Specified by:
hasKeepAllFeasibleSolutionsInPresolvein interfaceSatParametersOrBuilder- Returns:
- Whether the keepAllFeasibleSolutionsInPresolve field is set.
-
getKeepAllFeasibleSolutionsInPresolve
public 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];- Specified by:
getKeepAllFeasibleSolutionsInPresolvein interfaceSatParametersOrBuilder- Returns:
- The keepAllFeasibleSolutionsInPresolve.
-
setKeepAllFeasibleSolutionsInPresolve
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];- Parameters:
value- The keepAllFeasibleSolutionsInPresolve to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasFillTightenedDomainsInResponse
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];- Specified by:
hasFillTightenedDomainsInResponsein interfaceSatParametersOrBuilder- Returns:
- Whether the fillTightenedDomainsInResponse field is set.
-
getFillTightenedDomainsInResponse
public 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];- Specified by:
getFillTightenedDomainsInResponsein interfaceSatParametersOrBuilder- Returns:
- The fillTightenedDomainsInResponse.
-
setFillTightenedDomainsInResponse
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];- Parameters:
value- The fillTightenedDomainsInResponse to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasFillAdditionalSolutionsInResponse
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];- Specified by:
hasFillAdditionalSolutionsInResponsein interfaceSatParametersOrBuilder- Returns:
- Whether the fillAdditionalSolutionsInResponse field is set.
-
getFillAdditionalSolutionsInResponse
public 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];- Specified by:
getFillAdditionalSolutionsInResponsein interfaceSatParametersOrBuilder- Returns:
- The fillAdditionalSolutionsInResponse.
-
setFillAdditionalSolutionsInResponse
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];- Parameters:
value- The fillAdditionalSolutionsInResponse to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasInstantiateAllVariables
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];- Specified by:
hasInstantiateAllVariablesin interfaceSatParametersOrBuilder- Returns:
- Whether the instantiateAllVariables field is set.
-
getInstantiateAllVariables
public 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];- Specified by:
getInstantiateAllVariablesin interfaceSatParametersOrBuilder- Returns:
- The instantiateAllVariables.
-
setInstantiateAllVariables
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];- Parameters:
value- The instantiateAllVariables to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAutoDetectGreaterThanAtLeastOneOf
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];- Specified by:
hasAutoDetectGreaterThanAtLeastOneOfin interfaceSatParametersOrBuilder- Returns:
- Whether the autoDetectGreaterThanAtLeastOneOf field is set.
-
getAutoDetectGreaterThanAtLeastOneOf
public 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];- Specified by:
getAutoDetectGreaterThanAtLeastOneOfin interfaceSatParametersOrBuilder- Returns:
- The autoDetectGreaterThanAtLeastOneOf.
-
setAutoDetectGreaterThanAtLeastOneOf
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];- Parameters:
value- The autoDetectGreaterThanAtLeastOneOf to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasStopAfterFirstSolution
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];- Specified by:
hasStopAfterFirstSolutionin interfaceSatParametersOrBuilder- Returns:
- Whether the stopAfterFirstSolution field is set.
-
getStopAfterFirstSolution
public 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];- Specified by:
getStopAfterFirstSolutionin interfaceSatParametersOrBuilder- Returns:
- The stopAfterFirstSolution.
-
setStopAfterFirstSolution
For an optimization problem, stop the solver as soon as we have a solution.
optional bool stop_after_first_solution = 98 [default = false];- Parameters:
value- The stopAfterFirstSolution to set.- Returns:
- This builder for chaining.
-
clearStopAfterFirstSolution
For an optimization problem, stop the solver as soon as we have a solution.
optional bool stop_after_first_solution = 98 [default = false];- Returns:
- This builder for chaining.
-
hasStopAfterPresolve
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];- Specified by:
hasStopAfterPresolvein interfaceSatParametersOrBuilder- Returns:
- Whether the stopAfterPresolve field is set.
-
getStopAfterPresolve
public 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];- Specified by:
getStopAfterPresolvein interfaceSatParametersOrBuilder- Returns:
- The stopAfterPresolve.
-
setStopAfterPresolve
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];- Parameters:
value- The stopAfterPresolve to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasStopAfterRootPropagation
public boolean hasStopAfterRootPropagation()optional bool stop_after_root_propagation = 252 [default = false];- Specified by:
hasStopAfterRootPropagationin interfaceSatParametersOrBuilder- Returns:
- Whether the stopAfterRootPropagation field is set.
-
getStopAfterRootPropagation
public boolean getStopAfterRootPropagation()optional bool stop_after_root_propagation = 252 [default = false];- Specified by:
getStopAfterRootPropagationin interfaceSatParametersOrBuilder- Returns:
- The stopAfterRootPropagation.
-
setStopAfterRootPropagation
optional bool stop_after_root_propagation = 252 [default = false];- Parameters:
value- The stopAfterRootPropagation to set.- Returns:
- This builder for chaining.
-
clearStopAfterRootPropagation
optional bool stop_after_root_propagation = 252 [default = false];- Returns:
- This builder for chaining.
-
hasLnsInitialDifficulty
public boolean hasLnsInitialDifficulty()Initial parameters for neighborhood generation.
optional double lns_initial_difficulty = 307 [default = 0.5];- Specified by:
hasLnsInitialDifficultyin interfaceSatParametersOrBuilder- Returns:
- Whether the lnsInitialDifficulty field is set.
-
getLnsInitialDifficulty
public double getLnsInitialDifficulty()Initial parameters for neighborhood generation.
optional double lns_initial_difficulty = 307 [default = 0.5];- Specified by:
getLnsInitialDifficultyin interfaceSatParametersOrBuilder- Returns:
- The lnsInitialDifficulty.
-
setLnsInitialDifficulty
Initial parameters for neighborhood generation.
optional double lns_initial_difficulty = 307 [default = 0.5];- Parameters:
value- The lnsInitialDifficulty to set.- Returns:
- This builder for chaining.
-
clearLnsInitialDifficulty
Initial parameters for neighborhood generation.
optional double lns_initial_difficulty = 307 [default = 0.5];- Returns:
- This builder for chaining.
-
hasLnsInitialDeterministicLimit
public boolean hasLnsInitialDeterministicLimit()optional double lns_initial_deterministic_limit = 308 [default = 0.1];- Specified by:
hasLnsInitialDeterministicLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the lnsInitialDeterministicLimit field is set.
-
getLnsInitialDeterministicLimit
public double getLnsInitialDeterministicLimit()optional double lns_initial_deterministic_limit = 308 [default = 0.1];- Specified by:
getLnsInitialDeterministicLimitin interfaceSatParametersOrBuilder- Returns:
- The lnsInitialDeterministicLimit.
-
setLnsInitialDeterministicLimit
optional double lns_initial_deterministic_limit = 308 [default = 0.1];- Parameters:
value- The lnsInitialDeterministicLimit to set.- Returns:
- This builder for chaining.
-
clearLnsInitialDeterministicLimit
optional double lns_initial_deterministic_limit = 308 [default = 0.1];- Returns:
- This builder for chaining.
-
hasUseLns
public boolean hasUseLns()Testing parameters used to disable all lns workers.
optional bool use_lns = 283 [default = true];- Specified by:
hasUseLnsin interfaceSatParametersOrBuilder- Returns:
- Whether the useLns field is set.
-
getUseLns
public boolean getUseLns()Testing parameters used to disable all lns workers.
optional bool use_lns = 283 [default = true];- Specified by:
getUseLnsin interfaceSatParametersOrBuilder- Returns:
- The useLns.
-
setUseLns
Testing parameters used to disable all lns workers.
optional bool use_lns = 283 [default = true];- Parameters:
value- The useLns to set.- Returns:
- This builder for chaining.
-
clearUseLns
Testing parameters used to disable all lns workers.
optional bool use_lns = 283 [default = true];- Returns:
- This builder for chaining.
-
hasUseLnsOnly
public boolean hasUseLnsOnly()Experimental parameters to disable everything but lns.
optional bool use_lns_only = 101 [default = false];- Specified by:
hasUseLnsOnlyin interfaceSatParametersOrBuilder- Returns:
- Whether the useLnsOnly field is set.
-
getUseLnsOnly
public boolean getUseLnsOnly()Experimental parameters to disable everything but lns.
optional bool use_lns_only = 101 [default = false];- Specified by:
getUseLnsOnlyin interfaceSatParametersOrBuilder- Returns:
- The useLnsOnly.
-
setUseLnsOnly
Experimental parameters to disable everything but lns.
optional bool use_lns_only = 101 [default = false];- Parameters:
value- The useLnsOnly to set.- Returns:
- This builder for chaining.
-
clearUseLnsOnly
Experimental parameters to disable everything but lns.
optional bool use_lns_only = 101 [default = false];- Returns:
- This builder for chaining.
-
hasSolutionPoolSize
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];- Specified by:
hasSolutionPoolSizein interfaceSatParametersOrBuilder- Returns:
- Whether the solutionPoolSize field is set.
-
getSolutionPoolSize
public 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];- Specified by:
getSolutionPoolSizein interfaceSatParametersOrBuilder- Returns:
- The solutionPoolSize.
-
setSolutionPoolSize
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];- Parameters:
value- The solutionPoolSize to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseRinsLns
public boolean hasUseRinsLns()Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];- Specified by:
hasUseRinsLnsin interfaceSatParametersOrBuilder- Returns:
- Whether the useRinsLns field is set.
-
getUseRinsLns
public boolean getUseRinsLns()Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];- Specified by:
getUseRinsLnsin interfaceSatParametersOrBuilder- Returns:
- The useRinsLns.
-
setUseRinsLns
Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];- Parameters:
value- The useRinsLns to set.- Returns:
- This builder for chaining.
-
clearUseRinsLns
Turns on relaxation induced neighborhood generator.
optional bool use_rins_lns = 129 [default = true];- Returns:
- This builder for chaining.
-
hasUseFeasibilityPump
public boolean hasUseFeasibilityPump()Adds a feasibility pump subsolver along with lns subsolvers.
optional bool use_feasibility_pump = 164 [default = true];- Specified by:
hasUseFeasibilityPumpin interfaceSatParametersOrBuilder- Returns:
- Whether the useFeasibilityPump field is set.
-
getUseFeasibilityPump
public boolean getUseFeasibilityPump()Adds a feasibility pump subsolver along with lns subsolvers.
optional bool use_feasibility_pump = 164 [default = true];- Specified by:
getUseFeasibilityPumpin interfaceSatParametersOrBuilder- Returns:
- The useFeasibilityPump.
-
setUseFeasibilityPump
Adds a feasibility pump subsolver along with lns subsolvers.
optional bool use_feasibility_pump = 164 [default = true];- Parameters:
value- The useFeasibilityPump to set.- Returns:
- This builder for chaining.
-
clearUseFeasibilityPump
Adds a feasibility pump subsolver along with lns subsolvers.
optional bool use_feasibility_pump = 164 [default = true];- Returns:
- This builder for chaining.
-
hasUseLbRelaxLns
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 = true];- Specified by:
hasUseLbRelaxLnsin interfaceSatParametersOrBuilder- Returns:
- Whether the useLbRelaxLns field is set.
-
getUseLbRelaxLns
public 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 = true];- Specified by:
getUseLbRelaxLnsin interfaceSatParametersOrBuilder- Returns:
- The useLbRelaxLns.
-
setUseLbRelaxLns
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 = true];- Parameters:
value- The useLbRelaxLns to set.- Returns:
- This builder for chaining.
-
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 = true];- Returns:
- This builder for chaining.
-
hasLbRelaxNumWorkersThreshold
public boolean hasLbRelaxNumWorkersThreshold()Only use lb-relax if we have at least that many workers.
optional int32 lb_relax_num_workers_threshold = 296 [default = 16];- Specified by:
hasLbRelaxNumWorkersThresholdin interfaceSatParametersOrBuilder- Returns:
- Whether the lbRelaxNumWorkersThreshold field is set.
-
getLbRelaxNumWorkersThreshold
public int getLbRelaxNumWorkersThreshold()Only use lb-relax if we have at least that many workers.
optional int32 lb_relax_num_workers_threshold = 296 [default = 16];- Specified by:
getLbRelaxNumWorkersThresholdin interfaceSatParametersOrBuilder- Returns:
- The lbRelaxNumWorkersThreshold.
-
setLbRelaxNumWorkersThreshold
Only use lb-relax if we have at least that many workers.
optional int32 lb_relax_num_workers_threshold = 296 [default = 16];- Parameters:
value- The lbRelaxNumWorkersThreshold to set.- Returns:
- This builder for chaining.
-
clearLbRelaxNumWorkersThreshold
Only use lb-relax if we have at least that many workers.
optional int32 lb_relax_num_workers_threshold = 296 [default = 16];- Returns:
- This builder for chaining.
-
hasFpRounding
public boolean hasFpRounding()optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];- Specified by:
hasFpRoundingin interfaceSatParametersOrBuilder- Returns:
- Whether the fpRounding field is set.
-
getFpRounding
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];- Specified by:
getFpRoundingin interfaceSatParametersOrBuilder- Returns:
- The fpRounding.
-
setFpRounding
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];- Parameters:
value- The fpRounding to set.- Returns:
- This builder for chaining.
-
clearFpRounding
optional .operations_research.sat.SatParameters.FPRoundingMethod fp_rounding = 165 [default = PROPAGATION_ASSISTED];- Returns:
- This builder for chaining.
-
hasDiversifyLnsParams
public boolean hasDiversifyLnsParams()If true, registers more lns subsolvers with different parameters.
optional bool diversify_lns_params = 137 [default = false];- Specified by:
hasDiversifyLnsParamsin interfaceSatParametersOrBuilder- Returns:
- Whether the diversifyLnsParams field is set.
-
getDiversifyLnsParams
public boolean getDiversifyLnsParams()If true, registers more lns subsolvers with different parameters.
optional bool diversify_lns_params = 137 [default = false];- Specified by:
getDiversifyLnsParamsin interfaceSatParametersOrBuilder- Returns:
- The diversifyLnsParams.
-
setDiversifyLnsParams
If true, registers more lns subsolvers with different parameters.
optional bool diversify_lns_params = 137 [default = false];- Parameters:
value- The diversifyLnsParams to set.- Returns:
- This builder for chaining.
-
clearDiversifyLnsParams
If true, registers more lns subsolvers with different parameters.
optional bool diversify_lns_params = 137 [default = false];- Returns:
- This builder for chaining.
-
hasRandomizeSearch
public boolean hasRandomizeSearch()Randomize fixed search.
optional bool randomize_search = 103 [default = false];- Specified by:
hasRandomizeSearchin interfaceSatParametersOrBuilder- Returns:
- Whether the randomizeSearch field is set.
-
getRandomizeSearch
public boolean getRandomizeSearch()Randomize fixed search.
optional bool randomize_search = 103 [default = false];- Specified by:
getRandomizeSearchin interfaceSatParametersOrBuilder- Returns:
- The randomizeSearch.
-
setRandomizeSearch
Randomize fixed search.
optional bool randomize_search = 103 [default = false];- Parameters:
value- The randomizeSearch to set.- Returns:
- This builder for chaining.
-
clearRandomizeSearch
Randomize fixed search.
optional bool randomize_search = 103 [default = false];- Returns:
- This builder for chaining.
-
hasSearchRandomVariablePoolSize
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];- Specified by:
hasSearchRandomVariablePoolSizein interfaceSatParametersOrBuilder- Returns:
- Whether the searchRandomVariablePoolSize field is set.
-
getSearchRandomVariablePoolSize
public 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];- Specified by:
getSearchRandomVariablePoolSizein interfaceSatParametersOrBuilder- Returns:
- The searchRandomVariablePoolSize.
-
setSearchRandomVariablePoolSize
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];- Parameters:
value- The searchRandomVariablePoolSize to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasPushAllTasksTowardStart
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];- Specified by:
hasPushAllTasksTowardStartin interfaceSatParametersOrBuilder- Returns:
- Whether the pushAllTasksTowardStart field is set.
-
getPushAllTasksTowardStart
public 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];- Specified by:
getPushAllTasksTowardStartin interfaceSatParametersOrBuilder- Returns:
- The pushAllTasksTowardStart.
-
setPushAllTasksTowardStart
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];- Parameters:
value- The pushAllTasksTowardStart to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseOptionalVariables
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];- Specified by:
hasUseOptionalVariablesin interfaceSatParametersOrBuilder- Returns:
- Whether the useOptionalVariables field is set.
-
getUseOptionalVariables
public 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];- Specified by:
getUseOptionalVariablesin interfaceSatParametersOrBuilder- Returns:
- The useOptionalVariables.
-
setUseOptionalVariables
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];- Parameters:
value- The useOptionalVariables to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseExactLpReason
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];- Specified by:
hasUseExactLpReasonin interfaceSatParametersOrBuilder- Returns:
- Whether the useExactLpReason field is set.
-
getUseExactLpReason
public 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];- Specified by:
getUseExactLpReasonin interfaceSatParametersOrBuilder- Returns:
- The useExactLpReason.
-
setUseExactLpReason
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];- Parameters:
value- The useExactLpReason to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseCombinedNoOverlap
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];- Specified by:
hasUseCombinedNoOverlapin interfaceSatParametersOrBuilder- Returns:
- Whether the useCombinedNoOverlap field is set.
-
getUseCombinedNoOverlap
public 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];- Specified by:
getUseCombinedNoOverlapin interfaceSatParametersOrBuilder- Returns:
- The useCombinedNoOverlap.
-
setUseCombinedNoOverlap
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];- Parameters:
value- The useCombinedNoOverlap to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAtMostOneMaxExpansionSize
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];- Specified by:
hasAtMostOneMaxExpansionSizein interfaceSatParametersOrBuilder- Returns:
- Whether the atMostOneMaxExpansionSize field is set.
-
getAtMostOneMaxExpansionSize
public 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];- Specified by:
getAtMostOneMaxExpansionSizein interfaceSatParametersOrBuilder- Returns:
- The atMostOneMaxExpansionSize.
-
setAtMostOneMaxExpansionSize
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];- Parameters:
value- The atMostOneMaxExpansionSize to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasCatchSigintSignal
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];- Specified by:
hasCatchSigintSignalin interfaceSatParametersOrBuilder- Returns:
- Whether the catchSigintSignal field is set.
-
getCatchSigintSignal
public 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];- Specified by:
getCatchSigintSignalin interfaceSatParametersOrBuilder- Returns:
- The catchSigintSignal.
-
setCatchSigintSignal
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];- Parameters:
value- The catchSigintSignal to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasUseImpliedBounds
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];- Specified by:
hasUseImpliedBoundsin interfaceSatParametersOrBuilder- Returns:
- Whether the useImpliedBounds field is set.
-
getUseImpliedBounds
public 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];- Specified by:
getUseImpliedBoundsin interfaceSatParametersOrBuilder- Returns:
- The useImpliedBounds.
-
setUseImpliedBounds
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];- Parameters:
value- The useImpliedBounds to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasPolishLpSolution
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];- Specified by:
hasPolishLpSolutionin interfaceSatParametersOrBuilder- Returns:
- Whether the polishLpSolution field is set.
-
getPolishLpSolution
public 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];- Specified by:
getPolishLpSolutionin interfaceSatParametersOrBuilder- Returns:
- The polishLpSolution.
-
setPolishLpSolution
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];- Parameters:
value- The polishLpSolution to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasLpPrimalTolerance
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];- Specified by:
hasLpPrimalTolerancein interfaceSatParametersOrBuilder- Returns:
- Whether the lpPrimalTolerance field is set.
-
getLpPrimalTolerance
public 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];- Specified by:
getLpPrimalTolerancein interfaceSatParametersOrBuilder- Returns:
- The lpPrimalTolerance.
-
setLpPrimalTolerance
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];- Parameters:
value- The lpPrimalTolerance to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasLpDualTolerance
public boolean hasLpDualTolerance()optional double lp_dual_tolerance = 267 [default = 1e-07];- Specified by:
hasLpDualTolerancein interfaceSatParametersOrBuilder- Returns:
- Whether the lpDualTolerance field is set.
-
getLpDualTolerance
public double getLpDualTolerance()optional double lp_dual_tolerance = 267 [default = 1e-07];- Specified by:
getLpDualTolerancein interfaceSatParametersOrBuilder- Returns:
- The lpDualTolerance.
-
setLpDualTolerance
optional double lp_dual_tolerance = 267 [default = 1e-07];- Parameters:
value- The lpDualTolerance to set.- Returns:
- This builder for chaining.
-
clearLpDualTolerance
optional double lp_dual_tolerance = 267 [default = 1e-07];- Returns:
- This builder for chaining.
-
hasConvertIntervals
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];- Specified by:
hasConvertIntervalsin interfaceSatParametersOrBuilder- Returns:
- Whether the convertIntervals field is set.
-
getConvertIntervals
public 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];- Specified by:
getConvertIntervalsin interfaceSatParametersOrBuilder- Returns:
- The convertIntervals.
-
setConvertIntervals
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];- Parameters:
value- The convertIntervals to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasSymmetryLevel
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. At level 3, we also detect symmetries for very large models, which can be slow. At level 4, we try to break as much symmetry as possible in presolve.
optional int32 symmetry_level = 183 [default = 2];- Specified by:
hasSymmetryLevelin interfaceSatParametersOrBuilder- Returns:
- Whether the symmetryLevel field is set.
-
getSymmetryLevel
public 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. At level 3, we also detect symmetries for very large models, which can be slow. At level 4, we try to break as much symmetry as possible in presolve.
optional int32 symmetry_level = 183 [default = 2];- Specified by:
getSymmetryLevelin interfaceSatParametersOrBuilder- Returns:
- The symmetryLevel.
-
setSymmetryLevel
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. At level 3, we also detect symmetries for very large models, which can be slow. At level 4, we try to break as much symmetry as possible in presolve.
optional int32 symmetry_level = 183 [default = 2];- Parameters:
value- The symmetryLevel to set.- Returns:
- This builder for chaining.
-
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. At level 3, we also detect symmetries for very large models, which can be slow. At level 4, we try to break as much symmetry as possible in presolve.
optional int32 symmetry_level = 183 [default = 2];- Returns:
- This builder for chaining.
-
hasUseSymmetryInLp
public boolean hasUseSymmetryInLp()When we have symmetry, it is possible to "fold" all variables from the same orbit into a single variable, while having the same power of LP relaxation. This can help significantly on symmetric problem. However there is currently a bit of overhead as the rest of the solver need to do some translation between the folded LP and the rest of the problem.
optional bool use_symmetry_in_lp = 301 [default = false];- Specified by:
hasUseSymmetryInLpin interfaceSatParametersOrBuilder- Returns:
- Whether the useSymmetryInLp field is set.
-
getUseSymmetryInLp
public boolean getUseSymmetryInLp()When we have symmetry, it is possible to "fold" all variables from the same orbit into a single variable, while having the same power of LP relaxation. This can help significantly on symmetric problem. However there is currently a bit of overhead as the rest of the solver need to do some translation between the folded LP and the rest of the problem.
optional bool use_symmetry_in_lp = 301 [default = false];- Specified by:
getUseSymmetryInLpin interfaceSatParametersOrBuilder- Returns:
- The useSymmetryInLp.
-
setUseSymmetryInLp
When we have symmetry, it is possible to "fold" all variables from the same orbit into a single variable, while having the same power of LP relaxation. This can help significantly on symmetric problem. However there is currently a bit of overhead as the rest of the solver need to do some translation between the folded LP and the rest of the problem.
optional bool use_symmetry_in_lp = 301 [default = false];- Parameters:
value- The useSymmetryInLp to set.- Returns:
- This builder for chaining.
-
clearUseSymmetryInLp
When we have symmetry, it is possible to "fold" all variables from the same orbit into a single variable, while having the same power of LP relaxation. This can help significantly on symmetric problem. However there is currently a bit of overhead as the rest of the solver need to do some translation between the folded LP and the rest of the problem.
optional bool use_symmetry_in_lp = 301 [default = false];- Returns:
- This builder for chaining.
-
hasKeepSymmetryInPresolve
public boolean hasKeepSymmetryInPresolve()Experimental. This will compute the symmetry of the problem once and for all. All presolve operations we do should keep the symmetry group intact or modify it properly. For now we have really little support for this. We will disable a bunch of presolve operations that could be supported.
optional bool keep_symmetry_in_presolve = 303 [default = false];- Specified by:
hasKeepSymmetryInPresolvein interfaceSatParametersOrBuilder- Returns:
- Whether the keepSymmetryInPresolve field is set.
-
getKeepSymmetryInPresolve
public boolean getKeepSymmetryInPresolve()Experimental. This will compute the symmetry of the problem once and for all. All presolve operations we do should keep the symmetry group intact or modify it properly. For now we have really little support for this. We will disable a bunch of presolve operations that could be supported.
optional bool keep_symmetry_in_presolve = 303 [default = false];- Specified by:
getKeepSymmetryInPresolvein interfaceSatParametersOrBuilder- Returns:
- The keepSymmetryInPresolve.
-
setKeepSymmetryInPresolve
Experimental. This will compute the symmetry of the problem once and for all. All presolve operations we do should keep the symmetry group intact or modify it properly. For now we have really little support for this. We will disable a bunch of presolve operations that could be supported.
optional bool keep_symmetry_in_presolve = 303 [default = false];- Parameters:
value- The keepSymmetryInPresolve to set.- Returns:
- This builder for chaining.
-
clearKeepSymmetryInPresolve
Experimental. This will compute the symmetry of the problem once and for all. All presolve operations we do should keep the symmetry group intact or modify it properly. For now we have really little support for this. We will disable a bunch of presolve operations that could be supported.
optional bool keep_symmetry_in_presolve = 303 [default = false];- Returns:
- This builder for chaining.
-
hasSymmetryDetectionDeterministicTimeLimit
public boolean hasSymmetryDetectionDeterministicTimeLimit()Deterministic time limit for symmetry detection.
optional double symmetry_detection_deterministic_time_limit = 302 [default = 1];- Specified by:
hasSymmetryDetectionDeterministicTimeLimitin interfaceSatParametersOrBuilder- Returns:
- Whether the symmetryDetectionDeterministicTimeLimit field is set.
-
getSymmetryDetectionDeterministicTimeLimit
public double getSymmetryDetectionDeterministicTimeLimit()Deterministic time limit for symmetry detection.
optional double symmetry_detection_deterministic_time_limit = 302 [default = 1];- Specified by:
getSymmetryDetectionDeterministicTimeLimitin interfaceSatParametersOrBuilder- Returns:
- The symmetryDetectionDeterministicTimeLimit.
-
setSymmetryDetectionDeterministicTimeLimit
Deterministic time limit for symmetry detection.
optional double symmetry_detection_deterministic_time_limit = 302 [default = 1];- Parameters:
value- The symmetryDetectionDeterministicTimeLimit to set.- Returns:
- This builder for chaining.
-
clearSymmetryDetectionDeterministicTimeLimit
Deterministic time limit for symmetry detection.
optional double symmetry_detection_deterministic_time_limit = 302 [default = 1];- Returns:
- This builder for chaining.
-
hasNewLinearPropagation
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];- Specified by:
hasNewLinearPropagationin interfaceSatParametersOrBuilder- Returns:
- Whether the newLinearPropagation field is set.
-
getNewLinearPropagation
public 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];- Specified by:
getNewLinearPropagationin interfaceSatParametersOrBuilder- Returns:
- The newLinearPropagation.
-
setNewLinearPropagation
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];- Parameters:
value- The newLinearPropagation to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasLinearSplitSize
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];- Specified by:
hasLinearSplitSizein interfaceSatParametersOrBuilder- Returns:
- Whether the linearSplitSize field is set.
-
getLinearSplitSize
public 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];- Specified by:
getLinearSplitSizein interfaceSatParametersOrBuilder- Returns:
- The linearSplitSize.
-
setLinearSplitSize
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];- Parameters:
value- The linearSplitSize to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasLinearizationLevel
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];- Specified by:
hasLinearizationLevelin interfaceSatParametersOrBuilder- Returns:
- Whether the linearizationLevel field is set.
-
getLinearizationLevel
public 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];- Specified by:
getLinearizationLevelin interfaceSatParametersOrBuilder- Returns:
- The linearizationLevel.
-
setLinearizationLevel
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];- Parameters:
value- The linearizationLevel to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasBooleanEncodingLevel
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];- Specified by:
hasBooleanEncodingLevelin interfaceSatParametersOrBuilder- Returns:
- Whether the booleanEncodingLevel field is set.
-
getBooleanEncodingLevel
public 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];- Specified by:
getBooleanEncodingLevelin interfaceSatParametersOrBuilder- Returns:
- The booleanEncodingLevel.
-
setBooleanEncodingLevel
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];- Parameters:
value- The booleanEncodingLevel to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxDomainSizeWhenEncodingEqNeqConstraints
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];- Specified by:
hasMaxDomainSizeWhenEncodingEqNeqConstraintsin interfaceSatParametersOrBuilder- Returns:
- Whether the maxDomainSizeWhenEncodingEqNeqConstraints field is set.
-
getMaxDomainSizeWhenEncodingEqNeqConstraints
public 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];- Specified by:
getMaxDomainSizeWhenEncodingEqNeqConstraintsin interfaceSatParametersOrBuilder- Returns:
- The maxDomainSizeWhenEncodingEqNeqConstraints.
-
setMaxDomainSizeWhenEncodingEqNeqConstraints
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];- Parameters:
value- The maxDomainSizeWhenEncodingEqNeqConstraints to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxNumCuts
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];- Specified by:
hasMaxNumCutsin interfaceSatParametersOrBuilder- Returns:
- Whether the maxNumCuts field is set.
-
getMaxNumCuts
public 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];- Specified by:
getMaxNumCutsin interfaceSatParametersOrBuilder- Returns:
- The maxNumCuts.
-
setMaxNumCuts
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];- Parameters:
value- The maxNumCuts to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasCutLevel
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];- Specified by:
hasCutLevelin interfaceSatParametersOrBuilder- Returns:
- Whether the cutLevel field is set.
-
getCutLevel
public 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];- Specified by:
getCutLevelin interfaceSatParametersOrBuilder- Returns:
- The cutLevel.
-
setCutLevel
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];- Parameters:
value- The cutLevel to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasOnlyAddCutsAtLevelZero
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];- Specified by:
hasOnlyAddCutsAtLevelZeroin interfaceSatParametersOrBuilder- Returns:
- Whether the onlyAddCutsAtLevelZero field is set.
-
getOnlyAddCutsAtLevelZero
public 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];- Specified by:
getOnlyAddCutsAtLevelZeroin interfaceSatParametersOrBuilder- Returns:
- The onlyAddCutsAtLevelZero.
-
setOnlyAddCutsAtLevelZero
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];- Parameters:
value- The onlyAddCutsAtLevelZero to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAddObjectiveCut
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];- Specified by:
hasAddObjectiveCutin interfaceSatParametersOrBuilder- Returns:
- Whether the addObjectiveCut field is set.
-
getAddObjectiveCut
public 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];- Specified by:
getAddObjectiveCutin interfaceSatParametersOrBuilder- Returns:
- The addObjectiveCut.
-
setAddObjectiveCut
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];- Parameters:
value- The addObjectiveCut to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAddCgCuts
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];- Specified by:
hasAddCgCutsin interfaceSatParametersOrBuilder- Returns:
- Whether the addCgCuts field is set.
-
getAddCgCuts
public 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];- Specified by:
getAddCgCutsin interfaceSatParametersOrBuilder- Returns:
- The addCgCuts.
-
setAddCgCuts
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];- Parameters:
value- The addCgCuts to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAddMirCuts
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];- Specified by:
hasAddMirCutsin interfaceSatParametersOrBuilder- Returns:
- Whether the addMirCuts field is set.
-
getAddMirCuts
public 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];- Specified by:
getAddMirCutsin interfaceSatParametersOrBuilder- Returns:
- The addMirCuts.
-
setAddMirCuts
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];- Parameters:
value- The addMirCuts to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAddZeroHalfCuts
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];- Specified by:
hasAddZeroHalfCutsin interfaceSatParametersOrBuilder- Returns:
- Whether the addZeroHalfCuts field is set.
-
getAddZeroHalfCuts
public 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];- Specified by:
getAddZeroHalfCutsin interfaceSatParametersOrBuilder- Returns:
- The addZeroHalfCuts.
-
setAddZeroHalfCuts
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];- Parameters:
value- The addZeroHalfCuts to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAddCliqueCuts
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];- Specified by:
hasAddCliqueCutsin interfaceSatParametersOrBuilder- Returns:
- Whether the addCliqueCuts field is set.
-
getAddCliqueCuts
public 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];- Specified by:
getAddCliqueCutsin interfaceSatParametersOrBuilder- Returns:
- The addCliqueCuts.
-
setAddCliqueCuts
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];- Parameters:
value- The addCliqueCuts to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAddRltCuts
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];- Specified by:
hasAddRltCutsin interfaceSatParametersOrBuilder- Returns:
- Whether the addRltCuts field is set.
-
getAddRltCuts
public 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];- Specified by:
getAddRltCutsin interfaceSatParametersOrBuilder- Returns:
- The addRltCuts.
-
setAddRltCuts
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];- Parameters:
value- The addRltCuts to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxAllDiffCutSize
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];- Specified by:
hasMaxAllDiffCutSizein interfaceSatParametersOrBuilder- Returns:
- Whether the maxAllDiffCutSize field is set.
-
getMaxAllDiffCutSize
public 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];- Specified by:
getMaxAllDiffCutSizein interfaceSatParametersOrBuilder- Returns:
- The maxAllDiffCutSize.
-
setMaxAllDiffCutSize
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];- Parameters:
value- The maxAllDiffCutSize to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAddLinMaxCuts
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];- Specified by:
hasAddLinMaxCutsin interfaceSatParametersOrBuilder- Returns:
- Whether the addLinMaxCuts field is set.
-
getAddLinMaxCuts
public 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];- Specified by:
getAddLinMaxCutsin interfaceSatParametersOrBuilder- Returns:
- The addLinMaxCuts.
-
setAddLinMaxCuts
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];- Parameters:
value- The addLinMaxCuts to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxIntegerRoundingScaling
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];- Specified by:
hasMaxIntegerRoundingScalingin interfaceSatParametersOrBuilder- Returns:
- Whether the maxIntegerRoundingScaling field is set.
-
getMaxIntegerRoundingScaling
public 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];- Specified by:
getMaxIntegerRoundingScalingin interfaceSatParametersOrBuilder- Returns:
- The maxIntegerRoundingScaling.
-
setMaxIntegerRoundingScaling
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];- Parameters:
value- The maxIntegerRoundingScaling to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasAddLpConstraintsLazily
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];- Specified by:
hasAddLpConstraintsLazilyin interfaceSatParametersOrBuilder- Returns:
- Whether the addLpConstraintsLazily field is set.
-
getAddLpConstraintsLazily
public 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];- Specified by:
getAddLpConstraintsLazilyin interfaceSatParametersOrBuilder- Returns:
- The addLpConstraintsLazily.
-
setAddLpConstraintsLazily
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];- Parameters:
value- The addLpConstraintsLazily to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasRootLpIterations
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];- Specified by:
hasRootLpIterationsin interfaceSatParametersOrBuilder- Returns:
- Whether the rootLpIterations field is set.
-
getRootLpIterations
public 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];- Specified by:
getRootLpIterationsin interfaceSatParametersOrBuilder- Returns:
- The rootLpIterations.
-
setRootLpIterations
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];- Parameters:
value- The rootLpIterations to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMinOrthogonalityForLpConstraints
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];- Specified by:
hasMinOrthogonalityForLpConstraintsin interfaceSatParametersOrBuilder- Returns:
- Whether the minOrthogonalityForLpConstraints field is set.
-
getMinOrthogonalityForLpConstraints
public 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];- Specified by:
getMinOrthogonalityForLpConstraintsin interfaceSatParametersOrBuilder- Returns:
- The minOrthogonalityForLpConstraints.
-
setMinOrthogonalityForLpConstraints
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];- Parameters:
value- The minOrthogonalityForLpConstraints to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxCutRoundsAtLevelZero
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];- Specified by:
hasMaxCutRoundsAtLevelZeroin interfaceSatParametersOrBuilder- Returns:
- Whether the maxCutRoundsAtLevelZero field is set.
-
getMaxCutRoundsAtLevelZero
public 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];- Specified by:
getMaxCutRoundsAtLevelZeroin interfaceSatParametersOrBuilder- Returns:
- The maxCutRoundsAtLevelZero.
-
setMaxCutRoundsAtLevelZero
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];- Parameters:
value- The maxCutRoundsAtLevelZero to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMaxConsecutiveInactiveCount
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];- Specified by:
hasMaxConsecutiveInactiveCountin interfaceSatParametersOrBuilder- Returns:
- Whether the maxConsecutiveInactiveCount field is set.
-
getMaxConsecutiveInactiveCount
public 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];- Specified by:
getMaxConsecutiveInactiveCountin interfaceSatParametersOrBuilder- Returns:
- The maxConsecutiveInactiveCount.
-
setMaxConsecutiveInactiveCount
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];- Parameters:
value- The maxConsecutiveInactiveCount to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasCutMaxActiveCountValue
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];- Specified by:
hasCutMaxActiveCountValuein interfaceSatParametersOrBuilder- Returns:
- Whether the cutMaxActiveCountValue field is set.
-
getCutMaxActiveCountValue
public 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];- Specified by:
getCutMaxActiveCountValuein interfaceSatParametersOrBuilder- Returns:
- The cutMaxActiveCountValue.
-
setCutMaxActiveCountValue
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];- Parameters:
value- The cutMaxActiveCountValue to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasCutActiveCountDecay
public boolean hasCutActiveCountDecay()optional double cut_active_count_decay = 156 [default = 0.8];- Specified by:
hasCutActiveCountDecayin interfaceSatParametersOrBuilder- Returns:
- Whether the cutActiveCountDecay field is set.
-
getCutActiveCountDecay
public double getCutActiveCountDecay()optional double cut_active_count_decay = 156 [default = 0.8];- Specified by:
getCutActiveCountDecayin interfaceSatParametersOrBuilder- Returns:
- The cutActiveCountDecay.
-
setCutActiveCountDecay
optional double cut_active_count_decay = 156 [default = 0.8];- Parameters:
value- The cutActiveCountDecay to set.- Returns:
- This builder for chaining.
-
clearCutActiveCountDecay
optional double cut_active_count_decay = 156 [default = 0.8];- Returns:
- This builder for chaining.
-
hasCutCleanupTarget
public boolean hasCutCleanupTarget()Target number of constraints to remove during cleanup.
optional int32 cut_cleanup_target = 157 [default = 1000];- Specified by:
hasCutCleanupTargetin interfaceSatParametersOrBuilder- Returns:
- Whether the cutCleanupTarget field is set.
-
getCutCleanupTarget
public int getCutCleanupTarget()Target number of constraints to remove during cleanup.
optional int32 cut_cleanup_target = 157 [default = 1000];- Specified by:
getCutCleanupTargetin interfaceSatParametersOrBuilder- Returns:
- The cutCleanupTarget.
-
setCutCleanupTarget
Target number of constraints to remove during cleanup.
optional int32 cut_cleanup_target = 157 [default = 1000];- Parameters:
value- The cutCleanupTarget to set.- Returns:
- This builder for chaining.
-
clearCutCleanupTarget
Target number of constraints to remove during cleanup.
optional int32 cut_cleanup_target = 157 [default = 1000];- Returns:
- This builder for chaining.
-
hasNewConstraintsBatchSize
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];- Specified by:
hasNewConstraintsBatchSizein interfaceSatParametersOrBuilder- Returns:
- Whether the newConstraintsBatchSize field is set.
-
getNewConstraintsBatchSize
public 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];- Specified by:
getNewConstraintsBatchSizein interfaceSatParametersOrBuilder- Returns:
- The newConstraintsBatchSize.
-
setNewConstraintsBatchSize
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];- Parameters:
value- The newConstraintsBatchSize to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasExploitIntegerLpSolution
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];- Specified by:
hasExploitIntegerLpSolutionin interfaceSatParametersOrBuilder- Returns:
- Whether the exploitIntegerLpSolution field is set.
-
getExploitIntegerLpSolution
public 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];- Specified by:
getExploitIntegerLpSolutionin interfaceSatParametersOrBuilder- Returns:
- The exploitIntegerLpSolution.
-
setExploitIntegerLpSolution
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];- Parameters:
value- The exploitIntegerLpSolution to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasExploitAllLpSolution
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];- Specified by:
hasExploitAllLpSolutionin interfaceSatParametersOrBuilder- Returns:
- Whether the exploitAllLpSolution field is set.
-
getExploitAllLpSolution
public 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];- Specified by:
getExploitAllLpSolutionin interfaceSatParametersOrBuilder- Returns:
- The exploitAllLpSolution.
-
setExploitAllLpSolution
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];- Parameters:
value- The exploitAllLpSolution to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasExploitBestSolution
public boolean hasExploitBestSolution()When branching on a variable, follow the last best solution value.
optional bool exploit_best_solution = 130 [default = false];- Specified by:
hasExploitBestSolutionin interfaceSatParametersOrBuilder- Returns:
- Whether the exploitBestSolution field is set.
-
getExploitBestSolution
public boolean getExploitBestSolution()When branching on a variable, follow the last best solution value.
optional bool exploit_best_solution = 130 [default = false];- Specified by:
getExploitBestSolutionin interfaceSatParametersOrBuilder- Returns:
- The exploitBestSolution.
-
setExploitBestSolution
When branching on a variable, follow the last best solution value.
optional bool exploit_best_solution = 130 [default = false];- Parameters:
value- The exploitBestSolution to set.- Returns:
- This builder for chaining.
-
clearExploitBestSolution
When branching on a variable, follow the last best solution value.
optional bool exploit_best_solution = 130 [default = false];- Returns:
- This builder for chaining.
-
hasExploitRelaxationSolution
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];- Specified by:
hasExploitRelaxationSolutionin interfaceSatParametersOrBuilder- Returns:
- Whether the exploitRelaxationSolution field is set.
-
getExploitRelaxationSolution
public 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];- Specified by:
getExploitRelaxationSolutionin interfaceSatParametersOrBuilder- Returns:
- The exploitRelaxationSolution.
-
setExploitRelaxationSolution
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];- Parameters:
value- The exploitRelaxationSolution to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasExploitObjective
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];- Specified by:
hasExploitObjectivein interfaceSatParametersOrBuilder- Returns:
- Whether the exploitObjective field is set.
-
getExploitObjective
public 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];- Specified by:
getExploitObjectivein interfaceSatParametersOrBuilder- Returns:
- The exploitObjective.
-
setExploitObjective
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];- Parameters:
value- The exploitObjective to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasDetectLinearizedProduct
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];- Specified by:
hasDetectLinearizedProductin interfaceSatParametersOrBuilder- Returns:
- Whether the detectLinearizedProduct field is set.
-
getDetectLinearizedProduct
public 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];- Specified by:
getDetectLinearizedProductin interfaceSatParametersOrBuilder- Returns:
- The detectLinearizedProduct.
-
setDetectLinearizedProduct
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];- Parameters:
value- The detectLinearizedProduct to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipMaxBound
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];- Specified by:
hasMipMaxBoundin interfaceSatParametersOrBuilder- Returns:
- Whether the mipMaxBound field is set.
-
getMipMaxBound
public 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];- Specified by:
getMipMaxBoundin interfaceSatParametersOrBuilder- Returns:
- The mipMaxBound.
-
setMipMaxBound
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];- Parameters:
value- The mipMaxBound to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipVarScaling
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];- Specified by:
hasMipVarScalingin interfaceSatParametersOrBuilder- Returns:
- Whether the mipVarScaling field is set.
-
getMipVarScaling
public 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];- Specified by:
getMipVarScalingin interfaceSatParametersOrBuilder- Returns:
- The mipVarScaling.
-
setMipVarScaling
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];- Parameters:
value- The mipVarScaling to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipScaleLargeDomain
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];- Specified by:
hasMipScaleLargeDomainin interfaceSatParametersOrBuilder- Returns:
- Whether the mipScaleLargeDomain field is set.
-
getMipScaleLargeDomain
public 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];- Specified by:
getMipScaleLargeDomainin interfaceSatParametersOrBuilder- Returns:
- The mipScaleLargeDomain.
-
setMipScaleLargeDomain
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];- Parameters:
value- The mipScaleLargeDomain to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipAutomaticallyScaleVariables
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];- Specified by:
hasMipAutomaticallyScaleVariablesin interfaceSatParametersOrBuilder- Returns:
- Whether the mipAutomaticallyScaleVariables field is set.
-
getMipAutomaticallyScaleVariables
public 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];- Specified by:
getMipAutomaticallyScaleVariablesin interfaceSatParametersOrBuilder- Returns:
- The mipAutomaticallyScaleVariables.
-
setMipAutomaticallyScaleVariables
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];- Parameters:
value- The mipAutomaticallyScaleVariables to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasOnlySolveIp
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];- Specified by:
hasOnlySolveIpin interfaceSatParametersOrBuilder- Returns:
- Whether the onlySolveIp field is set.
-
getOnlySolveIp
public 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];- Specified by:
getOnlySolveIpin interfaceSatParametersOrBuilder- Returns:
- The onlySolveIp.
-
setOnlySolveIp
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];- Parameters:
value- The onlySolveIp to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipWantedPrecision
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];- Specified by:
hasMipWantedPrecisionin interfaceSatParametersOrBuilder- Returns:
- Whether the mipWantedPrecision field is set.
-
getMipWantedPrecision
public 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];- Specified by:
getMipWantedPrecisionin interfaceSatParametersOrBuilder- Returns:
- The mipWantedPrecision.
-
setMipWantedPrecision
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];- Parameters:
value- The mipWantedPrecision to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipMaxActivityExponent
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];- Specified by:
hasMipMaxActivityExponentin interfaceSatParametersOrBuilder- Returns:
- Whether the mipMaxActivityExponent field is set.
-
getMipMaxActivityExponent
public 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];- Specified by:
getMipMaxActivityExponentin interfaceSatParametersOrBuilder- Returns:
- The mipMaxActivityExponent.
-
setMipMaxActivityExponent
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];- Parameters:
value- The mipMaxActivityExponent to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipCheckPrecision
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];- Specified by:
hasMipCheckPrecisionin interfaceSatParametersOrBuilder- Returns:
- Whether the mipCheckPrecision field is set.
-
getMipCheckPrecision
public 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];- Specified by:
getMipCheckPrecisionin interfaceSatParametersOrBuilder- Returns:
- The mipCheckPrecision.
-
setMipCheckPrecision
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];- Parameters:
value- The mipCheckPrecision to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipComputeTrueObjectiveBound
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];- Specified by:
hasMipComputeTrueObjectiveBoundin interfaceSatParametersOrBuilder- Returns:
- Whether the mipComputeTrueObjectiveBound field is set.
-
getMipComputeTrueObjectiveBound
public 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];- Specified by:
getMipComputeTrueObjectiveBoundin interfaceSatParametersOrBuilder- Returns:
- The mipComputeTrueObjectiveBound.
-
setMipComputeTrueObjectiveBound
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];- Parameters:
value- The mipComputeTrueObjectiveBound to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipMaxValidMagnitude
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];- Specified by:
hasMipMaxValidMagnitudein interfaceSatParametersOrBuilder- Returns:
- Whether the mipMaxValidMagnitude field is set.
-
getMipMaxValidMagnitude
public 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];- Specified by:
getMipMaxValidMagnitudein interfaceSatParametersOrBuilder- Returns:
- The mipMaxValidMagnitude.
-
setMipMaxValidMagnitude
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];- Parameters:
value- The mipMaxValidMagnitude to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipTreatHighMagnitudeBoundsAsInfinity
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];- Specified by:
hasMipTreatHighMagnitudeBoundsAsInfinityin interfaceSatParametersOrBuilder- Returns:
- Whether the mipTreatHighMagnitudeBoundsAsInfinity field is set.
-
getMipTreatHighMagnitudeBoundsAsInfinity
public 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];- Specified by:
getMipTreatHighMagnitudeBoundsAsInfinityin interfaceSatParametersOrBuilder- Returns:
- The mipTreatHighMagnitudeBoundsAsInfinity.
-
setMipTreatHighMagnitudeBoundsAsInfinity
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];- Parameters:
value- The mipTreatHighMagnitudeBoundsAsInfinity to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipDropTolerance
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];- Specified by:
hasMipDropTolerancein interfaceSatParametersOrBuilder- Returns:
- Whether the mipDropTolerance field is set.
-
getMipDropTolerance
public 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];- Specified by:
getMipDropTolerancein interfaceSatParametersOrBuilder- Returns:
- The mipDropTolerance.
-
setMipDropTolerance
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];- Parameters:
value- The mipDropTolerance to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-
hasMipPresolveLevel
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];- Specified by:
hasMipPresolveLevelin interfaceSatParametersOrBuilder- Returns:
- Whether the mipPresolveLevel field is set.
-
getMipPresolveLevel
public 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];- Specified by:
getMipPresolveLevelin interfaceSatParametersOrBuilder- Returns:
- The mipPresolveLevel.
-
setMipPresolveLevel
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];- Parameters:
value- The mipPresolveLevel to set.- Returns:
- This builder for chaining.
-
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];- Returns:
- This builder for chaining.
-