27.11.2012 Views

Introduction to Sports Biomechanics: Analysing Human Movement ...

Introduction to Sports Biomechanics: Analysing Human Movement ...

Introduction to Sports Biomechanics: Analysing Human Movement ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

INTRODUCTION TO SPORTS BIOMECHANICS<br />

186<br />

FORCE–TIME GRAPHS AS MOVEMENT PATTERNS<br />

Consider an international volleyball coach who wishes <strong>to</strong> assess the vertical jumping<br />

capabilities of his or her squad members. Assume that this coach has access <strong>to</strong> a force<br />

plate, a device that records the variation with time of the contact force between a person<br />

and the surroundings (see below). The coach uses the force plate <strong>to</strong> record the force–<br />

time graph exerted by the players performing standing vertical jumps (see, for example,<br />

Figure 5.2). These graphs provide another movement pattern for both the qualitative<br />

and the quantitative movement analyst; our world is exceedingly rich in such patterns.<br />

Each player’s force–time graph, after subtracting his or her weight, is easily converted <strong>to</strong><br />

an acceleration–time graph (Figure 5.12(a)) as acceleration equals force divided by the<br />

player’s mass, where the acceleration is that of the jumper’s centre of mass.<br />

Qualitative evaluation of a force–time or acceleration–time pattern<br />

In Chapter 2, we saw how important it is for a qualitative analyst <strong>to</strong> be able <strong>to</strong> interpret<br />

movement patterns such as displacement or angle time series. Force–time or acceleration–time<br />

patterns are far less likely <strong>to</strong> be encountered by the qualitative movement<br />

analyst and are not so revealing about other kinematic patterns – velocity and displacement.<br />

However, if you are prepared <strong>to</strong> accept that the velocity equals the area between<br />

the horizontal zero-acceleration line – the time (t) axis of the graph – and the acceleration<br />

curve from the start of the movement at time 0 up <strong>to</strong> any particular time, and that<br />

areas below the time axis are negative and those above positive, then several key points<br />

on the velocity–time graph follow. Ignore, for the time being, the numbers on the<br />

vertical axes of Figure 5.12.<br />

At time A in Figure 5.12(a), the area (−A 1) under the time axis and above<br />

the acceleration–time curve from 0 <strong>to</strong> A reaches its greatest negative value, so the<br />

vertical velocity of the jumper’s centre of mass also reaches its greatest negative value<br />

there, corresponding <strong>to</strong> a zero acceleration. We can then sketch the velocity graph<br />

in Figure 5.12(b) up <strong>to</strong> time A.<br />

At time B in Figure 5.12(a), the area under the acceleration–time curve from A<br />

<strong>to</strong> B and above the time axis is +A 1 – the same magnitude as before but now<br />

positive. So the net area between the acceleration–time curve and the time axis<br />

from 0 <strong>to</strong> B is −A 1 + A 1 = 0. The vertical velocity of the jumper’s centre of mass at B<br />

is, therefore, zero; we can now sketch the vertical velocity curve from A <strong>to</strong> B in<br />

Figure 5.12(b).<br />

From B <strong>to</strong> C the area between the acceleration–time curve and the time axis is<br />

positive, so the area (A 2) reaches its greatest positive value at C. Now we can sketch<br />

the vertical velocity curve from B <strong>to</strong> C in Figure 5.12(b).<br />

Finally, from C <strong>to</strong> take-off at D (time T), we have a small negative area, A 3, and the<br />

vertical velocity decreases from its largest positive value by this small amount before<br />

take-off, as in Figure 5.12(b).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!