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

Let VROOM group duration (as optional) based on same contiguous location #608

Closed
mhosman opened this issue Nov 8, 2021 · 2 comments
Closed

Comments

@mhosman
Copy link

mhosman commented Nov 8, 2021

Let's say I have 100 jobs and 3 of them have the same location and are optimized by VROOM to be done in a row, in the same stop. There are also other scenarios that we have jobs with the same location but are not part of the same stop, but let's talk about the first scenario (1 stop). Now let's say each job duration is 5 minutes. Right now VROOM is gonna return the three jobs and is gonna put 5 minutes per each job. The idea/suggestion is to put 5 minutes for the same stop (all this 3 jobs together).

Why?
Sometimes you have pickups, deliveries, jobs, etc, from distinct orders and same locations, but and you don't know when you should group them or not (this is done by VROOM). So... maybe for those scenarios, it could be great to group those values.

@mhosman mhosman changed the title Let VROOM merge duration (as optional) based on same contiguous location Let VROOM group duration (as optional) based on same contiguous location Nov 8, 2021
@jcoupey
Copy link
Collaborator

jcoupey commented Nov 9, 2021

This has been discussed in #358 and we introduced the notion of "setup" time for that exact purpose in #547. See https://github.com/VROOM-Project/vroom/blob/master/docs/API.md#task-setup-times.

@jcoupey jcoupey closed this as completed Nov 9, 2021
@mhosman
Copy link
Author

mhosman commented Nov 10, 2021

Thank you @jcoupey !!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants