MétaCan
Menu
Back to cohort
Record W2029239161 · doi:10.1260/0309-524x.35.3.329

On Blade Arrangement for Multi-Blade Rotors

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

VenueWind Engineering · 2011
Typearticle
Languageen
FieldPhysics and Astronomy
TopicScientific Research and Discoveries
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsRotor (electric)Blade (archaeology)Blade element momentum theoryEccentricity (behavior)Structural engineeringWindmillSelection (genetic algorithm)Turbine bladeMathematicsEngineeringMechanical engineeringComputer scienceTurbineWind powerArtificial intelligence

Abstract

fetched live from OpenAlex

This paper concerns the blades of multi-bladed water-pumping windmills when they have variable mass and centre of mass. The paper explores blade arrangement strategies that will minimize the eccentricity of the rotor centre of mass and hence any rotor-induced vibration. The number of blades in the rotor is assumed to equal the number made in each production batch, in contrast to the case where a batch of up to 22 blades was optimally matched to produce two- and three-bladed rotors, Hitz & Wood [1]. Using the measured mass and centre of mass of 24 blades for the rotor of a 26 ft Kijito windmill described by Harries [3], three strategies are considered. Random matching of the blades is shown to become increasingly effective as blade number increases. Pairing the blades by ordering in the product of mass and centre of mass, d, followed by random selection of pairs also produces rotors with low eccentricities. The numerical experiments show that the best strategy involving random selection is to pair by ordering, swapping the blades of every second pair, and then randomly arrange the resulting pairs. Finally, a heuristic based on blade pairing is shown to give eccentricities which are high compared to the minimum value determined exactly for 12 blades or less, but apparently low enough to be useful.

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: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.660
Threshold uncertainty score0.370

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.059
GPT teacher head0.269
Teacher spread0.209 · 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