SolvingMode

  • The DEFAULT_SOLVE mode solves the model and may issue warnings in the OptimizeToursResponse.validation_errors.

  • The VALIDATE_ONLY mode validates the model without solving, populating as many OptimizeToursResponse.validation_errors as possible.

  • The DETECT_SOME_INFEASIBLE_SHIPMENTS mode identifies some infeasible shipments during preprocessing, populating OptimizeToursResponse.validation_errors or OptimizeToursResponse.skipped_shipments, but does not solve the request.

  • Invalid requests in modes other than VALIDATE_ONLY will result in an INVALID_REQUEST error.

  • The maximum number of validation errors returned can be capped using maxValidationErrors.

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 OptimizeToursResponse.validation_errors or OptimizeToursResponse.skipped_shipments, and doesn't actually solve the rest of the request (status and routes are unset in the response). If infeasibilities in injectedSolutionConstraint routes are detected they are populated in the OptimizeToursResponse.validation_errors field and OptimizeToursResponse.skipped_shipments is left empty.

IMPORTANT: not all infeasible shipments are returned here, but only the ones that are detected as infeasible during preprocessing.