Skip to content
This repository has been archived by the owner on May 10, 2023. It is now read-only.

Why not to have a time window for the pickup and for the delivery steps? #49

Closed
garciparedes opened this issue Oct 13, 2019 · 0 comments
Assignees
Labels
approved This issue is currently approved but waiting to be solved. enhancement New feature or request programming This issue is related with source code implementation.
Milestone

Comments

@garciparedes
Copy link
Owner

Is your feature request related to a problem? Please describe.
In the current implementation, there is only one time window (earliest and latest attributes) stored in the Trip object. In the Cordeau's Dial-a-Ride model there can be two types of time windows, the inbound and the outbound tasks so in the current implementation there is also a inbound boolean attribute that is in charge to give the proper meaning to the earliest and latest attributes.

Describe the solution you'd like
An easy way to clarify concepts and be more flexible can be to have two time windows for each Trip. One which represents the pickup's time window and another which represent the delivery's time window. An interesting naming scheme can be pickup_earliest, pickup_latest and delivery_earliest, delivery_latest.

Describe alternatives you've considered
One possible alternative (or extension) that could be implemented through a future issue can be to encapsulate the respective time window and position (for pickup and for delivery) in to a new object.

Additional context
This issue is strictly related with #48.

@garciparedes garciparedes added enhancement New feature or request approved This issue is currently approved but waiting to be solved. programming This issue is related with source code implementation. labels Oct 13, 2019
@garciparedes garciparedes self-assigned this Oct 13, 2019
garciparedes added a commit that referenced this issue Oct 19, 2019
* Included "Trip.destination_duration". #49
garciparedes added a commit that referenced this issue Oct 19, 2019
garciparedes added a commit that referenced this issue Oct 19, 2019
garciparedes added a commit that referenced this issue Oct 19, 2019
* Renamed "Trip.destination" to "Trip.destination_position". #49
@garciparedes garciparedes mentioned this issue Oct 21, 2019
garciparedes added a commit that referenced this issue Oct 21, 2019
@garciparedes garciparedes reopened this Oct 25, 2019
garciparedes added a commit that referenced this issue Oct 25, 2019
@garciparedes garciparedes mentioned this issue Oct 25, 2019
10 tasks
@garciparedes garciparedes added this to the r0.1.0 milestone Jan 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved This issue is currently approved but waiting to be solved. enhancement New feature or request programming This issue is related with source code implementation.
Projects
None yet
Development

No branches or pull requests

1 participant