Carriers¶
carriers¶
This table gives you an overview of each carrier’s results, with one row per carrier. It brings together revenue, passenger counts, capacity, and measures such as load factor and revenue per available seat mile. It is a useful starting point when you want to compare carriers or see how a change in the simulation affects their overall performance.
Most of the traffic and revenue measures are averages across samples, excluding burned samples. Keep in mind that an itinerary passenger and a leg passenger are different counts: someone taking a two-leg connecting trip makes one booking but occupies a seat on two legs. The table includes both views, as well as two ways to calculate load factor: an average across individual legs and a system-wide measure weighted by distance.
Access this table as summary.carriers.
Index¶
Field |
Type |
Meaning |
|---|---|---|
|
string |
Carrier code. |
Columns¶
Field |
Type |
Meaning |
|---|---|---|
|
string |
Carrier inventory-control mode. |
|
number |
Ticket revenue per retained sample. |
|
number |
Itinerary passengers per retained sample; connections count once. |
|
integer |
Carrier truncation rule identifier. |
|
number |
Unweighted average of individual leg load factors, in percent. |
|
number |
Available seat miles per retained sample. |
|
number |
Revenue passenger miles per retained sample. |
|
number |
Sum of ancillary price times sold counters at extraction; not normalized by the summary sample count. |
|
number |
Local leg passengers per retained sample. |
|
number |
Total leg passengers per retained sample; connections count on every leg. |
|
number |
Continuously priced passengers per retained sample. |
|
number |
Continuously priced ticket revenue per retained sample. |
|
string or null |
Revenue-management system name from carrier metadata. |
|
number |
|
|
number |
|
|
number |
|
|
number |
Distance-weighted system load factor, |
|
number |
|
|
number |
|
Activation¶
PassengerSim collects this information automatically during a normal simulation run. You do not need
to enable database recording or add the table to
outputs.reports.
There is no separate on/off switch for collecting this table. If you only want to leave it out of the returned summary, you can use selecting extracted tables to choose which tables to include.