MétaCan
Menu
Back to cohort
Record W4401633964 · doi:10.1109/ojvt.2024.3443630

Navigating the Handover: Reviewing Takeover Requests in Level 3 Autonomous Vehicles

2024· article· en· W4401633964 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueIEEE Open Journal of Vehicular Technology · 2024
Typearticle
Languageen
FieldEngineering
TopicTransportation and Mobility Innovations
Canadian institutionsWestern University
Fundersnot available
KeywordsHandoverComputer scienceComputer networkBusinessTelecommunications

Abstract

fetched live from OpenAlex

Autonomous vehicles (AVs) represent a transformative advance in automotive technology, promising increased safety and efficiency by reducing human error. However, integrating human factors remains a critical challenge, especially during takeover scenarios where the human driver must re-assume control of the vehicle. This review paper focuses on the <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">engineering and human-centred design of takeover requests (TORs) within Level 3 autonomous vehicles</i>, emphasizing the importance of seamless transitions between automated driving and manual control. We explore the concept of the Operational Design Domain (ODD), which dictates the specific conditions under which an AV may safely operate, and contextualize its role. Through a comprehensive analysis, we highlight how monitoring both the internal and external environment, and improving human-machine interfaces through the design of takeover requests (TOR), play pivotal roles in ensuring that transitions are safe and efficient. We argue for the necessity of integrating detailed human factors and ergonomic considerations to foster a human-centred approach in AV design. We aim to establish a symbiotic relationship between human drivers and autonomous systems, ensuring that AVs not only function optimally within their designated ODD, but also maintain high safety standards during critical takeover moments.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.690
Threshold uncertainty score0.454

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.037
GPT teacher head0.315
Teacher spread0.278 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it