MétaCan
Menu
Back to cohort
Record W3006785975 · doi:10.1016/j.rcrx.2020.100033

Optimal sizing of rainwater harvesting systems for domestic water usages: A systematic literature review

2020· article· en· W3006785975 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

VenueResources Conservation & Recycling X · 2020
Typearticle
Languageen
FieldEnvironmental Science
TopicUrban Stormwater Management Solutions
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsRainwater harvestingSizingComputer scienceCapital costOptimization problemEnvironmental scienceRisk analysis (engineering)Environmental economicsEngineeringBusinessEconomics

Abstract

fetched live from OpenAlex

Rainwater harvesting systems (RWHS) are increasing in popularity because of their ability to alleviate water pressure on centralized systems, minimize or delay rainfall runoff, and fit relatively easily in both the centralized/decentralized infrastructure organization. Adequately sizing RWHS is critical to optimizing their operation because under-sizing results in systems that are unable to provide a sufficient, reliable source of water while oversizing increases the capital costs incurred with limited marginal benefits and poses potential water quality risks. In this paper, we conduct a systematic literature review to assess the state-of-art in the field of optimization of domestic rainwater harvesting systems. Sizing of storage is identified as the most important objective of optimization, yet sizing for cost is the most frequently implemented outcome of optimization. Optimizing for a local maximum is often favored over simulation-based optimization methods that produce global maxima. To derive more realistic sizing estimates, future optimization studies will have to take into account greater variation in water demands as well as various climate change scenarios, especially given that rainfall frequency and quantity are critical design variables of a rainwater harvesting system.

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.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.443
Threshold uncertainty score0.632

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
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.039
GPT teacher head0.256
Teacher spread0.217 · 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