THE BOOK cover
The Unwritten Book
is Finally Written!

Read Excerpts & Reviews
E-Book available
as Amazon Kindle or
at iTunes for $9.99.

Hardcopy available at Amazon
SABR101 required reading if you enter this site. Check out the Sabermetric Wiki. And interesting baseball books.
Shop Amazon & Support This Blog
RECENT FORUM TOPICS
Jul 12 15:22 Marcels
Apr 16 14:31 Pitch Count Estimators
Mar 12 16:30 Appendix to THE BOOK - THE GORY DETAILS
Jan 29 09:41 NFL Overtime Idea
Jan 22 14:48 Weighting Years for NFL Player Projections
Jan 21 09:18 positional runs in pythagenpat
Oct 20 15:57 DRS: FG vs. BB-Ref

Advanced

Tangotiger Blog

<< Back to main

Wednesday, March 25, 2020

Statcast Lab: Is there a different run value needed based on the infield slice?

By Tangotiger 05:35 PM

One of the things that we’ve done in the long past is to give a different run value for 1B/3B, compared to 2B/SS. The idea was simple enough to understand: if a 2B or SS allowed a hit, it was likely a single. And if it was a 1B/3B, there’s a chance that it could be an extra base hit down the line.

Seems reasonable enough. So, what we ended up doing, in the long past, was to give .75 runs per play for 2B/SS and .80 runs for 1B/3B. Again, seems reasonable enough.

I looked at the Outs Above Average (for infielders only; I’ll do outfielders later today or tomorrow). And while the direction of that theory holds, the magnitude does not hold quite as much. For the 2B/SS roles, the impact of their play is -.005 runs, compared to the average infield play. While for the 1B/3B roles, the impact of their play is +.010 runs, compared to the average infield play. (The overall WEIGHTED average is 0, and you get there because there’s about 2X the plays at 2B/SS compared to 1B/3B).

So, the end result is that the gap in runs between the middle infielders and the corner infielders is about .015 runs, not the presumed long past value of .050 runs.

Why would that be? It’s probably easiest to say that 5% of the “assigned hits” are extrabase hits. But as we know, there’s alot more than just 5% hits that are extrabase hits, even if we limit it to the infield. For example, almost 10% of groundballs are extra base hits. So why the discrepancy? Well, half of those groundball extra base hits are “automatic hits”. In other words, they are hits not because the fielder wasn’t good enough to get there, but rather, his POSITIONING didn’t allow him for a chance to get there. And since Outs Above Average takes as an assumption of fact that the positioning of the player is not a skill of the player (easier to believe these days with shifting), then those auto-hits are not opportunities for the player. They end up being noise.

When we get to Layered Hit Probability (and by extension Layered wOBA), we will recover those “lost” hits, and be able to properly assign them to “team fielding alignment”. But, for the Outs Above Average metric, those aren’t in play (no pun intended).

Ok, so you may be thinking,we lost half, so maybe instead of the long past value of .050 runs, maybe it should be .025 runs? That is a good thought. Except, alot of those remaining extra base hits that are assigned to the fielder are “really difficult”. In other words, they remain in the pool for the player, but the hit probability is so low that they have limited damage to the fielder.

So, if you want a quick summary: the kind of hit that an infielder is responsible for is almost always a single. And because of that, when you look at outs saved, the translation to runs saved will be almost identical for middle infielders as for corner infielders.

Next time, I’ll compare IF to OF.


#1    Tangotiger 2020/03/26 (Thu) @ 18:59

With the outfield, it’s a big deal.  Whereas about 5% of basehits for infielders are extrabase hits, in the outfield, it’s over 50%.

That by itself establishes the run value for an OF play at 0.90 runs (and in the infield, it’s 0.75 runs).

***

The question is if different OF plays should get a different run value.  So, I watched dozens of plays by Buxton (who had among the fewest number of extra base hits allowed) and Heredia (who had among the highest).

Here’s two sample Buxton plays for your consideration:
https://baseballsavant.mlb.com/sporty-videos?playId=9fea8dbe-570d-450c-8dd2-3a4f2b36e74b

https://baseballsavant.mlb.com/sporty-videos?playId=609070f5-e65d-4ea7-b5fa-4bbb789c10ba


And in looking at these dozens, what it came down to me was: the skill of the player, and the leverage of the opportunity.  And there’s analogy with relievers and Leverage Index.  How to you give out wins in terms of leverage index, for opportunities that the reliever didn’t create, but he did… leverage.

If a pitcher keeps getting balls hit to the warning track, and Buxton keeps pulling them down, he’ll get tons of runs saved.

And if a pitcher keeps getting balls hit shallow, and the outfielder pulls them down, he won’t get as many runs saved.

If we give play specific runs to the outfielders, you may end up with an outfielder making 60% catch probability outs that are shallow getting less runs than 70% catch probability that are deep.

But in terms of the SKILL of the outfielder, what matters is the difficulty of the play, not the leverage of the play. 

FOR THAT PLAY, the outfielder may have gotten value.  But that’s alot like giving credit to a grand slam HR being worth more than a solo shot.  In terms of the SKILL of the hitter, 40 solo shots tells us more than 20 grand slams.

And so for a hitter, it makes more sense to give out the skill value for the HR, and then create a “timing bucket” for the leverage of the HR.

***

Even if we were to roll it all up together, when I looked at each outfielder, the “leverage” component came in at +/- 2 runs for every outfielder.  So, we’ll capture it, but not as a skill value, but something else.

***

Going back to IF v OF, if both are +20 OAA, the infielder will count as +15 runs and the outfielder as +18 runs.  This is not terribly different from counting all OAA as 0.8 runs (or +16). But in this case, the quality of infield and outfield plays are different enough as to warrant the differing run values.


#2    Tangotiger 2020/03/27 (Fri) @ 10:53

Another consideration for outfielders to consider, which makes the illustration stark: HR saving catches.

Suppose you have one outfielder that plays half his games at a park where the OF fence is 8 feet or under.  And another where the fence is 12+ feet.

It is easy therefore to see how one outfielder could have say 5-10 opps to “save” a HR. While another might end up with 0 for the season.

Now, suppose our CF “saved” 3 out of 10, where the league average is 1/10.  Will we give him the run value of 2x1.6 for saving these two extras?

And our other OF, he had 10 opps, but all warning tracks.  And again, assume the average was 1/10 and he caught 3/10.  His run value will be 2x1.1.

Finally, our other OF who misses out on all warning tracks, but is getting lots of balls running in.  And on those tough ones running in, he gets 3/10, with the average being 1/10.  His run value will be 2x0.8.

So, we have these run values:
+3.2 runs
+2.2 runs
+1.6 runs

Do we want to represent the skill displayed based on the “leverage” of the opportunity?

Or, is the leverage of the opportunity immaterial with respect to what we learn about a fielder’s skill?

In my view: we CAN account for that extra leverage, but as a separate component.  In the above, I’d give them all 0.9 runs, so it looks like this:
+3.2 runs = 1.8 skill runs + 1.4 leveraged runs
+2.2 runs = 1.8 skill runs + 0.4 leveraged runs
+1.6 runs = 1.8 skill runs - 0.2 leveraged runs

One guy is put into a position to leverage his skill.  Like Mariano.  And another guy, equally skilled (or even the same guy!), put into a position of low-leverage.

Analogous to looking at Rivera’s performance in high leverage and mopup situations.


Click MY ACCOUNT in top right corner to comment

<< Back to main


Latest...

COMMENTS

Aug 08 19:46
Walking Aaron Judge with bases empty?

Jul 15 10:56
King Willie is dead.  Long Live King Reid.

Jun 14 10:40
Bias in the x-stats?  Yes!

Jun 13 17:05
Bat Swing Checklist

Jun 07 12:10
Spray Angle is not needed, part 32

Jun 02 17:37
Stanton Swing Speed and Acceleration Curves

Jun 01 14:44
Statcast Lab: Pre-introducting Bat Acceleration

Jun 01 12:14
Bill James and Tango talk WAR

May 28 16:56
In support of Bill James against the implication of Catcher Framing

May 28 15:24
NaiveWAR and VictoryShares

May 28 15:20
Statcast Lab: Switch Hitters and Swing Speed

May 06 13:59
Team depending on Free Agency

Apr 24 15:03
How bad will the A’s be?

Apr 11 13:38
Re-introducing WOWY NetGoals and NetShots for NHL

Apr 02 21:16
Bayesian inference: How much new information is contained in a streak?

Apr 01 21:25
Extra Innings: whatsup?

Mar 31 09:34
Goodbye Pythag Wins, Hello Gradient Wins

Mar 21 11:55
Revenge of the Defense

Mar 20 17:14
NaiveWAR and WAR2.0: Jacob deGrom

Mar 15 17:22
Statcast Lab: Catcher knee height prior to pitch release