Encodes a full MPModelProto by way of referencing to a "baseline" MPModelProto stored in a file, and a "delta" to apply to this model.
More...
|
static pb::MessageParser< MPModelDeltaProto > | Parser [get] |
|
static pbr::MessageDescriptor | Descriptor [get] |
|
string | BaselineModelFilePath [get, set] |
|
bool | HasBaselineModelFilePath [get] |
| Gets whether the "baseline_model_file_path" field is set.
|
|
pbc::MapField< int, global::OperationsResearch.MPVariableProto > | VariableOverrides [get] |
| 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.
|
|
pbc::MapField< int, global::OperationsResearch.MPConstraintProto > | ConstraintOverrides [get] |
| Constraints can be changed (or added) in the same way as variables, see above. It's mostly like applying MergeFrom(), except that:
|
|
Encodes a full MPModelProto by way of referencing to a "baseline" MPModelProto stored in a file, and a "delta" to apply to this model.
Definition at line 5988 of file LinearSolver.pb.cs.
◆ MPModelDeltaProto() [1/2]
OperationsResearch.MPModelDeltaProto.MPModelDeltaProto |
( |
| ) |
|
|
inline |
◆ MPModelDeltaProto() [2/2]
◆ CalculateSize()
int OperationsResearch.MPModelDeltaProto.CalculateSize |
( |
| ) |
|
|
inline |
◆ ClearBaselineModelFilePath()
void OperationsResearch.MPModelDeltaProto.ClearBaselineModelFilePath |
( |
| ) |
|
|
inline |
◆ Clone()
◆ Equals() [1/2]
◆ Equals() [2/2]
override bool OperationsResearch.MPModelDeltaProto.Equals |
( |
object | other | ) |
|
|
inline |
◆ GetHashCode()
override int OperationsResearch.MPModelDeltaProto.GetHashCode |
( |
| ) |
|
|
inline |
◆ MergeFrom() [1/2]
◆ MergeFrom() [2/2]
void OperationsResearch.MPModelDeltaProto.MergeFrom |
( |
pb.CodedInputStream | input | ) |
|
|
inline |
◆ ToString()
override string OperationsResearch.MPModelDeltaProto.ToString |
( |
| ) |
|
|
inline |
◆ WriteTo()
void OperationsResearch.MPModelDeltaProto.WriteTo |
( |
pb.CodedOutputStream | output | ) |
|
|
inline |
◆ BaselineModelFilePathFieldNumber
const int OperationsResearch.MPModelDeltaProto.BaselineModelFilePathFieldNumber = 1 |
|
static |
◆ ConstraintOverridesFieldNumber
const int OperationsResearch.MPModelDeltaProto.ConstraintOverridesFieldNumber = 3 |
|
static |
◆ VariableOverridesFieldNumber
const int OperationsResearch.MPModelDeltaProto.VariableOverridesFieldNumber = 2 |
|
static |
◆ BaselineModelFilePath
string OperationsResearch.MPModelDeltaProto.BaselineModelFilePath |
|
getset |
◆ ConstraintOverrides
pbc.MapField<int, global.OperationsResearch.MPConstraintProto> OperationsResearch.MPModelDeltaProto.ConstraintOverrides |
|
get |
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.
Definition at line 6096 of file LinearSolver.pb.cs.
◆ Descriptor
pbr.MessageDescriptor OperationsResearch.MPModelDeltaProto.Descriptor |
|
staticget |
◆ HasBaselineModelFilePath
bool OperationsResearch.MPModelDeltaProto.HasBaselineModelFilePath |
|
get |
◆ Parser
◆ VariableOverrides
pbc.MapField<int, global.OperationsResearch.MPVariableProto> OperationsResearch.MPModelDeltaProto.VariableOverrides |
|
get |
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.
Definition at line 6076 of file LinearSolver.pb.cs.
The documentation for this class was generated from the following file: