-
Notifications
You must be signed in to change notification settings - Fork 73
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
Violation on optional break window #129
Comments
Thanks! Seems related to usage of offset break and departure time optimization. I've changed validation rule to address this. Essentially, you need to disable departure time optimization for that vehicle by setting shift.start.latest = shift.start.earliest if time offset on break is used |
Thanks for quick responses! The reason for that is an irl regulation where drivers have to make a break after maximum 4hrs of driving for minimum 30mins, so next break depends on when last has ended |
Hi, at the moment, there is no workaround as this is a limitation due to implementation. |
This release combines many changes, but essentials are: - internal route state api simplification - increased performance - several experimental features - bug fixes * original job place index in activity place to simplify activity-job place matching * `experimental`: a new type of location in pragmatic format to model zero distance/duration from it to any other location. This could be useful to model optional vehicle start location. * allow user to pass alternative objectives in goal context to guide the search * `experimental`: a new `fast-service` objective function to serve jobs as soon as possible * experimental `dispatch` feature * apply code style refactoring * improve selection sampling search * update dependencies * improve a bit documentation * refactor route state * do not use hashmaps to store activity states * double reload assignment when initial solution is used (#126) * unexpected total_order behavior in dynamic heuristic (#128) * improve validation rule for break with time offset (#129) * fix issue with skills (#133) * do not cluster jobs if they are defined in relations (#141)
Version: 1.22.1
problem.json
Command:
vrp-cli solve pragmatic problem.json --out-result result.json --log --max-time 15 --min-cv sample,10000,0.05,true --parallelism 1,1
result.json
Expected:
Break is scheduled between
[3600,4000]
seconds after departure.Actual:
Break is scheduled
2340
seconds after departure (2019-07-04T12:36:40Z
-2019-07-04T11:57:40Z
)The text was updated successfully, but these errors were encountered: