MétaCan
Menu
Back to cohort
Record W2986750671 · doi:10.4050/f-0072-2016-11569

Rotor Blade Optimization and Flight Testing of a Small UAV Rotorcraft

2016· article· en· W2986750671 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

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicAerospace Engineering and Control Systems
Canadian institutionsCarleton University
Fundersnot available
KeywordsBlade (archaeology)Aerospace engineeringHelicopter rotorRotor (electric)AeronauticsFlight testEngineeringComputer scienceMechanical engineering

Abstract

fetched live from OpenAlex

Rotor blade optimization with blade airfoil Reynolds numbers between 100,000 and 500,000 - characteristic of radio controlled (RC) helicopters - was performed using Blade Element Momentum theory (BEMT) and demonstrated via flight tests. BEMT was used to test various airfoil profiles and rotor blade shapes using airfoil data from 2D Computational Fluid Dynamics (CFD) simulations with Reynolds numbers representative of the blade elements. A blade design utilizing a cambered profile, taper and twist was developed for increased performance in hover. Selected blade designs were manufactured and flight tested on a Blade 600X RC helicopter (671 mm blade radius) to validate the theoretical results. The best of the improved blade designs increased the Figure of Merit (FM) by 20% and reduced power consumption by 22% while keeping the rotational frequency constant. Reducing the rotational frequency from 2,000 to 1,500 RPM resulted in an additional 55% increase in the FM and 35% reduction in the power consumption, while a one-bladed design further improved endurance and range performance of the helicopter by as much as 20%. The presented results could serve as useful guidelines to small Unmanned Aerial Vehicle (UAV) helicopter manufacturers and operators for increasing endurance, range and payload capabilities.

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.871
Threshold uncertainty score0.263

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.007
GPT teacher head0.155
Teacher spread0.147 · 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