public interface MPModelDeltaProtoOrBuilder
extends com.google.protobuf.MessageOrBuilder
Modifier and Type | Method and Description |
---|---|
boolean |
containsConstraintOverrides(int key)
Constraints can be changed (or added) in the same way as variables, see
above.
|
boolean |
containsVariableOverrides(int key)
The variable protos listed here will override (via MergeFrom()) the ones
in the baseline model: you only need to specify the fields that change.
|
java.lang.String |
getBaselineModelFilePath()
optional string baseline_model_file_path = 1; |
com.google.protobuf.ByteString |
getBaselineModelFilePathBytes()
optional string baseline_model_file_path = 1; |
java.util.Map<java.lang.Integer,MPConstraintProto> |
getConstraintOverrides()
Deprecated.
|
int |
getConstraintOverridesCount()
Constraints can be changed (or added) in the same way as variables, see
above.
|
java.util.Map<java.lang.Integer,MPConstraintProto> |
getConstraintOverridesMap()
Constraints can be changed (or added) in the same way as variables, see
above.
|
MPConstraintProto |
getConstraintOverridesOrDefault(int key,
MPConstraintProto defaultValue)
Constraints can be changed (or added) in the same way as variables, see
above.
|
MPConstraintProto |
getConstraintOverridesOrThrow(int key)
Constraints can be changed (or added) in the same way as variables, see
above.
|
java.util.Map<java.lang.Integer,MPVariableProto> |
getVariableOverrides()
Deprecated.
|
int |
getVariableOverridesCount()
The variable protos listed here will override (via MergeFrom()) the ones
in the baseline model: you only need to specify the fields that change.
|
java.util.Map<java.lang.Integer,MPVariableProto> |
getVariableOverridesMap()
The variable protos listed here will override (via MergeFrom()) the ones
in the baseline model: you only need to specify the fields that change.
|
MPVariableProto |
getVariableOverridesOrDefault(int key,
MPVariableProto defaultValue)
The variable protos listed here will override (via MergeFrom()) the ones
in the baseline model: you only need to specify the fields that change.
|
MPVariableProto |
getVariableOverridesOrThrow(int key)
The variable protos listed here will override (via MergeFrom()) the ones
in the baseline model: you only need to specify the fields that change.
|
boolean |
hasBaselineModelFilePath()
optional string baseline_model_file_path = 1; |
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
boolean hasBaselineModelFilePath()
optional string baseline_model_file_path = 1;
java.lang.String getBaselineModelFilePath()
optional string baseline_model_file_path = 1;
com.google.protobuf.ByteString getBaselineModelFilePathBytes()
optional string baseline_model_file_path = 1;
int getVariableOverridesCount()
The variable protos listed here will override (via MergeFrom()) the ones in the baseline model: you only need to specify the fields that change. To add a new variable, add it with a new variable index (variable indices still need to span a dense integer interval). You can't "delete" a variable but you can "neutralize" it by fixing its value, setting its objective coefficient to zero, and by nullifying all the terms involving it in the constraints.
map<int32, .operations_research.MPVariableProto> variable_overrides = 2;
boolean containsVariableOverrides(int key)
The variable protos listed here will override (via MergeFrom()) the ones in the baseline model: you only need to specify the fields that change. To add a new variable, add it with a new variable index (variable indices still need to span a dense integer interval). You can't "delete" a variable but you can "neutralize" it by fixing its value, setting its objective coefficient to zero, and by nullifying all the terms involving it in the constraints.
map<int32, .operations_research.MPVariableProto> variable_overrides = 2;
@Deprecated java.util.Map<java.lang.Integer,MPVariableProto> getVariableOverrides()
getVariableOverridesMap()
instead.java.util.Map<java.lang.Integer,MPVariableProto> getVariableOverridesMap()
The variable protos listed here will override (via MergeFrom()) the ones in the baseline model: you only need to specify the fields that change. To add a new variable, add it with a new variable index (variable indices still need to span a dense integer interval). You can't "delete" a variable but you can "neutralize" it by fixing its value, setting its objective coefficient to zero, and by nullifying all the terms involving it in the constraints.
map<int32, .operations_research.MPVariableProto> variable_overrides = 2;
MPVariableProto getVariableOverridesOrDefault(int key, MPVariableProto defaultValue)
The variable protos listed here will override (via MergeFrom()) the ones in the baseline model: you only need to specify the fields that change. To add a new variable, add it with a new variable index (variable indices still need to span a dense integer interval). You can't "delete" a variable but you can "neutralize" it by fixing its value, setting its objective coefficient to zero, and by nullifying all the terms involving it in the constraints.
map<int32, .operations_research.MPVariableProto> variable_overrides = 2;
MPVariableProto getVariableOverridesOrThrow(int key)
The variable protos listed here will override (via MergeFrom()) the ones in the baseline model: you only need to specify the fields that change. To add a new variable, add it with a new variable index (variable indices still need to span a dense integer interval). You can't "delete" a variable but you can "neutralize" it by fixing its value, setting its objective coefficient to zero, and by nullifying all the terms involving it in the constraints.
map<int32, .operations_research.MPVariableProto> variable_overrides = 2;
int getConstraintOverridesCount()
Constraints can be changed (or added) in the same way as variables, see above. It's mostly like applying MergeFrom(), except that: - the "var_index" and "coefficient" fields will be overridden like a map: if a key pre-exists, we overwrite its value, otherwise we add it. - if you set the lower bound to -inf and the upper bound to +inf, thus effectively neutralizing the constraint, the solver will implicitly remove all of the constraint's terms.
map<int32, .operations_research.MPConstraintProto> constraint_overrides = 3;
boolean containsConstraintOverrides(int key)
Constraints can be changed (or added) in the same way as variables, see above. It's mostly like applying MergeFrom(), except that: - the "var_index" and "coefficient" fields will be overridden like a map: if a key pre-exists, we overwrite its value, otherwise we add it. - if you set the lower bound to -inf and the upper bound to +inf, thus effectively neutralizing the constraint, the solver will implicitly remove all of the constraint's terms.
map<int32, .operations_research.MPConstraintProto> constraint_overrides = 3;
@Deprecated java.util.Map<java.lang.Integer,MPConstraintProto> getConstraintOverrides()
getConstraintOverridesMap()
instead.java.util.Map<java.lang.Integer,MPConstraintProto> getConstraintOverridesMap()
Constraints can be changed (or added) in the same way as variables, see above. It's mostly like applying MergeFrom(), except that: - the "var_index" and "coefficient" fields will be overridden like a map: if a key pre-exists, we overwrite its value, otherwise we add it. - if you set the lower bound to -inf and the upper bound to +inf, thus effectively neutralizing the constraint, the solver will implicitly remove all of the constraint's terms.
map<int32, .operations_research.MPConstraintProto> constraint_overrides = 3;
MPConstraintProto getConstraintOverridesOrDefault(int key, MPConstraintProto defaultValue)
Constraints can be changed (or added) in the same way as variables, see above. It's mostly like applying MergeFrom(), except that: - the "var_index" and "coefficient" fields will be overridden like a map: if a key pre-exists, we overwrite its value, otherwise we add it. - if you set the lower bound to -inf and the upper bound to +inf, thus effectively neutralizing the constraint, the solver will implicitly remove all of the constraint's terms.
map<int32, .operations_research.MPConstraintProto> constraint_overrides = 3;
MPConstraintProto getConstraintOverridesOrThrow(int key)
Constraints can be changed (or added) in the same way as variables, see above. It's mostly like applying MergeFrom(), except that: - the "var_index" and "coefficient" fields will be overridden like a map: if a key pre-exists, we overwrite its value, otherwise we add it. - if you set the lower bound to -inf and the upper bound to +inf, thus effectively neutralizing the constraint, the solver will implicitly remove all of the constraint's terms.
map<int32, .operations_research.MPConstraintProto> constraint_overrides = 3;
Copyright © 2025. All rights reserved.