-
Notifications
You must be signed in to change notification settings - Fork 22
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
Support relations in split & partitions #145
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
senhalil
force-pushed
the
feat/support_pud_in_split
branch
3 times, most recently
from
March 1, 2021 09:30
a0b22ea
to
53e86ae
Compare
senhalil
force-pushed
the
feat/support_pud_in_split
branch
3 times, most recently
from
March 10, 2021 17:17
0ae2c5c
to
cc891fe
Compare
senhalil
force-pushed
the
feat/support_pud_in_split
branch
2 times, most recently
from
March 16, 2021 15:46
8452622
to
396e841
Compare
senhalil
force-pushed
the
feat/support_pud_in_split
branch
2 times, most recently
from
March 16, 2021 16:31
5f36405
to
5c0ee9f
Compare
senhalil
requested review from
braktar and
fonsecadeline
and removed request for
fonsecadeline
March 16, 2021 16:42
senhalil
force-pushed
the
feat/support_pud_in_split
branch
from
March 17, 2021 10:36
5c0ee9f
to
44744fe
Compare
senhalil
commented
Mar 17, 2021
fonsecadeline
approved these changes
Mar 19, 2021
braktar
reviewed
Mar 24, 2021
braktar
approved these changes
Mar 24, 2021
LINKING_RELATIONS := Relations that link multiple services to be on the same route ( order, same_route, sequence, shipment ) are supported in split_solve algorithm (`max_split_size`) and partitions (`[:configuration][:preprocessing][:partitions]`) FORCING_RELATIONS := Relations that force multiple services/vehicle to stay in the same VRP ( vehicle_trips, meetup, minimum_duration_lapse, maximum_duration_lapse, minimum_day_lapse, maximum_day_lapse ) are respected by split_solve (`max_split_size`) algorithm
senhalil
force-pushed
the
feat/support_pud_in_split
branch
from
March 25, 2021 14:22
f2fd2b6
to
0131ee1
Compare
senhalil
changed the title
Support pud in split & partitions
Support relations in split & partitions
Mar 31, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds relations support to split_solve & partitions
LINKING_RELATIONS := Relations that link multiple services to be on the same route
(order, same_route, sequence, shipment) are supported in
split_solve algorithm (
max_split_size
) andpartitions (
[:configuration][:preprocessing][:partitions]
)FORCING_RELATIONS := Relations that force multiple services/vehicle to stay in the same VRP
(vehicle_trips, meetup, minimum_duration_lapse, maximum_duration_lapse, minimum_day_lapse, maximum_day_lapse)
are respected by split_solve (
max_split_size
) algorithmCloses 291, 544, 564, 634