loadsPerTour

open override val loadsPerTour: ResponseCIfc?(source)

How many loads each completed round carried.

The tour-level twin of the body's LoadsPerLoadedMove, and the two answer the same question at different scales: whether the room is being used, and whether the dispatcher is filling it. A fleet whose loaded moves average two but whose tours average two as well is consolidating within a round and never batching across one, which is a dispatching finding rather than a physical one.

It is here rather than on the body because a tour is not physical: a substrate knows nothing about rounds, only about journeys.