MétaCan
Menu
Back to cohort
Record W1999984627 · doi:10.2514/6.2004-3420

Satisfying Temperature Firing Requirements for Ordnance Devices

2004· article· en· W1999984627 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

Venue40th AIAA/ASME/SAE/ASEE Joint Propulsion Conference and Exhibit · 2004
Typearticle
Languageen
FieldEngineering
TopicEngineering and Test Systems
Canadian institutionsLockheed Martin (Canada)
Fundersnot available
KeywordsComputer scienceTemperature measurementPhysicsThermodynamics

Abstract

fetched live from OpenAlex

Ordnance devices have requirements to be fired at temperature for many programs. The intent of this paper is to provide material for discussion exploring this issue, how the requirement is frequently interpreted for implementation, rationale addressing that interpretation, and unique methods utilized to satisfy the requirement. Many programs allow temperature-conditioned devices to be fired outside the conditioning chamber for a variety of reasons. If this approach is implemented thoughtfully it will not invalidate results gained from testing, but at the same time there have been cases of supplier(s) who take advantage of this interpretation in such a manner as to produce successful results from a device that would not meet requirements if fired at the actual high or low temperature. The paper will discuss justification for firing devices outside the conditioning chamber and when it is important to maintain the correct device temperature until actual firing occurs, and will present some unique means used to ensure correct device temperature is maintained until firing.

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 categoriesMeta-epidemiology (narrow)
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.361
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
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.032
GPT teacher head0.241
Teacher spread0.209 · 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