Tuesday, September 10, 2013
WAR misconclusion
In this thread, there was this comment:
Then WAR isn't really measuring value over replacement level. It's an indispensible prerequisite to the concept of WAR that the (anticipated) production of the replacement level player in all three phases be identifiable and identified in a way that makes sense.
That is a false conclusion. His second sentence is correct, and actually, very well articulated. The key point is this:
identifiable and identified in a way that makes sense
And this is done by comparing the performance against the league AVERAGE player. This is the key part of the WAR framework as I've shown it many times. Everything is compared to the average, every little component. Heck, you can even break out the HR and BB and whatever, and compare it against the league average. Everything.
Then, at the end, you compare the total of all these components relative to average, and apply an overall average-to-replacement level adjustment. It's at the PLAYER level, not the component level.
And therefore the conclusion is that WAR *is* measuring against the replacement level... it's the replacement level player.
?
And later in the thread, you see the confusion of oWAR and dWAR. It’s really too bad that BR.com continues to do this.
I think the WAR framework is fantastic, and Rally’s implementation on his site is wonderful, as is David’s at Fangraphs.
Sean has done tremendous stuff in putting it out there as well. But these little things simply are obstacles that don’t need to be there. There’s confusion in the marketplace where none needs to be.