Statcast Stories

If you have been here before, you know about my preocupation with baseball statistics. I love 'em. I'm fascinated by 'em. I spend way too many hours every day thinking about them.

But it's also true, as Lina Lamont once said, I ca-a-an't stand 'em

Yes, it drives me to distration when people rattle off small-sample statistics like "Batter X is 0-for-3 against Pitcher Y" or unhelpful stats like "Fred is hitting .330 with runners in scoring position this month," or misleading stats like "He now has more postseason wins than Sandy Koufax."

Bill James has explained it as the "power of language" -- some statistics have the power of language and some do not. I tend to think of it in storytelling terms. The statistics I love are ones that, at least for me, open up the world just a little bit, take me into the history of the game, uncork a side of baseball I'd not seen before, challenge my beliefs and conviction. The best statistics do not necessarily give easy answers. They tell fascinating stories.

Statcast is a wonderful MLB tool that measures (in accurate terms previously unimaginable) player movements and baseball velocity and the geometry of the game. It is a Niagara Falls of data -- route efficiency, exit velocity, launch angle, hang time, velocity AND perceived velocity, on and on and on.

As always, the data comes first. And the storytelling follows slowly but surely.

Well, it takes time to figure out what these statistics mean ... and more time to figure out how they can add to our understanding and enjoyment of the game. I'm a huge tennis fan and so I watch match after match with absolute horror as the announcer give me the IBM Stat of the Day. It is always something stupefying like, "If Kei Nishikori wins 47% of his second serve points, he has a 72% chance of winning the set."

I have absolutely no doubt that there is some significant and intricuate math behind this, but even to me -- a hardened tennis fan -- it means absolutely NOTHING. It tells me NOTHING. It is like the Spinal Tap jazz odyssey -- it takes me nowhere. Even if I could do the various calculations to figure out what it means (which is probably no more than "Nishikori needs to win points on his second serve to win") it would leave me utterly cold.

I'm not saying I'm immune from such number dancing -- even a cursory glance at my archive shows that I go down the statistical rabbit hole more than most do. I'm saying that with all this extraordinary technology now and all these new ways to collect data, we are entering a wonderful and perilous new time. We can tell fantastic stories that would have been absolutely impossible to tell berfore. And we also can drown.

I'll give you two examples from Game 1 of the Cubs-Dodgers series because I thought the contrast was striking.

On TV during the game, they showed us the Statcast data on a nice play made by, I believe, Dexter Fowler. On the screen they showed that on the play, Fowler had a 96% route efficiency, which could be interesting if I knew what it meant.

And it showed that he reached a max-speed of 18 mph which isn't interesting at all.

The route efficiency, if I understand it right, shows how straight a line the outfielder made from his starting point to where the ball was eventually caught. There's promise in that one, but we need some context. Is 96% good? It sounds good. But, as the old line goes, if an airline 96% efficiency in planes landing safely, that would be a horrendous percentage. I'm sure people steeped in Statcast already have a good feel for what route efficiency means but I think it will take some time and history for that to translate into story telling. I know Tom Tango works hard on this.

The 18 mph max velocity thing -- it's just not impressive or revealing. It reminds me of another tennis stat, one where they show how much a player runs during a grueling point. That number is ALWAYS surprisingly low. It's always something like 113 feet. I mean: big deal. He ran 37 yards. Whoopee. The sheer physical beauty of watching Novak Djokovic run down four impossible balls in a row is so awesome that any number showing the distance run is bound to be an anticlimax. It's like showing Usain Bolt run the 100 and, in the awed aftermath, saying that he's about 40% as fast a jaguar.

So, all in all, that Statcast hit did very little for me.

But a little bit later on, there was another Statcast stat -- I don't know if they shared it on TV. The Dodgers' pinch-hitter Andre Ethier hit what appeared, off the bat, to be a pop-up. Seasoned announcers like Joe Buck rarely get fooled by a ball off the bat. They know to follow the outfielders' motion. But the outfielders were fooled by this one too. It caught the Chicago wind stream and just kept sailing and sailing until it was over the ivy at Wrigley. It was a fairly startling home run even to the naked eye.

Now, Buck and John Smoltz did make the point that the ball looked like a pop-up off the bat and it just carried. So the point was made.

But Statcast made the point in a much more interesting way. It told a story.

The exit velocity of the hit was 98.3 mph. The launch angle was 43 degrees.

That combination of speed and angle adds up to what is known in the business as an OUT. Every time. When you hit a ball at that speed, at that angle, it is a popup. It is a lazy pop-up.

And because Statcast is so precise, you can cross-reference and prove the point. Baseballs were hit at that speed and angle 40 times. Thirty-nine of those times, the ball was an out.

So you say -- well, wait, that means one time it was a hit. That's true. It was a double.

Here was that play:

Your browser does not support iframes.

So, uh, yeah. That's an out too. Yes, we could tell that the Ethier homer was unusual. But Statcast shows us that it was a bloody freak of nature. If the Cubs had lost that game, that home run could have become legendary, the immaculate homer. As it turned out, the homer ended up being incidental because Dodgers manager Dave Roberts decided to anger the Intentional Walk Gods, and lo they rained down harsh (but fair) justice upon his team.

But the point remains. I'm pumped up -- Tango has promised to help me learn the secrets of Statcast. There are stories in the them thar digits.