MétaCan
Menu
Back to cohort
Record W2899787558 · doi:10.1115/ipc2018-78666

A Canadian Operator Based Framework for Pipeline Pressure Tests: Lessons Learned

2018· article· en· W2899787558 on OpenAlexaboutno aff
Nicole-Lee M. Robertson, Bob Campbell

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicStructural Integrity and Reliability Analysis
Canadian institutionsnot available
Fundersnot available
KeywordsDocumentationPipeline (software)Project commissioningConsistency (knowledge bases)Process (computing)Hydrostatic testComputer scienceSystems engineeringAsset (computer security)Quality (philosophy)EngineeringTest (biology)ChecklistInstrumentation (computer programming)Reliability engineeringProcess managementRisk analysis (engineering)Computer securityBusinessMechanical engineeringPublishingOperating system

Abstract

fetched live from OpenAlex

Commissioning pressure tests are a critical life-of-asset record. Successfully achieving an acceptable pressure test can be challenging both at an execution and documentation perspective. This paper aims to assist in streamlining the approach to pipeline commissioning pressure tests between operators to increase efficiency and drive consistency across the pipeline industry. Key lessons learned from the planning stages through to the quality control turnover are highlighted. Lessons learned, respective to pressure tests, include: road map of Canadian regulations, tabulated equipment requirements, suggested instrumentation setup, template checklist for test plans, outlined company to contractor responsibilities, as well as a proposed internal process to manage and accept completed tests.

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 imitation

Not 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.

metaresearch head score (Codex)0.041
metaresearch head score (Gemma)0.034
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.103
Threshold uncertainty score0.747

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0410.034
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0090.008
Science and technology studies0.0120.011
Scholarly communication0.0190.009
Open science0.0120.006
Research integrity0.0050.010
Insufficient payload (model declined to judge)0.0140.005

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.027
GPT teacher head0.294
Teacher spread0.267 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreMethods

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".

Quick stats

Citations0
Published2018
Admission routes1
Has abstractyes

Explore more

Same topicStructural Integrity and Reliability AnalysisFrench-language works237,207