Reliability Modeling Approach and Hydraulic Actuators Designed Hinge-Moment Capability
Bibliographic record
Abstract
<div class="section abstract"><div class="htmlview paragraph">The hydraulic actuators are used to power flight control surfaces of the aircraft and to ensure surface movement. A system of two or three actuators is usually designed depending on the surface and intuitively these actuators are considered as a redundant architecture from a reliability and functionality point of view. The proper reliability modeling of the system of actuators must consider the system's functionality and design constraints for the remaining available actuator hinge-moment in the event of a partial or total actuator failure. As a result, this will affect the reliability assessment of that design. Furthermore, this system of actuators is also designed to provide a second function involving an assurance of the surface stiffness and damping. Generally, this second function does not require necessarily the same number of available actuators in order to be fully provided. Therefore, the criteria for the reliability model might be different depending on the failure definition and severity related to the specific function and the assumed redundant architecture for one function might not be valid for the second function. This will obviously result in a significantly different level of computed reliability. Additionally, this difference in the reliability modeling might lead to some difficulties in the assessment of potential latent failures at the actuators' system level related to the various functions of the actuator. This paper provides an approach to reliability modeling and latent failures designation for the system of actuators designed to perform two or more different functions. Specific actuator failure modes and their respective combinations resulting in a reduction in hinge-moment capability are discussed in regards to the criticality of the related failure conditions associated with both functions. The resulting failures at the system of actuators' level might be latent depending on the system's configuration in a partially failed state and on the specific failure mode. However, this latency may be designed out if the actuator is accurately specified. Some factual application examples are provided in order to illustrate the discussed topics.</div></div>
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.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".