Non-Mandatory Tour Scheduling

The non-mandatory tour scheduling model selects a tour departure and duration period (and therefore a start and end period as well) for each non-mandatory tour. This model uses person time_windows. Includes support for representative_logsums.

The main interface to the non-mandatory tour purpose scheduling model is the non_mandatory_tour_scheduling function. This function is registered as an Inject step in the example Pipeline.

Structure

• Configuration File: non_mandatory_tour_scheduling.yaml

• Core Table: tours

• Result Field: start, end, duration

• Skims Keys: TAZ, destination, MD time period, MD time period

Examples

• Prototype ARC

Implementation

activitysim.abm.models.non_mandatory_scheduling.non_mandatory_tour_scheduling(state: State, tours: DataFrame, persons_merged: DataFrame, tdd_alts: DataFrame) → None

This model predicts the departure time and duration of each activity for non-mandatory tours