MétaCan
Menu
Back to cohort
Record W2951205712 · doi:10.1080/13588265.2020.1807687

Modelling head injury due to unmanned aircraft systems collision: Crash dummy vs human body

2020· article· en· W2951205712 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

VenueInternational Journal of Crashworthiness · 2020
Typearticle
Languageen
FieldMedicine
TopicAutomotive and Human Injury Biomechanics
Canadian institutionsLaurentian University
Fundersnot available
KeywordsHybrid IIICrashCollisionNeck injuryPoison controlCrash testHead (geology)Human-body modelSimulationAeronauticsComputer scienceAutomotive engineeringPhysical medicine and rehabilitationEngineeringMedicineGeologyComputer securityEmergency medicineArtificial intelligence

Abstract

fetched live from OpenAlex

Recent developments in the concept of UAS operations in urban areas have led to risk concerns of UAS collision with human. To better understand this risk, head and neck injuries due to UAS collisions have been investigated by different research teams using crash dummies. Because of the limitations in biofidelity of a crash dummy, head injury level for a crash dummy impact may differ from the human body impact. Therefore, the aim of this paper is to investigate differences in head and neck injuries subject to UAS collision between an often-used Hybrid III crash dummy and a human body. To perform such investigation, multibody system (MBS) impact models have been used to simulate UAS impacts on validated models of the Hybrid III crash dummy and the human body at various impact conditions. The findings show that the Hybrid III predicts similar head and neck injury compared to the human body when UAS collides horizontally from front and rear. However, the Hybrid III over-predicts head injury due to horizontal side impact. Moreover, under vertical drop and 45 degree elevated impact of UAS, the Hybrid III under-predicts head injury, and over-predicts neck injury.

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.000
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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.200
Threshold uncertainty score0.987

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
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.038
GPT teacher head0.332
Teacher spread0.294 · 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