Update: Concept and Operation of the Performance Data Analysis and Reporting System (PDARS)
Bibliographic record
Abstract
This paper contains a factual update to the concept and operation of the performance data analysis and reporting system (PDARS) paper originally presented at the SAE conference, Montreal Canada, 2003 by den Braven and Schade. Since 1999 the Federal Aviation Administration (FAA) has been operating a system for the collection, analysis, and reporting of performance-related data from the National Airspace System (NAS). This performance data analysis and reporting system (PDARS) has been installed at twenty Air Route Traffic Control Centers (ARTCCs), nineteen Terminal Radar Approach Control facilities (TRACONs), three service area offices, the FAA's Air Traffic Control System Command Center in Herndon, Virginia and FAA Headquarters offices in Washington, DC. The system generates and distributes close to 1000 reports daily for these facilities. PDARS calculates a range of performance measures, including traffic counts, travel times, travel distances, traffic flows, and in-trail separations. It turns these measurement data into information useful to FAA facilities through a2n architecture that features (1) automatic collection and analysis of radar tracks and flight plans, (2) automatic generation and distribution of daily morning reports, (3) sharing of data and reports among facilities, and (4) support for exploratory and causal analysis. PDARS applications at FAA facilities include performance measurement, route and airspace design, noise abatement analysis, traffic flow management initiative assessment and design, training, and support for search and rescue. PDARS has also been used in a range of FAA and NASA studies. Examples are the measurement of actual benefits of the Dallas/Fort Worth (DFW) Metroplex airspace, an analysis of the Los Angeles Arrival Enhancement Procedure (AEP), an analysis of the Phoenix Dryheat departure procedure, measurement of navigation accuracy of aircraft using area navigation (RNAV) en route, a study on the detection and analysis of in-close approach changes, an evaluation of the benefits of domestic reduced vertical separation minimum implementation, and a baseline study for the airspace flow program.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.034 | 0.092 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.009 | 0.007 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.016 | 0.018 |
| Open science | 0.007 | 0.007 |
| Research integrity | 0.005 | 0.005 |
| Insufficient payload (model declined to judge) | 0.032 | 0.058 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".