z-logo
open-access-imgOpen Access
Relationship between oxygenation in inactive biceps brachii muscle and hyperventilation during leg cycling
Author(s) -
Haruhiko Ogata,
Takuma Arimitsu,
Ryouta Matsuura,
Takahiro Yunoki,
Masahiro Horiuchi,
Toshiaki Yano
Publication year - 2007
Publication title -
physiological research
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.647
H-Index - 70
eISSN - 1802-9973
pISSN - 0862-8408
DOI - 10.33549/physiolres.930888
Subject(s) - hyperventilation , oxygenation , biceps , cycling , respiratory compensation , forearm , chemistry , anesthesia , medicine , cardiology , anatomy , physical therapy , anaerobic exercise , archaeology , history
Inactive forearm muscle oxygenation has been reported to begin decreasing from the respiratory compensation point (RCP) during ramp leg cycling. From the RCP, hyperventilation occurs with a decrease in arterial CO2 pressure (PaCO2). The aim of this study was to determine which of these two factors, hyperventilation or decrease in PaCO2, is related to a decrease in inactive biceps brachii muscle oxygenation during leg cycling. Each subject (n = 7) performed a 6-min two-step leg cycling. The exercise intensity in the first step (3 min) was halfway between the ventilatory threshold and RCP (170+/-21 watts), while that in the second step (3 min) was halfway between the RCP and peak oxygen uptake (240+/-28 watts). The amount of hyperventilation and PaCO2 were calculated from gas parameters. The average cross correlation function in seven subjects between inactive muscle oxygenation and amount of hyperventilation showed a negative peak at the time shift of zero (r = -0.72, p<0.001), while that between inactive muscle oxygenation and calculated PaCO2 showed no peak near the time shift of zero. Thus, we concluded that decrease in oxygenation in inactive arm muscle is closely coupled with increase in the amount of hyperventilation.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here