[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

OPS: Be Gone! - Part 2

How accurate is OPS?

By Tangotiger

Last week, I looked at 6 players of varying degrees of profile (high-walk, low-power to low-walk, high-power) who had an equal impact in run production when surrounded by typical teammates. We learned that to equalize these players using only OBA and SLG, we need to use the best-fit equation of 1.64*OBA+SLG.

After that article came I out, I received two very interesting questions.

  • Instead of choosing 6 equal players, and trying to do figure out the best-fit equation, why not take 6 players of equal OPS (with widely varying OBA and SLG), and try to figure out how different their run production would be. That is, if we really really want to use OBA+SLG, how far off will we be?
  • Can you select 6 players of equal OBA and equal SLG, but with widely varying Batting Average? Essentially, how much error do we have by not looking at AVG as well?

Two great questions, and so, let's find out the answers.

Same OPS, widely differing OBA,SLG

The following table presents 6 players with the same OPS.

 
AVG OBA SLG OPS
0.267 0.29 0.453 0.743
0.267 0.313 0.431 0.743
0.267 0.333 0.41 0.743
0.267 0.353 0.39 0.743
0.267 0.371 0.372 0.743
0.267 0.389 0.354 0.743

 

In order to construct a typical team, I have to adhere to the following constraints: each team will generate the same number of outs, and each player on the team will have the same number of PAs. Now, I'm counting outs as AB-H, though technically that is not true. You can also get outs on base. However, given that these teams are very similar to begin with, we'd expect the outs on base to even out. Here are the 6 teams that result from using the above players.

 
AVG OBA SLG OPS BsR Diff from Baseline
0.267 0.329 0.415 0.744 675.5 -5.7
0.267 0.331 0.412 0.743 677.9 -2.9
0.267 0.333 0.41 0.743 680.3 0
0.267 0.336 0.408 0.743 682.8 3
0.267 0.338 0.406 0.744 685.3 6
0.267 0.34 0.404 0.744 687.8 9.1

 

The first 5 players in that group are the most realistic looking of the players. We see that while they have the same OPS, they do not have the same run impact. In fact, there is an 12-run swing from one realistic end to the other. So, if you rely on OPS, realize that you will be off by up to +/- 6 runs. And this is for this kind of player. If you choose star players instead of average players, the swing will be even greater, perhaps double that. It's up to the reader to decide if this is an acceptable deviation within his objectives.

Now, let's look at other run measures as well. The following table presents our 6 players, with their expected PAs and outs to conform to the above guidelines (that is, this is how they would do if they each played in the same number of games).

In addition to the typical numbers, I present

  • that player's BaseRuns,
  • his BaseRuns/440 outs,
  • his BaseRuns/440 outs relative to the baseline,
  • his static LWTS relative to the baseline, along with
  • the team run differential from the above table. This last value is the player's true value. For those who follow Keith Woolner's work, this is akin to his Marginal Lineup Value. I believe that Bill James does something similar with his Theoretical Team Construction as done Fanhome regulars David Smyth and Patriot.

 
PA Outs AVG OBA SLG OPS BsR BsR/440 BsR+/- LWTS Team diff from baseline
655.3 465.1 0.267 0.29 0.453 0.743 74.2 70.2 -5.4 -5.7 -5.7
657.7 452.2 0.267 0.313 0.431 0.743 75 73 -2.6 -2.9 -2.9
660 440 0.267 0.333 0.41 0.743 75.6 75.6 0 0 0
662.2 428.5 0.267 0.353 0.39 0.743 75.9 77.9 2.4 3 3
664.2 417.5 0.267 0.371 0.372 0.743 76 80.1 4.5 6 6
666.2 407.1 0.267 0.389 0.354 0.743 75.9 82.1 6.5 9 9.1

 

Alright, so what do we have here? We know that BaseRuns is not a precise measure of run production for hitters (only for pitchers and teams). However, how accurate is BaseRuns? We know that static Linear Weights is not a precise measure of an individual hitter (nor for a pitcher nor a team). But, how accurate is it?

The above table shows that static Linear Weights is very accurate (a virtual match). This statement comes with a disclaimer. Because I chose 8 typical players to form my team, and because the static Linear Weights values are based on the historical typical team, we should expect it to be very accurate. If I would have chosen 8 typical 1960's hitters, we would not have achieved this level of accuracy using the static LWTS model. (We need custom LWTS values.)

Among the first 5 realistic hitters, we see that BaseRuns is accurate to within 1.5 runs. That is rather impressive, considering that the interaction effect occurs at the team level, and not the individual level.

 

Same OBA, same SLG, widely differing AVG

The following table presents 6 players with the same OBA, same SLG, but widely differing batting averages.

 
PA AB H 2B 3B HR BB Outs AVG OBA SLG OPS BsR BsR/440 BsR+/- LWTS Team diff
from baseline
660 640 200 30 4 8.1 20 440 0.313 0.333 0.41 0.743 74.6 74.6 -1 -1.8 -1.7
660 620 180 30 4 12.1 40 440 0.29 0.333 0.41 0.743 75.1 75.1 -0.5 -0.9 -0.8
660 600 160 30 4 16 60 440 0.267 0.333 0.41 0.743 75.6 75.6 0 0 0
660 580 140 30 4 19.9 80 440 0.241 0.333 0.41 0.743 76.1 76.1 0.5 0.9 0.9
660 560 120 30 4 23.9 100 440 0.214 0.333 0.41 0.743 76.6 76.6 1.1 1.8 1.8
660 540 100 30 4 27.8 120 440 0.185 0.333 0.41 0.743 77.2 77.2 1.6 2.6 2.7

 

Essentially, as the walks and HR go up, I decrease the hits. In this way, I force the OBA and SLG to match, while varying the batting average.

We see that not considering the batting average in your OPS metric will have an effect of +/- 2 runs. We again see that Linear Weights, as expected, is an almost perfect match. BaseRuns comes to within 1 run of the true value

 

Conclusion

When using OPS, be aware of its accuracy and its limitations. As a back-of-the-envelope calculation, it works reasonably well. But, don't take it too far.