Lessons learned from an explosion in a large fractionator
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.
Bibliographic record
Abstract
Abstract During plant start‐up, a critical interface exists at block valves located at battery limits of process units. A relatively small leak at a battery‐limit isolation point was established as the source of gas that caused an explosion in a 26‐foot diameter fractionator on a Fluid Coker nearing the end of a maintenance turn a round. This incident could easily have occurred in any modern oil refinery or chemical plant. This paper shares the technology and learning associated with small release scenarios that are often overlooked in large‐scale plant operations. The explosion event did not damage the fractionator shell, but displaced all but two of the sieve trays in the column, and produced minor damage in the overhead condensers and receiver drum. Importantly, the consequent down‐time resulted in a major production loss. Damage analysis supports the proposition that a deflagration occurred in the top portion of the fractionator involving under 50 lbs. of fuel. It is believed that relatively small leaks, persisting over a period of a few hours, supplied the required amount of fuel. The accident investigation identified multiple potential pathways whereby natural gas leaking past battery limit block valves could have reached the fractionator. This incident highlights the importance of securing leak tight connections between active and inactive sections of process systems. As a result of this experience, several procedural and organizational reforms have been instituted.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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 it