MétaCan
Menu
Back to cohort
Record W2977546386 · doi:10.1002/ese3.438

Numerical investigations of a novel vertical axis wind turbine using Blade Element Theory‐Vortex Filament Method (<scp>BET</scp>‐<scp>VFM</scp>)

2019· article· en· W2977546386 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

VenueEnergy Science & Engineering · 2019
Typearticle
Languageen
FieldEngineering
TopicWind Energy Research and Development
Canadian institutionsNational Research Council CanadaCarleton University
Fundersnot available
KeywordsVertical axis wind turbineAerodynamicsAerospace engineeringVortexComputational fluid dynamicsTurbineFinite element methodWind powerStructural engineeringEngineeringMarine engineeringPhysicsMeteorologyElectrical engineering

Abstract

fetched live from OpenAlex

Abstract The aerodynamic performance of three different configurations of vertical axis wind turbines ( VAWT ), namely: (a) conventional Darrieus troposkein VAWT (based on turbines designed by Sandia National Laboratories), (b) novel 50% STS ‐ VAWT (50% shifted‐troposkein‐shaped STS ‐ VAWT ), and (c) novel 100% STS ‐ VAWT were investigated numerically. An in‐house code, which combined the blade element theory ( BET ) and the vortex filament method ( VFM ), was used. The main purpose of this work was to develop an aerodynamic code to predict the performance of conventional VAWT as well as assess the novel 50% and 100% STS ‐ VAWT configurations. Simulation results (power coefficients) were verified and then validated against experimental data available from the literature (2‐, 5‐, and 17‐m conventional troposkein VAWT measured by Sandia National Laboratories). Additional numerical results showed that the 50% STS ‐ VAWT outperformed both the conventional VAWT and the 100% STS ‐ VAWT by up to 14% (peak power), within the range of rotation and turbine sizes that were investigated in the present work.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.296
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.002
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.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.015
GPT teacher head0.247
Teacher spread0.232 · 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