[From Bill Powers (2011.04.18.0840 MDT)]
DG: Would there be any different
coaching tips you would give for someone learning to catch a flyball
based on the different models for what is attended to?
Rick Marken: So far, my
hypothesis fits the
data best, particularly in situations where the actual trajectory of
the ball (or object to be caught, such as a Frisbee) results in
disturbances that “push” the alternative variables (optical
trajectory
and vertical optical acceleration) away from their reference
states.
BP: Specifically, move yourself so the ball appears to be ascending
slowly at a constant speed and in a vertical direction. If you can do
this, the ball will pass within reach just above your head, and it won’t
hit you in the head or body if you miss it (unless your glove deflects it
downward, so angle the glove up a little). This was actually mentioned in
print first by a physicist named Chapman, if I remember the name right,
in Science, some time in the '60s I think. He didn’t know he was talking
about controlling a perception, but he was. I told Rick about this and he
used it as the starting point of his modeling.
I just Googled “chapman catch fly ball science” and came up
with
http://www.livescience.com/3445-baseball-players-catch-fly-balls.html
Chapman called his theory OAC or Optical Acceleration Cancellation,
but the way he described it was that the fielder would keep the tangent
of the vertical angle increasing at a constant rate. As a physicist, he
thought in terms of the actual vertical acceleration, which would
be proportional to the tangent of the apparent (angular) acceleration.
However, the fielder perceives the apparent acceleration, not the actual
acceleration, and keeping the apparent vertical angular acceleration at
zero works better (you don’t have to perceive the horizontal distance to
the ball accurately and multiply it by the tangent of the angle to get
the vertical acceleration). Of course keeping the angular acceleration at
zero means keeping the angular velocity constant, which is what we
actually do. My recommendation of keeping the velocity small and positive
(upward) is simply a safety precaution, though I believe Chapman also
described it that way. You will also be able to “Look the ball into
the glove” as baseball coaches put it, because the glove won’t hide
the ball as you catch it. If you keep the velocity small and downward,
the ball will hit you in the stomach if you miss the catch. What you
really don’t want to do is keep the vertical velocity at zero. If
you do that perfectly, the ball will hit you in your dominant eye when
you miss.
The author of the article in the link above missed the
control-of-perception point entirely: “First, great ballplayers will
not sprint to the exact spot on the field where they think the ball will
land and then wait for it. Rather, they usually adjust their speed to
arrive at the landing spot just as the ball arrives.” Of course they
don’t do that. The speed is simply adjusted however necessary as part of
keeping the ball slowly rising vertically as the moving fielder sees it.
It’s a very simple control system (or two of them operating at right
angles). That gets the fielder to the right spot at the right time
without having to make any predictions.
The author concludes, “So, if you’re now coaching Little Leaguers,
be patient. Their brains may still be learning the math.” This idea
of compute-and-execute is the new shibboleth we now have to fight – it
pervades neuroscience and is worse that the “inverse dynamics and
kinematics” arm-waving and stimulus-response stuff we’ve been
dealing with for decades. Of course an outfielder’s brain does no
mathematics on the way to catching a fly ball. If your average outfielder
who got an A in math could do it at all, he would probably miss the
catch. Even if you could do analytical geometry perfectly and instantly,
which a brain can’t do, you can neither perceive nor act accurately
enough to make that work.
Here’s a link to download a demo I wrote a few years ago, after Rick
started his fly ball project.
[
http://www.billpct.org/CatchBall.exe
](http://www.billpct.org/CatchBall.exe)The two structures you see are supposed to be left and right
grandstands. You’re an outfielder and you can move yourself on the field
by moving the mouse left-right or forward-backward. If you center
yourself relative to the two grandstands and move the mouse forward,
you’ll see the baselines with second base closest to center. A flyball
will be seen at first, but ignore it.
A left-click causes a fly ball (a black dot) to be batted in some
direction and with some speed. You have to move to catch it. You can’t
actually catch it, but for most trials, you can make it pass close to
you. You’ll see it getting bigger just as it gets to you. You can move a
lot faster than a real outfielder could. Just maneuver yourself to keep
the ball rising vertically (not drifting left or right) at a VERY slow
constant rate. It will come near enough to look like a black circle just
before it disappears. It’s the actual apparent size of a baseball. If you
back up a little you’ll see the ball where it landed (it doesn’t
roll).
I didn’t keep track of how the fielder moved so it could be displayed
after a catch. I guess I should do that, but the source code (Delphi) is
available if anyone else wants to do it first. Maybe I’ll use this as an
opportunity to learn more about using OpenGL, a nifty graphics system
built into most computers.
Best,
Bill P.
···
At 08:33 AM 4/18/2011 -0400, David Goldstein wrote: