THE BOOK cover
The Unwritten Book is Finally Written!
An in-depth analysis of: The sacrifice bunt, batter/pitcher matchups, the intentional base on balls, optimizing a batting lineup, hot and cold streaks, clutch performance, platooning strategies, and much more.
Read Excerpts & Customer Reviews

Buy The Book from Amazon


SABR101 required reading if you enter this site. Check out the Sabermetric Wiki. And interesting baseball books.
MOST RECENT ARTICLES
MAIL : You ask | We say

Advanced


THE BOOK--Playing The Percentages In Baseball

<< Back to main

Monday, September 08, 2008

Win% estimators

By Tangotiger, 09:45 AM

UPDATE: This post has been corrected due to a bug on my part.

=============================

Great job by Zach, but I’ll quibble on the conclusion:

What’s funny is that Clay Davenport, inventor of Pythagenport, denounced his method in favor of Pythagenpat, yet it is in reality the best method when compared to actual record.

When the RMSE of one is 3.990 and from another is 3.992, that is essentially a tie.  What I did is repeated Zach’s study, with a wrinkle of my own.  Through 2007, he has 1792 team-seasons in his study.  I figured out the Clay and Pat win%, which I then multiplied by W+L, and then rounded to the closest whole number to get a win estimate.

The results.  Out of those 1792 team-seasons, there was a tie 1713 times!  In the other 79 times, Clay did better 39 times and Patriot was 40.  If we give each of them half-wins for their ties, Clay’s head-to-head win% over Patriot is .4997.  What works in Patriot’s favor is that it is a simpler construction that doesn’t break down at the extremes.

It’s fair enough to say that they are both equals for the sample at hand (where most teams play in a 9-10 runs per game environment), while Patriot won’t break down at the extreme levels.


#1    Patriot      (see all posts) 2008/09/08 (Mon) @ 10:16

I’m not surprised at all that Pythport/pat have essentially equal accuracy for actual teams.  The way I “found” the exponent was to try to find a function that matched Davenport’s results in the normal RPG range but also would give an exponent of 1 @ 1 RPG.  So there was never any claim or expectation on my part that there would be any accuracy gain for normal teams.


#2    Tangotiger      (see all posts) 2008/09/08 (Mon) @ 10:39

I found a little bug, and have updated the main entry.  Now, it’s Patriot that “wins” 40-39, with all those ties.

No biggie really.


#3    Tangotiger      (see all posts) 2008/09/08 (Mon) @ 10:43

If I use .289 instead of .287, the Pat289 beats Pat287 36-31 (and those 1700+ ties).

Clay against Pat289 is now 53-47 in favor of Pat.


#4    Tangotiger      (see all posts) 2008/09/08 (Mon) @ 10:58

Comparing Clay against Pat289, with RPG under 8, Clay is 21-17, and at 8+ RPG, Pat is 36-26.

Pat287 v Pat289: at 8+ RPG, Pat289 wins 34-23.  But at under 7, Pat287 is the one that wins 8-2.

***

With a straight divide by 10, compared to Pat289 shows that Pat wins 607-385, with 800 ties.  That gives Pat a .562 win%.

Pat and Clay are extremely similar, virtually identical, and world’s apart from simple metrics.


#5    Peter Jensen      (see all posts) 2008/09/08 (Mon) @ 13:10

Using the Pythagenport formula, we can find out teams that have been lucky and unlucky, by comparing their actual wins to expected wins based on Pythagenport.

We’ve had this discussion in other threads, but I still say that you can’t design a metric whose standard of accuracy is to get as close as possible to the ACTUAL runs scored and then claim that any residual between that metric and actual runs scored is due to how lucky the teams were.  The residual represents ALL factors that weren’t included in the metric; i.e. the failure of the metric to model reality exactly 100% correctly.


#6    david smyth      (see all posts) 2008/09/08 (Mon) @ 18:50

Right in the middle of the pack is RPW=10.

I like that.


#7    dave smyth      (see all posts) 2010/03/30 (Tue) @ 19:16

I came across the following win estimator in an academic article which I don’t think I’m supposed to link to. It claims to be the most accurate.

W% = Pythag - .03257sdrs + .0323sdra

where pythag is the usual equation with an exponent of 2, sdrs means the SD of RS, and sdra is the SD of RA.

Essentially, this adjusts pythag for the consistency of RS and RA.

I wonder if this approach could be combined with Pythegenpat instead of just using basic pythag.


#8    Zach      (see all posts) 2010/03/30 (Tue) @ 23:38

If you wanted to look at SD’s, wouldn’t the Correlated Gaussian method (click name) be the most accurate, since it’s the most accurate for both basketball and football?


#9          (see all posts) 2010/03/31 (Wed) @ 09:53

If a StD adjustment like the one David describes can work with Pyth x = 2, then I’m sure one could be devised that would work with a floating exponent.  The same equation would probably do ok, although who knows how it would behave at the extremes without testing.

Personally, I’m not big on StD adjustments, because if you do it, you have to know the team’s exact distribution of runs/runs allowed by game.  And once you have that, why not go all the way and base your estimated W% on the frequency of runs per game, rather than the average of runs/game with a correction?  Once you go down that road, you might as well use that data to its full potential, IMO.


Page 1 of 1 pages


Name (required)
E-Mail (optional; WILL be published)
Website (optional)

<< Back to main


Latest...

COMMENTS

Feb 11 18:07
Hero of the month: Brittney Baxter

Feb 11 17:59
MGL: Today on Clubhouse Confidential

Feb 11 17:58
Clutch analogy

Feb 11 16:48
Reader Mail of the Day: Why do we need X years of fielding data?  And what about outliers?

Feb 11 11:54
Who is Jeremy Lin?

Feb 11 10:29
Dwight Evans

Feb 11 02:12
Performance through the ages

Feb 10 23:01
For Your Soul

Feb 10 18:32
Moneyball at Villanova

Feb 10 17:00
Psst… wanna intern in Canada?