MétaCan
Menu
Back to cohort
Record W2998525110 · doi:10.2514/6.2020-0681

Comparison of Surrogate Modeling Methods for Finite Element Analysis of Landing Gear Loads

2020· article· en· W2998525110 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

VenueAIAA Scitech 2020 Forum · 2020
Typearticle
Languageen
FieldEngineering
TopicMechanical Engineering and Vibrations Research
Canadian institutionsSafran Electronics (Canada)
Fundersnot available
KeywordsFinite element methodComputer scienceLanding gearStructural engineeringEngineering

Abstract

fetched live from OpenAlex

Aircraft landing gear structures are exposed to complex loading in-service. Coupled with the geometry and joints used within landing gear structural assemblies, finite element models tend to be used to compute the loads acting on landing gear components during ground maneuvers. Concerning novel design approaches for complex structural assemblies, such as probabilistic assessment, optimization or ‘digital-twins’, the computational expense of using finite element models is prohibitive. Surrogate modeling methods have been proposed as a route to reducing the computational expense of assessing complex structural assemblies for static and fatigue design. This paper investigates the application of Response Surfaces, Radial Basis Functions, Gaussian Process Regression and Artificial Neural Networks as approaches to surrogate modeling for landing gear load models. Following the construction of the surrogate models within case studies representing a side stay and complex drag brace component, it was identified that Response Surface and Gaussian Process Regression surrogate models could be used to reduce the computational expense of a landing gear loads assessment from 20 seconds to less than a millisecond. As a result, surrogate modeling methods provide the required reduction in computational expense to support probabilistic design and optimization of complex structural assemblies.

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: Methods · Consensus signal: none
Teacher disagreement score0.884
Threshold uncertainty score0.463

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.001
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.081
GPT teacher head0.402
Teacher spread0.320 · 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