AI-generated Key Takeaways
-
Defines how the solver processes the request, dictating whether it solves the model, validates it, or detects infeasible shipments.
-
Offers three modes:
DEFAULT_SOLVEfor solving,VALIDATE_ONLYfor validation, andDETECT_SOME_INFEASIBLE_SHIPMENTSfor identifying problematic shipments. -
In all modes except
VALIDATE_ONLY, invalid requests will return anINVALID_REQUESTerror, with potential for controlling the number of error messages. -
The
DETECT_SOME_INFEASIBLE_SHIPMENTSmode focuses on pre-processing infeasibility detection without fully solving the problem.
Defines how the solver should handle the request. In all modes but VALIDATE_ONLY
, if the request is invalid, you will receive an INVALID_REQUEST
error. See maxValidationErrors
to cap the number of errors returned.
| Enums | |
|---|---|
DEFAULT_SOLVE
|
Solve the model. Warnings may be issued in [OptimizeToursResponse.validation_errors][google.cloud.optimization.v1.OptimizeToursResponse.validation_errors]. |
VALIDATE_ONLY
|
Only validates the model without solving it: populates as many OptimizeToursResponse.validation_errors
as possible. |
DETECT_SOME_INFEASIBLE_SHIPMENTS
|
Only populates IMPORTANT : not all infeasible shipments are returned here, but only the ones that are detected as infeasible during preprocessing. |
TRANSFORM_AND_RETURN_REQUEST
|
This mode only works if Experimental: See https://developers.google.com/maps/tt/route-optimization/experimental/objectives/make-request for more details. |

