Time
Demand carrier that maps each (filler, sender) edge to its own transport-time distribution. A single demand filler can serve many senders; a sender can be served by multiple fillers — but each (filler, sender) pair has at most one configured time.
Demands whose (filler, sender) pair has no configured time are either rejected with NoCarrierOptionException or, if immediateTransportFlag is true, shipped and delivered immediately (zero simulated time).
Parameters
the parent model element
optional model-element name
See sc.transportlayer.TimeBasedNetworkDemandCarrier
Properties
When true, demands whose (filler, sender) pair has no configured transport time are shipped and delivered immediately (zero simulated time) instead of throwing NoCarrierOptionException. Default false.
Read-only view of the amount-in-transit response.
Read-only view of the per-shipment transit-time response.
Functions
Attach sender to every currently registered filler with the shared zero-delay edge.
Side-effect-free probe: returns true iff demand would route successfully under the carrier's current configuration. A false result indicates transportDemand would either throw or silently drop the demand. Useful as a self-guard inside carrier implementations and as a configuration test from external code.
Register a zero-delay transport edge between filler and sender. The shared myNoDelayRV is reused for efficiency.
Register a transport-time distribution on the (filler, sender) edge. If a previous edge used the shared zero-delay RV, it is replaced with a fresh RandomVariable wrapping distribution.
Transport demand from its origin to its destination.