Thoughts from Diamond Mind

Welcome to the Diamond Mind weblog. For a while, we've been looking for the best way to publish small pieces of baseball commentary and research, items that may not warrant a full article (such as the ones we've been writing for ESPN.com since 1998) or items that would be outdated by the time our next email newsletter is due to be issued. A weblog seems perfectly suited to this purpose, and we hope you enjoy what you read here.

To provide feedback, email us at blog@diamond-mind.com. We won't be able to reply to those messages individually, but we'll read them all, and we may respond by posting a reply in the weblog itself.


Blog Archives

Weblog Home

This page is powered by Blogger.

Friday, August 01, 2003

Seeing Red
 
In the aftermath of the trade deadline, members of the media and fans expressed anger and disgust for the deals made by the Cincinnati Reds. This is typical in the wake of a perceived fire sale, but is it fair to imply that ownership destroyed the future of the team?

I think much of the anger stems from the false assessment that the pre-fire sale Reds weren't that bad. Entering today's games, they are on pace to finish 74-88 which is far from Tiger territory and only a few games worse than our pre-season projection, but are they even that good?

As Tom has written in his projection updates, Cinci's record is better than their run and TBW margins suggest. They have won 5 more games than expected of a team that has been outscored by 110 runs and 3 more games than expected of a team that has allowed 301 more total bases and walks than they have gained. Basically, they're more like a 100-loss team.

Despite losing Griffey for most of the season, the Reds' offense has been on target with our expectations (thanks to Jose Guillen's exceptional efforts as Junior's replacement), but they have allowed 94 more runs than we expected. They've allowed 34 more runs than the NL's second worst team, Colorado, who plays their home games in Denver's thin air. Clearly, there's a need for pitching.

There's not much pitching help on the way from a farm system ranked 24th by Baseball America before the season, so they had to look outside the organization. By acquiring Brandon Claussen, Aaron Harang, Phil Dumatrait, Joe Valentine, Charlie Manning, and Jeff Bruksch, they added six young arms to their system. Claussen and Harang may already be better than what they have in their rotation (granted, that's not saying much) and Dumatrait may be a year or two away from contributing.

What did they give up? Perhaps Jose Guillen has finally figured it out at age 27 in his 7th major league season or perhaps he's having his Brady Anderson anomaly season. The truth is that his trade value will never be higher, Dunn and Kearns are their corner outfielders, Griffey is still under contract, and it's time to see what Wily Mo Pena can do given his odd deal that forces him to stay with the major league team. Boone is a solid player but we're not talking about Scott Rolen. In fact, Boone's .808 OPS is only slightly higher than Wil Cordero's (Boone's career .785 OPS is only 20 points higher than Cordero's career OPS), and I doubt anyone in Montreal would shed a tear over losing Cordero (maybe they would in Puerto Rico). Gabe White is a 31-year-old mediocre reliever. Scott Williamson is still young and has a great arm so they gave up 75 very good innings per year for a couple young players and payroll flexibility.

More veterans like Sean Casey may be dealt before the season is over, but management seems to believe that this team has no chance to compete unless they rebuild their pitching staff, and I can't fault them for taking that realistic approach.

posted by Zack at 4:02 PM


Thursday, July 31, 2003

On complete games
 
As everyone knows, complete games are becoming more and more rare with each passing season. The other day, as I was thinking about this trend, I had the following thought...

Most of the time, it takes 27 outs to get a complete game. Sure, you can have a complete game loss on the road in which you pitch only eight innings, and some games are shortened by weather. But the most interesting complete games, I'm sure you'll agree, are complete-game victories.

Let's say it takes an average of five pitches to get an out these days. That means you need to make 135 pitches to make 27 outs. There have been a few outings of that length in the 2003 season, but only a few, and many of the them have been greeted by expressions of grave concerns about the possible damage done to the pitcher in question.

Very few pitchers are allowed to throw 135 pitches in a game any more. Most are routinely lifted soon after they cross the century mark, and those pitchers need to get an out for every four pitches if they want to finish what they start.

Getting an out for every four pitches isn't easy. These days, the average batter sees about 3.7 to 3.8 pitches per plate appearance. If you're around that average, you're going to throw 100 pitches even if you toss a perfect game. If you allow even a handful of baserunners, your pitches-to-outs ratio will deteriorate in a hurry unless you're dispatching a good number of batters on the first, second or third pitch.

It's not a big thing, obviously, but in the past few days I've found myself thinking about this ratio while watching a game on TV or looking over a real-time boxscore on the web. I realize it's not really any different than tracking pitches per inning, but somehow the idea of needing an out every 4 to 4.5 pitches made me realize just how hard it is to get a complete game in an era when pitch counts are low, walk and strikeout rates are high, and hitters are being told to work the count at every opportunity.



posted by Tom at 11:37 AM


In-play average, the aftermath, part 1
 
In the week and a half since we posted our study on the ability of pitchers to prevent hits on balls in play, we've received some very thoughtful email on the subject, and the Baseball Primer web site has a long discussion thread on the topic.

(I don't always have time to keep up with what's being written on Baseball Primer, but when I do, I usually learn something. As with any internet forum, the quality of the posts isn't uniformly high, but there are a number of people doing some very interesting work over there.)

For those of you who are interested, here's a summary of what I've read ...

1. A few Baseball Primer folks chastised me for failing to reference a follow-on article (called "DIPS Version 2.0") that Voros McCracken posted to that site in early 2002. I did make a point of looking for other articles of his, and when I found the Voros home page on www.baseballstuff.com, I thought that was a complete list of his work on this subject. Well, it wasn't, and I wish I had seen the Primer article before publishing mine.

In that follow-on article, McCracken made two points that are consistent with my findings. First, he acknowledged that there are small differences between pitchers in their ability to prevent hits on balls in play, and those differences "appear to be statistically significant if generally not very relevant." He also pointed out that knuckleball pitchers are particularly successful at preventing in-play hits.

As a result, I've made a couple of edits to my article to make it clear that McCracken had made these two observations long before I did my research. (He also had other things to say about fly-ball versus ground-ball pitchers, left-handers versus right-handers, height, and a few other topics, but the two comments I mentioned in the last paragraph are the ones most relevant to my work.)

By the way, I learned this morning that Keith Woolner of Baseball Prospectus published an article shortly after the first McCracken piece appeared. Keith wrote to tell me that his findings were consistent with mine, or maybe I should say that the other way around, since his article appeared two years earlier.

2. A few people claimed that the low correlation of IPAvg from year to year proves that in-play performance is irrelevant in the evaluation of pitchers and the projection of future performance.

These folks point out that McCracken got better results in projecting next-year performance if he used the team's IPAvg from the previous season than if he used the pitcher's own IPAvg.

I haven't done that sort of projection work myself, but I'm willing to accept it. There is a lot of noise in a pitcher's IPAvg, and if a method puts no weight on a pitcher's IPAvg, it's not unreasonable to expect it to produce better projections than a method that gives full weight to his prior-year IPAvg.

But what if we put some weight on a pitcher's IPAvg? What if we could find a pitcher's true level of in-play ability? That may not be easy to do, but it may produce better projections than other systems that are being used today.

In particular, a projection system that uses the team's IPAvg assumes that pitchers with lousy IPAvg results will improve to match the team's IPAvg. But what if the career-length breakdown proves that some of them simply aren't good enough? Wouldn't an approach that assumes all pitchers are equal on IPAvg overestimate their value? Maybe that wouldn't matter to folks who use projections like this for fantasy leagues, because these guys aren't likely to be drafted anyway, but wouldn't that be very important to a big-league front office?

Finally, if pitchers do have some control over in-play outcomes, it casts doubt on the use of team IPAvg as a pure measure of the impact of the park and the defense. Team IPAvg also measures the quality of the pitchers on that staff to some degree, so it has less value in projecting the future performance of individual pitchers on that team.

3. A couple of people attacked my career-length charts as meaningless because (a) after 2000 batters faced the differences are small and (b) there's a selection bias because the guys with short careers were probably just unlucky on balls in play and were out of the majors before they could bring their IPAvg numbers back to the average.

I'm sure there are some pitchers in the short-career group who lost an opportunity for a longer career based on bad in-play luck, but it's a huge (and unsubstantiated) leap to assume that most of them were just unlucky. Those pitchers were also worse than average on walks, strikeouts and homers, so it's likely that they just weren't good enough to get their fair share of easy outs on balls in play.

4. A couple of people have noted that homeruns are balls in play and shouldn't be set aside as they are in McCracken's methodology. I understand completely. After I had crunched all the numbers, I wished that I had looked at in-play average with and without homers included.

It made sense to leave them out because my plan was to test McCracken's idea against a larger dataset, so it was important to apply his method as it was originally laid out. And that method makes sense: McCracken's goal was to isolate events for which the pitcher has sole responsibility, and the defense has very little involvement in the vast majority of homeruns. On the other hand, we might be able to learn something else by adding them in, so both approaches have merit.

In particular, as I was writing the article, I found myself wondering about the interaction between strikeouts and homeruns. McCracken removed strikeouts before computing IPAvg, but didn't remove them before computing HR rates. Isn't it possible that Roger Clemens' HR rate looks good only because he strikes out so many hitters? Maybe his HR rate is merely average when computed as a percentage of balls in play rather than a percentage of batters faced?

It turns out that it's not average, but it is closer to the average. If we assume that the norm was about 25 homers per 1000 batters faced during Roger's career, his surplus of 1355 strikeouts may have saved him about 34 homers. He was 101 homers better than average, so the strikeouts account for about 1/3 of his success in this area. I looked at a few other pitchers and found that, in general, the strikeouts accounted for only a small fraction of their net homerun savings. Still, it would be interesting to look at homers both ways for a much larger group of hurlers.

5. Others have pointed out that when a pitcher makes a lousy pitch that is crushed for a homer, his IPAvg doesn't suffer. But if he makes a slightly better pitch and gives up a double off the wall, his IPAvg does suffer. This may be one reason why differences in IPAvg are relatively small.

Hits on balls in play are intermediate results. Make a great pitch and you get a strikeout. Make an okay pitch and you produce a ball in play. Make a terrible pitch and you give up a homer. IPAvg excludes the best and worst possible results, so it may make pitchers look more similar in that respect.

6. Some suggested that we look at the percentage of in-play hits that go for doubles and triples to see if there are more striking differences among pitchers than when you simply compute a batting average. I agree that this would be worth doing, though we'd have to be very sure to account properly for park effects.

7. Others suggested that we look at GDP rates to see how different pitchers are in that respect. I had the same thought when I looked at the Tommy John career profile, but it was too late to go back and run all the GDP numbers at the time.

8. I think it would be interesting to apply this method to hitters. I haven't done that, and I haven't seen any articles on that subject, but I've heard that others (McCracken among them, I believe) found large differences among hitters when measured by IPAvg. That wouldn't surprise me.

9. I mentioned this briefly in the Greg Maddux comment, but it's possible that the pitcher's own defensive ability has something to do with his IPAvg. I don't think that would change the outcome of the study, but it's worth investigating.

10. Mike Emeigh made the very interesting point on Baseball Primer that differences among pitchers on the same staff may be affected by which parts of the defense they test. As an extreme ground-ball pitcher, Derek Lowe's IPAvg has a lot more to do with infield defense than outfield defense. McCracken's method evaluates pitchers relative to the team's overall IPAvg, so all pitchers on the staff are assumed to get the same amount of help from their defense.

11. It's interesting how the same words can cause very different reactions in different people. I received two email messages from people who said my tone was condescending toward McCracken's work. The same day, I received messages from two others who commended me for going out of my way to praise McCracken's contribution. Meanwhile, a few posts on Baseball Primer described McCracken's original article as condescending, but I certainly didn't feel that way when I read it, and I don't think it's fair to describe it that way.


OK, that's enough for now. Some of these questions represent interesting research projects. We'll be looking at the projection system implications before we release our 2004 Projection Disk in the spring, but I'm not sure when we'll have time to work on the others. Some of you may do this before we can get to it, and if so, I look forward to seeing your results.

Finally, I want to say something about the more extreme reactions to the article. Some McCracken supporters dismissed this research entirely and seemed offended that anyone would dare challenge their hero. Some McCracken skeptics went out of their way to praise me for refuting all of this DIPS nonsense and delighted in the fact that we wouldn't have to talk about it any more.

Neither view is anywhere close to accurate.

To those who say that I refuted McCracken's work, I say "hogwash". It's true that I came away believing that pitchers do influence in-play outcomes, and it's true that I presented some contrary evidence regarding some specific comments in his first article. But my work fully supports several of McCracken's most important observations: that pitchers have much less influence than most of us believed, that there's a lot of randomness in single-season results, and projections of future performance need to take these two things into account.

To those who say I wasted my time because McCracken had already said, or at least hinted at, everything I wrote, I say "hogwash". I believe there are some original findings in the article, but even if you don't agree, it was worth making the effort to see how the ideas would hold up when applied more broadly.

I'm sure we haven't heard the last on this subject. That's one reason why the title of this blog entry says "part 1". In addition, I plan to write about IPAvg in the coming days and weeks, in at least the following ways:

- if any of you would like to see career charts for pitchers not covered in the article, let me know, and I'll see if I can work them up

- in our work on version 9 of the Diamond Mind Baseball game, we've added IPAvg as a stat that can be included in various batting and pitching reports, and we'll be using those reports to identify and write about notable IPAvg performances (projected versus actual, 2002 versus 2003, and whatever else seems interesting).

posted by Tom at 11:12 AM


Correction: Quadruple Crown of team batting
 
Sorry, folks, but my eyes failed me when I was scanning my list of team totals. The two 1947 teams weren't as close to sweeping all four categories as I suggested in my last post.

The 1947 Cardinals were nowhere near the leaders in doubles and homers, so they shouldn't have been on the list at all. I have no idea why I got so confused about them.

The 1947 Yankees led the league in triples and homers and were only four doubles short of the co-leaders in that category, but trailed the Red Sox by 27 singles.

I'll try to be more careful next time.

posted by Tom at 10:59 AM


Tuesday, July 29, 2003

Quadruple Crown of team batting
 
Todd Sullivan writes:

The Red Sox currently lead the AL in singles, doubles, triples and are a close second in HRs (with Texas putting their HR hitters on the block). Any idea if/when a team last led the league in all four categories of hits?
It's never happened, not really, anyway.

In the 1873 and 1874 National Association, the Boston entry swept all four categories, but that team played quite a few more games than anyone else, so it doesn't really count.

The 1902 Pirates came very close, finishing first in singles, doubles, and triples and tying for second in homers, only one back of the leaders.

The 1947 Yankees led all three categories of extra-base hits but finished 27 singles behind the leader.

The 1947 Cardinals were also a very balanced group, with only 7 singles and 6 doubles standing between them and a sweep of these four categories.

The 1966 Pirates led the NL in singles, doubles, and triples but were well back of the league-leading homer total posted by the Braves.

But Boston isn't quite as close as Todd thought they were. Perhaps he meant to say that they lead the league in hits, but they don't lead in singles. The team totals on ESPN.com show the Red Sox with 655 singles through Sunday's action, but Baltimore had 690, Seattle 680, Minnesota 668, and Toronto 661.

Still, that's a very impressive all-around effort by the Boston lineup, especially when you consider that they're also second in walks. And it's not out of the question that the Sox could catch the leaders in singles and do something that's never been done before.

posted by Tom at 10:07 AM


Monday, July 28, 2003

Projection watch, National League, week 17
 
Atlanta -- just when I thought the Braves offense was slowing down, they went out and scored 86 runs in their first 11 games after the break, and they've tacked on another ten in tonight's game ... Rafael Furcal was batting .341 as recently as May 28th, and he's below .280 now, but plenty of other guys are picking up the slack ... it's a good thing, too, because the once-dominant Atlanta mound corps has allowed 70 runs in those 11 games since the break ... overall, the Braves have scored 109 more runs than we projected and they've allowed 36 more, for a net gain of 73 runs ... but they're 13 wins ahead of forecast because they've also beaten their pythagorean record by 7 games.

Philadelphia -- to all intents and purposes, Philly has been the statistical equal of the Braves, but who cares if it doesn't translate into wins? ... the Phillies' run margin of +87 is second-best in the NL, as is its TBW margin of +222, but they're four games behind their pythagorean record ... if Atlanta and Philly were both in line with the pythagorean records, it would be a virtual dead heat for first place in the East.

Florida -- this is getting very interesting ... the offense is 61 runs ahead of forecast even though there are only two players (Mike Lowell and Alex Gonzalez) who are way ahead of their individual projections ... that's because the other starters are at or slightly ahead of where we thought they'd be, and nobody is having a bad year.

Montreal -- the Expos are trying to hold on, but when you've been outproduced to the tune of 131 TBW, it's a sign that the club hasn't been as strong as its record suggests ... to date, Montreal is 10 runs better than expected offensively and 19 runs better defensively ... the offense has been around that level most of the season, but the pitching was 53 runs better nine weeks ago, so they've given back 60% of that advantage.

New York -- the Mets have begun the second half by going 3-8, adding 23 runs to their deficit, and being outproduced by 57 TBW ... at -355, their TBW margin is 29th in the majors (the Tigers are at -366) and on pace for the 10th worst mark by any team in the past thirty years.

Houston -- a typical Jimy Williams team ... not especially impressive on offense, exceeding expectations defensively, and falling a few games short of its pythagorean record ... the pitchers are 46 runs better than forecast, and that should translate into four extra wins, but they're only one win ahead of pace.

St. Louis -- in terms of run margin and TBW differential, the Cards are right with the Astros, but doing it in a very different way ... pounding the ball (82 runs ahead of forecast) but giving back almost as many runs (59 runs worse than forecast defensively) ... treading water since the break, with a 5-5 record, a run margin of +1, and a TBW margin of -2.

Chicago -- last week's trade may have fixed the problem at the top of the lineup ... if Kenny Lofton has a good half-season left in him, and with Mark Grudzielanek having a very good year, they're much better off than when Grudz and Alex Gonzalez were batting 1-2 ... to date, this is our best projection of the season, with a win-loss record that's right on target, an offense that has scored 3 more runs than projected, and a defense that has allowed 7 more runs.

Pittsburgh -- not exactly a good team, but better than the Reds, and worthy of their fourth-place standing ... slightly better than expected on both sides of the ball, and that puts them two wins ahead of the pace they set in our preseason simulations.

Cincinnati -- in the first half, the Reds hung around the .500 mark despite some awful underlying stats, mainly because they were 7 games ahead of their pythagorean record ... since the break, their run margin and TBW margin has stabilized, but they're losing the close ones ... now only +4 in pythagorean terms ... have allowed 98 more runs than expected, making them the most disappointing NL team in that regard.

Milwaukee -- no surprises here ... one win behind forecast ... run margin is five runs worse than forecast ... they've been slightly better than the Reds statistically, so if that trend continues, there's a chance the Brewers could escape the basement, but this team is going nowhere, and fifth place is the best they can hope for.

San Francisco -- another torrid stretch from Barry Bonds has helped carry the Giants to a 10-1 record since the break ... still, it's not a dominant team by any means ... nine wins ahead of projection, but that's mostly because their actual record is six games better than their pythagorean record ... run margin of +79 is nice but nothing special for a division leader, so they won't necessarily be favored in the postseason.

Arizona -- made a nice run before the break but stumbled to a 4-7 record since ... the underlying stats are still headed in the right direction, though, as they've outproduced their opponents by 26 TBW in those 11 games ... I still like them for second place, but I don't think they're good enough to catch the Giants.

Los Angeles -- were outscored 3-2 by the Diamondbacks in their recent confrontation ... if that was one game, it would simply be a disappointing loss ... the fact that it was the total score of a three-game series basically tells the whole story of the LA season.

Colorado -- seemingly unable to break out of their pattern of dominating at home and being dominated on the road ... earlier in the year, I considered them a factor in the wildcard race because of a soft schedule, but they failed to make a big move when they had the chance ... now they have 35 games remaining against winning teams and only 19 against losing teams ... the only plus is that many of the winning teams have to play in Denver, while they get most of the losing teams on the road.

San Diego -- an impressive 5-5 since the break despite playing three good teams (SF, Ari, StL), but their run margin and TBW differential continue to deteriorate ... have outscored our forecast by 2 runs, but the pitchers have allowed 66 more than expected ... would have to go 32-24 the rest of the way to match our forecast, and that's not likely.

Top teams in run differential -- Atlanta +96, Philadelphia +87, San Francisco +79, Houston +75, St. Louis +62, Arizona +43.

Top teams in TBW differential -- Atlanta +257, Philadelphia +222, San Francisco +191, Arizona +140, Florida +130, Chicago +124 ... note the absence of St. Louis (+106) and Houston (+103) from the top six ... the Dodgers, picked by some to win the division, are at -16.

Best performance relative to projection -- Atlanta, which needs only a 18-40 record the rest of the way to match the 86 wins they posted in our preseason simulations.

posted by Tom at 11:25 PM


Projection Watch, American League, week 17
 
With the trade deadline only a few days away, let's take another look at how each AL team is faring relative to our preseason projections...

New York -- three games behind forecast and showing some signs of vulnerability ... since the All-Star break, have outscored their opponents by only three runs and have been out-produced by their opponents by 6 total bases and walks (TBW) ... getting Nick Johnson back should be a big help, but Alfonso Soriano has followed up his torrid April with three consecutive months in which his OPS has been below the league average.

Boston -- an offensive juggernaut, on pace for over 1000 runs and about 425 doubles, which would shatter the all-time record for two-baggers by a team ... still leading the wildcard race by two games, but not out of the woods by any means, mainly because they're still not getting enough quality starts from anyone other than Pedro ... run margin of +113 is second only to Seattle's ... net TBW of +370 leads the majors.

Toronto -- now only two games ahead of the pace they set in our preseason simulations ... have scored 75 more runs than we forecast and allowed 18 more, so they should be further ahead in wins, but they're three games behind their pythagorean record ... run margin of +53 is fifth-best in the AL and better than every AL Central team.

Baltimore -- the AL's most surprising offense, with 80 more runs scored than we expected based on our preseason simulations ... Melvin Mora and Luis Matos are a huge part of that offensive success, though Mora has lost 36 points off his batting average in three weeks and Matos has lost 24 points in five days.

Tampa Bay -- we projected the D-Rays to be the worst team in baseball, but they've exceeded our projected run margin by 64 runs so far, with almost equal gains on both sides of the ball ... even so, they're 28th in the majors in run margin and 27th in net TBW, so they have a long way to go.

Kansas City -- about ten days ago, I gave them a 55% chance to win the division, but their lead has shrunk from 7 to 4 games in that time ... the good news is that it's the White Sox giving chase, and Chicago has the toughest remaining schedule of the AL Central contenders ... if I was a Royals fan, I'd be worrying about the fact that KC's net TBW mark of -141 is better than only three other AL teams (TB, Det, Tex) ... still 12 wins ahead of our projected pace, and needing only to go 13-46 the rest of the way to match the 70-92 record they averaged in our fifty March simulations.

Chicago -- on a tear, obviously, having won ten of twelve since the break and adding 29 to their run margin and 64 to their net TBW figure during that time ... the pitching, which has allowed 60 fewer runs than we forecast, has been the league's biggest surprise ... the offense is still 75 runs behind our projection, but that figure was -92 at the break, so things are moving in the right direction.

Minnesota -- a statistical puzzle ... since the break, the Twins have seen their opponents generate 32 more TBW but Minnesota has still managed to outscore those opponents by four runs over that span ... overall, they're 93 runs worse than we projected, with about two-thirds of that deficit belonging to the pitching and defense ... anyone out there predict that Minnesota would have given up 67 more runs than the White Sox at this stage?

Cleveland -- overall, the Indians are only a little worse than we forecast, with an offense that has scored 64 fewer runs and a pitching staff that has allowed 41 fewer ... the offensive shortfall can be blamed on the injury/trade of Karim Garcia, the injury to Ellis Burks, and a complete lack of production from second base and catcher ... they'll match our projection of 73 wins if they go 29-28 the rest of the way.

Detroit -- I keep hoping they'll improve, but it's hard to find any signs of that ... since the break, they're 3-8 with a run differential of -31 and a TBW deficit of 64 bases ... overall, the Tigers are 97 runs behind our offensive forecast and 73 runs ahead of our pitching forecast, so scoring is down on both sides of the ball.

Seattle -- own the best run margin in the league (+122) and the circuit's third-best TBW differential (+266), so this continues to be a very good team that won't be easy for the A's to catch, even though the lead is down to three games ... if only they could figure out what to do about third base.

Oakland -- since the break, Seattle is +30 TBW with a 5-6 record while Oakland is +63 TBW with a 6-5 record, so both teams have been more impressive statistically than their win-loss records suggest ... the problem for the A's is offense, which is tenth in scoring but was projected to be fourth ... overall, though, Oakland is only one game behind forecast, so the difference in this race is that Seattle has been better than expected.

Anaheim -- we didn't expect them to be able to match last year's success, but we're surprised they're still under .500 ... the offense has scored one less run than we projected, while the team has allowed 19 more ... that's not much of a difference, but when you combine that with a record that is 5 games worse than their pythagorean mark, you get a team that is 7 games back of their pace from our preseason simulations.

Texas -- has taken the art of allowing runs to new heights ... it's not easy for a team that was projected to have the league's third-worst pitching to allow 104 more runs than forecast, but they've managed to do it anyway ... only Boston, which has allowed 105 more runs than forecast, has been a bigger disappointment.

Top teams in run differential -- Seattle +122, Boston +113, New York +95, Oakland +75, Toronto +53, Anaheim +41.

Top teams in TBW differential -- Boston +370, New York +330, Seattle +266, Oakland +207, Toronto +76, Chicago +71.

Strangest performance relative to projection -- KC is 12 games ahead of pace, but they'd be 48-55 and only 3 games ahead of pace if their win-loss record was consistent with their net TBW of -141.

posted by Tom at 3:34 PM