MétaCan
Menu
Back to cohort
Record W2139831829 · doi:10.1109/tie.2007.899936

Velocity Estimation by Using Position and Acceleration Sensors

2007· article· en· W2139831829 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

VenueIEEE Transactions on Industrial Electronics · 2007
Typearticle
Languageen
FieldEngineering
TopicTeleoperation and Haptic Systems
Canadian institutionsCanadian Space Agency
Fundersnot available
KeywordsAccelerometerEncoderControl theory (sociology)Computer scienceBandwidth (computing)AccelerationRotary encoderObserver (physics)Artificial intelligencePhysicsTelecommunications

Abstract

fetched live from OpenAlex

Knowledge of velocity is crucial to certain industrial applications involving high-bandwidth modeling and control. In conventional approaches, the velocities obtained from encoders or tachometers are quite noisy, and low-pass filters are usually engaged to generate usable velocity signals. The low-pass filter, however, causes significant phase lag that can severely affect both modeling and control accuracy in the mid- and high-frequency ranges. In this paper, two approaches using a combination of an encoder and an imperfect accelerometer are proposed to estimate velocities with high bandwidth. The two approaches, namely the two-channel approach and the observer-based approach, estimate velocities by applying proper frequency weightings to the encoder and accelerometer signals. The encoder mainly contributes to the low-frequency components of velocity estimation, and the accelerometer mainly contributes to the high-frequency components of velocity estimation. An adaptive mechanism for estimating the accelerometer gain is also presented. The effectiveness of the two velocity estimation approaches is verified experimentally with respect to a one-degree-of-freedom robot performing both rigid contact modeling and control. Extension to 3-D applications is discussed.

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.577
Threshold uncertainty score0.627

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.028
GPT teacher head0.249
Teacher spread0.220 · 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