MétaCan
Menu
Back to cohort
Record W2257381655 · doi:10.5539/jmsr.v5n2p65

The Dynamic Behaviour of the Floor of a Surrogate Vehicle Under Explosive Blast Loading

2016· article· en· W2257381655 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of Materials Science Research · 2016
Typearticle
Languageen
FieldEngineering
TopicStructural Response to Dynamic Loads
Canadian institutionsnot available
FundersImperial College LondonRoyal British Legion
KeywordsExplosive materialStructural engineeringComputer simulationMaterials scienceComputer scienceSimulationEngineering

Abstract

fetched live from OpenAlex

<p class="1Body">Improvised Explosive Devices have been the signature weapon in the recent conflicts in Iraq and Afghanistan. High-rate axial forces exerted by the vehicle floor to the lower limbs of occupants have been the cause of severe injuries. In order to gain a greater understanding of the mechanisms of these injuries so that countermeasures can be developed, one is required to know how the vehicle floor behaves; therefore, the purpose of this study was to characterise the behaviour of a vehicle floor surrogate to a range of explosive loads. Explosive loads between 1 and 6 kg TNT were detonated beneath a vehicle floor surrogate resulting in peak floor velocities between 5.8 and 80.5 m/s reached in a time between 0.10 and 3.13 ms. The data can now be used to (a) test numerical models of blast and its interaction with structures for validity, and (b) ensure that the velocity profiles replicated in a laboratory environment to understand human tolerance to injury are relevant to the blast process. These will ensure that preventive measures are developed based on realistic physical and numerical models of injury.</p>

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.005
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.037
Threshold uncertainty score0.486

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.001
Scholarly communication0.0000.000
Open science0.0010.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.034
GPT teacher head0.334
Teacher spread0.300 · 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