-
Notifications
You must be signed in to change notification settings - Fork 339
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
Vroom not finding a possible high priority route #1161
Comments
Thanks for sharing the data. What happens here is that for some reason none of the initial heuristic solutions we build contain shipments with priority. I can't really understand why since it's hard to reason on instances without locations (if you can share full instances, that would help). Then the local search phases do not manage to increase the priority score. This is very similar to the problem addressed back in #988 for job-based instances. The best way to make that happen on this kind of instance would be to extend the current Funny note: the changes made for #1155 favor priority when re-inserting stuff in ruined routes, so current |
Thanks very much for the fast response! I will try out the master branch version. |
As you mention, the matrix adjustments probably prevent to "normally" reach the high-priority solution in the first place. I was quite surprised that none of the heuristic solutions did include a non-zero priority shipments, that would be the reason. Related: if you want to use pre-planned routes, you should check out the |
I am submitting an input (input 1) to vroom using version 1.14. It is failing to find a route which has total priority 1200, instead finding a route of priority 0 (output 1). It does however find the high priority route when only the high priority orders are submitted (input 2, output 2). Is vroom first trying to optimise for priority, and if so why doesn't it find the high priority route?
input_2.json
output_2.json
input_1.json
output_1.json
The text was updated successfully, but these errors were encountered: