MétaCan
Menu
Back to cohort
Record W4231625009 · doi:10.1115/1.2908180

Dynamic Modeling and Experimental Testing of a Piano Action Mechanism With a Flexible Hammer Shank

2008· article· en· W4231625009 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

VenueJournal of Computational and Nonlinear Dynamics · 2008
Typearticle
Languageen
FieldComputer Science
TopicMusic Technology and Sound Studies
Canadian institutionsUniversity of Waterloo
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsHammerMechanism (biology)PianoFlexibility (engineering)LeverStructural engineeringRotation (mathematics)EngineeringAction (physics)Mechanical engineeringAcousticsPhysicsMathematicsGeometry

Abstract

fetched live from OpenAlex

The piano action is the mechanism that transforms the finger force applied to a key into a motion of a hammer that strikes a piano string. This paper presents a state-of-the-art model of a grand piano action, which is based on the five main components of the action mechanism (key, whippen, jack, repetition lever, and hammer). Even though some piano action researchers (e.g., Askenfelt and Jansson) detected some flexibility for the hammer shank in their experiments, all previous piano models have assumed the hammers to be rigid bodies. In this paper, we have accounted for the hammer shank flexibility using a Rayleigh beam model. It turns out that the flexibility of the hammer shank does not significantly affect the rotation of the other parts of the piano mechanism and the impact velocity of the hammer head, compared to the case that the hammer shank has been modeled as a rigid part. However, the flexibility of the hammer shank causes a greater scuffing motion for the hammer head during the contact with the string. To validate the theoretical results, experimental measurements were taken by two strain gauges mounted on the hammer shank, and by optical encoders at three of the joints.

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.209
Threshold uncertainty score0.276

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.032
GPT teacher head0.269
Teacher spread0.237 · 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