MétaCan
Menu
Back to cohort
Record W2270522139 · doi:10.1680/wama.2011.164.9.463

Design–operation optimisation of run-of-river power plants

2011· article· en· W2270522139 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

VenueProceedings of the Institution of Civil Engineers - Water Management · 2011
Typearticle
Languageen
FieldEngineering
TopicWater resources management and optimization
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsPenstockHydropowerTurbineMathematical optimizationComputer scienceEngineeringReliability engineeringMathematicsMechanical engineering

Abstract

fetched live from OpenAlex

This paper addresses a strategy for the optimal design, control and operation of small hydropower (run-of-river (RoR) power) plants with the honey bee mating optimisation (HBMO) algorithm, while taking into account optimal design of the associated penstock as well as the turbines' number, type and their operation in the system. Civil engineering and electromechanical cost-effectiveness and constraints in an expected stream flow are also considered. The optimisation is driven by an objective function that includes the annual difference between generated energy, operating costs and depreciation costs for both initial investment and operation costs, considering various performance and hydraulic constraints. The HBMO algorithm specifies the annual benefit of generated energy and simultaneously determines the annualised operating cost. The solution includes selection of turbine types, number of turbines, penstock diameter, as well as scheduling the operation of an RoR power plant that results in maximum annualised benefit for a given set of river inflow histograms. The results of the proposed algorithm, which are compared with those of an analytical approach using Lagrange multipliers (LM), highlight the advantages in design, effective operation, ease of application and capability of the proposed HBMO algorithm for solving complex problems of this type.

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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.907
Threshold uncertainty score0.439

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.014
GPT teacher head0.166
Teacher spread0.152 · 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