Time course of changes in the long latency feedback response parallels the fast process of short term motor adaptation
Bibliographic record
Abstract
Abstract Adapting to novel dynamics involves modifying both feedforward and feedback control. We investigated whether the motor system alters feedback responses during adaptation to a novel force field in a manner similar to adjustments in feedforward control. We simultaneously tracked the time course of both feedforward and feedback systems via independent probes during a force field adaptation task. Participants (n=35) grasped the handle of a robotic manipulandum and performed reaches to a visual target while the hand and arm were occluded. We introduced an abrupt counter-clockwise velocity-dependent force field during a block of reaching trials. We measured movement kinematics and shoulder and elbow muscle activity with surface EMG electrodes. We tracked the feedback stretch response throughout the task. Using force channel trials we measured overall learning, which was later decomposed into a fast and slow process. We found that the long-latency feedback response (LLFR) was upregulated in the early stages of learning and was correlated with the fast component of feedforward adaptation. The change in feedback response was specific to the long-latency epoch (50-100 ms after muscle stretch) and was observed only in the triceps muscle, which was the muscle required to counter the force field during adaptation. The similarity in time course for the LLFR and the estimated time course of the fast process suggests both are supported by common neural circuits. While some propose that the fast process reflects an explicit strategy, we argue instead that it may be a proxy for the feedback controller. New & Noteworthy We investigated whether changes in the feedback stretch response were related to the proposed fast and slow processes of motor adaptation. We found that the long latency component of the feedback stretch response was upregulated in the early stages of learning, and the time course was correlated with the fast process. While some propose that the fast process reflects an explicit strategy, we argue instead that it may be a proxy for the feedback controller.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.003 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".