MétaCan
Menu
Back to cohort
Record W3193337379 · doi:10.1002/prs.12298

Living with oversized <scp>spring‐loaded</scp> vapor relief valves

2021· article· en· W3193337379 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

VenueProcess Safety Progress · 2021
Typearticle
Languageen
FieldMaterials Science
TopicEngineering and Material Science Research
Canadian institutionsSmiths Detection (Canada)
Fundersnot available
KeywordsRelief valveOverpressureSymptom reliefStress reliefFull serviceEnvironmental scienceEngineeringPoor reliefForensic engineeringMechanical engineeringMaterials scienceBusinessMedicineSurgeryPhysicsLawComposite material

Abstract

fetched live from OpenAlex

Abstract Pressure relief valves are installed on pressurized systems to mitigate consequences related to excessive pressure. Since relief valves come in discrete sizes, a relief system designer specifies a relief device with a rated capacity greater than the largest required relief rate. An oversized relief device is one in which a credible overpressure scenario exists; that is, the relief device capacity is more than a multiple (typically five times) the scenario's required relief rate. Most systems have more than one credible overpressure scenario (e.g., external fire or blocked outlet). In some other cases, installations in vapor service have been identified with an oversized relief device concern, without verification of whether or not these installations have a history of instability‐related damage (e.g., excessive relief device damage). Typically damage from oversized vapor relief devices is less severe than chatter which is caused by the coupling of the inlet line and the relief device, not the flow through the relief device. Some owners/operators have specified that oversized relief devices require mitigation. However, this paper shows why an oversized relief device in vapor service may not require mitigation.

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.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.018
Threshold uncertainty score0.799

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
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.011
GPT teacher head0.269
Teacher spread0.258 · 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