MétaCan
Menu
Back to cohort
Record W2965614339 · doi:10.1080/13588265.2019.1633818

Multibody system modelling of unmanned aircraft system collisions with the human head

2019· article· en· W2965614339 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 · 2019
Typearticle
Languageen
FieldMedicine
TopicAutomotive and Human Injury Biomechanics
Canadian institutionsLaurentian University
Fundersnot available
KeywordsCrashHybrid IIICollisionPoison controlCrash testMultibody systemSimulationNeck injuryHead (geology)Human-body modelExperimental dataComputer scienceEngineeringAutomotive engineeringAeronauticsArtificial intelligence

Abstract

fetched live from OpenAlex

Understanding the impact severity of unmanned aircraft system (UAS) collisions with the human body remains a challenge and is essential to the development of safe UAS operations. Complementary to performing experiments of UAS collisions with a crash dummy, a computational impact model is needed in order to capture the large variety of UAS types and impact scenarios. This article presents the development of a multibody system (MBS) model of a collision of one specific UAS type with the human body as well with a crash dummy. This specific UAS type has been chosen because data from experimental drop tests on a crash dummy is available. This allows the validation of the MBS model of UAS impacting a crash dummy versus experimental data. The validation shows that the MBS model closely matches experimental UAS drop tests on a crash dummy. Subsequently, the validated UAS MBS model is applied to predict human body injury using a biomechanical human body model. Head and neck injury from the frontal, side and rear impact on the human head are predicted at various elevation angles and impact velocities. The results show that neck injury is not a concern for this specific UAS type, but a serious head injury is probable.

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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.447
Threshold uncertainty score0.380

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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
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.024
GPT teacher head0.300
Teacher spread0.275 · 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