MétaCan
Menu
Back to cohort

Life-Cycle Energy Analysis of a Water Distribution System

2004· article· en· W1970743258 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.

Bibliographic record

VenueJournal of Infrastructure Systems · 2004
Typearticle
Languageen
FieldEngineering
TopicWater Systems and Optimization
Canadian institutionsUniversity of Toronto
FundersU.S. Department of Commerce
KeywordsDispose patternEnergy (signal processing)Service lifeEngineeringEnvironmental scienceEnergy recoveryReliability engineeringProcess engineeringWaste managementStatisticsMathematics

Abstract

fetched live from OpenAlex

The paper presents a life-cycle energy analysis (LCEA) to quantify energy expenditures in the fabrication, use, and end-of-life stages of the pipes of a water distribution system. The methodology incorporates the capabilities of environmental input-output life-cycle analysis to quantify the energy required to fabricate pipes. The EPANET2 hydraulic model is applied in conjunction with a pipe-aging model to calculate the theoretical energy recovery in the use stage. An exponential pipe-break model is applied to quantify the energy required to repair pipe breaks during the use stage of a system. Simple formulations are developed to estimate the energy required to dispose of and recycle pipes once their service period has expired. The LCEA methodology is then applied to the New York City (NYC) water supply tunnels example to quantify energy expenditures in four planning scenarios with 10-, 20-, 50-, and 100-year pipe replacement frequencies. The results of the NYC example highlight the tension between the energy costs incurred in the fabrication and end-of-life stages of a system and those incurred in the use stage. A pipe-replacement period roughly equal to 50 years yielded the lowest overall energy expenditure in the three life stages. A sensitivity analysis was carried out to assess the influence of uncertain system parameters on energy expenditure estimates.

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: none
Teacher disagreement score0.589
Threshold uncertainty score0.415

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.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.002
GPT teacher head0.160
Teacher spread0.158 · 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