Crash/Near-Crash Analysis of Naturalistic Driving Data Using Association Rule Mining
Bibliographic record
Abstract
This study explores the associations between crash/near-crash (C/NC) events and roadway, driver-related, and environmental factors in naturalistic driving studies (NDS). We used the Naturalistic Engagement in Secondary Tasks (NEST) dataset, which is massive and detailed and contains 50 million miles of naturalistic driving data resulting from the Strategic Highway Research Program 2 (SHRP2). Association rule mining (ARM) is applied to extract the rules for frequently occurring events. The generated association rules are filtered by four metrics (support, confidence, lift, and conviction) and validated by the lift increase criterion. A three-step analysis is performed to obtain a comprehensive understanding of the rules of C/NC events. The 20 most frequent items are first selected to investigate their relationship with the C/NC events. Subsequently, the association rules are used to identify the factors contributing to C/NC events. Finally, correlations between contributing factors and different severities of crashes (I—most severe, II—police-reportable, III—minor crash, and IV—low-risk tire strike) are analyzed by ARM. The results demonstrate that C/NC events occur most frequently on straight and level road segments with no controlled intersections or traffic control devices when drivers are performing secondary tasks. Thus, the reasons for these crashes are carelessness and overconfidence. In addition, a median strip or barrier and a wider road can significantly reduce the frequency and severity of crash events. Moreover, gender, age, average annual mileage, and secondary tasks are highly correlated with the frequency and severity of C/NC events. Drivers with visual-spatial disabilities or crash records are more likely to be involved in the most severe crash events. Near-crash events occur more frequently at higher traffic density and on roads with traffic control devices and controlled intersections. These conditions may keep drivers alert, preventing crashes.
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.002 | 0.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.005 | 0.004 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
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".