Java Reference

Java Reference

MPModelDeltaProtoOrBuilder

Detailed Description

Definition at line 6 of file MPModelDeltaProtoOrBuilder.java.

Public Member Functions

boolean hasBaselineModelFilePath ()
 optional string baseline_model_file_path = 1; More...
 
java.lang.String getBaselineModelFilePath ()
 optional string baseline_model_file_path = 1; More...
 
com.google.protobuf.ByteString getBaselineModelFilePathBytes ()
 optional string baseline_model_file_path = 1; More...
 
int getVariableOverridesCount ()
 
boolean containsVariableOverrides (int key)
 
.lang.Deprecated java.util.Map< java.lang.Integer, com.google.ortools.linearsolver.MPVariableProtogetVariableOverrides ()
 Use getVariableOverridesMap() instead. More...
 
java.util.Map< java.lang.Integer, com.google.ortools.linearsolver.MPVariableProtogetVariableOverridesMap ()
 
com.google.ortools.linearsolver.MPVariableProto getVariableOverridesOrDefault (int key, com.google.ortools.linearsolver.MPVariableProto defaultValue)
 
com.google.ortools.linearsolver.MPVariableProto getVariableOverridesOrThrow (int key)
 
int getConstraintOverridesCount ()
 
boolean containsConstraintOverrides (int key)
 
.lang.Deprecated java.util.Map< java.lang.Integer, com.google.ortools.linearsolver.MPConstraintProtogetConstraintOverrides ()
 Use getConstraintOverridesMap() instead. More...
 
java.util.Map< java.lang.Integer, com.google.ortools.linearsolver.MPConstraintProtogetConstraintOverridesMap ()
 
com.google.ortools.linearsolver.MPConstraintProto getConstraintOverridesOrDefault (int key, com.google.ortools.linearsolver.MPConstraintProto defaultValue)
 
com.google.ortools.linearsolver.MPConstraintProto getConstraintOverridesOrThrow (int key)
 

Member Function Documentation

◆ containsConstraintOverrides()

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;

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ containsVariableOverrides()

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;

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ getBaselineModelFilePath()

java.lang.String getBaselineModelFilePath ( )

optional string baseline_model_file_path = 1;

Returns
The baselineModelFilePath.

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ getBaselineModelFilePathBytes()

com.google.protobuf.ByteString getBaselineModelFilePathBytes ( )

optional string baseline_model_file_path = 1;

Returns
The bytes for baselineModelFilePath.

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ getConstraintOverrides()

.lang.Deprecated java.util.Map<java.lang.Integer, com.google.ortools.linearsolver.MPConstraintProto> getConstraintOverrides ( )

◆ getConstraintOverridesCount()

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;

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ getConstraintOverridesMap()

java.util.Map<java.lang.Integer, com.google.ortools.linearsolver.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;

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ getConstraintOverridesOrDefault()

com.google.ortools.linearsolver.MPConstraintProto getConstraintOverridesOrDefault ( int  key,
com.google.ortools.linearsolver.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;

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ getConstraintOverridesOrThrow()

com.google.ortools.linearsolver.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;

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ getVariableOverrides()

.lang.Deprecated java.util.Map<java.lang.Integer, com.google.ortools.linearsolver.MPVariableProto> getVariableOverrides ( )

◆ getVariableOverridesCount()

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;

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ getVariableOverridesMap()

java.util.Map<java.lang.Integer, com.google.ortools.linearsolver.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;

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ getVariableOverridesOrDefault()

com.google.ortools.linearsolver.MPVariableProto getVariableOverridesOrDefault ( int  key,
com.google.ortools.linearsolver.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;

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ getVariableOverridesOrThrow()

com.google.ortools.linearsolver.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;

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.

◆ hasBaselineModelFilePath()

boolean hasBaselineModelFilePath ( )

optional string baseline_model_file_path = 1;

Returns
Whether the baselineModelFilePath field is set.

Implemented in MPModelDeltaProto.Builder, and MPModelDeltaProto.


The documentation for this interface was generated from the following file: