MétaCan
Menu
Back to cohort
Record W2004239461 · doi:10.1115/1.1864116

Force Balancing of Robotic Mechanisms Based on Adjustment of Kinematic Parameters

2004· article· en· W2004239461 on OpenAlex
P. R. Ouyang, Wenjun Zhang

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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueJournal of Mechanical Design · 2004
Typearticle
Languageen
FieldEngineering
TopicRobotic Mechanisms and Dynamics
Canadian institutionsUniversity of Saskatchewan
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsKinematicsMechanism (biology)TorqueControl theory (sociology)Joint (building)Computer scienceMechanism designEngineeringSimulationMathematicsStructural engineeringPhysicsClassical mechanicsControl (management)Artificial intelligence

Abstract

fetched live from OpenAlex

Force balancing is a very important issue in mechanism design and has only recently been introduced to the design of robotic mechanisms. In this paper, a force balancing method called adjusting kinematic parameters (AKP) for robotic mechanisms or real-time controllable (RTC) mechanisms is proposed, as opposed to force balancing methods, e.g., the counterweights (CW) method. Both the working principle of the AKP method and the design equation with which to construct a force balanced mechanism are described in detail. A particular implementation of the AKP method for the RTC mechanisms where two pivots on a link are adjustable is presented. A comparison of the two methods, namely the AKP method and the CW method, is made for two RTC mechanisms with different mass distribution. The joint forces and torques are calculated for the trajectory tracking of the RTC mechanisms. The result shows that the AKP method is consistently better than the CW method in terms of the reduction of the joint forces and the torques in the servomotors, and the smoothing of the fluctuation of the joint force.

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.001
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: Methods
Teacher disagreement score0.479
Threshold uncertainty score0.710

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.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.018
GPT teacher head0.216
Teacher spread0.198 · 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