You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2024. It is now read-only.
Currently, the DistributionCarrierScheduler creates one or more* carrier_s_ to distribute the incoming LSPShipments.
IMO this does not make sence, because it should be only one carrier, which can decide on its one, which LSPShipments were put in which tour. --> Need for an pickupTimeWindow, with earliest pickuptime = arrivalAtHub + handlingDuration in hub.
This is only possible with CarrierShipments, which has TimeWindows for Pickup and Delivery.
This will have consequences in the whole setup, because also the ScheduledShipmentLoad, ScheduledShipmentTransport, ScheduledShipmentUnload must accept CarrierServices (as is) OR CarrierShipments (missing).
Going from there, I expect the need for follow-up adaptions... argh :(
(( I started with it on branch: kmt_makeDeliveryUsingCarrierShipments ))
The text was updated successfully, but these errors were encountered:
Re-start working on this now....
As a first step, a new configGroup is added, allowing to set desired behavior. Default setting is "serviceBased" (see #261 )
To reduce the complexity, I am now checking, where the CarrierService is really needed (and why) in: ScheduledShipmentLoad, ScheduledShipmentTransport, ScheduledShipmentUnload. If I can rid of it there, it gets at least a bit less complex...
Currently, the
DistributionCarrierScheduler
creates one or more* carrier_s_ to distribute the incomingLSPShipment
s.IMO this does not make sence, because it should be only one carrier, which can decide on its one, which
LSPShipment
s were put in which tour. --> Need for anpickupTimeWindow
, with earliestpickuptime = arrivalAtHub + handlingDuration
in hub.This is only possible with
CarrierShipment
s, which has TimeWindows for Pickup and Delivery.This will have consequences in the whole setup, because also the
ScheduledShipmentLoad
,ScheduledShipmentTransport
,ScheduledShipmentUnload
must acceptCarrierService
s (as is) ORCarrierShipment
s (missing).Going from there, I expect the need for follow-up adaptions... argh :(
(( I started with it on branch: kmt_makeDeliveryUsingCarrierShipments ))
The text was updated successfully, but these errors were encountered: