MétaCan
Menu
Back to cohort
Record W1985655115 · doi:10.1115/ipc2014-33477

Comparison of PIR to PIPESAFE-Based 1% Lethality Zones for Natural Gas Pipelines

2014· article· en· W1985655115 on OpenAlex
Aleksandar Tomić, Shahani Kariyawasam

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

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicStructural Integrity and Reliability Analysis
Canadian institutionsTransCanada (Canada)
Fundersnot available
KeywordsLethalityPipeline transportNatural gasPipeline (software)Boundary (topology)RADIUSEnvironmental scienceComputer sciencePetroleum engineeringForensic engineeringGeologyEngineeringMathematicsBiologyEnvironmental engineeringEcologyToxicologyComputer security

Abstract

fetched live from OpenAlex

A lethality zone due to an ignited natural gas release is often used to characterize the consequences of a pipeline rupture. A 1% lethality zone defines a zone where the lethality to a human is greater than or equal to 1%. The boundary of the zone is defined by the distance (from the point of rupture) at which the probability of lethality is 1%. Currently in the gas pipeline industry, the most detailed and validated method for calculating this zone is embodied in the PIPESAFE software. PIPESAFE is a software tool developed by a joint industry group for undertaking quantitative risk assessments of natural gas pipelines. PIPESAFE consequence models have been verified in laboratory experiments, full scale tests, and actual failures, and have been extensively used over the past 10–15 years for quantitative risk calculations. The primary advantage of using PIPESAFE is it allows for accurate estimation of the likelihood of lethality inside the impacted zone (i.e. receptors such as structures closer to the failure are subject to appropriately higher lethality percentages). Potential Impact Radius (PIR) is defined as the zone in which the extent of property damage and serious or fatal injury would be expected to be significant. It corresponds to the 1% lethality zone for a natural gas pipeline of a certain diameter and pressure when thermal radiation and exposure are taken into account. PIR is one of the two methods used to identify HCAs in US (49 CFR 192.903). Since PIR is a widely used parameter and given that it can be interpreted to delineate a 1% lethality zone, it is important to understand how PIR compares to the more accurate estimation of the lethality zones for different diameters and operating pressures. In previous internal studies, it was found that PIR, when compared to the more detailed measures of the 1% lethality zone, could be highly conservative. This conservatism could be beneficial from a safety perspective, however it is adding additional costs and reducing the efficiency of the integrity management process. Therefore, the goal of this study is to determine when PIR is overly conservative and to determine a way to address this conservatism. In order to assess its accuracy, PIR was compared to a more accurate measure of the 1% lethality zone, calculated by PIPESAFE, for a range of different operating pressures and line diameters. Upon comparison of the distances calculated through the application of PIR and PIPESAFE, it was observed that for large diameters pipelines the distances calculated by PIR are slightly conservative, and that this conservativeness increases exponentially for smaller diameter lines. The explanation for the conservatism of the PIR for small diameter pipelines is the higher wall friction forces per volume transported in smaller diameter lines. When these higher friction forces are not accounted for it leads to overestimation of the effective outflow rate (a product of the initial flow rate and the decay factor) which subsequently leads to the overestimation of the impact radius. Since the effective outflow rate is a function of both line pressure and diameter, a simple relationship is proposed to make the decay factor a function of these two variables to correct the excess conservatism for small diameter pipelines.

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.256
Threshold uncertainty score0.456

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.022
GPT teacher head0.303
Teacher spread0.281 · 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