MétaCan
Menu
Back to cohort

Joint sensor fault detection for fault tolerant parallel manipulators

2000· article· en· W2012502856 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

VenueJournal of Robotic Systems · 2000
Typearticle
Languageen
FieldEngineering
TopicRobotic Mechanisms and Dynamics
Canadian institutionsQueen's University
Fundersnot available
KeywordsPayload (computing)Fault detection and isolationFault toleranceJoint (building)KinematicsDisplacement (psychology)Fault (geology)Control theory (sociology)Computer scienceParallel manipulatorActuatorStewart platformEngineeringControl engineeringReal-time computingArtificial intelligenceRobotDistributed computingStructural engineering

Abstract

fetched live from OpenAlex

Parallel manipulators with redundant joint displacement sensing can be exploited to develop fault tolerant implementations. This is possible since fundamental problems of the associated kinematics can still be solved after the elimination of faulty sensor readings. The ability of detecting faulty sensor readings is a requirement of any fault tolerant implementation scheme. A sensor fault detection method is presented for redundantly sensed parallel manipulators. A broad class of three-branch manipulators is considered where each branch consists of three main-arm joints and supports a common payload through respective passive spherical joints. The detection method is based on the comparison of forward displacement solutions for different cases of joint sensor readings. The existence of common solutions based on the branches–sensors considered, is used to effectively identify the existence of a failed sensor. Once a faulty sensor is identified, continued (fault tolerant) operation is possible using a forward displacement solution based on the readings of the accurate sensors. The detection method is implemented in a computer simulation of a calibrated three-branch parallel manipulator. © 2000 John Wiley & Sons, Inc.

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.907
Threshold uncertainty score0.662

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.019
GPT teacher head0.214
Teacher spread0.195 · 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