MétaCan
Menu
Back to cohort
Record W4295918947 · doi:10.4050/f-0078-2022-17636

RACER Coumpound Helicopter: Operational Wireless FTI Data Transfer from ROTOR's up to Fuselage

2022· article· en· W4295918947 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
TopicAdvanced Measurement and Detection Methods
Canadian institutionsSafran Electronics (Canada)
Fundersnot available
KeywordsFuselageWirelessData acquisitionRotor (electric)EngineeringComputer scienceFrame (networking)Instrumentation (computer programming)Systems engineeringReal-time computingMarine engineeringAeronauticsTelecommunicationsAerospace engineeringElectrical engineering

Abstract

fetched live from OpenAlex

Acquiring helicopter rotor data is always a very sensitive point that requires at least "effort and special attention". This data acquisition is generally managed by a "physical link" (slip ring for example) whereas wireless products are now present everywhere with a technology more than promising. The objective of this paper is to show how the wireless technology was developed within the framework of RACER COUMPOUND HELICOPTER to monitor the three rotors in accordance with CS29 regulations for the mechanical assembly, DO160 rules for environmental constraints and IRIG 106 standard for Flight Test Instrumentation domain notwithstanding that this wireless acquisition means will be used on a daily basis to monitor the data from the three rotors of the RACER. The paper provides an overview of this project, supported by the CEE (Horizon 2020/CS2), and from the initial requirement up to the operational results obtained during the flight test campaigns carried out on the H175. Finally, this paper, based on this use case ( RACER oriented) , aims also to open the perspective of using such a wireless application on helicopters in service in the frame of health monitoring 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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.819
Threshold uncertainty score0.995

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.0060.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.071
GPT teacher head0.293
Teacher spread0.222 · 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