MétaCan
Menu
Back to cohort
Record W1997150293 · doi:10.2514/1.39953

Use of Pitch and Heave Motion Cues in a Pitch Control Task

2009· article· en· W1997150293 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.

fundA Canadian funder is recorded on the work.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of Guidance Control and Dynamics · 2009
Typearticle
Languageen
FieldEngineering
TopicAerospace and Aviation Technology
Canadian institutionsnot available
FundersConnaught FundUniversity of Toronto
KeywordsPitch controlRotation (mathematics)Motion (physics)Rotation around a fixed axisPitch angleSimulationCenter of gravityEngineeringComputer scienceControl theory (sociology)Aerospace engineeringControl (management)PhysicsComputer visionMechanical engineeringArtificial intelligence

Abstract

fetched live from OpenAlex

During pitch rotation of the aircraft, a pilot, seated in front of the aircraft center of gravity, is subjected to rotational pitch and vertical heave motion. The heave motion is a combination of the vertical motion of the aircraft center of gravity and the heave motion as a result of the pitch rotation. In a pitch tracking task, all of these cues could potentially have a positive effect on performance and control behavior, as they are all related to the aircraft pitch attitude. To improve the tuning of flight simulator motion filters, a better understanding of how these motion components are used by the pilot is required. First, the optimal use of the different motion components was evaluated using an optimal control analysis. Next, an aircraft pitch attitude control experiment was performed in the SIMONA Research Simulator, investigating the effects of pitch rotation, pitch heave, and center of gravity heave on pilot control behavior. Pilot performance significantly improved with pitch motion, with an increased crossover frequency for the disturbance open loop. The increase in performance was a result of an increased visual gain and a reduction in visual lead, allowed for by the addition of pitch motion. Pitch heave motion showed similar but smaller effects. The center of gravity heave motion, although taking up most of the simulator motion space, was found to have no significant effects on performance and control behavior.

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

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.005
GPT teacher head0.198
Teacher spread0.193 · 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