Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The CP-SAT solution in VRP Routing Solver is not returned #4439

Open
chenyw1994 opened this issue Nov 14, 2024 · 0 comments
Open

The CP-SAT solution in VRP Routing Solver is not returned #4439

chenyw1994 opened this issue Nov 14, 2024 · 0 comments
Assignees
Labels
Solver: CP-SAT Solver Relates to the CP-SAT solver
Milestone

Comments

@chenyw1994
Copy link

What version of OR-Tools and what language are you using?
Version: v9.11
Language: Python

Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
VRP routing solver + CP-SAT

What operating system (Linux, Windows, ...) and version?
macos

What did you do?
Steps to reproduce the behavior:

  1. I builded a very simple vrp model by using pywrapcp.RoutingModel()
  2. Set search_parameters.use_cp_sat = BOOL_TRUE and search_parameters.use_cp = BOOL_TRUE to force the solver to use the CP-SAT
  3. I call "solution = routing.SolveWithParameters(search_parameters)"
  4. CP-SAT get the optimal solution. I can see the logs: CpSolverResponse summary: \n status: OPTIMAL
  5. But the result of CP-SAT not in 'solution' and solution.status() == 3 which means routing fail.

What did you expect to see
I can get the CP-SAT results.

Make sure you include information that can help us debug (full error message, model Proto).

Anything else we should know about your project / environment

@Mizux Mizux added the Solver: CP-SAT Solver Relates to the CP-SAT solver label Nov 14, 2024
@Mizux Mizux added this to the v10.0 milestone Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Solver: CP-SAT Solver Relates to the CP-SAT solver
Projects
None yet
Development

No branches or pull requests

3 participants