Skip to content

Path Class Detail

The path_class_detail database table stores details about the results of the simulation at the path-class level.

The table is created by the create_table_path_class_detail function, and (potentially) populated during a simulation run. To be populated with data, one of the follow flags must be set on Config.db.write_items:

  • "pathclass": The table will be populated at each DCP during the simulation.

  • "pathclass_final": The table will be populated only at the end of each sample (i.e. DCP 0) during the simulation

Table Schema

Column Data Type Description
scenario VARCHAR(20) NOT NULL Scenario name 1
iteration INT NOT NULL
trial INT NOT NULL
sample INT NOT NULL Sample number within trial
rrd INT NOT NULL Days before departure
path_id INT NOT NULL Unique identifier for a given path
booking_class VARCHAR(10) NOT NULL Booking class name
sold INT Number of seats sold at this point in time
revenue FLOAT Revenue attributed to this bucket from seats sold
untruncated_demand FLOAT
forecast_mean FLOAT
forecast_stdev FLOAT
forecast_closed_in_tf FLOAT
forecast_closed_in_future FLOAT
updated_at DATETIME NOT NULL Time each row was written to the database

  1. The scenario name should be a string, and a unique name should be used for each unique scenario, which allows multiple scenarios to be saved in the same database. When using SQLite (the default database engine) it is preferred to simply create a new database file for each unique scenario, but this database schema is designed to accommodate other database engines where that may be inconvenient. ↩