Package com.google.ortools.linearsolver

Interface MPModelDeltaProtoOrBuilder

  • All Superinterfaces:
    com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
    All Known Implementing Classes:
    MPModelDeltaProto, MPModelDeltaProto.Builder
    public interface MPModelDeltaProtoOrBuilder
extends com.google.protobuf.MessageOrBuilder

    • Method Detail

      • hasBaselineModelFilePath

        boolean hasBaselineModelFilePath()
        optional string baseline_model_file_path = 1;
        Returns:
        Whether the baselineModelFilePath field is set.

      • getBaselineModelFilePath

        java.lang.String getBaselineModelFilePath()
        optional string baseline_model_file_path = 1;
        Returns:
        The baselineModelFilePath.

      • getBaselineModelFilePathBytes

        com.google.protobuf.ByteString getBaselineModelFilePathBytes()
        optional string baseline_model_file_path = 1;
        Returns:
        The bytes for baselineModelFilePath.

      • 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;

      • 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;

      • getVariableOverridesMap

        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;

      • getVariableOverridesOrDefault

        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;

      • getVariableOverridesOrThrow

        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;

      • 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;

      • 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;

      • getConstraintOverridesMap

        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;

      • getConstraintOverridesOrDefault

        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;

      • getConstraintOverridesOrThrow

        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;