Key to cricket: Keep your eye on the ball?

i-eca0cf2af9fc3ac4445c7dff7d8aab70-research.gif"Keep your eye on the ball" is a mantra I've heard applied to several sports: baseball, for hitting, football, for receiving, and golf, for teeing it up. It wasn't surprising to me when I read recently that cricketers also use this platitude to teach batsmen how to hit effectively.

The sum total of my experience with cricket is watching multi-ethic games in Van Cortland Park through our Bronx apartment window while Greta and I were finishing graduate school about 12 years ago. I didn't pick up on many of the rules, but I was stunned to see that cricketers, unlike baseball players, actually had to hit balls on the bounce.

A study by Michael Land and Peter McLeod takes a close look at exactly how cricket batsmen are able to follow the ball closely enough to accurately hit it. The authors point out that a fast ball takes just 600 milliseconds to reach the batsman. The fastest batsmen can adjust their shots in 200 milliseconds, which also corresponds to the time from the bounce to reaching the bat on a "good ball" -- the ideal bounce point. If the ball bounces closer to the batsman, it's relatively easy to hit because the batsman need not react to the bounce. If the ball bounces farther from the batsmen, he has time to react, even to an odd bounce.

What Land and McLeod wanted to know is whether good batsmen actually followed the "keep your eye on the ball" advice. They monitored the play of three batsmen: one professional, one a good amateur, and one a poor amateur, to see if they could identify consistent patterns in their batting behavior.

Players faced an automated bowling machine ("bowling" is the cricket term for delivering the ball to the batsman [see Chris's comment below for an explanation of the process]; the person doing the bowling is the bowler). Each player was equipped with a headset that videotaped in the precise direction the player's head was facing. A second videocamera monitored the player's eye movements. Take a look at this sample of the results:

i-4c4abf0afa20d5cac480074469f87b6e-cricket.jpg

These six frames of the good amateur's view, taken at intervals of about 100 milliseconds, show both the path of the ball and the orientation of the fovea -- the tiny area of our visual system that can accurately focus on details. I've enhanced the image to make it easier to see what's going on: the yellow dot represents the fovea, while the red dot is the ball.

Notice that in frame 1, the player is focused right on the ball. In frame 2, when the ball has just been bowled, again the fovea is close to the ball. But in frame three, the fovea quickly moves ahead of the path of the ball -- approximately to its bounce point. In frame 4, where the ball bounces, the fovea and ball again overlap. But by frame 6, the fovea again moves away from the ball -- remember, by this point, it's impossible for the batsman to react to the ball's movement.

Land and McLeod plotted the angle of the ball and fovea relative to the head position for each player, as well as for each type of pitch. A typical plot looked like this:

i-083fc8a39cab2d95e34eb1005f262106-cricket2.gif

These plots show that each player used essentially the same strategy: they followed the ball closely for the first 200 or so milliseconds. Then they quickly shifted their view to the predicted bounce point and waited for the ball. When the ball bounced, they maintained focus on it for as long as possible, even though at this point it was no longer possible to react to the ball's movement. The main difference between the better and worse players was how closely they followed the ball's trajectory: the professional followed the ball most closely, both at the beginning and the end of its flight.

How did this translate into game-time performance? The professional and the talented amateur were able to attack balls that bounced either earlier or later than the ideal bounce point. The less talented amateur was forced to make defensive swings on all but the early-bouncing balls ("short pitches"). Better players were able to make good swings more often than poorer players.

What information were the batsmen using to make their swings? Based on the data they gathered, Land and McLeod argued that batsmen rely primarily on the time it takes from the ball to leave the bowlers hand and when it hits the ground: this, combined with the location of the bounce, can give a good judgment of the ball's speed, allowing them to predict the height and time it will reach their bat. Other factors, such as binocular disparity (triangulating the distance to the ball based on the different perspectives offered by each eye), were determined to be too difficult to calculate given the distance to the ball and amount of information available.

Now, if only Land and McLeod could explain the meaning and origin of the phrase "sticky wicket," and why cricket only has two bases, I think I might begin to understand how this elusive game is played.

Land, M.F., & McLeod, P. (2000). From eye movements to actions: How batsmen hit the ball. Nature Neuroscience, 3(12), 1340-1345.

More like this

Nice review of an interesting article. It's also worth noting the typical latency from light hitting the retina to the signal actual being passed to the bipolar cells. If I can remember my undergraduate lectures correctly, it takes around 100ms for the photoreceptors to undergo conformation changes, altered transductin --> phosphodiesterase activity ---> cGMP levels ---> Sodium channel activity.

According to wikipedia:

"The term sticky wicket comes from a situation in which rain has dampened the pitch. This makes the path of the ball more unpredictable thus making the job of defending the stumps that much more difficult. Such pitches were commonplace at all levels of the game (i.e. up to Test Match level) until the late 1950s." http://en.wikipedia.org/wiki/Wicket

As for two "bases", why does baseball have four?

My inner Englishman takes great offence to:

'"bowling" is the cricket term for throwing the ball to the batsman.'

One most certainly does not throw the ball to the batsman.

The bowler must keep their arm straight and use an over-arm action. A failure to keep the arm straight is classed as a throw and is illegal.

Chris

Chris, thanks for straightening me out on that one. I've fixed the post.

Lab Cat, so if you're in a "sticky wicket," it means that you're in an impossible situation, right?

nice post Dave.

re: "sticky wicket" - it really means 'tricky' or 'difficult' rather than 'impossible' situation.

re: Chris' comment about keeping the arm straight through the delivery - yes and no. It's the act of changing the bend of the arm that makes it illegal. Two examples to illustrate: 1) if I bowl starting with my arm straight but the arm bends as I let go of the ball or just after it, that is illegal 2) if I start with a bent arm but it remains bent while and after the ball is let go then that is legal. My point it that the arm doesn't *have* to be straight, but it can't straightEN or bend just before, during or just after delivery.

Another thing young cricketers are taught is to keep their head still while batting, especially when hitting through the ball: any rocking, or jerking of head reduces the balance of the batter and decreases the chance of the batter to predict the ball's trajectory.

And what, exactly, is a 'Test Match'?

Dave, I find this article fascinating!

RSG you may be interested to read:
http://en.wikipedia.org/wiki/Cricket

To put together a few quotes from Wikipedia;

Test matches are two innings per side, usually played over five consecutive days. The name "Test" is thought to arise from the idea that the matches are a "test of strength" between the sides involved. It seems to have been used first to describe an English team that toured Australia in 1861-62, although these matches are not considered Test matches today.
Test Cricket remains the highest-regarded form of the game, although the comparatively new One-day International cricket is now more popular amongst some audiences.

By An Australian (not verified) on 09 Jul 2006 #permalink