Build a Better WAR Metric, Part 7
So far, we’ve looked at seeing the overall impact be the same, but for different reasons, like the bases loaded walk versus the solo HR. And you are either given a choice of “same” or “this one is better”. It’s been designed to see if you prefer a DIRECTION. In the above case, the direction is based on whether the event matters.
Now, we’ll have two situations that have an overall different impact. We have our trusty solo HR. We all love the HR. It gives us a guaranteed run. It tells us about the hitter, and if given better circumstances, we can dream of even more runs.
If I ask about a double with a runner on second, I’d get into the same question as with the bases loaded walk: the impact is exactly one run, and we’re left with the same state that we entered. And 80% of Fangraphs readers will prefer the solo HR to the double with the runner on 2nd.
But how about a bases-clearing double? Any way you want to measure it, the impact is going to be alot(*) more than the 1 run from the solo HR. Run expectancy tables tell us it’s 1.7 to 2.2 runs depending on the number of outs.
(*) “Get over it.” — Scalia
So, how much of a hurdle are Fangraphs readers willing to climb to keep their allegiance to the event in a context-neutral setting, and ignore the context of a somewhat inferior event, but in a highly more leverageable setting?
Gosh, I am almost tempted to abstain because this comparison seems unfair (and of course it’s intended that way). The discrete partial run values of each event that created the runners on base has been credited right? Do we give double credit for timing those events well or give timing credit to a hitter put in a clutch situation? I think I am OK with there being a sequencing bucket that is not attributable to any individual players because it takes a team to sequence.