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

Consideration of pickup/delivery duration --> Missing Events? #174

Open
kt86 opened this issue Nov 17, 2023 · 0 comments
Open

Consideration of pickup/delivery duration --> Missing Events? #174

kt86 opened this issue Nov 17, 2023 · 0 comments

Comments

@kt86
Copy link
Contributor

kt86 commented Nov 17, 2023

It looks to me, that in the simulation results it gets a bit confused, when to add the time needed for loading/unloading the goods.
This needs to be sorted out.
I assume that this is also an issue due to the fact, that the carrier internally works with Services instead of Shipments

See e.g. the MultipleShipmentsCompleteLSPMobsimTest:

For the LspShipment it is defined as follows:
grafik

  • During Collection it has the 180 sec as Service duration for loading. But there is information for unloading at the hub. (There is also no event, that the good has arrived because services do not arrive) --> this is totally contrary to the definition.
  • The main run has the service-Event at the end of the transport, but no information for loading the goods into the vehicle. Here
  • In Distribution the service is at the dropoff, and this takes the 180s. But here also the information is missing, that the goods are loaded into the vehicle.

Re main run: I am not sure whether it is possible to "loading"/"pickup"event, or not. Here we do not have any jsprit logic, so we may get the information from somewhere early enough.

Re distribution run: I think it is not possible to add another "loading"/"pickup"event (and consider any additional duration for the laoding in the simultion) so easily. This is because services only has on time, and we get some information once, the Service started event is thrown, which is presumable too late to throw another event.

Conclusion: For me it gets more and more clear, that we need to change the internal logic from Servicesth Shipments. Then we have by default pickup and dropoff events, and their duration is part of the planning. see e.g. #44

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

No branches or pull requests

1 participant