MétaCan
Menu
Back to cohort
Record W583838366 · doi:10.1139/l08-059

Anticipating the post-blast condition of structuresThis article is one of a selection of papers published in the Special Issue on Blast Engineering.

2009· article· en· W583838366 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

VenueCanadian Journal of Civil Engineering · 2009
Typearticle
Languageen
FieldEngineering
TopicStructural Response to Dynamic Loads
Canadian institutionsnot available
Fundersnot available
KeywordsEngineering design processEngineeringFacadeSelection (genetic algorithm)Process (computing)Construction engineeringArchitectural engineeringForensic engineeringComputer scienceStructural engineeringMechanical engineering

Abstract

fetched live from OpenAlex

Designers charged to develop blast-resistant structural designs must be able to address the technical aspects of the explosion process and provide structural components with sufficient strength and ductility to resist the applied pressures. The blast environment is different from those of other loads with which designers deal, and uncertainties about the actual response of structures often are higher. For these reasons, designers often have less confidence in their abilities to explain to their clients their expectations about the actual response of the building to a blast event. This paper identifies some elements of the conventional design process that do not translate directly to blast-resistant design, reasons why uncertainties in performance expectations differ from those encountered with other load sources, and the need to understand and acknowledge residual risks for the facade, the structure, and the safety of the occupants of blast resistant buildings.

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.001
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.613
Threshold uncertainty score0.946

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
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.0010.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.004
GPT teacher head0.187
Teacher spread0.183 · 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