MétaCan
Menu
Back to cohort
Record W2940964888 · doi:10.1016/j.promfg.2019.02.255

Implementation of an Absorber Design for Vibration Control in Automation Systems

2019· article· en· W2940964888 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueProcedia Manufacturing · 2019
Typearticle
Languageen
FieldEngineering
TopicIndustrial Automation and Control Systems
Canadian institutionsMcMaster University
FundersMcMaster University
KeywordsVibrationDynamic Vibration AbsorberAutomationEngineeringVibration controlNoise (video)Mechanical resonanceMechanical systemComputer scienceAcousticsControl engineeringMechanical engineeringPhysicsArtificial intelligence

Abstract

fetched live from OpenAlex

Vibration problems occur in automation and robotics systems frequently. Automation systems often have components that rotate at high speeds. When rotating equipment is unbalanced, it could cause a lot of vibration. This type of forced vibration not only will create mechanical noise, it could cause accuracy issues and affect production yield in precision equipment. Even if the source of the vibration can be identified, sometimes it is difficult to fix the issue due to cost or schedule concerns. In such cases, vibration absorbers can be used to control the vibration amplitude and allow production to continue. A passive vibration absorber is a mechanical device with no electrical components. It is designed or tuned to a certain oscillation frequency, typically, one of the systems resonance frequencies. A vibration absorber is only effective when the excitation frequency is close to the resonance frequency of the system. In a system with multiple modes of vibrations, vibration absorbers can only be designed specifically to a single mode of vibration. In this paper, an example will be examined to understand how vibration absorbers can be implemented and their limitations.

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: Empirical
Teacher disagreement score0.123
Threshold uncertainty score0.430

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.013
GPT teacher head0.238
Teacher spread0.224 · 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