Class ConstraintProto.Builder
java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<ConstraintProto.Builder>
com.google.protobuf.GeneratedMessage.Builder<ConstraintProto.Builder>
com.google.ortools.sat.ConstraintProto.Builder
- All Implemented Interfaces:
ConstraintProtoOrBuilder
,com.google.protobuf.Message.Builder
,com.google.protobuf.MessageLite.Builder
,com.google.protobuf.MessageLiteOrBuilder
,com.google.protobuf.MessageOrBuilder
,Cloneable
- Enclosing class:
ConstraintProto
public static final class ConstraintProto.Builder
extends com.google.protobuf.GeneratedMessage.Builder<ConstraintProto.Builder>
implements ConstraintProtoOrBuilder
Next id: 31Protobuf type
operations_research.sat.ConstraintProto
-
Method Summary
Modifier and TypeMethodDescriptionaddAllEnforcementLiteral
(Iterable<? extends Integer> values) The constraint will be enforced iff all literals listed here are true.addEnforcementLiteral
(int value) The constraint will be enforced iff all literals listed here are true.build()
clear()
The all_diff constraint forces all variables to take different values.The at_most_one constraint enforces that no more than one literal is true at the same time.The automaton constraint forces a sequence of variables to be accepted by an automaton.The bool_and constraint forces all of the literals to be true.The bool_or constraint forces at least one literal to be true.The bool_xor constraint forces an odd number of the literals to be true.The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.This constraint is not meant to be used and will be rejected by the solver.The element constraint forces the variable with the given index to be equal to the target.The constraint will be enforced iff all literals listed here are true.The exactly_one constraint force exactly one literal to true and no more.The int_div constraint forces the target to equal exprs[0] / exprs[1].The interval constraint takes a start, end, and size, and forces start + size == end.The int_mod constraint forces the target to equal exprs[0] % exprs[1].The int_prod constraint forces the target to equal the product of all variables.The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.The lin_max constraint forces the target to equal the maximum of all linear expressions.For debug/logging only.The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.The no_overlap_2d constraint prevents a set of boxes from overlapping.The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.The routes constraint implements the vehicle routing problem.The table constraint enforces what values a tuple of variables may take.The all_diff constraint forces all variables to take different values.The all_diff constraint forces all variables to take different values.The all_diff constraint forces all variables to take different values.The at_most_one constraint enforces that no more than one literal is true at the same time.The at_most_one constraint enforces that no more than one literal is true at the same time.The at_most_one constraint enforces that no more than one literal is true at the same time.The automaton constraint forces a sequence of variables to be accepted by an automaton.The automaton constraint forces a sequence of variables to be accepted by an automaton.The automaton constraint forces a sequence of variables to be accepted by an automaton.The bool_and constraint forces all of the literals to be true.The bool_and constraint forces all of the literals to be true.The bool_and constraint forces all of the literals to be true.The bool_or constraint forces at least one literal to be true.The bool_or constraint forces at least one literal to be true.The bool_or constraint forces at least one literal to be true.The bool_xor constraint forces an odd number of the literals to be true.The bool_xor constraint forces an odd number of the literals to be true.The bool_xor constraint forces an odd number of the literals to be true.The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.static final com.google.protobuf.Descriptors.Descriptor
com.google.protobuf.Descriptors.Descriptor
This constraint is not meant to be used and will be rejected by the solver.This constraint is not meant to be used and will be rejected by the solver.This constraint is not meant to be used and will be rejected by the solver.The element constraint forces the variable with the given index to be equal to the target.The element constraint forces the variable with the given index to be equal to the target.The element constraint forces the variable with the given index to be equal to the target.int
getEnforcementLiteral
(int index) The constraint will be enforced iff all literals listed here are true.int
The constraint will be enforced iff all literals listed here are true.The constraint will be enforced iff all literals listed here are true.The exactly_one constraint force exactly one literal to true and no more.The exactly_one constraint force exactly one literal to true and no more.The exactly_one constraint force exactly one literal to true and no more.The int_div constraint forces the target to equal exprs[0] / exprs[1].The int_div constraint forces the target to equal exprs[0] / exprs[1].The int_div constraint forces the target to equal exprs[0] / exprs[1].The interval constraint takes a start, end, and size, and forces start + size == end.The interval constraint takes a start, end, and size, and forces start + size == end.The interval constraint takes a start, end, and size, and forces start + size == end.The int_mod constraint forces the target to equal exprs[0] % exprs[1].The int_mod constraint forces the target to equal exprs[0] % exprs[1].The int_mod constraint forces the target to equal exprs[0] % exprs[1].The int_prod constraint forces the target to equal the product of all variables.The int_prod constraint forces the target to equal the product of all variables.The int_prod constraint forces the target to equal the product of all variables.The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.The lin_max constraint forces the target to equal the maximum of all linear expressions.The lin_max constraint forces the target to equal the maximum of all linear expressions.The lin_max constraint forces the target to equal the maximum of all linear expressions.getName()
For debug/logging only.com.google.protobuf.ByteString
For debug/logging only.The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.The no_overlap_2d constraint prevents a set of boxes from overlapping.The no_overlap_2d constraint prevents a set of boxes from overlapping.The no_overlap_2d constraint prevents a set of boxes from overlapping.The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.The routes constraint implements the vehicle routing problem.The routes constraint implements the vehicle routing problem.The routes constraint implements the vehicle routing problem.getTable()
The table constraint enforces what values a tuple of variables may take.The table constraint enforces what values a tuple of variables may take.The table constraint enforces what values a tuple of variables may take.boolean
The all_diff constraint forces all variables to take different values.boolean
The at_most_one constraint enforces that no more than one literal is true at the same time.boolean
The automaton constraint forces a sequence of variables to be accepted by an automaton.boolean
The bool_and constraint forces all of the literals to be true.boolean
The bool_or constraint forces at least one literal to be true.boolean
The bool_xor constraint forces an odd number of the literals to be true.boolean
The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.boolean
The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.boolean
This constraint is not meant to be used and will be rejected by the solver.boolean
The element constraint forces the variable with the given index to be equal to the target.boolean
The exactly_one constraint force exactly one literal to true and no more.boolean
The int_div constraint forces the target to equal exprs[0] / exprs[1].boolean
The interval constraint takes a start, end, and size, and forces start + size == end.boolean
The int_mod constraint forces the target to equal exprs[0] % exprs[1].boolean
The int_prod constraint forces the target to equal the product of all variables.boolean
The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.boolean
The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.boolean
The lin_max constraint forces the target to equal the maximum of all linear expressions.boolean
The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.boolean
The no_overlap_2d constraint prevents a set of boxes from overlapping.boolean
The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.boolean
The routes constraint implements the vehicle routing problem.boolean
hasTable()
The table constraint enforces what values a tuple of variables may take.protected com.google.protobuf.GeneratedMessage.FieldAccessorTable
final boolean
The all_diff constraint forces all variables to take different values.mergeAtMostOne
(BoolArgumentProto value) The at_most_one constraint enforces that no more than one literal is true at the same time.The automaton constraint forces a sequence of variables to be accepted by an automaton.mergeBoolAnd
(BoolArgumentProto value) The bool_and constraint forces all of the literals to be true.mergeBoolOr
(BoolArgumentProto value) The bool_or constraint forces at least one literal to be true.mergeBoolXor
(BoolArgumentProto value) The bool_xor constraint forces an odd number of the literals to be true.The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.This constraint is not meant to be used and will be rejected by the solver.The element constraint forces the variable with the given index to be equal to the target.mergeExactlyOne
(BoolArgumentProto value) The exactly_one constraint force exactly one literal to true and no more.mergeFrom
(ConstraintProto other) mergeFrom
(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) mergeFrom
(com.google.protobuf.Message other) mergeIntDiv
(LinearArgumentProto value) The int_div constraint forces the target to equal exprs[0] / exprs[1].The interval constraint takes a start, end, and size, and forces start + size == end.mergeIntMod
(LinearArgumentProto value) The int_mod constraint forces the target to equal exprs[0] % exprs[1].mergeIntProd
(LinearArgumentProto value) The int_prod constraint forces the target to equal the product of all variables.The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.mergeLinear
(LinearConstraintProto value) The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.mergeLinMax
(LinearArgumentProto value) The lin_max constraint forces the target to equal the maximum of all linear expressions.The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.The no_overlap_2d constraint prevents a set of boxes from overlapping.The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.mergeRoutes
(RoutesConstraintProto value) The routes constraint implements the vehicle routing problem.mergeTable
(TableConstraintProto value) The table constraint enforces what values a tuple of variables may take.The all_diff constraint forces all variables to take different values.setAllDiff
(AllDifferentConstraintProto.Builder builderForValue) The all_diff constraint forces all variables to take different values.setAtMostOne
(BoolArgumentProto value) The at_most_one constraint enforces that no more than one literal is true at the same time.setAtMostOne
(BoolArgumentProto.Builder builderForValue) The at_most_one constraint enforces that no more than one literal is true at the same time.The automaton constraint forces a sequence of variables to be accepted by an automaton.setAutomaton
(AutomatonConstraintProto.Builder builderForValue) The automaton constraint forces a sequence of variables to be accepted by an automaton.setBoolAnd
(BoolArgumentProto value) The bool_and constraint forces all of the literals to be true.setBoolAnd
(BoolArgumentProto.Builder builderForValue) The bool_and constraint forces all of the literals to be true.setBoolOr
(BoolArgumentProto value) The bool_or constraint forces at least one literal to be true.setBoolOr
(BoolArgumentProto.Builder builderForValue) The bool_or constraint forces at least one literal to be true.setBoolXor
(BoolArgumentProto value) The bool_xor constraint forces an odd number of the literals to be true.setBoolXor
(BoolArgumentProto.Builder builderForValue) The bool_xor constraint forces an odd number of the literals to be true.setCircuit
(CircuitConstraintProto value) The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.setCircuit
(CircuitConstraintProto.Builder builderForValue) The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.setCumulative
(CumulativeConstraintProto.Builder builderForValue) The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.This constraint is not meant to be used and will be rejected by the solver.setDummyConstraint
(ListOfVariablesProto.Builder builderForValue) This constraint is not meant to be used and will be rejected by the solver.setElement
(ElementConstraintProto value) The element constraint forces the variable with the given index to be equal to the target.setElement
(ElementConstraintProto.Builder builderForValue) The element constraint forces the variable with the given index to be equal to the target.setEnforcementLiteral
(int index, int value) The constraint will be enforced iff all literals listed here are true.setExactlyOne
(BoolArgumentProto value) The exactly_one constraint force exactly one literal to true and no more.setExactlyOne
(BoolArgumentProto.Builder builderForValue) The exactly_one constraint force exactly one literal to true and no more.setIntDiv
(LinearArgumentProto value) The int_div constraint forces the target to equal exprs[0] / exprs[1].setIntDiv
(LinearArgumentProto.Builder builderForValue) The int_div constraint forces the target to equal exprs[0] / exprs[1].The interval constraint takes a start, end, and size, and forces start + size == end.setInterval
(IntervalConstraintProto.Builder builderForValue) The interval constraint takes a start, end, and size, and forces start + size == end.setIntMod
(LinearArgumentProto value) The int_mod constraint forces the target to equal exprs[0] % exprs[1].setIntMod
(LinearArgumentProto.Builder builderForValue) The int_mod constraint forces the target to equal exprs[0] % exprs[1].setIntProd
(LinearArgumentProto value) The int_prod constraint forces the target to equal the product of all variables.setIntProd
(LinearArgumentProto.Builder builderForValue) The int_prod constraint forces the target to equal the product of all variables.setInverse
(InverseConstraintProto value) The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.setInverse
(InverseConstraintProto.Builder builderForValue) The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.setLinear
(LinearConstraintProto value) The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.setLinear
(LinearConstraintProto.Builder builderForValue) The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.setLinMax
(LinearArgumentProto value) The lin_max constraint forces the target to equal the maximum of all linear expressions.setLinMax
(LinearArgumentProto.Builder builderForValue) The lin_max constraint forces the target to equal the maximum of all linear expressions.For debug/logging only.setNameBytes
(com.google.protobuf.ByteString value) For debug/logging only.The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.setNoOverlap
(NoOverlapConstraintProto.Builder builderForValue) The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.The no_overlap_2d constraint prevents a set of boxes from overlapping.setNoOverlap2D
(NoOverlap2DConstraintProto.Builder builderForValue) The no_overlap_2d constraint prevents a set of boxes from overlapping.The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.setReservoir
(ReservoirConstraintProto.Builder builderForValue) The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.setRoutes
(RoutesConstraintProto value) The routes constraint implements the vehicle routing problem.setRoutes
(RoutesConstraintProto.Builder builderForValue) The routes constraint implements the vehicle routing problem.setTable
(TableConstraintProto value) The table constraint enforces what values a tuple of variables may take.setTable
(TableConstraintProto.Builder builderForValue) The table constraint enforces what values a tuple of variables may take.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, setUnknownFieldsProto3
Methods inherited from class com.google.protobuf.AbstractMessage.Builder
findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toString
Methods inherited from class com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageException
Methods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
Methods inherited from interface com.google.protobuf.Message.Builder
mergeDelimitedFrom, mergeDelimitedFrom
Methods inherited from interface com.google.protobuf.MessageLite.Builder
mergeFrom
Methods 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:
internalGetFieldAccessorTable
in classcom.google.protobuf.GeneratedMessage.Builder<ConstraintProto.Builder>
-
clear
- Specified by:
clear
in interfacecom.google.protobuf.Message.Builder
- Specified by:
clear
in interfacecom.google.protobuf.MessageLite.Builder
- Overrides:
clear
in classcom.google.protobuf.GeneratedMessage.Builder<ConstraintProto.Builder>
-
getDescriptorForType
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()- Specified by:
getDescriptorForType
in interfacecom.google.protobuf.Message.Builder
- Specified by:
getDescriptorForType
in interfacecom.google.protobuf.MessageOrBuilder
- Overrides:
getDescriptorForType
in classcom.google.protobuf.GeneratedMessage.Builder<ConstraintProto.Builder>
-
getDefaultInstanceForType
- Specified by:
getDefaultInstanceForType
in interfacecom.google.protobuf.MessageLiteOrBuilder
- Specified by:
getDefaultInstanceForType
in interfacecom.google.protobuf.MessageOrBuilder
-
build
- Specified by:
build
in interfacecom.google.protobuf.Message.Builder
- Specified by:
build
in interfacecom.google.protobuf.MessageLite.Builder
-
buildPartial
- Specified by:
buildPartial
in interfacecom.google.protobuf.Message.Builder
- Specified by:
buildPartial
in interfacecom.google.protobuf.MessageLite.Builder
-
mergeFrom
- Specified by:
mergeFrom
in interfacecom.google.protobuf.Message.Builder
- Overrides:
mergeFrom
in classcom.google.protobuf.AbstractMessage.Builder<ConstraintProto.Builder>
-
mergeFrom
-
isInitialized
public final boolean isInitialized()- Specified by:
isInitialized
in interfacecom.google.protobuf.MessageLiteOrBuilder
- Overrides:
isInitialized
in classcom.google.protobuf.GeneratedMessage.Builder<ConstraintProto.Builder>
-
mergeFrom
public ConstraintProto.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException - Specified by:
mergeFrom
in interfacecom.google.protobuf.Message.Builder
- Specified by:
mergeFrom
in interfacecom.google.protobuf.MessageLite.Builder
- Overrides:
mergeFrom
in classcom.google.protobuf.AbstractMessage.Builder<ConstraintProto.Builder>
- Throws:
IOException
-
getConstraintCase
- Specified by:
getConstraintCase
in interfaceConstraintProtoOrBuilder
-
clearConstraint
-
getName
For debug/logging only. Can be empty.
string name = 1;
- Specified by:
getName
in interfaceConstraintProtoOrBuilder
- Returns:
- The name.
-
getNameBytes
public com.google.protobuf.ByteString getNameBytes()For debug/logging only. Can be empty.
string name = 1;
- Specified by:
getNameBytes
in interfaceConstraintProtoOrBuilder
- Returns:
- The bytes for name.
-
setName
For debug/logging only. Can be empty.
string name = 1;
- Parameters:
value
- The name to set.- Returns:
- This builder for chaining.
-
clearName
For debug/logging only. Can be empty.
string name = 1;
- Returns:
- This builder for chaining.
-
setNameBytes
For debug/logging only. Can be empty.
string name = 1;
- Parameters:
value
- The bytes for name to set.- Returns:
- This builder for chaining.
-
getEnforcementLiteralList
The constraint will be enforced iff all literals listed here are true. If this is empty, then the constraint will always be enforced. An enforced constraint must be satisfied, and an un-enforced one will simply be ignored. This is also called half-reification. To have an equivalence between a literal and a constraint (full reification), one must add both a constraint (controlled by a literal l) and its negation (controlled by the negation of l). Important: as of September 2018, only a few constraint support enforcement: - bool_or, bool_and, linear: fully supported. - interval: only support a single enforcement literal. - other: no support (but can be added on a per-demand basis).
repeated int32 enforcement_literal = 2;
- Specified by:
getEnforcementLiteralList
in interfaceConstraintProtoOrBuilder
- Returns:
- A list containing the enforcementLiteral.
-
getEnforcementLiteralCount
public int getEnforcementLiteralCount()The constraint will be enforced iff all literals listed here are true. If this is empty, then the constraint will always be enforced. An enforced constraint must be satisfied, and an un-enforced one will simply be ignored. This is also called half-reification. To have an equivalence between a literal and a constraint (full reification), one must add both a constraint (controlled by a literal l) and its negation (controlled by the negation of l). Important: as of September 2018, only a few constraint support enforcement: - bool_or, bool_and, linear: fully supported. - interval: only support a single enforcement literal. - other: no support (but can be added on a per-demand basis).
repeated int32 enforcement_literal = 2;
- Specified by:
getEnforcementLiteralCount
in interfaceConstraintProtoOrBuilder
- Returns:
- The count of enforcementLiteral.
-
getEnforcementLiteral
public int getEnforcementLiteral(int index) The constraint will be enforced iff all literals listed here are true. If this is empty, then the constraint will always be enforced. An enforced constraint must be satisfied, and an un-enforced one will simply be ignored. This is also called half-reification. To have an equivalence between a literal and a constraint (full reification), one must add both a constraint (controlled by a literal l) and its negation (controlled by the negation of l). Important: as of September 2018, only a few constraint support enforcement: - bool_or, bool_and, linear: fully supported. - interval: only support a single enforcement literal. - other: no support (but can be added on a per-demand basis).
repeated int32 enforcement_literal = 2;
- Specified by:
getEnforcementLiteral
in interfaceConstraintProtoOrBuilder
- Parameters:
index
- The index of the element to return.- Returns:
- The enforcementLiteral at the given index.
-
setEnforcementLiteral
The constraint will be enforced iff all literals listed here are true. If this is empty, then the constraint will always be enforced. An enforced constraint must be satisfied, and an un-enforced one will simply be ignored. This is also called half-reification. To have an equivalence between a literal and a constraint (full reification), one must add both a constraint (controlled by a literal l) and its negation (controlled by the negation of l). Important: as of September 2018, only a few constraint support enforcement: - bool_or, bool_and, linear: fully supported. - interval: only support a single enforcement literal. - other: no support (but can be added on a per-demand basis).
repeated int32 enforcement_literal = 2;
- Parameters:
index
- The index to set the value at.value
- The enforcementLiteral to set.- Returns:
- This builder for chaining.
-
addEnforcementLiteral
The constraint will be enforced iff all literals listed here are true. If this is empty, then the constraint will always be enforced. An enforced constraint must be satisfied, and an un-enforced one will simply be ignored. This is also called half-reification. To have an equivalence between a literal and a constraint (full reification), one must add both a constraint (controlled by a literal l) and its negation (controlled by the negation of l). Important: as of September 2018, only a few constraint support enforcement: - bool_or, bool_and, linear: fully supported. - interval: only support a single enforcement literal. - other: no support (but can be added on a per-demand basis).
repeated int32 enforcement_literal = 2;
- Parameters:
value
- The enforcementLiteral to add.- Returns:
- This builder for chaining.
-
addAllEnforcementLiteral
The constraint will be enforced iff all literals listed here are true. If this is empty, then the constraint will always be enforced. An enforced constraint must be satisfied, and an un-enforced one will simply be ignored. This is also called half-reification. To have an equivalence between a literal and a constraint (full reification), one must add both a constraint (controlled by a literal l) and its negation (controlled by the negation of l). Important: as of September 2018, only a few constraint support enforcement: - bool_or, bool_and, linear: fully supported. - interval: only support a single enforcement literal. - other: no support (but can be added on a per-demand basis).
repeated int32 enforcement_literal = 2;
- Parameters:
values
- The enforcementLiteral to add.- Returns:
- This builder for chaining.
-
clearEnforcementLiteral
The constraint will be enforced iff all literals listed here are true. If this is empty, then the constraint will always be enforced. An enforced constraint must be satisfied, and an un-enforced one will simply be ignored. This is also called half-reification. To have an equivalence between a literal and a constraint (full reification), one must add both a constraint (controlled by a literal l) and its negation (controlled by the negation of l). Important: as of September 2018, only a few constraint support enforcement: - bool_or, bool_and, linear: fully supported. - interval: only support a single enforcement literal. - other: no support (but can be added on a per-demand basis).
repeated int32 enforcement_literal = 2;
- Returns:
- This builder for chaining.
-
hasBoolOr
public boolean hasBoolOr()The bool_or constraint forces at least one literal to be true.
.operations_research.sat.BoolArgumentProto bool_or = 3;
- Specified by:
hasBoolOr
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the boolOr field is set.
-
getBoolOr
The bool_or constraint forces at least one literal to be true.
.operations_research.sat.BoolArgumentProto bool_or = 3;
- Specified by:
getBoolOr
in interfaceConstraintProtoOrBuilder
- Returns:
- The boolOr.
-
setBoolOr
The bool_or constraint forces at least one literal to be true.
.operations_research.sat.BoolArgumentProto bool_or = 3;
-
setBoolOr
The bool_or constraint forces at least one literal to be true.
.operations_research.sat.BoolArgumentProto bool_or = 3;
-
mergeBoolOr
The bool_or constraint forces at least one literal to be true.
.operations_research.sat.BoolArgumentProto bool_or = 3;
-
clearBoolOr
The bool_or constraint forces at least one literal to be true.
.operations_research.sat.BoolArgumentProto bool_or = 3;
-
getBoolOrBuilder
The bool_or constraint forces at least one literal to be true.
.operations_research.sat.BoolArgumentProto bool_or = 3;
-
getBoolOrOrBuilder
The bool_or constraint forces at least one literal to be true.
.operations_research.sat.BoolArgumentProto bool_or = 3;
- Specified by:
getBoolOrOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasBoolAnd
public boolean hasBoolAnd()The bool_and constraint forces all of the literals to be true. This is a "redundant" constraint in the sense that this can easily be encoded with many bool_or or at_most_one. It is just more space efficient and handled slightly differently internally.
.operations_research.sat.BoolArgumentProto bool_and = 4;
- Specified by:
hasBoolAnd
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the boolAnd field is set.
-
getBoolAnd
The bool_and constraint forces all of the literals to be true. This is a "redundant" constraint in the sense that this can easily be encoded with many bool_or or at_most_one. It is just more space efficient and handled slightly differently internally.
.operations_research.sat.BoolArgumentProto bool_and = 4;
- Specified by:
getBoolAnd
in interfaceConstraintProtoOrBuilder
- Returns:
- The boolAnd.
-
setBoolAnd
The bool_and constraint forces all of the literals to be true. This is a "redundant" constraint in the sense that this can easily be encoded with many bool_or or at_most_one. It is just more space efficient and handled slightly differently internally.
.operations_research.sat.BoolArgumentProto bool_and = 4;
-
setBoolAnd
The bool_and constraint forces all of the literals to be true. This is a "redundant" constraint in the sense that this can easily be encoded with many bool_or or at_most_one. It is just more space efficient and handled slightly differently internally.
.operations_research.sat.BoolArgumentProto bool_and = 4;
-
mergeBoolAnd
The bool_and constraint forces all of the literals to be true. This is a "redundant" constraint in the sense that this can easily be encoded with many bool_or or at_most_one. It is just more space efficient and handled slightly differently internally.
.operations_research.sat.BoolArgumentProto bool_and = 4;
-
clearBoolAnd
The bool_and constraint forces all of the literals to be true. This is a "redundant" constraint in the sense that this can easily be encoded with many bool_or or at_most_one. It is just more space efficient and handled slightly differently internally.
.operations_research.sat.BoolArgumentProto bool_and = 4;
-
getBoolAndBuilder
The bool_and constraint forces all of the literals to be true. This is a "redundant" constraint in the sense that this can easily be encoded with many bool_or or at_most_one. It is just more space efficient and handled slightly differently internally.
.operations_research.sat.BoolArgumentProto bool_and = 4;
-
getBoolAndOrBuilder
The bool_and constraint forces all of the literals to be true. This is a "redundant" constraint in the sense that this can easily be encoded with many bool_or or at_most_one. It is just more space efficient and handled slightly differently internally.
.operations_research.sat.BoolArgumentProto bool_and = 4;
- Specified by:
getBoolAndOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasAtMostOne
public boolean hasAtMostOne()The at_most_one constraint enforces that no more than one literal is true at the same time. Note that an at most one constraint of length n could be encoded with n bool_and constraint with n-1 term on the right hand side. So in a sense, this constraint contribute directly to the "implication-graph" or the 2-SAT part of the model. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto at_most_one = 26;
- Specified by:
hasAtMostOne
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the atMostOne field is set.
-
getAtMostOne
The at_most_one constraint enforces that no more than one literal is true at the same time. Note that an at most one constraint of length n could be encoded with n bool_and constraint with n-1 term on the right hand side. So in a sense, this constraint contribute directly to the "implication-graph" or the 2-SAT part of the model. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto at_most_one = 26;
- Specified by:
getAtMostOne
in interfaceConstraintProtoOrBuilder
- Returns:
- The atMostOne.
-
setAtMostOne
The at_most_one constraint enforces that no more than one literal is true at the same time. Note that an at most one constraint of length n could be encoded with n bool_and constraint with n-1 term on the right hand side. So in a sense, this constraint contribute directly to the "implication-graph" or the 2-SAT part of the model. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto at_most_one = 26;
-
setAtMostOne
The at_most_one constraint enforces that no more than one literal is true at the same time. Note that an at most one constraint of length n could be encoded with n bool_and constraint with n-1 term on the right hand side. So in a sense, this constraint contribute directly to the "implication-graph" or the 2-SAT part of the model. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto at_most_one = 26;
-
mergeAtMostOne
The at_most_one constraint enforces that no more than one literal is true at the same time. Note that an at most one constraint of length n could be encoded with n bool_and constraint with n-1 term on the right hand side. So in a sense, this constraint contribute directly to the "implication-graph" or the 2-SAT part of the model. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto at_most_one = 26;
-
clearAtMostOne
The at_most_one constraint enforces that no more than one literal is true at the same time. Note that an at most one constraint of length n could be encoded with n bool_and constraint with n-1 term on the right hand side. So in a sense, this constraint contribute directly to the "implication-graph" or the 2-SAT part of the model. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto at_most_one = 26;
-
getAtMostOneBuilder
The at_most_one constraint enforces that no more than one literal is true at the same time. Note that an at most one constraint of length n could be encoded with n bool_and constraint with n-1 term on the right hand side. So in a sense, this constraint contribute directly to the "implication-graph" or the 2-SAT part of the model. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto at_most_one = 26;
-
getAtMostOneOrBuilder
The at_most_one constraint enforces that no more than one literal is true at the same time. Note that an at most one constraint of length n could be encoded with n bool_and constraint with n-1 term on the right hand side. So in a sense, this constraint contribute directly to the "implication-graph" or the 2-SAT part of the model. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto at_most_one = 26;
- Specified by:
getAtMostOneOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasExactlyOne
public boolean hasExactlyOne()The exactly_one constraint force exactly one literal to true and no more. Anytime a bool_or (it could have been called at_least_one) is included into an at_most_one, then the bool_or is actually an exactly one constraint, and the extra literal in the at_most_one can be set to false. So in this sense, this constraint is not really needed. it is just here for a better description of the problem structure and to facilitate some algorithm. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto exactly_one = 29;
- Specified by:
hasExactlyOne
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the exactlyOne field is set.
-
getExactlyOne
The exactly_one constraint force exactly one literal to true and no more. Anytime a bool_or (it could have been called at_least_one) is included into an at_most_one, then the bool_or is actually an exactly one constraint, and the extra literal in the at_most_one can be set to false. So in this sense, this constraint is not really needed. it is just here for a better description of the problem structure and to facilitate some algorithm. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto exactly_one = 29;
- Specified by:
getExactlyOne
in interfaceConstraintProtoOrBuilder
- Returns:
- The exactlyOne.
-
setExactlyOne
The exactly_one constraint force exactly one literal to true and no more. Anytime a bool_or (it could have been called at_least_one) is included into an at_most_one, then the bool_or is actually an exactly one constraint, and the extra literal in the at_most_one can be set to false. So in this sense, this constraint is not really needed. it is just here for a better description of the problem structure and to facilitate some algorithm. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto exactly_one = 29;
-
setExactlyOne
The exactly_one constraint force exactly one literal to true and no more. Anytime a bool_or (it could have been called at_least_one) is included into an at_most_one, then the bool_or is actually an exactly one constraint, and the extra literal in the at_most_one can be set to false. So in this sense, this constraint is not really needed. it is just here for a better description of the problem structure and to facilitate some algorithm. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto exactly_one = 29;
-
mergeExactlyOne
The exactly_one constraint force exactly one literal to true and no more. Anytime a bool_or (it could have been called at_least_one) is included into an at_most_one, then the bool_or is actually an exactly one constraint, and the extra literal in the at_most_one can be set to false. So in this sense, this constraint is not really needed. it is just here for a better description of the problem structure and to facilitate some algorithm. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto exactly_one = 29;
-
clearExactlyOne
The exactly_one constraint force exactly one literal to true and no more. Anytime a bool_or (it could have been called at_least_one) is included into an at_most_one, then the bool_or is actually an exactly one constraint, and the extra literal in the at_most_one can be set to false. So in this sense, this constraint is not really needed. it is just here for a better description of the problem structure and to facilitate some algorithm. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto exactly_one = 29;
-
getExactlyOneBuilder
The exactly_one constraint force exactly one literal to true and no more. Anytime a bool_or (it could have been called at_least_one) is included into an at_most_one, then the bool_or is actually an exactly one constraint, and the extra literal in the at_most_one can be set to false. So in this sense, this constraint is not really needed. it is just here for a better description of the problem structure and to facilitate some algorithm. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto exactly_one = 29;
-
getExactlyOneOrBuilder
The exactly_one constraint force exactly one literal to true and no more. Anytime a bool_or (it could have been called at_least_one) is included into an at_most_one, then the bool_or is actually an exactly one constraint, and the extra literal in the at_most_one can be set to false. So in this sense, this constraint is not really needed. it is just here for a better description of the problem structure and to facilitate some algorithm. This constraint does not support enforcement_literal. Just use a linear constraint if you need to enforce it. You also do not need to use it directly, we will extract it from the model in most situations.
.operations_research.sat.BoolArgumentProto exactly_one = 29;
- Specified by:
getExactlyOneOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasBoolXor
public boolean hasBoolXor()The bool_xor constraint forces an odd number of the literals to be true.
.operations_research.sat.BoolArgumentProto bool_xor = 5;
- Specified by:
hasBoolXor
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the boolXor field is set.
-
getBoolXor
The bool_xor constraint forces an odd number of the literals to be true.
.operations_research.sat.BoolArgumentProto bool_xor = 5;
- Specified by:
getBoolXor
in interfaceConstraintProtoOrBuilder
- Returns:
- The boolXor.
-
setBoolXor
The bool_xor constraint forces an odd number of the literals to be true.
.operations_research.sat.BoolArgumentProto bool_xor = 5;
-
setBoolXor
The bool_xor constraint forces an odd number of the literals to be true.
.operations_research.sat.BoolArgumentProto bool_xor = 5;
-
mergeBoolXor
The bool_xor constraint forces an odd number of the literals to be true.
.operations_research.sat.BoolArgumentProto bool_xor = 5;
-
clearBoolXor
The bool_xor constraint forces an odd number of the literals to be true.
.operations_research.sat.BoolArgumentProto bool_xor = 5;
-
getBoolXorBuilder
The bool_xor constraint forces an odd number of the literals to be true.
.operations_research.sat.BoolArgumentProto bool_xor = 5;
-
getBoolXorOrBuilder
The bool_xor constraint forces an odd number of the literals to be true.
.operations_research.sat.BoolArgumentProto bool_xor = 5;
- Specified by:
getBoolXorOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasIntDiv
public boolean hasIntDiv()The int_div constraint forces the target to equal exprs[0] / exprs[1]. The division is "rounded" towards zero, so we can have for instance (2 = 12 / 5) or (-3 = -10 / 3). If you only want exact integer division, then you should use instead of t = a / b, the int_prod constraint a = b * t. If 0 belongs to the domain of exprs[1], then the model is deemed invalid.
.operations_research.sat.LinearArgumentProto int_div = 7;
- Specified by:
hasIntDiv
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the intDiv field is set.
-
getIntDiv
The int_div constraint forces the target to equal exprs[0] / exprs[1]. The division is "rounded" towards zero, so we can have for instance (2 = 12 / 5) or (-3 = -10 / 3). If you only want exact integer division, then you should use instead of t = a / b, the int_prod constraint a = b * t. If 0 belongs to the domain of exprs[1], then the model is deemed invalid.
.operations_research.sat.LinearArgumentProto int_div = 7;
- Specified by:
getIntDiv
in interfaceConstraintProtoOrBuilder
- Returns:
- The intDiv.
-
setIntDiv
The int_div constraint forces the target to equal exprs[0] / exprs[1]. The division is "rounded" towards zero, so we can have for instance (2 = 12 / 5) or (-3 = -10 / 3). If you only want exact integer division, then you should use instead of t = a / b, the int_prod constraint a = b * t. If 0 belongs to the domain of exprs[1], then the model is deemed invalid.
.operations_research.sat.LinearArgumentProto int_div = 7;
-
setIntDiv
The int_div constraint forces the target to equal exprs[0] / exprs[1]. The division is "rounded" towards zero, so we can have for instance (2 = 12 / 5) or (-3 = -10 / 3). If you only want exact integer division, then you should use instead of t = a / b, the int_prod constraint a = b * t. If 0 belongs to the domain of exprs[1], then the model is deemed invalid.
.operations_research.sat.LinearArgumentProto int_div = 7;
-
mergeIntDiv
The int_div constraint forces the target to equal exprs[0] / exprs[1]. The division is "rounded" towards zero, so we can have for instance (2 = 12 / 5) or (-3 = -10 / 3). If you only want exact integer division, then you should use instead of t = a / b, the int_prod constraint a = b * t. If 0 belongs to the domain of exprs[1], then the model is deemed invalid.
.operations_research.sat.LinearArgumentProto int_div = 7;
-
clearIntDiv
The int_div constraint forces the target to equal exprs[0] / exprs[1]. The division is "rounded" towards zero, so we can have for instance (2 = 12 / 5) or (-3 = -10 / 3). If you only want exact integer division, then you should use instead of t = a / b, the int_prod constraint a = b * t. If 0 belongs to the domain of exprs[1], then the model is deemed invalid.
.operations_research.sat.LinearArgumentProto int_div = 7;
-
getIntDivBuilder
The int_div constraint forces the target to equal exprs[0] / exprs[1]. The division is "rounded" towards zero, so we can have for instance (2 = 12 / 5) or (-3 = -10 / 3). If you only want exact integer division, then you should use instead of t = a / b, the int_prod constraint a = b * t. If 0 belongs to the domain of exprs[1], then the model is deemed invalid.
.operations_research.sat.LinearArgumentProto int_div = 7;
-
getIntDivOrBuilder
The int_div constraint forces the target to equal exprs[0] / exprs[1]. The division is "rounded" towards zero, so we can have for instance (2 = 12 / 5) or (-3 = -10 / 3). If you only want exact integer division, then you should use instead of t = a / b, the int_prod constraint a = b * t. If 0 belongs to the domain of exprs[1], then the model is deemed invalid.
.operations_research.sat.LinearArgumentProto int_div = 7;
- Specified by:
getIntDivOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasIntMod
public boolean hasIntMod()The int_mod constraint forces the target to equal exprs[0] % exprs[1]. The domain of exprs[1] must be strictly positive. The sign of the target is the same as the sign of exprs[0].
.operations_research.sat.LinearArgumentProto int_mod = 8;
- Specified by:
hasIntMod
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the intMod field is set.
-
getIntMod
The int_mod constraint forces the target to equal exprs[0] % exprs[1]. The domain of exprs[1] must be strictly positive. The sign of the target is the same as the sign of exprs[0].
.operations_research.sat.LinearArgumentProto int_mod = 8;
- Specified by:
getIntMod
in interfaceConstraintProtoOrBuilder
- Returns:
- The intMod.
-
setIntMod
The int_mod constraint forces the target to equal exprs[0] % exprs[1]. The domain of exprs[1] must be strictly positive. The sign of the target is the same as the sign of exprs[0].
.operations_research.sat.LinearArgumentProto int_mod = 8;
-
setIntMod
The int_mod constraint forces the target to equal exprs[0] % exprs[1]. The domain of exprs[1] must be strictly positive. The sign of the target is the same as the sign of exprs[0].
.operations_research.sat.LinearArgumentProto int_mod = 8;
-
mergeIntMod
The int_mod constraint forces the target to equal exprs[0] % exprs[1]. The domain of exprs[1] must be strictly positive. The sign of the target is the same as the sign of exprs[0].
.operations_research.sat.LinearArgumentProto int_mod = 8;
-
clearIntMod
The int_mod constraint forces the target to equal exprs[0] % exprs[1]. The domain of exprs[1] must be strictly positive. The sign of the target is the same as the sign of exprs[0].
.operations_research.sat.LinearArgumentProto int_mod = 8;
-
getIntModBuilder
The int_mod constraint forces the target to equal exprs[0] % exprs[1]. The domain of exprs[1] must be strictly positive. The sign of the target is the same as the sign of exprs[0].
.operations_research.sat.LinearArgumentProto int_mod = 8;
-
getIntModOrBuilder
The int_mod constraint forces the target to equal exprs[0] % exprs[1]. The domain of exprs[1] must be strictly positive. The sign of the target is the same as the sign of exprs[0].
.operations_research.sat.LinearArgumentProto int_mod = 8;
- Specified by:
getIntModOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasIntProd
public boolean hasIntProd()The int_prod constraint forces the target to equal the product of all variables. By convention, because we can just remove term equal to one, the empty product forces the target to be one. Note that the solver checks for potential integer overflow. So the product of the maximum absolute value of all the terms (using the initial domain) should fit on an int64. Otherwise the model will be declared invalid.
.operations_research.sat.LinearArgumentProto int_prod = 11;
- Specified by:
hasIntProd
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the intProd field is set.
-
getIntProd
The int_prod constraint forces the target to equal the product of all variables. By convention, because we can just remove term equal to one, the empty product forces the target to be one. Note that the solver checks for potential integer overflow. So the product of the maximum absolute value of all the terms (using the initial domain) should fit on an int64. Otherwise the model will be declared invalid.
.operations_research.sat.LinearArgumentProto int_prod = 11;
- Specified by:
getIntProd
in interfaceConstraintProtoOrBuilder
- Returns:
- The intProd.
-
setIntProd
The int_prod constraint forces the target to equal the product of all variables. By convention, because we can just remove term equal to one, the empty product forces the target to be one. Note that the solver checks for potential integer overflow. So the product of the maximum absolute value of all the terms (using the initial domain) should fit on an int64. Otherwise the model will be declared invalid.
.operations_research.sat.LinearArgumentProto int_prod = 11;
-
setIntProd
The int_prod constraint forces the target to equal the product of all variables. By convention, because we can just remove term equal to one, the empty product forces the target to be one. Note that the solver checks for potential integer overflow. So the product of the maximum absolute value of all the terms (using the initial domain) should fit on an int64. Otherwise the model will be declared invalid.
.operations_research.sat.LinearArgumentProto int_prod = 11;
-
mergeIntProd
The int_prod constraint forces the target to equal the product of all variables. By convention, because we can just remove term equal to one, the empty product forces the target to be one. Note that the solver checks for potential integer overflow. So the product of the maximum absolute value of all the terms (using the initial domain) should fit on an int64. Otherwise the model will be declared invalid.
.operations_research.sat.LinearArgumentProto int_prod = 11;
-
clearIntProd
The int_prod constraint forces the target to equal the product of all variables. By convention, because we can just remove term equal to one, the empty product forces the target to be one. Note that the solver checks for potential integer overflow. So the product of the maximum absolute value of all the terms (using the initial domain) should fit on an int64. Otherwise the model will be declared invalid.
.operations_research.sat.LinearArgumentProto int_prod = 11;
-
getIntProdBuilder
The int_prod constraint forces the target to equal the product of all variables. By convention, because we can just remove term equal to one, the empty product forces the target to be one. Note that the solver checks for potential integer overflow. So the product of the maximum absolute value of all the terms (using the initial domain) should fit on an int64. Otherwise the model will be declared invalid.
.operations_research.sat.LinearArgumentProto int_prod = 11;
-
getIntProdOrBuilder
The int_prod constraint forces the target to equal the product of all variables. By convention, because we can just remove term equal to one, the empty product forces the target to be one. Note that the solver checks for potential integer overflow. So the product of the maximum absolute value of all the terms (using the initial domain) should fit on an int64. Otherwise the model will be declared invalid.
.operations_research.sat.LinearArgumentProto int_prod = 11;
- Specified by:
getIntProdOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasLinMax
public boolean hasLinMax()The lin_max constraint forces the target to equal the maximum of all linear expressions. Note that this can model a minimum simply by negating all expressions.
.operations_research.sat.LinearArgumentProto lin_max = 27;
- Specified by:
hasLinMax
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the linMax field is set.
-
getLinMax
The lin_max constraint forces the target to equal the maximum of all linear expressions. Note that this can model a minimum simply by negating all expressions.
.operations_research.sat.LinearArgumentProto lin_max = 27;
- Specified by:
getLinMax
in interfaceConstraintProtoOrBuilder
- Returns:
- The linMax.
-
setLinMax
The lin_max constraint forces the target to equal the maximum of all linear expressions. Note that this can model a minimum simply by negating all expressions.
.operations_research.sat.LinearArgumentProto lin_max = 27;
-
setLinMax
The lin_max constraint forces the target to equal the maximum of all linear expressions. Note that this can model a minimum simply by negating all expressions.
.operations_research.sat.LinearArgumentProto lin_max = 27;
-
mergeLinMax
The lin_max constraint forces the target to equal the maximum of all linear expressions. Note that this can model a minimum simply by negating all expressions.
.operations_research.sat.LinearArgumentProto lin_max = 27;
-
clearLinMax
The lin_max constraint forces the target to equal the maximum of all linear expressions. Note that this can model a minimum simply by negating all expressions.
.operations_research.sat.LinearArgumentProto lin_max = 27;
-
getLinMaxBuilder
The lin_max constraint forces the target to equal the maximum of all linear expressions. Note that this can model a minimum simply by negating all expressions.
.operations_research.sat.LinearArgumentProto lin_max = 27;
-
getLinMaxOrBuilder
The lin_max constraint forces the target to equal the maximum of all linear expressions. Note that this can model a minimum simply by negating all expressions.
.operations_research.sat.LinearArgumentProto lin_max = 27;
- Specified by:
getLinMaxOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasLinear
public boolean hasLinear()The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.
.operations_research.sat.LinearConstraintProto linear = 12;
- Specified by:
hasLinear
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the linear field is set.
-
getLinear
The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.
.operations_research.sat.LinearConstraintProto linear = 12;
- Specified by:
getLinear
in interfaceConstraintProtoOrBuilder
- Returns:
- The linear.
-
setLinear
The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.
.operations_research.sat.LinearConstraintProto linear = 12;
-
setLinear
The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.
.operations_research.sat.LinearConstraintProto linear = 12;
-
mergeLinear
The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.
.operations_research.sat.LinearConstraintProto linear = 12;
-
clearLinear
The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.
.operations_research.sat.LinearConstraintProto linear = 12;
-
getLinearBuilder
The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.
.operations_research.sat.LinearConstraintProto linear = 12;
-
getLinearOrBuilder
The linear constraint enforces a linear inequality among the variables, such as 0 <= x + 2y <= 10.
.operations_research.sat.LinearConstraintProto linear = 12;
- Specified by:
getLinearOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasAllDiff
public boolean hasAllDiff()The all_diff constraint forces all variables to take different values.
.operations_research.sat.AllDifferentConstraintProto all_diff = 13;
- Specified by:
hasAllDiff
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the allDiff field is set.
-
getAllDiff
The all_diff constraint forces all variables to take different values.
.operations_research.sat.AllDifferentConstraintProto all_diff = 13;
- Specified by:
getAllDiff
in interfaceConstraintProtoOrBuilder
- Returns:
- The allDiff.
-
setAllDiff
The all_diff constraint forces all variables to take different values.
.operations_research.sat.AllDifferentConstraintProto all_diff = 13;
-
setAllDiff
The all_diff constraint forces all variables to take different values.
.operations_research.sat.AllDifferentConstraintProto all_diff = 13;
-
mergeAllDiff
The all_diff constraint forces all variables to take different values.
.operations_research.sat.AllDifferentConstraintProto all_diff = 13;
-
clearAllDiff
The all_diff constraint forces all variables to take different values.
.operations_research.sat.AllDifferentConstraintProto all_diff = 13;
-
getAllDiffBuilder
The all_diff constraint forces all variables to take different values.
.operations_research.sat.AllDifferentConstraintProto all_diff = 13;
-
getAllDiffOrBuilder
The all_diff constraint forces all variables to take different values.
.operations_research.sat.AllDifferentConstraintProto all_diff = 13;
- Specified by:
getAllDiffOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasElement
public boolean hasElement()The element constraint forces the variable with the given index to be equal to the target.
.operations_research.sat.ElementConstraintProto element = 14;
- Specified by:
hasElement
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the element field is set.
-
getElement
The element constraint forces the variable with the given index to be equal to the target.
.operations_research.sat.ElementConstraintProto element = 14;
- Specified by:
getElement
in interfaceConstraintProtoOrBuilder
- Returns:
- The element.
-
setElement
The element constraint forces the variable with the given index to be equal to the target.
.operations_research.sat.ElementConstraintProto element = 14;
-
setElement
The element constraint forces the variable with the given index to be equal to the target.
.operations_research.sat.ElementConstraintProto element = 14;
-
mergeElement
The element constraint forces the variable with the given index to be equal to the target.
.operations_research.sat.ElementConstraintProto element = 14;
-
clearElement
The element constraint forces the variable with the given index to be equal to the target.
.operations_research.sat.ElementConstraintProto element = 14;
-
getElementBuilder
The element constraint forces the variable with the given index to be equal to the target.
.operations_research.sat.ElementConstraintProto element = 14;
-
getElementOrBuilder
The element constraint forces the variable with the given index to be equal to the target.
.operations_research.sat.ElementConstraintProto element = 14;
- Specified by:
getElementOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasCircuit
public boolean hasCircuit()The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.
.operations_research.sat.CircuitConstraintProto circuit = 15;
- Specified by:
hasCircuit
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the circuit field is set.
-
getCircuit
The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.
.operations_research.sat.CircuitConstraintProto circuit = 15;
- Specified by:
getCircuit
in interfaceConstraintProtoOrBuilder
- Returns:
- The circuit.
-
setCircuit
The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.
.operations_research.sat.CircuitConstraintProto circuit = 15;
-
setCircuit
The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.
.operations_research.sat.CircuitConstraintProto circuit = 15;
-
mergeCircuit
The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.
.operations_research.sat.CircuitConstraintProto circuit = 15;
-
clearCircuit
The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.
.operations_research.sat.CircuitConstraintProto circuit = 15;
-
getCircuitBuilder
The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.
.operations_research.sat.CircuitConstraintProto circuit = 15;
-
getCircuitOrBuilder
The circuit constraint takes a graph and forces the arcs present (with arc presence indicated by a literal) to form a unique cycle.
.operations_research.sat.CircuitConstraintProto circuit = 15;
- Specified by:
getCircuitOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasRoutes
public boolean hasRoutes()The routes constraint implements the vehicle routing problem.
.operations_research.sat.RoutesConstraintProto routes = 23;
- Specified by:
hasRoutes
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the routes field is set.
-
getRoutes
The routes constraint implements the vehicle routing problem.
.operations_research.sat.RoutesConstraintProto routes = 23;
- Specified by:
getRoutes
in interfaceConstraintProtoOrBuilder
- Returns:
- The routes.
-
setRoutes
The routes constraint implements the vehicle routing problem.
.operations_research.sat.RoutesConstraintProto routes = 23;
-
setRoutes
The routes constraint implements the vehicle routing problem.
.operations_research.sat.RoutesConstraintProto routes = 23;
-
mergeRoutes
The routes constraint implements the vehicle routing problem.
.operations_research.sat.RoutesConstraintProto routes = 23;
-
clearRoutes
The routes constraint implements the vehicle routing problem.
.operations_research.sat.RoutesConstraintProto routes = 23;
-
getRoutesBuilder
The routes constraint implements the vehicle routing problem.
.operations_research.sat.RoutesConstraintProto routes = 23;
-
getRoutesOrBuilder
The routes constraint implements the vehicle routing problem.
.operations_research.sat.RoutesConstraintProto routes = 23;
- Specified by:
getRoutesOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasTable
public boolean hasTable()The table constraint enforces what values a tuple of variables may take.
.operations_research.sat.TableConstraintProto table = 16;
- Specified by:
hasTable
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the table field is set.
-
getTable
The table constraint enforces what values a tuple of variables may take.
.operations_research.sat.TableConstraintProto table = 16;
- Specified by:
getTable
in interfaceConstraintProtoOrBuilder
- Returns:
- The table.
-
setTable
The table constraint enforces what values a tuple of variables may take.
.operations_research.sat.TableConstraintProto table = 16;
-
setTable
The table constraint enforces what values a tuple of variables may take.
.operations_research.sat.TableConstraintProto table = 16;
-
mergeTable
The table constraint enforces what values a tuple of variables may take.
.operations_research.sat.TableConstraintProto table = 16;
-
clearTable
The table constraint enforces what values a tuple of variables may take.
.operations_research.sat.TableConstraintProto table = 16;
-
getTableBuilder
The table constraint enforces what values a tuple of variables may take.
.operations_research.sat.TableConstraintProto table = 16;
-
getTableOrBuilder
The table constraint enforces what values a tuple of variables may take.
.operations_research.sat.TableConstraintProto table = 16;
- Specified by:
getTableOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasAutomaton
public boolean hasAutomaton()The automaton constraint forces a sequence of variables to be accepted by an automaton.
.operations_research.sat.AutomatonConstraintProto automaton = 17;
- Specified by:
hasAutomaton
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the automaton field is set.
-
getAutomaton
The automaton constraint forces a sequence of variables to be accepted by an automaton.
.operations_research.sat.AutomatonConstraintProto automaton = 17;
- Specified by:
getAutomaton
in interfaceConstraintProtoOrBuilder
- Returns:
- The automaton.
-
setAutomaton
The automaton constraint forces a sequence of variables to be accepted by an automaton.
.operations_research.sat.AutomatonConstraintProto automaton = 17;
-
setAutomaton
The automaton constraint forces a sequence of variables to be accepted by an automaton.
.operations_research.sat.AutomatonConstraintProto automaton = 17;
-
mergeAutomaton
The automaton constraint forces a sequence of variables to be accepted by an automaton.
.operations_research.sat.AutomatonConstraintProto automaton = 17;
-
clearAutomaton
The automaton constraint forces a sequence of variables to be accepted by an automaton.
.operations_research.sat.AutomatonConstraintProto automaton = 17;
-
getAutomatonBuilder
The automaton constraint forces a sequence of variables to be accepted by an automaton.
.operations_research.sat.AutomatonConstraintProto automaton = 17;
-
getAutomatonOrBuilder
The automaton constraint forces a sequence of variables to be accepted by an automaton.
.operations_research.sat.AutomatonConstraintProto automaton = 17;
- Specified by:
getAutomatonOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasInverse
public boolean hasInverse()The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.
.operations_research.sat.InverseConstraintProto inverse = 18;
- Specified by:
hasInverse
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the inverse field is set.
-
getInverse
The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.
.operations_research.sat.InverseConstraintProto inverse = 18;
- Specified by:
getInverse
in interfaceConstraintProtoOrBuilder
- Returns:
- The inverse.
-
setInverse
The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.
.operations_research.sat.InverseConstraintProto inverse = 18;
-
setInverse
The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.
.operations_research.sat.InverseConstraintProto inverse = 18;
-
mergeInverse
The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.
.operations_research.sat.InverseConstraintProto inverse = 18;
-
clearInverse
The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.
.operations_research.sat.InverseConstraintProto inverse = 18;
-
getInverseBuilder
The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.
.operations_research.sat.InverseConstraintProto inverse = 18;
-
getInverseOrBuilder
The inverse constraint forces two arrays to be inverses of each other: the values of one are the indices of the other, and vice versa.
.operations_research.sat.InverseConstraintProto inverse = 18;
- Specified by:
getInverseOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasReservoir
public boolean hasReservoir()The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.
.operations_research.sat.ReservoirConstraintProto reservoir = 24;
- Specified by:
hasReservoir
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the reservoir field is set.
-
getReservoir
The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.
.operations_research.sat.ReservoirConstraintProto reservoir = 24;
- Specified by:
getReservoir
in interfaceConstraintProtoOrBuilder
- Returns:
- The reservoir.
-
setReservoir
The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.
.operations_research.sat.ReservoirConstraintProto reservoir = 24;
-
setReservoir
The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.
.operations_research.sat.ReservoirConstraintProto reservoir = 24;
-
mergeReservoir
The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.
.operations_research.sat.ReservoirConstraintProto reservoir = 24;
-
clearReservoir
The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.
.operations_research.sat.ReservoirConstraintProto reservoir = 24;
-
getReservoirBuilder
The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.
.operations_research.sat.ReservoirConstraintProto reservoir = 24;
-
getReservoirOrBuilder
The reservoir constraint forces the sum of a set of active demands to always be between a specified minimum and maximum value during specific times.
.operations_research.sat.ReservoirConstraintProto reservoir = 24;
- Specified by:
getReservoirOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasInterval
public boolean hasInterval()The interval constraint takes a start, end, and size, and forces start + size == end.
.operations_research.sat.IntervalConstraintProto interval = 19;
- Specified by:
hasInterval
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the interval field is set.
-
getInterval
The interval constraint takes a start, end, and size, and forces start + size == end.
.operations_research.sat.IntervalConstraintProto interval = 19;
- Specified by:
getInterval
in interfaceConstraintProtoOrBuilder
- Returns:
- The interval.
-
setInterval
The interval constraint takes a start, end, and size, and forces start + size == end.
.operations_research.sat.IntervalConstraintProto interval = 19;
-
setInterval
The interval constraint takes a start, end, and size, and forces start + size == end.
.operations_research.sat.IntervalConstraintProto interval = 19;
-
mergeInterval
The interval constraint takes a start, end, and size, and forces start + size == end.
.operations_research.sat.IntervalConstraintProto interval = 19;
-
clearInterval
The interval constraint takes a start, end, and size, and forces start + size == end.
.operations_research.sat.IntervalConstraintProto interval = 19;
-
getIntervalBuilder
The interval constraint takes a start, end, and size, and forces start + size == end.
.operations_research.sat.IntervalConstraintProto interval = 19;
-
getIntervalOrBuilder
The interval constraint takes a start, end, and size, and forces start + size == end.
.operations_research.sat.IntervalConstraintProto interval = 19;
- Specified by:
getIntervalOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasNoOverlap
public boolean hasNoOverlap()The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.
.operations_research.sat.NoOverlapConstraintProto no_overlap = 20;
- Specified by:
hasNoOverlap
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the noOverlap field is set.
-
getNoOverlap
The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.
.operations_research.sat.NoOverlapConstraintProto no_overlap = 20;
- Specified by:
getNoOverlap
in interfaceConstraintProtoOrBuilder
- Returns:
- The noOverlap.
-
setNoOverlap
The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.
.operations_research.sat.NoOverlapConstraintProto no_overlap = 20;
-
setNoOverlap
The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.
.operations_research.sat.NoOverlapConstraintProto no_overlap = 20;
-
mergeNoOverlap
The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.
.operations_research.sat.NoOverlapConstraintProto no_overlap = 20;
-
clearNoOverlap
The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.
.operations_research.sat.NoOverlapConstraintProto no_overlap = 20;
-
getNoOverlapBuilder
The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.
.operations_research.sat.NoOverlapConstraintProto no_overlap = 20;
-
getNoOverlapOrBuilder
The no_overlap constraint prevents a set of intervals from overlapping; in scheduling, this is called a disjunctive constraint.
.operations_research.sat.NoOverlapConstraintProto no_overlap = 20;
- Specified by:
getNoOverlapOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasNoOverlap2D
public boolean hasNoOverlap2D()The no_overlap_2d constraint prevents a set of boxes from overlapping.
.operations_research.sat.NoOverlap2DConstraintProto no_overlap_2d = 21;
- Specified by:
hasNoOverlap2D
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the noOverlap2d field is set.
-
getNoOverlap2D
The no_overlap_2d constraint prevents a set of boxes from overlapping.
.operations_research.sat.NoOverlap2DConstraintProto no_overlap_2d = 21;
- Specified by:
getNoOverlap2D
in interfaceConstraintProtoOrBuilder
- Returns:
- The noOverlap2d.
-
setNoOverlap2D
The no_overlap_2d constraint prevents a set of boxes from overlapping.
.operations_research.sat.NoOverlap2DConstraintProto no_overlap_2d = 21;
-
setNoOverlap2D
The no_overlap_2d constraint prevents a set of boxes from overlapping.
.operations_research.sat.NoOverlap2DConstraintProto no_overlap_2d = 21;
-
mergeNoOverlap2D
The no_overlap_2d constraint prevents a set of boxes from overlapping.
.operations_research.sat.NoOverlap2DConstraintProto no_overlap_2d = 21;
-
clearNoOverlap2D
The no_overlap_2d constraint prevents a set of boxes from overlapping.
.operations_research.sat.NoOverlap2DConstraintProto no_overlap_2d = 21;
-
getNoOverlap2DBuilder
The no_overlap_2d constraint prevents a set of boxes from overlapping.
.operations_research.sat.NoOverlap2DConstraintProto no_overlap_2d = 21;
-
getNoOverlap2DOrBuilder
The no_overlap_2d constraint prevents a set of boxes from overlapping.
.operations_research.sat.NoOverlap2DConstraintProto no_overlap_2d = 21;
- Specified by:
getNoOverlap2DOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasCumulative
public boolean hasCumulative()The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.
.operations_research.sat.CumulativeConstraintProto cumulative = 22;
- Specified by:
hasCumulative
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the cumulative field is set.
-
getCumulative
The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.
.operations_research.sat.CumulativeConstraintProto cumulative = 22;
- Specified by:
getCumulative
in interfaceConstraintProtoOrBuilder
- Returns:
- The cumulative.
-
setCumulative
The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.
.operations_research.sat.CumulativeConstraintProto cumulative = 22;
-
setCumulative
The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.
.operations_research.sat.CumulativeConstraintProto cumulative = 22;
-
mergeCumulative
The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.
.operations_research.sat.CumulativeConstraintProto cumulative = 22;
-
clearCumulative
The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.
.operations_research.sat.CumulativeConstraintProto cumulative = 22;
-
getCumulativeBuilder
The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.
.operations_research.sat.CumulativeConstraintProto cumulative = 22;
-
getCumulativeOrBuilder
The cumulative constraint ensures that for any integer point, the sum of the demands of the intervals containing that point does not exceed the capacity.
.operations_research.sat.CumulativeConstraintProto cumulative = 22;
- Specified by:
getCumulativeOrBuilder
in interfaceConstraintProtoOrBuilder
-
hasDummyConstraint
public boolean hasDummyConstraint()This constraint is not meant to be used and will be rejected by the solver. It is meant to mark variable when testing the presolve code.
.operations_research.sat.ListOfVariablesProto dummy_constraint = 30;
- Specified by:
hasDummyConstraint
in interfaceConstraintProtoOrBuilder
- Returns:
- Whether the dummyConstraint field is set.
-
getDummyConstraint
This constraint is not meant to be used and will be rejected by the solver. It is meant to mark variable when testing the presolve code.
.operations_research.sat.ListOfVariablesProto dummy_constraint = 30;
- Specified by:
getDummyConstraint
in interfaceConstraintProtoOrBuilder
- Returns:
- The dummyConstraint.
-
setDummyConstraint
This constraint is not meant to be used and will be rejected by the solver. It is meant to mark variable when testing the presolve code.
.operations_research.sat.ListOfVariablesProto dummy_constraint = 30;
-
setDummyConstraint
This constraint is not meant to be used and will be rejected by the solver. It is meant to mark variable when testing the presolve code.
.operations_research.sat.ListOfVariablesProto dummy_constraint = 30;
-
mergeDummyConstraint
This constraint is not meant to be used and will be rejected by the solver. It is meant to mark variable when testing the presolve code.
.operations_research.sat.ListOfVariablesProto dummy_constraint = 30;
-
clearDummyConstraint
This constraint is not meant to be used and will be rejected by the solver. It is meant to mark variable when testing the presolve code.
.operations_research.sat.ListOfVariablesProto dummy_constraint = 30;
-
getDummyConstraintBuilder
This constraint is not meant to be used and will be rejected by the solver. It is meant to mark variable when testing the presolve code.
.operations_research.sat.ListOfVariablesProto dummy_constraint = 30;
-
getDummyConstraintOrBuilder
This constraint is not meant to be used and will be rejected by the solver. It is meant to mark variable when testing the presolve code.
.operations_research.sat.ListOfVariablesProto dummy_constraint = 30;
- Specified by:
getDummyConstraintOrBuilder
in interfaceConstraintProtoOrBuilder
-