MétaCan
Menu
Back to cohort
Record W2744032119 · doi:10.1061/9780784480885.045

Developing and Implementing a PCCP Condition Assessment Program

2017· article· en· W2744032119 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenuePipelines 2017 · 2017
Typearticle
Languageen
FieldHealth Professions
TopicQuality and Safety in Healthcare
Canadian institutionsImpactOttawa Public Health
Fundersnot available
KeywordsComputer science

Abstract

fetched live from OpenAlex

This paper presents the City of Ottawa’s recent experiences developing and implementing a condition assessment program for large-diameter watermains. A significant portion of the inventory is comprised of prestressed concrete cylinder pipe (PCCP) lines, and due to recent failures on these pipes, efforts have been focused on understanding the condition and failure mechanisms of the PCCP in their system. As the City has embarked on their inspection program, it has become apparent that compiling and managing available data, filling in missing critical pieces of data, selecting appropriate PCCP inspection tools, and interpreting inspection results are all critical to developing a complete program. The goal of the City’s condition assessment program is to identify distressed pipes with broken prestressing wires, evaluate the risk of failure of such distressed pipes, and repair or replace pipes at high risk of failure. In order to achieve this goal, the City needs to understand the structural capacity of the pipes, the sensitivity of the pipes to prestressing wire breaks, and which inspection technologies provide sufficient resolution in the distress estimation. This paper will present an overview of the original condition assessment approach at the City of Ottawa, data sources and gathering efforts, how the program evolved as well as the lessons learned and improvements of the program over time.

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.002
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.237
Threshold uncertainty score0.996

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0060.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.332
GPT teacher head0.620
Teacher spread0.288 · 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