SolvingMode

  • The solver's behavior is determined by the selected mode, with modes other than VALIDATE_ONLY returning an INVALID_REQUEST error for invalid requests.

  • DEFAULT_SOLVE solves the model and may provide warnings in OptimizeToursResponse.validation_errors.

  • VALIDATE_ONLY solely validates the model, populating OptimizeToursResponse.validation_errors with as many errors as possible.

  • DETECT_SOME_INFEASIBLE_SHIPMENTS focuses on identifying and populating infeasible shipments into OptimizeToursResponse.validation_errors or OptimizeToursResponse.skipped_shipments without fully solving the request, but it doesn't find all infeasible shipments.

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.