Next id: 9.
Protobuf type
operations_research.MPModelRequest
Definition at line 949 of file MPModelRequest.java.
| Builder clearSolverSpecificParameters |
( |
| ) |
|
|
inline |
Advanced usage. Solver-specific parameters in the solver's own format,
different for each solver. For example, if you use SCIP and you want to
stop the solve earlier than the time limit if it reached a solution that is
at most 1% away from the optimal, you can set this to "limits/gap=0.01".
Note however that there is no "security" mechanism in place so it is up to
the client to make sure that the given options don't make the solve
non thread safe or use up too much memory for instance.
If the option format is not understood by the solver, the request will be
rejected and yield an RPC Application error with code
MPSOLVER_MODEL_INVALID_SOLVER_PARAMETERS.
optional string solver_specific_parameters = 5;
- Returns
- This builder for chaining.
Definition at line 1637 of file MPModelRequest.java.
| Builder clearSolverTimeLimitSeconds |
( |
| ) |
|
|
inline |
Maximum time to be spent by the solver to solve 'model'. If the server is
busy and the RPC's deadline_left is less than this, it will immediately
give up and return an error, without even trying to solve.
The client can use this to have a guarantee on how much time the
solver will spend on the problem (unless it finds and proves
an optimal solution more quickly).
If not specified, the time limit on the solver is the RPC's deadline_left.
optional double solver_time_limit_seconds = 3;
- Returns
- This builder for chaining.
Definition at line 1436 of file MPModelRequest.java.
| .lang.Override boolean getEnableInternalSolverOutput |
( |
| ) |
|
|
inline |
If this is set, then EnableOutput() will be set on the internal MPSolver
that solves the model.
WARNING: if you set this on a request to prod servers, it will be rejected
and yield the RPC Application Error code MPSOLVER_SOLVER_TYPE_UNAVAILABLE.
optional bool enable_internal_solver_output = 4 [default = false];
- Returns
- The enableInternalSolverOutput.
Implements MPModelRequestOrBuilder.
Definition at line 1471 of file MPModelRequest.java.
| java.lang.String getSolverSpecificParameters |
( |
| ) |
|
|
inline |
Advanced usage. Solver-specific parameters in the solver's own format,
different for each solver. For example, if you use SCIP and you want to
stop the solve earlier than the time limit if it reached a solution that is
at most 1% away from the optimal, you can set this to "limits/gap=0.01".
Note however that there is no "security" mechanism in place so it is up to
the client to make sure that the given options don't make the solve
non thread safe or use up too much memory for instance.
If the option format is not understood by the solver, the request will be
rejected and yield an RPC Application error with code
MPSOLVER_MODEL_INVALID_SOLVER_PARAMETERS.
optional string solver_specific_parameters = 5;
- Returns
- The solverSpecificParameters.
Implements MPModelRequestOrBuilder.
Definition at line 1548 of file MPModelRequest.java.
| com.google.protobuf.ByteString getSolverSpecificParametersBytes |
( |
| ) |
|
|
inline |
Advanced usage. Solver-specific parameters in the solver's own format,
different for each solver. For example, if you use SCIP and you want to
stop the solve earlier than the time limit if it reached a solution that is
at most 1% away from the optimal, you can set this to "limits/gap=0.01".
Note however that there is no "security" mechanism in place so it is up to
the client to make sure that the given options don't make the solve
non thread safe or use up too much memory for instance.
If the option format is not understood by the solver, the request will be
rejected and yield an RPC Application error with code
MPSOLVER_MODEL_INVALID_SOLVER_PARAMETERS.
optional string solver_specific_parameters = 5;
- Returns
- The bytes for solverSpecificParameters.
Implements MPModelRequestOrBuilder.
Definition at line 1580 of file MPModelRequest.java.
| .lang.Override double getSolverTimeLimitSeconds |
( |
| ) |
|
|
inline |
Maximum time to be spent by the solver to solve 'model'. If the server is
busy and the RPC's deadline_left is less than this, it will immediately
give up and return an error, without even trying to solve.
The client can use this to have a guarantee on how much time the
solver will spend on the problem (unless it finds and proves
an optimal solution more quickly).
If not specified, the time limit on the solver is the RPC's deadline_left.
optional double solver_time_limit_seconds = 3;
- Returns
- The solverTimeLimitSeconds.
Implements MPModelRequestOrBuilder.
Definition at line 1398 of file MPModelRequest.java.
| .lang.Override boolean hasEnableInternalSolverOutput |
( |
| ) |
|
|
inline |
If this is set, then EnableOutput() will be set on the internal MPSolver
that solves the model.
WARNING: if you set this on a request to prod servers, it will be rejected
and yield the RPC Application Error code MPSOLVER_SOLVER_TYPE_UNAVAILABLE.
optional bool enable_internal_solver_output = 4 [default = false];
- Returns
- Whether the enableInternalSolverOutput field is set.
Implements MPModelRequestOrBuilder.
Definition at line 1456 of file MPModelRequest.java.
| boolean hasSolverSpecificParameters |
( |
| ) |
|
|
inline |
Advanced usage. Solver-specific parameters in the solver's own format,
different for each solver. For example, if you use SCIP and you want to
stop the solve earlier than the time limit if it reached a solution that is
at most 1% away from the optimal, you can set this to "limits/gap=0.01".
Note however that there is no "security" mechanism in place so it is up to
the client to make sure that the given options don't make the solve
non thread safe or use up too much memory for instance.
If the option format is not understood by the solver, the request will be
rejected and yield an RPC Application error with code
MPSOLVER_MODEL_INVALID_SOLVER_PARAMETERS.
optional string solver_specific_parameters = 5;
- Returns
- Whether the solverSpecificParameters field is set.
Implements MPModelRequestOrBuilder.
Definition at line 1528 of file MPModelRequest.java.
| .lang.Override boolean hasSolverTimeLimitSeconds |
( |
| ) |
|
|
inline |
Maximum time to be spent by the solver to solve 'model'. If the server is
busy and the RPC's deadline_left is less than this, it will immediately
give up and return an error, without even trying to solve.
The client can use this to have a guarantee on how much time the
solver will spend on the problem (unless it finds and proves
an optimal solution more quickly).
If not specified, the time limit on the solver is the RPC's deadline_left.
optional double solver_time_limit_seconds = 3;
- Returns
- Whether the solverTimeLimitSeconds field is set.
Implements MPModelRequestOrBuilder.
Definition at line 1380 of file MPModelRequest.java.
| Builder setEnableInternalSolverOutput |
( |
boolean |
value | ) |
|
|
inline |
If this is set, then EnableOutput() will be set on the internal MPSolver
that solves the model.
WARNING: if you set this on a request to prod servers, it will be rejected
and yield the RPC Application Error code MPSOLVER_SOLVER_TYPE_UNAVAILABLE.
optional bool enable_internal_solver_output = 4 [default = false];
- Parameters
-
| value | The enableInternalSolverOutput to set. |
- Returns
- This builder for chaining.
Definition at line 1486 of file MPModelRequest.java.
| Builder setSolverSpecificParameters |
( |
java.lang.String |
value | ) |
|
|
inline |
Advanced usage. Solver-specific parameters in the solver's own format,
different for each solver. For example, if you use SCIP and you want to
stop the solve earlier than the time limit if it reached a solution that is
at most 1% away from the optimal, you can set this to "limits/gap=0.01".
Note however that there is no "security" mechanism in place so it is up to
the client to make sure that the given options don't make the solve
non thread safe or use up too much memory for instance.
If the option format is not understood by the solver, the request will be
rejected and yield an RPC Application error with code
MPSOLVER_MODEL_INVALID_SOLVER_PARAMETERS.
optional string solver_specific_parameters = 5;
- Parameters
-
| value | The solverSpecificParameters to set. |
- Returns
- This builder for chaining.
Definition at line 1610 of file MPModelRequest.java.
| Builder setSolverSpecificParametersBytes |
( |
com.google.protobuf.ByteString |
value | ) |
|
|
inline |
Advanced usage. Solver-specific parameters in the solver's own format,
different for each solver. For example, if you use SCIP and you want to
stop the solve earlier than the time limit if it reached a solution that is
at most 1% away from the optimal, you can set this to "limits/gap=0.01".
Note however that there is no "security" mechanism in place so it is up to
the client to make sure that the given options don't make the solve
non thread safe or use up too much memory for instance.
If the option format is not understood by the solver, the request will be
rejected and yield an RPC Application error with code
MPSOLVER_MODEL_INVALID_SOLVER_PARAMETERS.
optional string solver_specific_parameters = 5;
- Parameters
-
| value | The bytes for solverSpecificParameters to set. |
- Returns
- This builder for chaining.
Definition at line 1661 of file MPModelRequest.java.
| Builder setSolverTimeLimitSeconds |
( |
double |
value | ) |
|
|
inline |
Maximum time to be spent by the solver to solve 'model'. If the server is
busy and the RPC's deadline_left is less than this, it will immediately
give up and return an error, without even trying to solve.
The client can use this to have a guarantee on how much time the
solver will spend on the problem (unless it finds and proves
an optimal solution more quickly).
If not specified, the time limit on the solver is the RPC's deadline_left.
optional double solver_time_limit_seconds = 3;
- Parameters
-
| value | The solverTimeLimitSeconds to set. |
- Returns
- This builder for chaining.
Definition at line 1416 of file MPModelRequest.java.