MétaCan
Menu
Back to cohort
Record W3009771866 · doi:10.3390/safety6010015

High-Pressure Hydrogen Sulfide Experiments: How Did Our Safety Measures and Hazard Control Work during a Failure Event?

2020· article· en· W3009771866 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueSafety · 2020
Typearticle
Languageen
FieldEngineering
TopicCombustion and Detonation Processes
Canadian institutionsUniversity of Calgary
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsFlammable liquidHydrogen sulfideHazardous wasteWaste managementHazardLeakEngineeringHazard analysisSour gasEnvironmental scienceWork (physics)Forensic engineeringPetroleum engineeringNatural gasChemistryReliability engineeringEnvironmental engineeringMechanical engineeringSulfur

Abstract

fetched live from OpenAlex

Hydrogen sulfide (H2S) is a hazardous, colorless, flammable gas with a distinct rotten-egg smell at low concentration. Exposure to a concentration greater than 500 ppm of H2S can result in irreversible health problems and death within minutes. Because of these hazards, operations such as oil and gas processing and sewage treatment that handle or produce H2S and/or sour gas require effective and well-designed hazard controls, as well as state-of-the-art gas monitoring/detection mechanisms for the safety of workers and the public. Laboratories studying H2S for improved understanding must also develop and continually improve upon lab-specific safety standards with unique detection systems. In this study, we discuss various H2S detection methods and hazard control strategies. Also, we share our experience regarding a leak that occurred as a result of the failure of a perfluoroelastomer O-ring seal on a small stirred autoclave vessel used for studying H2S hydrate dissociation/formation conditions in our laboratory, and discuss how our emergency response plan was activated to mitigate the risk of exposure to the researchers and public.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.730
Threshold uncertainty score0.948

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.204
Teacher spread0.195 · 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