MétaCan
Menu
Back to cohort
Record W4413363263 · doi:10.1002/prs.70012

Experimental evaluation of restricted lift effects on pressure relief valve stability and system dynamics

2025· article· en· W4413363263 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 · 2025
Typearticle
Languageen
FieldEngineering
TopicHydraulic and Pneumatic Systems
Canadian institutionsSmiths Detection (Canada)
Fundersnot available
KeywordsRelief valveLift (data mining)Control theory (sociology)Dynamics (music)EngineeringMechanicsComputer scienceMechanical engineeringPhysicsArtificial intelligence

Abstract

fetched live from OpenAlex

Abstract Restricting the lift of relief devices is seen as a solution to various challenges associated with installing pressure relief valves (PRVs), particularly in addressing high inlet pressure drops and meeting criteria set by standards such as API STD 520. Previous studies and industry presentations have suggested that restricted lift can mitigate issues related to oversized valves and excessive inlet losses. However, there is ongoing debate regarding its impact on PRV operational stability. This paper presents comprehensive test data showing that restricting the lift of a direct spring‐operated relief device does not improve valve stability in vapor/gas service. The data further indicate that stability is not influenced by the required relief rate. While restricted lift reduces capacity, it does not alter the valve's dynamic characteristics. These findings are consistent with earlier work reporting negligible effects on blowdown and valve performance when lift is restricted. Data from over 1500 tests suggest that the reduction in lift can help mitigate some negative system effects caused by valve instability. These results underscore the importance of understanding the trade‐offs involved in applying restricted lift as a strategy to address PRV installation challenges without assuming improved stability.

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.694
Threshold uncertainty score0.706

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.009
GPT teacher head0.267
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