Mets vs. Nationals

Oh man, what a brutal game. Once again, solid-looking offense that still fails to deliver while our pitching falls apart. Pelfrey was looking so good at the beginning. It just seems weird that the Mets could outhit Washington and yet end up nine runs down. I mean, we had a bunch of walks, but nine runs' worth? I guess we were making hits when they didn't matter, while the Nats made theirs count. And how is Ronnie Belliard so good against the Mets defense?

One of the viewer questions answered by the broadcast team was about the OPS offensive stat, which I hadn't heard of before. At first it sounded pretty reasonable from a math standpoint—a sum of two percentages, which isn't extremely rigorous as far as quantifying events, but comes pretty close for disjoint events (e.g., the percentage of days in which I play tennis plus the percentage of days in which I play squash is very close to the percentage of days in which I play racquet sports, since I don't play other racquet sports and very rarely play both in the same day) and is very easy to calculate.

(I don't have a problem with the loose application of terms like "average" and "percentage" in baseball stats. Bad assumptions about what these kinds of terms say about the underlying data is already a huge problem in the general population's understanding of things like economic data ("the median income is rising!"), so the more we can encourage people to think about what dynamic is actually driving a given number, whether it's called "average" or "percentage" or something else, the better.)

But if you actually start to think about what the two stats that are added together to get OPS, on-base percentage and slugging percentage, actually stand for, the meaningfulness of it starts looking a little questionable.

Slugging percentage is pretty straightforward: it's a hitter's total number of bases gained on hits, divided by their at-bats. As a predictive metric, that's easy to understand: we should expect a player slugging .500 to get about five bases in ten at-bats. The stat appears to say something very simple about a player's hitting ability, and only their hitting ability. In statistical terms, it's the expected value of bases a runner will hit for in an official at-bat.

On-base percentage is a little more subtle. It's a ratio between two multiple-term expressions, but basically what it boils down to is, absent any mistakes or decisions made by a manager or a defensive player other than the pitcher, how likely is it that a given batter currently at the plate will end up on base? This means that on-base percentage incorporates some offensively valuable metrics—the ability to draw a walk, for example—that are not accounted for by slugging percentage. But note also that, statistically, on-base percentage is a probability, not an expected value.

So what do these things say about a player when they're added together? By the admission of the people who came up with OPS, nothing real. But the OPS does represent something like "offensive value" that neither on-base nor slugging percentage captures on its own: a given player may get more extra base hits than another, but their greater ability to draw walks means that in the end they bring a similar offensive value to the team.

Is there a more meaningful way of calculating that same information? I'm not sure. Wikipedia makes it sound as though OPS was conceived as a more easily calculated alternative to SLOB (the product of the two stats instead of the sum) and "runs created" (the product of SLOB and at-bats). Simple addition "works" as an alternative because the two statistics are of the same order of magnitude. But neither SLOB nor runs created deals with the problem of trying to combine an expected value and a probability.

I might prefer instead to replace the "hits" term in the numerator of the on-base percentage with the "total bases" value used to measure slugging. The resulting figure would be a valid expected value, but taking into account plate appearances, such as walks, that are excluded from official at-bats. At the very least, we should no longer allow difficulty of calculation to limit the statistics used for comparing aspects of play. There may be any number of reasons for eschewing SLOB, but the fact that it requires a sliderule to determine should not be among them.

Anyway, all of that aside, OPS as a measure of offensive value reminds me of IQ as a measure of human intelligence. Indeed, there is even a statistic called OPS+, which measures on-base and slugging percentages against the park-adjusted totals for the league, and then scales them so the league average is at 100. A player with an OPS+ over 150 could be said to have a genius-level offense, while one with an OPS+ of 50 might be considered an offensive imbecile.

In fact, the original purpose of OPS+ was to identify challenged players who required extra instruction during batting practice. Then later it was misapplied in an attempt to demonstrate that Negro League batters were innately inferior to their Major League counterparts. (Okay, this paragraph is made up.)

OPS and OPS+ are useful metrics for comparing the offensive abilities of different players. OPS+ probably correlates pretty well with RBI and does a fair job of predicting career runs, not to mention player salary. A pocket calculator with access to the statistics could be programmed to organize starting batting orders strictly by OPS+ and probably come pretty close to making the same decisions as a Major League manager. If you had to guess which non-pitchers (nullus) on an A-class rookie squad would go on to make the big leagues, you could probably do worse than to pick the group of players whose OPS+ figures are over, say, 125.

And yet, OPS is not something unknown that we've managed to measure with some sort of test and then stuck with because it's just so damn useful. There's no mystery behind what OPS "is": it's just something we've defined arbitrarily, this formula of different well-understood concrete statistics cobbled together, and which we know for a fact has no intrinsic meaning except as an abstraction. It's a convenience, a tool for making comparisons without having to get into the fine details of the fundamental attributes (both inborn and learned) like upper body strength, mental reaction time, experience at the game of baseball, and sprinting ability, many of which might prove difficult to measure, if not impossible. We would be mistaken to take the utility of OPS as evidence of an underlying phenomenon of the baseball player body, some organ the fitness of which determines offensive ability.

Implicit in our OPS-centered discussion of "offensive value" is the knowledge that no single figure can hope to sum up all of what makes a given player valuable in an offense, and that real offensive value is only truly meaningful in the context of an actual in-game situation. We have no reason to consider the existence of "general offensive ability" anything other than a statistical abstraction; and certainly not as the product of some "general offensive ability factor" behind all the various quantifiable and non-quantifiable aspects that figure into offensive value.

With one exception, everything that I've stated about OPS and OPS+ applies analogously to IQ. Both can be useful metrics for making comparisons, can be used to estimate or predict more concrete information to which we may not have access, and can lead to poor decision-making when misapplied or taken out of context. The exception is that whereas we can say exactly how we determine OPS, how the actual figure, devoid of intrinsic meaning though it may be, is calculated from raw data. In contrast, we have no real idea what an IQ test measures. We call it "intelligence," but there's no breakdown in terms of rates of neural activity, or brain volume, or anything measurable beyond the fact that it correlates with a bunch of other things to an extent that we find it useful in making comparisons and predictions. We give it extrinsic meaning, but there is still nothing at all to believe that IQ "is" anything, that it comes from anywhere, that it is anything other than a statistical abstraction, like OPS+, useful to us only because our limited minds cannot deal with the whole array of information, some of it perhaps not even quantifiable, that lurks behind that single figure.