Experimental evaluation of restricted lift effects on pressure relief valve stability and system dynamics
Bibliographic record
Abstract
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".