BASEBALL NOTEBOOK BLOG

Sunday, April 29, 2007

Rookies and the YTD Drag

This is the final Sunday before we debut a new weekly schedule report, the first of which will run in this space a week from today. I thought I'd take advantage of the open slot to talk a bit about rookies who struggle in April and the threat an early slump has on their playing time.

Just before I get to today's main topic, I want to clarify or remind readers about our minor league translations, available to certain subscribers in our members only section. A reader wrote to ask about the translation for Yankees' pitcher Chase Wright, pointing out that the translated ERA showed 0.00 but that the reader had personally watched (and as a Red Sox fan enjoyed) Wright giving up four home runs in the majors recently.

I wrote the reader back directly to clarify several items which other readers may also need to keep in mind: (a) the minor league translation is a translation of only minor league statistics and does not include nor incorporate any major league performance, (b) the minor league translation is not a projection of ability. It's simply a conversion of a player's minor league stats-to-date into a neutral big league context. A pitcher could easily be a bad pitcher but have a good translated ERA - of course, that good translated ERA won't hold up in the long run but it doesn't lessen his minor league performance to date... and (c) the minor league stats that are considered are through play completed the Sunday prior to the Friday morning publication of the translations.

I suspect for readers who have subscribed to the translations for a long time, none of this is news but for those who are new to the feature or were uncertain, I wanted to offer those additional clarifications. I made a few extra comments about the translations in the debut of our new Thursday translated leaders report, which began running this past week.

Now, in the main issue of the day, I always remind readers throughout the off-season that the most solid plans of a team can quickly be abandoned if a rookie goes out and goes 0 for April. In fact, during spring training, I happened to use Kevin Kouzmanoff as an example of a player with a good projection but the highest uncertainty ratings I assign out. As fate would have it, Kouzmanoff has proven to be just one of those types of players. While the uncertainty of a rookie forecast is somewhat rooted in the uncertainty of ability, it's more often tied to the uncertainty of whether a rookie will play well enough immediately to actually hang on to the job he won in spring training.

Many readers have noticed that I've significantly downgraded Kouzmanoff's forecast the past two weeks, more a week ago than in this weekend's edition of the projections but in both cases in a downward spiral. It's not that I've downgraded his ability much, though I had to at least somewhat downgrade him given the severity of the terrible start. In fact, the weight of evidence supporting the theory of his ability still isn't outweighed by even this disastrous April he's suffered through.

Still, we can't rule out that he could end up as a Kirk Saarloos type player, who was a pitcher who made it as high as #12 on one of my annual prospect lists and who has never approached major league hitters as he did minor league hitters, even though he's managed to stick around. That is, there are players who look different in the majors when they get their shot, who actually approach the game differently than they did in their minor league successful seasons. I don't know if it's nerves or something else but it's often difficult to reconcile how such players can look so comfortable in, say, spring training against veteran major leaguers but then go out in front of the big crowds and collapse.

In any case, it's not so much that I want to talk about rookies and disappointment. There are so many rookies off to terrible starts this year, some of whom were considered "can't miss" by many of the prognosticators.

But in Kouzmanoff's case, if I can use him as the best example of a phenomenon (even more than Alex Gordon), there is now an effect on his performance that I have in past years referred to as the "year-to-date drag" if you will. This year-to-date drag is the effect that if you slump early, it makes your season look worse than if you slump late, even if in total you do exactly the same thing. I used a graphic example of this in the archived essay On Fantasy Trading in which I showed in May of 2005 that the perception of Andruw Jones' season at that time was skewed by his slump coming in April rather than in May. In other words, if you reversed the order of a season, Jones would have seemed to be having a better year even though in sum he would have produced exactly the same totals.

Particularly when it comes to rookies, here's the problem of what the drag does - It costs them their job because even if they're good enough to play, their season feels intolerable to management no matter how hot they eventually get. Such players usually find themselves back in the minors by May and I suspect that Kouzmanoff, unfortunately, is now close to that. I hope I'm wrong because I still believe he's a better player than we've seen but I have to set aside hope and go with the evidence.

To illustrate this point, I want to again use simulation modeling, much as I did the other day in this space in reference to David Wright. The simulation example seemed to generate much positive feedback because readers said it graphically illustrated something that they were already wondering about. I'll use Kouzmanoff in today's example since he's the rookie who's arguably been getting the most opportunity and been falling the most short of anyone's expectations.

Through play completed on Saturday, Kouzmanoff is now hitting just .127 in 63 at bats on the season. More specifically, he has 8 hits in those 63 at bats. Before we talk about the drag, let's ask ourselves this question? If our Opening Day theory was correct that he is actually a .286 hitter, what are the chances that he would have only 8 hits after 63 at bats?

Sadly, the chances are extremely slim. In 10,000 simulations of a .286 hitter getting 63 at bats, just 18 of them or 1 in about 600 simulated seasons resulted in a hitter hitting only .127 or worse over that stretch. Thus, this explains at least the partial downgrade of Kouzmanoff in recent days and I've now reduced him to a .268 hitter and this number continues to drop. In other words, the poor performance is outside of the margin of error enough that we had to downgrade him. There are cases where players perform outside of the margin because of bad luck (a margin after all is only right a certain percentage of the time) and more often, because they're hiding or playing through an injury. We do know that Kouzmanoff was nursing a minor elbow injury in mid-April but it didn't seem enough to explain this extended slump.

Now here comes the worse news. Let's say that he's really a .300 hitter and just suffered through a miserable stretch of bad luck or something else. I'm only floating this because now expecting him to be a .300 hitter as his real hidden ability would seem to be on the highest end of anyone's updated expectations. Let's use a simulation but this time, let's mix in the year-to-date stats. You see, those year-to-date stats can't be erased and so even if Kouzmanoff happens to go on a tear, he may not be able to hit enough to hang on to his job for much longer.

In fact, no hitter in all of baseball last year managed to finish with more than 100 at bats and an average of under .180. It doesn't mean that no player had an average of below .180 after 100 at bats but it does mean that the longer you slump, the more likely you are to lose your job.

So, in framing this simulation, I'm going to speculate that if Kouzmanoff is hitting below .180 as late as May 5th or 10th or so, he will lose at least his starting spot at third base if not his roster spot. Now, if we pretend he's a .300 hitter to give him the most benefit of the doubt and we mix in this terrible start so far, here's the breakdown of 10,000 simulated seasons where we give him 37 more at bats for an even 100 total on the season:

The hits column refers to how many hits he gets in the simulation in 37 more at bats. The "NEW AVG" column is what his new batting average would be at the end of the 100 at bats, including the terrible start he's had so far. So, using this simulation, even if we let Kouzmanoff be treated as a .300 hitter, almost half of the simulations result in him still having an average below .180 at the end of that stretch.

By the way, a 21 for 37 stretch like that which happened twice in our 10,000 simulations are possible. Nick Markakis last year was hitting in the low .200s into early June but managed to raise his average up in one incredible stretch in June and July that saw him turn around his season and end up with a .291 average. The Orioles stuck with him and he delivered but comebacks like that are rare, not only because most players aren't capable of them but because most players who slump as badly as Markakis did don't get the chance to turn it around.

So now let's put in our latest theory that Kouzmanoff's actually a .268 hitter (a downgrade of almost 20 points from the Opening Day set). Here then is how his first 100 at bats would play out then, again including the year-to-date drag:

So, even if our latest theory of his ability is correct, almost 60% of the simulations result in him still having an average below .180 at the end of 100 at bats. This is why I often will drop a player's playing time forecast even if I haven't entirely downgraded the projection of his ability. We must consider: If Kouzmanoff really is hitting .180 or worse after another 35 or 40 at bats, is it reasonable to imagine the Padres sticking with him much longer? I suspect not and that's why playing time reductions often happen before the most severe of ability downgrades.

Ironically, the year-to-date effect can work in a rookie's favor. A rookie who goes out and hits .300 in April can suffer through a miserable May and keep his job. This is because that great April performance boosts the appearance of his season. In baseball, ironically, it's the opposite of "what have you done for me lately?" While players are all noticed when they're on a hot streak, the earlier any performance occurs, the more it confuses our perception of a player's season... and more importantly, the more it influences managerial decisions about whether to continue giving that player opportunities.

Saturday, April 28, 2007

Weekly Depth Charts

This is to advise RSS/blog readers that our latest weekly depth charts have been published and are available at the BaseballNotebook.com website. Also, our new-style "Scheduled Advantage" report as described last Sunday at the site will make its debut a week from tomorrow, on Sunday May 6th.

Friday, April 27, 2007

Good Luck, Bad Luck

This is to notify RSS/blog readers that our weekly "Good Luck, Bad Luck" report has now been published at the BaseballNotebook.com website. This report is not available in the blog format but can be accessed from our home page.

Thursday, April 26, 2007

Translated Minor League Leaders

Most readers have likely noticed by now that Thursday is often a day I am away from the blog, with Monday being the other day of the week I am almost always offline. As we've added so many new reports this year, we have two remaining to be unveiled with one in this space today and the other to be the new style weekly schedule report we talked about last Sunday, which is to debut either this upcoming Sunday or a week from Sunday.

Many of our readers subscribe to what's called our "minor league translation" reports, the first of which is to be published at the site within the next 24 hours and then every Friday morning until the end of the minor league season. Those readers get detailed reports that attempt to "translate" the minor league performances of every player from Single-A on up (in full season leagues) into a neutral major league environment.

The translation methods have been built and adjusted over many years and account for the minor league park effects, the varying quality of competition, the level the league is at (i.e. it is easier to hit a home run at Single-A than it is at Triple-A) and adjusts all these numbers into a single translated line that attempts to represent the following: If this player had played in a neutral big league environment this year with roughly the same amount of playing time as he's had in the minors, this is how his performance would have looked. I often have to remind readers that the translation is not a projection of ability. A player can have a translated average of .500 in the same way that a minor league player can be called up and hit .500 for a couple of weeks and then revert to reality. It simply represents the player's minor league performance to date in a big league setting.

Even with the caveats out of the way, the translations have served us extremely well over the years and are the reason why we often don't project the vast majority of rookies to achieve instant success in the majors. As we look back on old translations published at this site - we started publishing these in 2002 - among people who have topped our translation boards, Dontrelle Willis was our 2002 translated minor league ERA leader, Ryan Howard was our 2003 translated home run leader (with Prince Fielder just behind him), Jeff Francis was the translated 2004 ERA leader, Chuck James was the translated 2005 ERA champion and so on. In fact, if we go back to that earliest of translation lists at the end of 2002, just looking back at that leaderboard from the minors, we can also find names like Adam Wainwright, Rich Harden, Cliff Lee, Danny Haren, Brad Hawpe, Scott Hairston, Victor Martinez, Chad Tracy, Jose Lopez, Rocco Baldelli, Adam LaRoche and Orlando Hudson, among others.

So, with elevated members at our site about to get full access to the complete translations and a much more extensive leaderboard, I've decided to fill my often-empty Thursday slot with a short summary of translated leaders from the minors. Unlike those that members get, which is a top 20 and has many more categories, this will usually be a top ten and will only focus on a few of the key categories. I expect we'll run this report frequently on Thursdays up until the conclusion of the minor league regular season.

Again, a translation is not a raw statistic nor is it a projection of actual ability. It is an adjusted number that takes the player's minor league statistics to date and modifies them based on as many factors and information as we can consider. It attempts to place them in a neutral big league context, meaning the player's major league team and environment has no bearing on the translation as we're trying to put everyone into a typical, neutral major league environment.

We hope readers benefit from this information. Because of the time it takes for us to translate several thousand minor league performances, as always, statistics each week are through the completion of play on the previous Sunday:

TRANSLATED BATTING AVERAGE LEADERS - MINIMUM 36 PLATE APPEARANCES.

Appert, Luke (OAK) .419 (43 AB)
D'Antona, Jamie (ARI) .382 (55 AB)
Ellsbury, Jacoby (BOS) .378 (45 AB)
Pie, Felix (CHC) .371 (35 AB)
Tripp, Brandon (BAL) .367 (60 AB)
Doumit, Ryan (PIT) .362 (47 AB)
Holt, John (ATL) .353 (34 AB)
Piepkorn, Jeremiah (CIN) .352 (54 AB)
Choy Foo, Rodney (CLE) .349 (43 AB)
Valencia, Daniel (MIN) .349 (43 AB)

TRANSLATED HOME RUNS

Brinkley, Dante (FLO) 5
Braun, Ryan (MIL) 4
Buckman, Brandon (STL) 4
Collaro, Tom (CHW) 4
Cust, Jack (SD) 4
Duncan, Shelley (NYY) 4
Lindsey, John (LAD) 4
May, Lucas (LAD) 4
Maybin, Cameron (DET) 4
Owings, Jon (ATL) 4
Pettway, Brian (TOR) 4
Ryan, Dusty (DET) 4
Valencia, Daniel (MIN) 4

TRANSLATED RUNS BATTED IN

Hoffpauir, Micah (CHC) 16
Diaz, Victor (TEX) 15
Butler, Billy (KC) 14
Collaro, Tom (CHW) 14
Bell, Bubba (BOS) 13
Esquivel, Matt (ATL) 13
May, Lucas (LAD) 13
Ankiel, Rick (STL) 12
Doumit, Ryan (PIT) 12
Larish, Jeffrey (DET) 12
Pence, Hunter (HOU) 12
Rozema, Mike (ATL) 12

TRANSLATED STOLEN BASES

Furmaniak, J.J. (OAK) 6
Gomez, Carlos (NYM) 6
Morgan, Nyjer (PIT) 6
Suero, Ovandy (DET) 6
Anderson, Josh (HOU) 5
Bernadina, Rogearvin (WAS) 5
Bocock, Brian (SF) 5
Coon, Bradley (LAA) 5
Davis, Quentin (ATL) 5
Donovan, Todd (TEX) 5
Graham, Tyler (SF) 5
Haynes, Nathan (LAA) 5
Owens, Jerry (CHW) 5
Requena, Alex (SF) 5

TRANSLATED EARNED RUN AVERAGE LEADERS - MINIMUM 12 INNINGS.

Katz, Ethan (COL) 0.00 (12 IP)
Stevens, Jeffrey (CLE) 0.00 (12 IP)
Wilding, Taylor (SF) 0.00 (12 IP)
Wright, Chase (NYY) 0.00 (13 IP)
Morales, Angelo (KC) 0.75 (12 IP)
Purcey, David (TOR) 0.75 (12 IP)
Lincecum, Timothy (SF) 1.00 (18 IP)
Bergesen, Bradley (BAL) 1.06 (17 IP)
Dumatrait, Phillip (CIN) 1.06 (17 IP)
Colon, Bartolo (LAA) 1.13 (16 IP)

TRANSLATED WHIP LEADERS - MINIMUM 12 INNINGS.

Wright, Chase (NYY) 0.462 (13 IP)
Stevens, Jeffrey (CLE) 0.583 (12 IP)
Wilding, Taylor (SF) 0.583 (12 IP)
Bergesen, Bradley (BAL) 0.647 (17 IP)
Laffey, Aaron (CLE) 0.647 (17 IP)
Katz, Ethan (COL) 0.667 (12 IP)
Colon, Bartolo (LAA) 0.750 (16 IP)
Morales, Angelo (KC) 0.750 (12 IP)
Purcey, David (TOR) 0.750 (12 IP)
Braden, Dallas (OAK) 0.765 (17 IP)

TRANSLATED STRIKEOUTS

Hochevar, Luke (KC) 22
Gallardo, Yovani (MIL) 21
Gonzalez, Giovany (CHW) 21
Lincecum, Timothy (SF) 21
Marmol, Carlos (CHC) 20
Vasquez, Matt (DET) 20
Hanson, Thomas (ATL) 19
Cody, Christopher (DET) 18
Norton, Timothy (NYY) 18
Richardson, Dustin (BOS) 17

Wednesday, April 25, 2007

Pinto, Wright's Power, Ryan, Prior

It's not often that I'll mention taking a gamble on a name neither projected to do well nor someone in a prominent role but I want to at least draw attention to a pitcher that's getting my attention as I revisit and review the forecasts for the next update. Renyel Pinto of the Marlins is a guy I didn't project to pitch well because of control problems. In fact, in the skill ratings I assign out for most pitchers, I had given his stuff a B- and his ability to keep the ball down a B, which would definitely be good enough to succeed if it weren't for the control rating of F, which is obviously the lowest I assign out.

In 13 innings this year, he has indeed been wild, walking 8, but he's also struck out 14, hasn't allowed a home run and has an ERA of just 1.38 on the season. The lefty didn't have a particularly dominant year in the minors in 2006 (8-2, 3.40 ERA as a starter in 18 games) but what I see developing here is that it's possible the Marlins may turn to the hot hand in the bullpen at some point. Henry Owens actually has pitched well this year but he's also been far less dominant than the Marlins had expected and the other day, Atlanta knocked him around a little bit.

I must emphasize that I'm not upgrading Pinto's projection right now but I want to alert readers that he's at least beginning to move into the territory of being a saves sleeper here (readers know I'm not fond of the term sleeper as it's overused but I think I'm using it correctly here), just based on what he's done so far. Whether I believe his real ability is to be good, if the team believes that it represents something, that could move him into a more prominent role. Thus, Pinto becomes that rarest of pitcher who still gets no projected value on our ranking sheets but whom I just picked up for my reserve list in a couple of leagues. I'll probably hang on to him for a couple of weeks to see if his ERA returns to reality and/or if this is just me imagining that the Marlins are not as confident in Owens as they say they are.

At least a few readers have asked me about David Wright's power, or lack thereof so far. Let me put it simply - Barring injury, the overwhelming majority of players do not suddenly lose their power in their early twenties. Sure, a player can overachieve and hit 35 home runs when he's actually a 20 home run hitter in terms of real ability. But a player cannot hit 25 and 26 home runs when he's twenty-two and twenty-three respectively, as Wright did, and then suddenly lose all power and become, say, Jason Tyner. So, Wright still does have power and we just haven't seen it yet.

Let me remind readers what a 26 home run hitter really is. That is a player who, in 154 games (the number Wright played last year), should average a home run about every six games. Wright has played a grand total of 19 games so far and so even by last year's pace, we'd only expect him to have 3 home runs by now. Don't allow your views of home run pace to be incorrectly influenced by the league leaders at this stage, who always put up ridiculous numbers over short stretches. Understandably, everyone's looking at A-Rod's current totals and wondering why their star hitter has "only" 4 home runs right now. A hitter who has 4 home runs after 19 games is on a pace to hit around 35 in a 162 game season.

I'd say my concern with Wright isn't so much the power but the contact rate. Some media types who have a better eye for these things than I do have been saying he looks worse than usual, chasing pitches that he didn't used to. Wright's contact rate last year was 80.6% and his contact rate this year, so far, is 72.6%. While that's concerning, that puts him six strikeouts off his pace of last year in 73 at bats. That's entirely possible that a player can experience a six strikeout swing in a 73 at bat pace but it's the contact rate that has me at least slightly concerned here.

In any case, I suspect Wright still has the same power as always. His slow start may cost him a few home runs in the final tally but I haven't seen enough to significantly downgrade him just yet. On a related note, let's use one more tool here. I always like to use high speed simulations to get a visual image of how likely a particular distribution may be. If I know the standard deviation, I can actually calculate a distribution using statistics but an actual simulation can offer an immediate and visual distribution to give us at least a rough idea about possibilities and for some readers, I know they have told me it makes it feel less theoretical if an actual simulation is performed against a percentage chance of an event occuring.

Let's say Wright's real ability is to homer once every 22.38 at bats. If we were, at high speeds, to simulate blocks of 73 at bats with that ability, here's how 10,000 simulations I just did came out, using the theory that 2006 represented his real home run ability:

As you can see, of the 10,000 simulations we ran, 3.7% of the time, a player with the theoretical home run skill of the 2006 David Wright would still have no home runs by this point of the season. Now, 3.7% may seem like a small number but actually, it isn't for this reason - Wright has not been randomly chosen as the subject of today's column. That is, we've picked him because he's in a home run slump. Of course, if Wright is hiding an injury, then this will explain everything and I've seen that happen before, where a player is less effective than usual and then later admits that they were nursing a problem but didn't want to make a big deal out of it.

So, while I am admittedly at least slightly concerned about his power, it's not unrealistic to consider that he may just be in one of those slumps that affect every player. I still remember Andruw Jones slumping so terribly to start the 2005 season, suffering through a miserable 0 for 27 streak in April and ending up with 51 home runs by season's end. You can begin to make new conclusions about players at this stage but you have to be very careful about how much weight you assign to April performance.

By the way, I had mentioned the other day that Jason Frasor's value would be directly tied to how quickly B.J. Ryan can return. One transaction that sort of quietly floated across the wire was that the Blue Jays moved Ryan to the 60-day disabled list on Monday. That may not seem like a big deal but to fantasy leaguers, it is because it guarantees that Ryan can't return from the DL until at least sometime in June. The original estimate for his return that I had seen had been "four to six weeks" but this is clearly longer than that.

It doesn't give Jason Frasor absolute job security until then - He still has to pitch well enough to hang on to the job. I would say that Frasor's the most likely to lead the team in saves until Ryan's return, though, and so his value again rises just on this seemingly harmless Toronto transaction of moving Ryan to the longer DL.

Finally, all of the readers who have been writing me asking about what to do with Mark Prior... Though I've been projecting bad results for him in 2007 anyway (meaning I'm surprised how many readers have continued to hold out hope that I'm wrong), you can now officially let him go. Just as I write today's entry, we get word that Prior has indeed undergone surgery on his shoulder that will officially end his 2007 season before it began.

I know there are many who rate Prior not against his good years in the majors but against their own expectations of how great a pitcher he would be. He may very well end up rebounding into the pitcher he once was expected to be (and was in the majors over a few years) but he's reached the point of being a low percentage gamble. If you have him signed for 2008 and have to pay him a salary for next season no matter what you do, by all means hang on to him. But if you've been keeping him on your reserve list only for 2007, well it's time to eat the salary and free up that spot for a pitcher you can shuttle in and out of your active roster.

Tuesday, April 24, 2007

Too Many Saves, Jeff Weaver, Igawa, Wainwright

A reader wrote to share that he had managed to draft Todd Jones, Joe Borowski and Al Reyes and also added Jason Frasor recently. Because of the way these pitchers have started, the reader has 14 saves already (at the time he sent his email) and he says the next-closest team has only 4 saves. He's wondering if he can hope to remain in first place if he trades one or two of these pitchers and if so, he wants to know which pitcher he should consider trading.

The problem with a 14-4 save lead is that on the surface it looks insurmountable - after all, you're more than tripling your next closest competitor. However, if you look back at, say, last July, you could easily find a stretch where one team picked up 14 saves and another strong team picked up only 4. Thinking of it in terms of a whole season, all you've got so far is a 10 save lead. That's good but it's not a lead so big that you've already clinched the saves category.

However, I have always advocated that if you're going to finish first in a category, you want to barely finish first in that category. As of today, every save above your 5th save so far has been wasted. It doesn't mean it always will be as other teams catch up but for now, your 6th through 14th saves aren't helping you in the scoring.

The approach I usually take to these situations is actually to build up a huge lead until close to the trade deadline. Then, if I really feel I've clinched the saves category (and there have been times when I knew I had it locked up in June), I re-run my fantasy ranking sheets and simply remove saves as a category to see what pitchers would be worth to me. This way, I don't completely disregard the value the strongest relief pitchers have to me in terms of their ERA and WHIP contributions and occasionally even strikeouts. I can then move one or more of the relievers for someone who can help me in another category in which I've been less competitive.

If you really feel comfortable with your lead because the other rosters really can't compete with you (i.e. let's say no other team has even two closers, which can happen in AL or NL only leagues), then by all means you may want to dangle one of these guys. I'd suggest there are two approaches here: (a) trade the guy who has the lowest job security for the whole season. Of the four you mentioned, that would be Jason Frasor if B.J. Ryan's injury turns out to be as reported and he can return at some point in the next couple of months. If Ryan doesn't return, then Reyes probably has the lowest job security among your group as Frasor's a pretty solid percentage play to keep closing until Ryan returns... or (b) trade the guy who has started above his ability - which would easily be Todd Jones. Jones has a 1.93 ERA and 7 saves already and 7 saves in 19 games puts him on a pace for 60 saves, a number that isn't going to happen barring a record-breaking season. Pitchers who start like Jones can be irresistible to teams in desperate need of saves.

You're smart to be thinking about trading from your strengths and if you target the right team - say a team desperately in need of any saves at all - you should be able to strength another area. Look for a category where even a bit of improvement on your part could make big differences in points and don't add to an area you're already among the leaders in. That way, you'll be maximizing your chances to win.

There are three pitchers readers have been wondering about in recent days and at least a couple who have been mentioned in the context of our new "Good Luck, Bad Luck" series that runs on Fridays. They are Jeff Weaver, Kei Igawa and Adam Wainwright.

One reader specifically asked of Weaver whether there was any reason to hope he's going to turn things around soon or if he really is at the end of the line.

I didn't project much of an exciting season for Weaver, having put him down for 13 wins and a 4.95 ERA on Opening Day (with the ERA at least helped somewhat by his new home park being favorable for pitchers). I was projecting 201 hits allowed and 43 walks in 185 innings. So far, Weaver has been absolutely hammered, so much so that he got pulled after only 3 innings in his latest start even though he wasn't injured. In 11 innings, he's allowed 24 hits, 3 walks and 17 earned runs for a terrible 13.91 ERA.

If it's possible to extract any good news out of this mess of a season so far, Weaver is short of qualifying but otherwise, would now take over the leaderboard among the unluckiest pitchers in terms of non home run hits allowed per ball in play. That is, he's now allowed about 46% of balls in play (other than home runs) to fall for a hit, which is an unsustainably high number that would right itself in the long run if he keeps getting a chance to pitch. Unfortunately for him, he may not keep getting opportunities. His contract is worth more than $8 million for this season but it wouldn't surprise me to see him pitching for a different team within the next few months if the Mariners can find some way, within the parameters of his contract, to move him.

There are two pitchers I'm incredibly surprised to see readers telling me they drafted and are starting to get worried about them. One is Kei Igawa of the Yankees, who is off to a horrible start. The reason I'm surprised readers own him is that on virtually all fantasy league formats, he was projected to have little no value on our ranking sheets, largely because the Opening Day projection was for 11 wins but going with a 5.40 projected ERA and a forecasted WHIP approaching 1.60. Igawa's been even worse than that with an ERA over 7.00. Obviously, he's better than a 7.00 ERA pitcher but his WHIP so far has been almost exactly what we projected. Admittedly, I don't know enough about him to speculate about whether he's going to turn it around and the forecast was almost entirely statistically based using our Japanese translation methods.

The other pitcher commonly mentioned in emails lately is Adam Wainwright. Readers keep writing to tell me they're beginning to get frustrated with him and want to know what's wrong with him. Like Igawa, I'm surprised there are readers who ask me about him because I can't help. Our Opening Day forecast for Wainwright was for only 9 wins and a projected 5.31 ERA and WHIP over 1.50. It's not that I think he's not suited for starting - this goes with our projection of his ability and stuff.

Unlike Igawa, at least we have some evidence we can use for optimism if we happen to have him on our roster. We can look to spring training or we can use 2007 to at least give us some hope that he's better than he's shown this season. Wainwright seemed to start well but actually wasn't pitching as well as his ERA appeared and now the long run is starting to balance that out. In 25 innings, he's allowed 32 hits and 13 walks for an ERA of 5.04.

To summarize, I believe Wainwright has better control than he's shown but his ERA should also be higher based on how he's pitched so far. I'm now begining to contemplate at least one error here on my part - If Wainwright pitches as poorly as I projected him, it's possible that the Cardinals may decide that it's because he's not suited for starting and then move him back to the bullpen. For now, I'd say his job security is pretty good and as I say, even though his ERA is in the ballpark of what we projected, he's still a better pitcher than he's shown this season in terms of walks. He's already walked more than half the number of batters he walked all of last season and he's pitched less than a third of the number of innings.

Sunday, April 22, 2007

Upcoming New Style Report on the Week Ahead

Before I write briefly about another new weekly report that we have in final development, I just have to pose this rhetorical question about how easy it is to get caught up in the short run and the frustration of a few bad moments - Where are all those people who were at Yankee Stadium booing Alex Rodriguez mercilessly the day before he started this tremendous stretch? We haven't heard from you lately...

In any case, I mentioned last week that we're going to soon be introducing another new report to run most Sundays up until the end of our publishing season in early September. Originally I didn't expect to have this until at least 2008 but things came together in the past couple of weeks, fortunately, for us to produce this in 2007, albeit a bit late into the start of the season. I'm sure readers would rather we introduce it if/when we have it ready rather than hold it back for future years.

In fact, I suggested about a week ago that there was a chance it would be ready for this Sunday but unfortunately, I'm just not satisfied that the data and report coding has been tested and verified enough to feel confident publishing our first report. I do expect that within the next two Sundays, this report will be up and running and will join our new weekly depth charts and weekly "good luck, bad luck" style reports as part of a regular series.

I can, however, give a preview of the sort of information the report is likely to contain by highlighting two teams. I suppose it's best to just show you a snapshot of one team (reminding the reader that this information is produced from the rough and still incomplete report program):


This is the Atlanta schedule for the upcoming week but with a rating for each key fantasy category based on the combination of factors we talked about considering in our archived piece entitled The Scheduled Advantage. This is a report concept that has always been on my own wish list and so I'm as eager to get it as any reader might be.

What the report does is break down the schedule from Monday to Sunday for the upcoming week. It attempts to neutralize the quality of the opposition so that the home park doesn't affect the ratings for the opponent until the park effect is applied at the end of the process. Year-to-date performance by each team carries considerable weight in terms of rating the quality of opposition, perhaps even a bit much, but it will even out as we get lots of data in the books. Early in the season, some of the percentages will be a bit extreme.

We attempt to reverse neutralize the effects of the home park so that an apparently good-pitching team like San Diego might come out as being more ordinary pitching-wise if they're playing a road game. It then applies the effect of the park in which the game will be actually played, considers other factors talked about in the Scheduled Advantage strategy and so on. Ratings are multiplied together (rather than averaged) to produce a daily rating of how much each category should be affected by the schedule for that day. Finally, an average of the games for the week are presented in each category.

Admittedly, as new as this report is, there are some limitations to it. First, because this will be created with a program that has the original schedule in it, this report will in most cases use that originally published schedule. That means that games that are cancelled and made at up at a later date may not show up, though we're already looking into ways to remedy this. Also, as I said last week, we've gotten away from attempting to project which days a pitcher will actually start on. We found that as early as our Sunday pieces needed to go to press (offering the free essays is not a 7-day, 24 hour operation unfortunately), that pitchers far too often started on different days than we expected.

However, the value of this report format means that if you know your pitcher is starting only on Wednesday, instead of looking at the average effects for the team he plays for, you'll be able to zoom in on that day's column and see what effects that particular pitcher should be experiencing, on average. We believe this will lead to better informed decisions. We also believe that by presenting the whole week in columns, the format now becomes quite important to those who play in daily transaction leagues.

The first example above was a fairly typical team schedule. The Braves, according to this rough report, should experience a pretty normal week in terms of home runs for their hitters and pitchers should have an easier time, on average, winning games. The environment in Colorado can't offset that the Rockies are actually a poor hitting team if you take away Coors Field (they're now hitting .221 on the road this year) and so the opposition effect sort of cancels out the park effect here. In any case, both WHIP and ERA should suffer a bit.

What's particularly interesting in this example is the stolen base row, which tells us that the Braves, on average, should be expected to only steal at 75% of the rate that they usually do. In the long run, that means that a 30 base stealer in this schedule would look like a 22 or 23 SB type, which can make a big difference in the long run.

Let's turn to a more extreme example, also from the real upcoming week's schedule:


This is the upcoming week's Seattle Mariners schedule. Notice that by looking at this, we can quickly see what types of players, on average, we'd want to have playing. Home run hitters would be expected to really prosper in this packed schedule because of the two games in Texas (the Rangers lead the majors in home runs allowed). The potential for Seattle pitchers to get wins and saves is huge given that five of the seven games come against teams that are really struggling. The Mariners, so far, are a bad team but in this week, they're against teams they've got a good shot to beat - note that the win/save effect is not just based on season to date wins but also updated projected team strength ratings which we will adjust as the season goes on. Strikeouts for pitchers should be up significantly because Seattle pitchers get three games against Kansas City hitters, who have struck out 144 times in 599 at bats this year. Stolen bases may suffer a bit but most categories are beneficial to Seattle players here.

As I say, these samples are rough ones but they are based on the logic of how the report will work. We sincerely believe that reports like these will help those in weekly and daily transaction leagues to maximize the value on their roster. Of course, we'll always notice when our pitcher happens to pitch well in Colorado or poorly in San Diego but fantasy baseball is a long run game and these reports are designed to turn the schedule into one big "long run" of maximizing your potential. If you have deep reserve lists, imagine if you could make your entire hitting staff play in Colorado and your entire pitching staff pitch in San Diego and you'll get an idea of just how important taking advantage of the schedule really is.

As I say, we expect to introduce these new-style reports within the next two weeks and they will then run on Sundays until early September.

Saturday, April 21, 2007

Weekly Depth Charts

This is to notify readers that our latest "Weekly Depth Charts" report is now available for free at the BaseballNotebook.com website. This report is not available in the usual blog format.

Friday, April 20, 2007

Good Luck, Bad Luck

Our latest "Good Luck, Bad Luck" report is now available at the BaseballNotebook.com site. This report is not available in the usual blog format but can be accessed by visiting our home page and by clicking on the link entitled "Good Luck, Bad Luck" in the current free essays section.

Wednesday, April 18, 2007

Rookies and Job Insecurity

I've alluded to this before when explaining low games played projections but I want to focus a little today on rookies and job security, or lack thereof. I'll use two prominent rookies in Alex Gordon and Kevin Kouzmanoff as examples but if you look hard enough, you could probably find twenty rookies who fit the profile I'm describing here.

All the talent in the world, as I always say, can never overcome when a rookie starts 0 for April. It doesn't matter whether we're right or wrong about a player's hidden real talent if their own team doesn't believe in that level. In fact, last year, Nick Markakis was a great example of a rookie who almost lost his job after starting miserably. Fortunately for Markakis fantasy owners, the Orioles did stick with him and he got hot at just the right time. Markakis ended up with a .291 average on the season in just short of 500 at bats. Unfortunately, rookie rebounds like that are rare, not only because there are few rookies capable of hitting .291 but because (a) the slow start gets mixed with the eventual stats, (b) most rookies get sent back to the minors once they struggle sufficiently in April and/or May and (c) a lot of rookies really aren't ready for instant success in the majors.

There are a couple of rookies who come to mind who are definitely more talented than they've shown so far but who are moving closer to territory that could cost them their job. The first is Alex Gordon. My own forecast for Gordon was called pessimistic by at least a few readers and I understood that considering so many sources have picked him to win Rookie of the Year. I didn't and still don't think I was that low on Gordon considering I was projecting a .264 average with a bit of power (13 home runs and 50-55 RBI) but I suppose compared to the lofty expectations of those who expect him to be an instant superstar, I can understand why this might seem to be a grim expectation. I haven't downgraded that expectation much - Despite the slow start, Gordon's better than we've seen.

In any case, he's now dangerously close to losing his job. I talked about this last week but things have not improved. As I edit this blog for publication on Wednesday afternoon, Gordon is 0 for 2 in today's game against the Tigers and his average has fallen to just .128. While his potential replacement at third base, current outfielder Mark Teahen, is hitting only .190, Teahen has the advantage of having a track record, albeit a limited one. The Royals are not going to ruin Gordon by keeping him in the majors much longer.

Yesterday's entry talked a bit about how Clay Hensley's terrible start will now be mixed in with everything he does from now on. I pointed out that if Hensley threw two straight shutouts, his ERA would still be above 5.00. Well, in the case of Gordon, he's now 6 for 47 including the 2 hitless at bats in today's game. That means that if he were to go on an incredibly hot stretch, say, hitting .350 for the next 47 at bats (which would take us into early May), his average at the end of the stretch would still be only .239. Gordon needs to get hot like that right now or he will not be a regular third baseman in the majors for much longer. I know there are denials from official sources and so on but I can't even find the last rookie who kept his regular job into June hitting under .200.

In the so-called senior circuit, Kevin Kouzmanoff is off to a miserable start with the Padres. Like Gordon, a third baseman, Kouzmanoff has the slight advantage that he had a good spring right from the start and so the Padres openly said that if he struggled in April, they wouldn't immediately give up on him. Unlike Gordon, I've been projecting Kouzmanoff higher than most forecasters with a projected .286 average, 21 home runs and 71 RBI. I don't know if he'll get to be this year's version of Nick Markakis, partially because the Padres do have at least two temporarily viable options at third base in Russell Branyan and Geoff Blum.

Kouzmanoff is older than Gordon and I suspect the Padres are less worried about "ruining" him by keeping him in the majors. Their concern, rightfully, has to be whether he really can produce for him the way they envisioned a month ago. I believe he can but also like Gordon, Kouzmanoff needs to get hot right now to keep his job. He's hitting just .135 in 37 at bats and the Padres are being a little more generous with him because he missed a few games with an elbow contusion in the second week of the season. His defense has looked good so that's another advantage he has over Alex Gordon, who has looked shaky throughout April at the hot corner.

In any case, these two serve as examples of something I always find challenging but must take into account when making a forecast. That is, how a rookie starts the season has much more of an effect on their playing time than how a veteran starts. Frank Thomas is hitting only .191 but has absolutely no risk right now of losing his job. If he were a rookie DH (the Jays have brought rookies to the majors before through the DH position, including John Olerud), his job would already be in jeopardy but because he's Frank Thomas and because he's being paid a lot of money to hit, he'll still be in the majors in June if he's healthy.

So, when you're considering fantasy trades for guys who you know are better than they've shown so far, remember that rookies have a constant state of job insecurity. They're always one extended slump away from a return trip to Triple-A. You must keep this in mind because you could be right about their real hidden ability but wrong about their ability to contribute to your fantasy team if they're not going to stay in the majors.

Tuesday, April 17, 2007

Clay Hensley

I'm posting Tuesday's entry earlier than usual as my email inbox has already started to fill up with disgruntled Clay Hensley owners who have decided that his single disastrous performance to date negates the utility of the projections. At least a few wanted to know if the blister he's been suffering through has been the problem and others want to know if I see anything different than the pitcher I expected to see, stuff-wise that is... obviously results-wise he's been a complete mess.

Just in case you didn't know, my name is not Clay Hensley. Judging by a few of the comments directed to the BN inbox, there are people who want to blame someone (anyone) for Hensley being a complete wreck to date, especially in this latest effort.

Some readers might have noticed since this blog started back in November that I will rarely give much space to responding to the unconstructive critical comments of readers. I want the blog to be a place where we can examine ideas and see what works and what doesn't and talk about news that's of interest. It took me a while to learn that in past years I was giving short-run thinking and related comments far too much space in these entries, so much so that it encouraged it.

Also, I came to realize more than ever that forecasting will always have players who perform well outside expecations and there will be certain readers who focus on that specific player throughout a season, perhaps because that single player ruins their fantasy team. It's the nature of the forecasting game. In previous years, I far too often found myself repeating the same type of comments about specific players that you can still read in the archives at our site in any of the annual "Best of Ask David" series that are still there.

However, there are times when a projection that is starting poorly needs to be examined to see whether it needs major revision.

I want to address the issue of focusing on single players. Sure, we all notice when the pitcher we happened to think was a sleeper bombs but in fact, the projections remain and always have been a long run effort. In fact, if you take our Opening Day projection set from this year and look at all pitchers who have a projected ERA of 3.15 or better, you'll quickly discover that even with Hensley's terrible start, the combined ERA of this entire group so far in 2007 (over more than 100 innings already) is 3.30. That's not fantastic but it's within the margin of error for the group. There will be players who perform better and there will be others who perform worse in the short run and we simply can't control that nor can we do better. Every year, I can almost guarantee that there will be at least one or two pitchers who start terribly compared to the forecast. Some right themselves and some don't.

So let's focus on Hensley. There really are two issues worth looking at here...

First, is an injury causing Hensley to be worse than he really is? Actually, if you watched his first two games this season, his velocity and location has been up to standards and he hadn't allowed a home run in either of his first two starts. He did have a blister break in his second game of the season and he suffered through miserable defense behind him in the first game but despite him saying that he was throwing in pain, his fastball has only been a bit off normal, maybe enough to cause some problems but not enough to cause this sort of start.

So, we have to ask whether how bad he's looked really is as bad as he's pitched. I will not say that he's pitched well because that would be misrepresenting things. However, I can easily show you that he has pitched much better than the results would indicate so far and has suffered through one of the most miserable stretches of bad luck that I've tracked in pitchers. In fact, we first alluded to this in last week's inaugural "Good Luck, Bad Luck" column about pitchers and the number of "non home run hits" they allow on balls in play.

If we add in Monday night's Chicago disaster to have our stats up to date, Hensley has now given up a hit on an amazing 39.3% of balls put in play against him. To put that in perspective, there isn't a single qualifying starting pitcher in modern major league history who ever had a BABIP that high. In fact, if we even include relievers, there wasn't a pitcher in all of baseball in the past two years who has even pitched 40 innings with a BABIP rate that high. It's simply not a sustainable rate in the long run and is an absolute indication of tremendously bad luck.

Sure, Hensley has been terrible and even with his 2006 BABIP rate (which was 27.7%), he would have allowed about 16 hits and 2 home runs for 18 hits in just 14 innings but that's a far different pitching line than the way things look right now. So, while he's bad, I can tell you with extreme confidence that he's not this bad.

Of course, the tough decision is always deciding whether to bench a player because of a bad start or to stick with him. Hensley's next start is in Colorado and if there is an injury, which the Padres might suspect, it wouldn't be surprising to see him get a rest soon. The biggest threat to a projection is that a player never gets a chance to right himself because he loses his role. Now that has to at least become a remote possibility if Hensley continues to get knocked around. Also, no matter how well he pitches, each of these bad starts he's had so far are now going to be included in his ERA which means he'll have an uphill battle to get his ERA back to respectable status. In fact, if he goes out and throws back to back complete game shutouts, his ERA will only be 5.34 after the second shutout. That means I can also tell you with high confidence that what he's done so far is going to make his ERA be above 5.00 for quite a while, likely into late May no matter how he pitches.

One thing that did surprise me is that the Padres kept him out there when he was getting hammered so badly Monday. Anyway, there's nothing you can do when a projection starts so badly except revisit it to see if the evidence is there to warrant a revision. I'll leave it to the reader to consider what I've said here and decide if Hensley really is the worst pitcher in modern history in terms of allowing hits on balls in play. If you believe that's the case, by all means then he really is this bad. For now, I'm sticking with him on my teams and, as I said, his ERA is going to remain high for quite a while because of what's happened so far.

Sunday, April 15, 2007

Ryan/Frasor, The Week Ahead

In case you missed it, the Blue Jays just placed B.J. Ryan on the DL with an injured elbow. That means that if you can pick up AL pitchers, you should move quickly to grab Jason Frasor, who will likely fill in for Ryan as the closer. Frasor actually briefly was Toronto's closer back in 2004 when he saved 17 games in 19 opportunities. He has a nice fastball and a career 3.82 ERA in 193 big league innings before the start of this season so there's good reason to have some optimism. Unfortunately, all of this happened after we had already published the latest projection sets and so that's why I want to draw it to readers' attention right away. It's almost as if the Toronto front office considered that many of us have Sunday night fantasy cutoff deadlines...

I've continued to be unsatisfied with the information I have available (and thus can offer to readers) regarding the upcoming week's schedule but this week I have some good news which will lead into next Sunday.

I had talked before about the desire to focus on specific matchups in a weekly schedule and try to combine most of the elements of the Scheduled Advantage strategy into a single number or index rating which we can share with readers. It now looks like we will be able to do that this year, possibly even by next Sunday.

Basically, we're going to attempt to produce something that shows, for each team, a list of its opponents in the upcoming week and a list of how all of the park factors, opposition factors and other factors come together to create an "index" or multiplier that should affect each player's performance. It looks like we'll have to offer multiple index ratings. For example, we might be able to say that if a team plays Detroit, hitters should experience a stolen base index of 0.40 (that's just a number I picked out of the air as an example and not a real number). If that were the number, it would tell the reader that during the games against Detroit, on average, base-stealers would only steal at 40% of their usual rate.

This is a real challenge to produce but readers may have noticed that what we're trying to do with the site this year is to share more of the tools that we (and I personally) actually use when making informed fantasy league decisions. In the past, I've manually examined the schedule and this should help get a better sense of how a schedule actually shapes up.

One aspect we've moved away from compared to past years is the idea of attempting to project double-start weeks for pitchers. I'm aware that at least a few readers benefited from this but I became frustrated with the information available at press time - these articles are often created a day in advance - and we're simply not a 24-hour operation capable of holding back double start lists until Sunday night.

The good news is that MLB.com is apparently publishing lists of double-start weeks for free at their site. For example, the upcoming week is detailed through this link:

http://mlb.mlb.com/mlb/fantasy/mlb_fantasy_columns.jsp?story=ahead0413

In any case, just to briefly touch on the upcoming week's schedule, I'm no longer going to single out specific players as we prepare to move to the new report format I've touched on above.

Just in terms of the upcoming week's schedule, Colorado not only has seven games this week but is home for the entire week, which should benefit hitters. San Diego pitchers only get the help of the home park for two games (against Arizona) and then spend the rest of the week playing in Wrigley Field and in Colorado so you would expect it would be a good week to have San Diego hitters active and consider resting some San Diego pitchers. Clay Hensley does get two starts but the first will be in Chicago and the other in Colorado. Jake Peavy's only start of the week will come at home against Arizona. One other pitcher who will be facing the Colorado effect is Derek Lowe, whose only start of the week will likely come there against Rodrigo Lopez.

Kansas City hitters face a tall task as they play only six games (many teams have a seven game schedule this week) with three in Detroit and three at home against Minnesota. Oakland hitters might be worth resting as the A's have just five games on the schedule with off-days on both Monday and Thursday. Of course, there is a potential payoff in the five games as three of them will be played in hitter-friendly Texas.

Just on a final note regarding the upcoming week, there may be more to be learned from watching The Weather Network over ESPN when making fantasy decisions. A major storm affecting several parts of the US has already caused airlines to cancel flights and it wouldn't be a surprise to see several days of cancellations in the schedule. At least a few major cities have possible snow in the forecast again for Monday so keep your eye on the forecast if you play in daily transaction fantasy leagues.

Saturday, April 14, 2007

Weekly Depth Charts

This is to notify readers that Baseball Notebook's latest Weekly Depth Charts report has now been published at the BaseballNotebook.com site. This report is not available in this blog format but can be accessed for free at the site.

Friday, April 13, 2007

Good Luck, Bad Luck

Today's essay is a significantly longer one than usual so we'll ask readers to take the time to go through it carefully as it sets in context a new report we'll be publishing most Friday evenings until early September.

This report is designed to replace our old "Going Up, Going Down" series that used to run in the newsletter for a few years. One of the problems with that other series was that it was often out of date within a day or two as players constantly shuffled in and out of roles. Since it's not possible for us to produce a daily report of that type, at least for now, I've personally been focused on trying to identify the elements that I believe reveal a player who's likely to see a better or worse performance in the near future.

The report may eventually be entitled with a different name as we add categories that refer to player trends but for now, it seems to be an appropriate name to call it "Good Luck, Bad Luck" as all elements of the report relate to performances that are misleading if you look at raw 2007 stats. Normally, we will provide just the lists but this edition, we try to explain each list and how the reader can best use it.

SINGLES PER BALL IN PLAY

Singles per ball in play is calculated by taking the number of singles a hitter has hit (H-DB-TR-HR) and dividing it by the number of times he put the ball in play to resolve a plate appearance (AB-K). The highest sustainable 1B/BIP rate over the long run, at least in recent seasons, is about 30-35%. Among qualifiers for the batting title, Derek Jeter led the majors with a 30.3% rate in 2006. In 2005, Willy Taveras managed a 31.1% rate while Ichiro amazed us all in 2004 with an incredibly high 35.1% rate. Most hitters are not capable of sustaining such a rate over the long run, though.

The reason this category is so important is that it can instantly reveal hitters who are doing better so far than is possibly sustainable. Thus, our first list is one that provides the names of the highest 1B/BIP rate so far. These players will usually have unsustainable batting averages because the 1B/BIP rate will reveal a lot of 2007 luck so far in terms of how often they're putting the ball in play. Moreover, the number in brackets right after the player's average tells you what the player's batting average would be if they were only singling at a league-leading type 35% rate. Now, a player can still severely overachieve in terms of how often they're making contact - we'll look at that separately here shortly.

All data is through play completed Thursday.

Highest 1B/BIP rate, minimum 30 at bats

Number in brackets refers to what the player's average would be if they were actually singling at "only" a 35% league-leading type singles rate:

Gary Bennett, STL, 10 AB, 50% 1B/BIP Rate, .500 Avg (.350)
Nelson Cruz, TEX, 20 AB, 50% 1B/BIP Rate, .300 Avg (.210)
B.J. Upton, TB, 26 AB, 47% 1B/BIP Rate, .385 Avg (.317)
Yorvit Torrealba, COL, 12 AB, 44% 1B/BIP Rate, .333 Avg (.263)
Todd Linden, SF, 10 AB, 43% 1B/BIP Rate, .300 Avg (.245)
Derrek Lee, CHC, 33 AB, 42% 1B/BIP Rate, .424 Avg (.367)
Aramis Ramirez, CHC, 32 AB, 42% 1B/BIP Rate, .406 Avg (.347)
Akinori Iwamura, TB, 30 AB, 42% 1B/BIP Rate, .433 Avg (.370)
Matt Kemp, LAD, 14 AB, 42% 1B/BIP Rate, .429 Avg (.371)
Victor Martinez, CLE, 12 AB, 40% 1B/BIP Rate, .500 Avg (.458)

Just as the top players may be lucky, there can be players who are doing everything right and are simply suffering the effects of bad luck. I recall a reader asking a question back in May 2005 (you can read it about 60% of the way down in the Best of Ask David - Volume 3) where he wanted to know if Vernon Wells would rebound from a terrible start. I used the singles per ball in play explanation to show that Wells was making contact at his usual rate but just wasn't getting the singles.

The lowest 1B/BIP rate a hitter will usually sustain over the long run is about 15%. Carlos Beltran was the lowest, among qualifiers, in 2006 with a 14.6% rate. However, this is often the case with power hitters. Power hitters are singling at a low rate because they're getting plenty of other types of hits. It is important to note here that hitters actually perform at a relatively consistent rate in this category over the long run and, so, if the reader sees a player among the lowest at getting singles per ball in play, it can help the analysis to look at the player's past performance to see if he traditionally has been a low achiever in this category. Note that it is possible for a player's real singles per ball in play rate to be below a typical league-trailing rate. That's because the players who can't hit the ball sharply enough to sustain such a rate would rarely get enough at bats to qualify for the batting title. Here's how 2007 shapes up to date on the other side of the ledger. Yuniesky Betancourt is an excellent example of a player who may seem to be off to a terrible start but actually, so far, is doing everything right and just apparently suffering through some miserable luck.

Lowest 1B/BIP Rate, minimum 30 at bats

Number in brackets refers to what the player's average would be if they were actually singling at even a 15% league-trailing type singles rate:

Yuniesky Betancourt, SEA, 15 AB, 0% 1B/BIP Rate, .133 Avg (.273)
Brad Eldred, PIT, 11 AB, 0% 1B/BIP Rate, .182 Avg (.305)
Andy Marte, CLE, 22 AB, 0% 1B/BIP Rate, .136 Avg (.245)
Robb Quinlan, LAA, 12 AB, 0% 1B/BIP Rate, .000 Avg (.113)
Richie Sexson, SEA, 17 AB, 0% 1B/BIP Rate, .176 Avg (.274)
Jason LaRue, KC, 18 AB, 0% 1B/BIP Rate, .167 Avg (.275)
Rod Barajas, PHI, 10 AB, 0% 1B/BIP Rate, .000 Avg (.135)
Kelly Johnson, ATL, 31 AB, 4% 1B/BIP Rate, .161 Avg (.260)
Torii Hunter, MIN, 31 AB, 4% 1B/BIP Rate, .258 Avg (.352)
Alex Rodriguez, NYY, 31 AB, 4% 1B/BIP Rate, .355 Avg (.444)

CONTACT RATE

Contact rate simply refers to what percentage of a player's at bats are resolved by making contact. It is calculated by taking (AB-K) and dividing it by AB to get a number. The highest sustainable contact rate is about 95%. Juan Pierre was tops in the majors, among qualifiers, with a 94.6% rate in this category last year.

The key to interpreting contact rate is to look for players who are achieving unsustainable rates. Players do improve in this category and so the utility of a list here is more limited than the singles per ball in play rate because it's possible a player is really a newfound star here. If a player makes contact more often than he really can sustain in the long run, his batting average will usually temporarily benefit from his good luck. The luck part here could be that he's just faced easier pitchers than he will, on average. Of course, it's also possible that hitters on this list really do have the skill shown. Eventually, the best contact hitters will find their way to the top of this list:

Top Contact Rates, minimum 30 at bats

David Eckstein, STL, 36 AB, 97.2% Rate
Luis Gonzalez, LAD, 31 AB, 96.8% Rate
Casey Kotchman, LAA, 31 AB, 96.8% Rate
Mike Lowell, BOS, 30 AB, 96.7% Rate
Jacque Jones, CHC, 30 AB, 96.7% Rate
Placido Polanco, DET, 40 AB, 95.0% Rate
Miguel Tejada, BAL, 39 AB, 94.9% Rate
Brian Giles, SD, 36 AB, 94.4% Rate
Nomar Garciaparra, LAD, 34 AB, 94.1% Rate
Derek Jeter, NYY, 34 AB, 94.1% Rate

Looking at the other side of the ledger, there's no such thing as an unsustainably bad contact rate. The only thing that might make it unsustainable is that if you don't ever hit a ball, you won't stay in the majors. In any case, the worst hitters in this category, at least those who last long enough to play a full season, typically have contact rates of about 60-65%. Brad Wilkerson, worst in the majors in 2006, had a contact rate of just 63.8% and ended up with an average of just .222 to go with it. Still, if you see a veteran player with a good track record for making contact on this list, chances are good that he's either faced extremely tough competition so far or is just suffering through an unusual slump that won't last.

Bottom Contact Rates, minimum 30 a bats

Adam LaRoche, PIT, 31 AB, 54.8% Rate
Mark Teahen, KC, 30 AB, 60.0% Rate
Alex Gordon, KC, 33 AB, 60.6% Rate
Andruw Jones, ATL, 33 AB, 60.6% Rate
Troy Tulowitzki, COL, 30 AB, 63.3% Rate
Craig Monroe, DET, 30 AB, 63.3% Rate
Ryan Howard, PHI, 33 AB, 63.6% Rate
Curtis Granderson, DET, 36 AB, 66.7% Rate
Ryan Freel, CIN, 30 AB, 70.0% Rate
Aaron Rowand, PHI, 30 AB, 70% Rate

NON HOME RUN HITS ON BALLS IN PLAY

I've said before that while I don't entirely subscribe to all the aspects of Voros McCracken's "DIPS Theory" (which argues that pitchers have limited or no control over what happens to one of their pitches after a hitter makes contact, except on home runs), I do entirely believe that a pitcher can suffer through a miserable stretch simply because a disproportionate share of his pitches are falling for hits.

In that respect, I want to focus on which pitchers so far are giving up an unusually number of non home run hits (i.e. singles, doubles and triples) per time that they're allowing a hitter to make contact.

This category can't really help us for relievers as the sample size is far too small but for starting pitchers, we can get a sense of who's been suffering from some bad defense or bad luck or who's been facing teams with hitters who hit the ball more sharply.

We estimate balls in play here with the available statistics, which are calculated as:

Balls in Play = Batters Faced - HR - BB - STRIKEOUTS
BABIP = (H-HR) / Balls in Play

I'm not sure whom to credit for these formulae because I've seen them so many places. In addition to McCracken, I can tell you that I've seen these published by Baseball Prospectus' Keith Woolner and I have no reluctance to credit him as a source for the formula, not sure whether he devised this way of roughly estimating them or if they came from McCracken himself.

To summarize for those who don't care about the formula details, basically, the BABIP metric will tell you what percentage of balls put in play (excluding home runs) are falling for hits. Those holding the most extreme viewpoints under DIPS theory would argue that any deviation from the average result here would be bad luck where by definition bad luck can include having a bad defense behind the pitcher. I tend to hold the view that a pitcher has some control over how squarely a hittter hits his pitches, which is why I believe Mariano Rivera annually has better results than Andy Pettitte in this category.

In any case, long run performance in this category over a full season of at least 600 batters faced rarely goes outside the range of about .225-.350 and the average in baseball in 2006 was around .270-.275 using our estimated BABIP method.

This first list should show you pitchers who have suffered extraordinarily bad luck so far in terms of how they've actually pitched. The presence of Clay Hensley on this list should come as no surprise to readers who've actually watched both games he's pitched so far. A BABIP rate of above .350 is simply not going to last over a full season and, in fact, more than 60% of starting pitchers in 2006 had a rate of between .250 and .300 in this category and a rate above .350 is almost certainly unsustainably bad luck.

HIGHEST BABIP (minimum 40 batters faced)

Jae Seo, TB, 50 BFP, .421 BABIP
Brandon Webb, ARI, 55 BFP, .400 BABIP
Doug Davis, ARI, 51 BFP, .394 BABIP
David Bush, MIL, 51 BFP, .389 BABIP
C.C. Sabathia, CLE, 57 BFP, .372 BABIP
Clay Hensley, SD, 46 BFP, .371 BABIP
Kevin Millwood, TEX, 48 BFP, .353 BABIP
Dontrelle Willis, FLO, 53 BFP, .351 BABIP
Zack Greinke, KC, 53 BFP, .350 BABIP
Jason Schmidt, LAD, 41 BFP, .346 BABIP

On the flipside of this equation, we look at the ten pitchers who've had things go their way so far, likely above how they've actually pitched. Here are the ten pitchers who've recorded the best BABIP rates so far, meaning that they may be experiencing either extraordinarily good defense behind them or just a lot of balls happening to be hit at the right spot. A rate better than about .225 simply cannot be sustained by most starting pitchers in modern history, though there have been rare exceptions:

LOWEST BABIP (minimum 40 batters faced)

Felix Hernandez, SEA, 58 BFP, .111 BABIP
Matt Cain, SF, 51 BFP, .121 BABIP
Tim Hudson, ATL, 51 BFP, .121 BABIP
Justin Verlander, DET, 53 BFP, .139 BABIP
Steve Trachsel, BAL, 51 BFP, .140 BABIP
Orlando Hernandez, NYM, 49 BFP, .143 BABIP
Josh Beckett, BOS, 45 BFP, .143 BABIP
Jeremy Sowers, CLE, 51 BFP, .167 BABIP
John Maine, NYM, 49 BFP, .167 BABIP
Ramon Ortiz, MIN, 56 BFP, .174 BABIP

On a related note, I used to publish a statistic called "ERMA" which referred to Earned Runs Manufactured Average. I've had several variations of my ERM formula but similar to Bill James' ERC, it attempts to project how many earned runs a pitcher should have allowed based on his component numbers. There are at least three versions of the ERM formula but the one I use most frequently is this one:

ERM = (-.2477*ip)+(.4705*h)+(.7668*hr)+(.0829*sh)+(.2725*sf)+(.9819*hb)+(.2538*bb)+(.0241*k)+(.1294*wp)

ERMA = ERM / IP * 9

The ERMA formula actually helps me to project pitcher's ERA, though I still have to make adjustments for other factors such as how a pitcher is being used.

Here are the top ten widest gaps between current actual ERA and what ERMA says a pitcher's ERA should be. In the long run, I would expect these pitchers to have had a higher ERA than they actually do:

Pitchers With ERA Better than ERMA (minimum 40 batters faced)

Number in brackets is ERMA

Sergio Mitre, FLO, 56 BFP, 4.09 ERA (8.18)
Adam Loewen, BAL, 47 BFP, 1.80 ERA (5.40)
Joe Kennedy, OAK, 48 BFP, 1.64 ERA (4.91)
Doug Davis, ARI, 51 BFP, 1.64 ERA (4.91)
Carlos Silva, MIN, 49 BFP, 0.77 ERA (3.85)
John Lackey, LAA, 50 BFP, 0.75 ERA (3.75)
Jamie Moyer, PHI, 57 BFP, 3.54 ERA (6.38)
C.C. Sabathia, CLE, 57 BFP, 2.77 ERA (5.54)
Brad Penny, LAD, 53 BFP, 0.68 ERA (3.38)
Chuck James, ATL, 47 BFP, 0.82 ERA (3.27)

On the flipside of the equation, there are pitchers whose ERA looks much worse than it should actually be. Remember too that ERMA continues to penalize the pitcher for the bad luck of hits that may have fallen in unfairly so if you see a pitcher on this next list who's also on the bad luck BABIP list, well then chances are he's just been suffering through some tough breaks to date:

Pitchers With ERA Worse than ERMA (minimum 40 batters faced)

Number in brackets is ERMA

Clay Hensley, SD, 46 BFP, 9.00 ERA (5.00)
Barry Zito, SF, 50 BFP, 8.18 ERA (4.91)
John Patterson, WAS, 44 BFP, 9.31 ERA (6.21)
Boof Bonser, MIN, 47 BFP, 6.99 ERA (4.37)
Adam Eaton, PHI, 51 BFP, 6.92 ERA (4.62)
Brett Myers, PHI, 52 BFP, 6.75 ERA (4.50)
Ben Sheets, MIL, 56 BFP, 3.60 ERA (1.80)
Scott Olsen, FLO, 45 BFP, 4.37 ERA (2.62)
Chris Capuano, MIL, 44 BFP, 4.37 ERA (2.62)
Derek Lowe, LAD, 51 BFP, 5.72 ER (4.09)

There are no doubt other categories we can add as it would be nice to work in a list that involves relief pitchers and maybe playing time indicators. In any case, we hope readers benefit from these lists and use them wisely. Often, a player really isn't performing as well or as bad as they seem to and the smart fantasy GM needs to look beyond the boxscore to get a sense of how players are actually performing. As I said, updated versions of these lists will run most Friday evenings up until our publishing season ends in early September. Enjoy!

Wednesday, April 11, 2007

Jorge Julio, Al Reyes, Branyan/Kouzmanoff, Gordon

If you're searching the waiver wire for potential pick-ups, you may want to move quickly on any of the former closing candidates in Florida. Jorge Julio got a very watered-down vote of confidence in a piece that ran at the Marlins' official site late last night. New Marlins manager Fredi Gonzalez was asked wheter Julio might be moved into a setup role and Gonzalez replied that he hadn't "decided on that yet."

I continue to be amazed at how quickly closer roles can be re-shuffled based on a couple of bad outings. It's not to say that a pitcher who has bad outings is necessarily a better pitcher than everyone else in the bullpen. All the evidence and factors that went into a decision to make a guy the closer before the season began shouldn't be automatically set aside (barring an obvious injury or instant drop in velocity) just because a pitcher struggles for a couple of outings. In any case, that seems to be close to happening here now and suddenly all of the spring training candidates are back in the closer mix. For what it's worth, Taylor Tankersley is about to return from the DL and he could be a good play here, especially given how well he pitched last year in 49 games with the Marlins.

Elsewhere in the state of Florida, Al Reyes has indeed established himself as the Florida closer. At least one reader asked why I haven't projected more games for Reyes (just 25 in the previous edition). It's not that I'm not aware of his role and his projected games will continue to increase as he demonstrates that he is healthy. Reyes is an extremely high injury risk, having missed almost all of last season after undergoing Tommy John surgery in late 2005. There's a concern that he can't pitch two days in a row and given that he has no recent track record, even the slightest of slumps would set him back out of the role he's just gained. In any case, I had already bumped him up to 13 saves in the previous edition of the forecasts and I'm considering just how many more I can project for him given this new affirmed role and his injury risk potential.

Readers who get alarmed that Kevin Kouzmanoff's name isn't in the boxscores much this week shouldn't falsely presume that Russell Branyan is unseating him because of a slow start. In fact, Kouzmanoff was hit by a pitch on Monday that has given him a lingering sore elbow. Kouzmanoff may not be back until the weekend and so this gives Branyan a chance to show off his power and confirm his presence as an option if Kouzmanoff's early-season struggles continue into late April.

Last night, I stepped away from the television long enough to just miss Alex Gordon's first major league home run. I've maintained throughout the off-season that Gordon is anything but a sure thing but he's still better than he's looked so far. I remind readers what I said several times this winter (and this applies to Kevin Kouzmanoff too) and that is that rookies who win starting jobs in spring training can't go 0 for April and keep a job into May.

Royals' GM Dayton Moore is a smart baseball fellow who knows that the Royals have rushed far too many prospects to the major leagues the past ten years. Though everyone wonders whether Mark Teahen could move back to third base after playing the outfield all spring, they may decide at some point that even a defensively-rusty Teahen at third base would still offset the offensive hole at third base that Gordon has been so far. Two more weeks of 0-fers would threaten Gordon's job security here as they're not going to ruin their top prospect if it turns out he's overmatched. I believe he's much better than this, even though my projection has actually been described as pessimistic by at least a few readers. It won't make any difference if he's actually better and doesn't show it.

Because earlier season stats have greater weight in perception (read our essay On Fantasy Trading for graphic examples of this from 2005), Gordon needs to get his average up above .200 by the end of April to keep his job. Given how he's started, that means he probably needs to hit about .235 or .240 for the remaining portion of April just to still be a big league regular into May. That is, if he's hitting .199 on May 1st, I don't believe the Royals will keep him in the majors.

With Gordon off to a slow start and in the majors faster than I expected he would be, I looked back on the past fifteen years of Royals' first picks in the June draft:

1991 Joe Vitiello
1992 Michael Tucker
1993 Jeff Granger
1994 Matt Smith
1995 Juen Lebron
1996 Dee Brown
1997 Dan Reichert
1998 Jeff Austin
1999 Kyle Snyder
2000 Mike Stodolka
2001 Colt Green
2002 Zack Greinke
2003 Chris Lubanski
2004 Billy Butler
2005 Alex Gordon

I'm not being critical of the Royals on how they handle top prospects. The list tells a story on its own and many top draft picks don't work out in baseball. Still, there's not a first pick in the past fifteen years who's yet become a star (Michael Tucker hammered out a decent career), unless you count Greinke and Gordon as stars because of perceived potential. I suspect Dayton Moore will change things for the better here and that's why I believe Gordon's on a shorter leash than some seem to think.

Tuesday, April 10, 2007

Sample Size, Wheeler/Lidge, Carpenter

One of the toughest jobs any forecaster faces is deciding when a sample size is large enough to convince him or her of something new. That is, we all go into a season with a theory about a player's ability and a theory about his playing time. Then, the season begins and new data becomes available.

The danger with making new conclusions too soon is that you can write off a player or think he's better than he is only to have him turn things the other direction. In late May last year, I made this mistake with Frank Thomas, who was hitting under .200 and who had not only hit poorly but looked bad too as his bat speed seemed to have slowed. As we all know now, Thomas came back to turn things around and have a monstrous second half, one I didn't forecast.

Part of forecasting is going to be accepting that a percentage of players are going to do the unexpected and that the data will not tell the real story. Still, if we're to make the best effort we can, we have to use the data available.

The first changes have already begun to the forecasts and while they're minor, readers should be able to see the effects even a first week can have. I've bumped up a couple of steals on the projection for Darin Erstad, largely thanks to a two stolen base effort in the first week. He hasn't convinced me that he's a 20 stolen base guy just yet but my original 6 steal forecast now seems light and mixed with the 2 he already has, 10 steals could be within reach for him.

Basically, this early in the season, the sample size is still small enough that the only thing powerful enough to really move a forecast is something that is so outside the margin of error that it's unlikely that a player who has the skills of the original projection could really do what he did in the first week. There haven't been many performances that fit that criteria so far.

The way things typically work is that hitters really begin to have a meaningful sample size in the third or fourth week of the season. Starting pitchers would have a big enough sample if it were not for them facing the same teams over and over again. That is, I'd rather have 125 at bats from a hitter against ten different teams than 200 batters faced from a pitcher against four different teams. We need the quality of the opposition to be as variable as possible if we're to get a true sense of a player's hidden, neutral ability.

The reader who wondered how it is that I can say it's too early to adjust because of sample size while, at the same time, raising the projected batting average for Eric Byrnes by 9 points upward needs to be reminded that a seemingly large 9 point increase in batting average is actually less than a 1% adjustment. We've become so used to batting average being a three digit number that a 10 point difference seems massive but in fact, 10 points of batting average is actually only a 1% difference in performance (not a 10% difference) and it's easy to forget that.

Another reader was wondering why I "downgraded" David Ortiz, Jose Reyes and Johan Santana in the latest projections. On the contrary, these top players make the list of the most significant changes because, simply, a week is now off the schedule. Because a week is off the schedule, each of these players are projected to do less because there's less of the schedule remaining. The projection always refers to the portion of the season that hasn't been played yet and so it's common for the best players in any category to make the top ten list of "most significant changes" since the previous report, especially if there hasn't been a lot of movement to the forecasts just yet.

On an unrelated matter, I want to talk about the dangers of reading the boxscore this early in the year. Obviously, we're all doing it because we want to see how our favorite players are doing and which of our fantasy players are performing. It's just so easy to put far too much weight in early season performance and to be discouraged by one bad performance, especially from a starting pitcher.

In fact, I saw an excellent example of how the boxscore can really mislead in San Diego pitcher Clay Hensley's first start this past week against San Francisco. If you looked at the boxscore, you'd see 4.2 inning, 7 hits allowed, 3 walks, 2 strikeouts and 5 earned runs. What you couldn't see is that Hensley was actually quite sharp for the first four innings. In the fifth inning, already with two outs, he faced an incredibly tight strike zone that led to three consecutive walks. After starting Ray Durham 2-0 on two more close pitches, Hensley came in with a mistake fastball (apparently in an effort to get a single strike called in his favor) which Durham drove for a 2 RBI single. Then, with two outs, Rich Aurilia hit a pop up that dropped between three fielders and was generously called a base hit, allowing another run to score rather than ending the inning. This meant that everything that continued to happen was charged as earned so the run he would allow right after this, on a single, also was charged to his record.

In any case, whether Hensley had thrown six shutout innings or allowed 10 earned runs in his first start, it would be far too early to make a new conclusion but I thought I'd share with readers an example of how the boxscore can often be misleading. Setting aside what looked like a tight strike zone, Hensley easily could have been charged with only 3 earned runs here and 5 hits, which would have a very different feel to it than the final official stats. I didn't think Hensley looked to be particularly dominant in this outing but he was far better than the pitching line would reveal.

On a related note, the Houston Astros decided that the first week of the season was all they needed to see to revise their plans to have Brad Lidge close games and announced yesterday that Dan Wheeler will take over as the closer. Lidge blew his first save opportunity of the season and then got knocked around in a non-save situation on Sunday.

Phil Garner referred to Lidge not being "as sharp as he used to be" and Wheeler's had two consecutive solid seasons so he made a pretty obvious choice. What's worth noting is that Lidge, in 2006, pitched much better than his ERA reflected. In any case, saves are a category where what the manager thinks is paramount and so Lidge will be getting a massive downgrade in projected saves if this situation continues as is until next weekend.

Returning to the topic of Chris Carpenter, the dreaded "it's not a major injury" quote from officials has indeed been followed up with a trip to the DL. Now we get word that Carpenter could miss a month or more with a sore elbow. Injuries to a pitcher of his class can devastate a fantasy roster but here's hoping he gets back to the mound soon...

Sunday, April 08, 2007

Upcoming Week Schedule

I said last week that when I write on Sundays, I plan to highlight some players whom I'd be playing based on the upcoming week's schedule. This will be the first week we'll be doing that and I'll be tracking how all players listed do compared to how they do in the rest of the season when they weren't on these lists.

However, consistent with our theme of constant improvement and development, we are already in discussions to see if we can take this a step further than just highlighting specific players. My goal, eventually, would be to have something that listed an upcoming week's index for each team to show which teams could benefit in specific categories like steals and so on. The goal of an index rating would combine all the elements of our Scheduled Advantage tactics into one single rating for a team for each category. If we manage to develop something new like that, we would introduce that this year if it can be in place before the end of April. That report would then replace the idea of me singling out only certain names and would better accomplish what I've been striving to in this Sunday space.

Otherwise, for now, remember that the players on both lists are so-called long run plays and there's no guarantee that a player I'd have on my bench won't have a good week and vice versa. These are simply percentage plays based on how we read the schedule in the context of our Scheduled Advantage approach.

Here are some names I would want to have active the upcoming week, based on the way the schedule shapes up...

A.J. Burnett, TOR
Carlos Delgado, NYM
Curtis Granderson, DET
Andruw Jones, ATL
Magglio Ordonez, DET
Mark Teixeira, TEX
Rondell White, MIN

And some players I'd consider benching this week for a typically comparable player...

Pat Burrell, PHI
Robinson Cano, NYY
Dan Haren, OAK
Adam Loewen, BAL
John Patterson, WAS
Joe Saunders, LAA
Javier Vazquez, CHW
Jerome Williams, WAS

Saturday, April 07, 2007

Weekly Depth Charts

Today we introduce a new feature to Baseball Notebook which will run every Saturday up until Saturday, September 8. To access our new Weekly Depth Charts feature, you'll need to visit the BaseballNotebook.com website, where you can find it on our home page. This feature will typically be published on or before 6 PM EST on Saturdays. We hope readers benefit from and enjoy the new report! - DL

Friday, April 06, 2007

Mid-Auction Trades

A reader wrote me this week to describe a fascinating situation where about two thirds of the way through his fantasy auction, the owner sitting beside the reader "privately proposed trading Vladimir Guerrero ($39) to (the reader) for Manny Ramirez ($36) so he could pick up an additional $3 to spend for the rest of the auction. (The reader) agreed and (they) announced the trade to an uproar among several owners." The reader says that he "argued that both players were already off the board and money to spend had merely shifted from one team to another so no one's remaining bidding strategy shold have been affected." The reader goes on to ask me whether I think mid-auction trades should be allowed.

Often, we get readers who want me to weigh in an on issue, usually a position qualification rule, so that they can cite Baseball Notebook to their league as a source that has officially published an opinion about an issue. I understand that but whether a reader is a subscriber of ours isn't going to change me offering my unbiased view of a situation.

There are two parts to my opinion. The first part is what I think should be the rule and then second is weighing in on whether that rule really does exist in this league.

This is a case where absolutely I think that leagues should state in the rules that trades are not allowed during the auction. I have several reasons for this belief and while there could be a valid argument on the other side, I feel quite strongly about this.

First, the spirit of trading in any fantasy league should at least open up the idea that trades, theoretically, are available to all teams. It doesn't mean that the burden is on any fantasy GM to go seek a better offer nor does it mean he must make himself reachable but it does mean, to me, that no other team in the league should be blocked from making a deal with that team. In the case the reader describes here, the only reason a trade discussion was even possible was because the other owner happened to be sitting adjacent to the reader. Some leagues actually have seating arrangements before a draft, to put everyone in draft order, and others simply have fellow fantasy GMs happen to sit next to each other because they're friendly with the other owners and so on. The problem here is that the owner of the fantasy team who happens to be sitting the farthest from our reader during the draft is at an unfair disadvantage for proposing or negotiating a trade than the one who happens to be sitting adjacent.

But moreover, it's not so much physical distance that comes into play here. The reader argues that draft strategy would not be affected when salary moves from one team to another and I disagree. Frequently during a draft/auction, especially late, I am basing my decisions on what other teams are capable of doing with their roster given the way they've managed the auction so far. If a team has filled positions so it can't add certain players, that goes into my decision about which name to call out. Now, if teams are allowed to move players between the points at which I bring specific names for auction, then it completely eliminates that. I could announce a second baseman's name on the belief that the only team who could outbid me for the catcher I want has already plugged his catcher spots. Now, just before his turn comes up, under this circumstance, he could announce that he just traded away one of the catchers he purchased and opened up his catching slot.

In the case of a keeper league, this is a little easier to rule on. Most leagues have in place a rule that says that once keepers are submitted, the rosters are frozen. I assume the reader is suggesting that keepers aren't frozen in his/her league because if they are, then it goes now beyond implicit that keepers freeze the rosters for trading purposes until the conclusion of the draft/auction.

The reader asked an opinion and I would be hard-pressed to prove in any set of rules, which don't explicitly state it, that trades are prohibited during an auction. I would suggest that leagues out there who don't have a rule defined on this can and should define a date at which trading is frozen and then trading is restarted. I don't blame any fantasy player for being creative within the context of rules and while I do tend to be one who interprets rules more literally than by the so-called "spirit of the rule" I do believe that there are such things as implicit rules that apply to a league with the same force as the clearly articulated rules. I suspect in this reader's case, if it's a keeper league, the league's rules defining the effect of submitting a keeper list and how it gets frozen will resolve the issue once and for all. If not, all I can express is the opinion that during a draft or auction, it should be a rule that trading is not permitted. However, if your league never stated in its rules explicitly or implicitly that it wasn't allowed, then what should be a rule has no force and the trade should be allowed.

That is, I don't believe the burden was on the reader to prove why no one's strategy was affected, as he said that he made the case for during the auction. If other owner strategies are ruined because the reader did something under the rules, then that becomes the problem of the other owners. The one and only case that should be made is whether the rules allow an action or disallow an action. If the rules say that trades are permitted and do not state a time where they're not permitted, then the reader has a fairly strong case to make. If owners argue that it's implicit that rosters are frozen during the draft, then the reader would have to ask what a set of league rules would look like that do allow trading during the auction. That is, how would the current rules be different if trading was permitted? This often forces opponents into the corner of arguing that such a league would have to state that they're allowed during the draft and then that brings one back to the rules about trading itself. If trading is permitted and not explicitly disallowed at certain times of the season, then it's a loophole in the rules that does, in my opinion, technically allow trading during the auction, even if I don't like that as a rule.

Now here comes the bad news for our reader, which I think will likely end the issue against the trade, if the other rules about keepers or trading didn't already. Let me give you an example of a league rule governing the auction: "Each team can spend no more than $260 during the auction." In this case, the trade of Ramirez/Guerrero may be allowed but the team that tried to shed $3 in salary still doesn't gain $3. That is, under the literal interpretation of this rule as it's phrased, whether the owner moved Guerrero, he still spent the money on Guerrero and that counts toward the $260 he could spend in the auction. Conversely, you only spent $3 less on Ramirez and thus, it is Ramirez's salary which counts against your $260 total. You'll need to look closely at your league rules to see how the auction rules are phrased.

In that respect, I've always disliked playing in leagues which invent rules on the fly when situations come up that they didn't like. That is, if your league did not specifically prohibit trading - most leagues would be doing so either under the keeper/freeze rules or under the section of the rules which even dictate that trading is part of your league at all - then I don't believe that the league should simply decide that because it didn't anticipate how you and another owner would use the rules to your advantage, that the rule should be changed instantly. I believe in rules constantly being improved but that rule changes should apply to subsequent seasons and not the one already in progress. Otherwise, it becomes impossible to build a strategy and execute it.

Wednesday, April 04, 2007

Gameday and Pitch Velocity, Carpenter, Bonds Stealing?

I want to mention an online tool that I've found is vastly improved this year, enough so that I think a lot of readers who like to do their own forecasting or analysis will really benefit from it. That is, it's a feature a lot of us have used for years called MLB.com's free "gameday" feature. This is not a paid plug or anything like that - the closest affiliation I've personally ever had to MLB's site was spending one year as a writer for them - but the tool brings something to the game that you really can't get from the boxscore.

Specifically, this year, it seems that for certain games, you can get the velocity of every pitch a pitcher throws as a game transpires. This is priceless information that had been tracked for a long time by various sources, including Baseball Notebook's primary stats provider, Baseball Info Solutions. However, being able to see an entire plate appearance with velocity and location of every pitch at a quick glance (you can even go back to a single plate appearance and watch it quickly) tells quite a bit of the story about a pitcher's power that day. At least based on my quite early read of things, the radar tracker in question doesn't seem to be a so-called "fast" gun that's producing extraordinarily high pitch speed numbers either.

The only bad news is that so far, it doesn't seem to be available on every game. For example, today's Arizona/Colorado game just has the pitch location but the Cleveland/Chicago game is showing me the release velocity, the end velocity and the break on the pitch from every pitch Jake Westbrook is throwing. It seems that only selected games have the pitch velocity but that could be because the teams haven't all staffed up or trained their fastball pitch operator positions, which I had noticed advertised this winter for every big league team.

Just in case you hadn't already heard, Chris Carpenter will sit out at least his next start with a sore right elbow. I had finally moved Carpenter out of the high risk injury category heading into this year after two consecutive healthy seasons and at least the preliminary reports are that this isn't a major injury (of course many major injuries start out as being suspect minor injuries). As it stands now, the best I can gather is that Carpenter's status will be revisited on Tuesday.

I always remind readers never to put much weight on the first week of the season because everything that happens in week one is exaggerated in importance. In fact, I wrote an article about fantasy baseball trades and perception a couple of years back showing the effect that the order of events has on throwing off perception. If you're interested, it's still available here and used Andruw Jones as an example in May of 2005, just as he was starting to get into the groove of what would become a great season.

However, there was something this week that got my attention because if it had happened in July or happened in April, it still would have been worth noticing and that was that for at least a brief instance in the Giants' season opener, Barry Bonds ran quickly. I don't mean he fluked his way to a stolen base but rather that he stole a base intentionally and looked fast doing it. I've projected only 2.5 steals for Bonds this year in almost 350 at bats and so, naturally, this has me considering that Bonds' legs are in better shape than I thought. Of course, a bit later, he was thrown out at home standing up on a play at the plate.

I always tell readers that early season performance can't get too much attention but when a player already has a stolen base in the first game and has been projected to steal only two or three for the full season, that sets the wheels in motion for me to at least reconsider what's projected, even this early. So, Bonds joins my extra watch list for the next week or two as I try to discern if he's going to be capable of (and willing to) steal more bases this year than he has in a while. Lots of players talk about running and by mid-April discover that deciding to do so doesn't help if you don't run fast enough. Bonds hasn't stolen more than three in a season since 2004 and hasn't hit double digits in steals since 2001 so it's a bit early to get excited about him as a potential base-stealer again... for now.

Tuesday, April 03, 2007

Hermanson, Pudge, Experimental Fantasy Teams

It took only about two hours after the final Opening Day projections were published for the first major transaction to happen that would have clearly affected them. Dustin Hermanson, whom I had maintained a near "zero saves" forecast up until around the 65% mark of spring training but who had been announced as the closer in the third week of March, was released by the Cincinnati Reds after getting knocked around the final week of spring training.

We had actually expected Hermanson to pitch pretty well this season but from a closer's perspective, even my Opening Day forecast of 15.7 saves was the second-lowest of any designated closer (Eric Gagne's 13.8 saves are/were the lowest). We also got to see the uncertainty index at work here as Hermanson's uncertainty rating for saves was the third highest in the entire set. In any case, his release still came as a great surprise to me and it appears that David Weathers is going to be the immediate beneficiary of Hermanson's release.

I watched the TV broadcasts of the better part of three full games the past two days and parts of others, including the entire Toronto/Detroit season opener on Monday afternoon. During that game, I saw something I don't recall seeing in all the games I've watched Ivan Rodriguez over the years. Pudge had an apparent lack of focus this game, defensively, that caused Toronto to take advantage of him. Early in the game, both Reed Johnson and Vernon Wells stole bases against him not because they had beaten the throw but because both times, Rodriguez's throw to second was well off the mark. The strength of the throw was there but it seemed he wasn't expecting a steal attempt. A bit later in the game, on a pop out behind home plate, Pudge could have easily doubled the runner off of first but just watched as the runner trotted back safely.

For any other catcher, I'd be far less concerned but this relates a little to what I said on Sunday about lacking the abiity to forecast catcher's throwing percentage. Last year, in 123 games behind the plate, Rodriguez allowed a grand total of 25 stolen bases for the entire season or an average of about 1.4 every seven games. This will be worth watching to see if it was my imagination or perhaps even that he just expected his reputation and the baserunners involved would stop Toronto from running. Later in the game, there were no more attempts against him.

Something I want to preview here is that I'm playing fantasy baseball a bit differently this year than in past years. I've actually dropped out of several of the leagues I've played in for many years because I'm now more interested in trying new approaches and new leagues, without the benefit of having built up strong keepers. I still enjoy the fantasy game and am already committed to at least four or five leagues this year but my focus in the blog is going to be on a few experimental rosters that could easily get crushed in the regular season. I thought readers might enjoy hearing from me occasionally on how I might handle a challenging roster, dealing with injuries, using the schedule, etc...

So, I've selected three 5x5 mixed league Diamond Challenge teams (these were all picked this past Sunday morning), each of them with a different approach. While the bench/reserve players are picked from any criteria, the original starting lineup has one of three approaches. The first is what I call a "safe" approach. It's not to say that it's a team that has a safe chance of winning as it may be overly conservative. Not too different from the SSDS strategy I talked about back in December, the safe team was restricted to players who were projected to be worse in at least three of the five scoring categories compared to what they did in 2006.

The second team, which I nickname the "Dice" is a team that takes the opposite approach. Its starting roster is picked only from players who are projected to be better in at least three of the five scoring categories compared to what they did in 2006. In other words, the entire team is made up of players projected to have better seasons than they did in 2006. Much like I would expect the safe team to be too safe to contend, I would expect this team to be too filled with gambles to be one I could rely on.

Finally, the third team is called the "mix" because it allows equal distribution of risky and safe players. The team is not necessarily what you would expect me to draft when you use our online ranking sheets but only projections from the site were used to build the rosters. Basically, the mixed team is made up of a mix of the players from the other two rosters plus some other picks that fit in well based on the $30 million salary cap. While the roster is different than one I would pick if this weren't a complete experiment, my theory would be that this team should do the best of the three but only time will tell.

In a future blog entry, I'll share the full rosters with readers and I'll also mention how the teams are doing. I'll feel little disappointment if these experimental teams get creamed because none of the three rosters are ones that I would have picked based purely on the ranking sheets - you can use the ranking sheets yourself to have easily seen which players I prefer. Rather, I want to see if we can use our own forecasts in completely different ways beyond the straight order of the ranking sheets to put together teams that do well anyway. The three criteria used to pick the teams (safe, risky and mixed) were only used to build the initial starting rosters and are not to be a factor in considering reserves or replacements later.

I've always experimented with new strategies but I don't remember ever having so many of them all at one time so if any or all of these are getting crushed in the standings early, I may very well avoid mentioning them again once it's clear that they don't work. I'm hoping readers get some entertainment out of me occasionally mentioning what sort of transactions I'm making, both in my real leagues and in my experimental leagues. I'll have more to say about these teams in this space in the near future.

Sunday, April 01, 2007

Opening Day!

Before I get to today's entry, I want to mention to any readers who downloaded our Opening Day projection set before 1 PM EST today that for some reason, Brandon Morrow's projected pitching line and projected value was showing as a scrambled or unusual set of numbers. I don't think I've ever seen anything like that before at the site but it seemed to affect all formats, including the comma files and e-book. In any case, we've re-uploaded the projections to the site and that seemed to have corrected it. Nothing else was changed and this didn't affect any other player but if you have interest in Morrow or if he was showing up in an obviously peculiar place on your ranking sheets, you can re-download anything you like and you should get the correct projection showing now. I doubt he'll register on the fantasy radar even with the strange numbers that were showing up at the site this morning but it's worth noting, just in case.

I said previously that I plan to replace our old so-called Scheduled Advantage format with something that focuses more on key teams and key players in the upcoming week schedule. I'll try to at least mention the upcoming week most Sundays up until our final projection set on September 9 but the blog won't necessarily be confined to that in all cases if there's other news just as important.

Of course, the absence of the old Scheduled Advantage format doesn't mean that you should ignore the advice I gave in the original piece, entitled The Scheduled Advantage and if you play in a league that allows weekly transactions, I encourage you to check out that essay.

It is, admittedly, too early for me to be able to highlight some items because catcher throwing percentage, for example, is an area I've had little success at forecasting (which is one of several reasons why we still don't publish projected fielding data). Once even a week or two is in the books, it becomes quite clear which teams have trouble throwing out base-runners.

Just as difficult to project sometimes are park effects, which can vary from season to season. Some parks already have limited data because they've only been around for a short time so being able to add new data to the equation helps us more accurately estimate the true effect a park has on the game.

Step one of your fantasy league should be determining if your league uses the stats from tonight's season opener of the Mets and Cardinals. That's because if you have either Tom Glavine or Chris Carpenter on your team, you could miss out on their first start of the season if you're in one of those leagues that doesn't start counting stats until tomorrow.

If we include the Mets/Cardinals game as part of the upcoming week's schedule, that would give the Mets and Cardinals six games each on the schedule between today and next Sunday. If you don't count today's game, you'll only be getting a league-low five games out of the Mets and Cardinals this week.

Most of the teams play six games this week but the Angels, Oakland, Arizona and Washington are all scheduled for seven games. There are many pitchers likely to make two starts this week, far too many to count, and I expect most fantasy teams will be starting their aces anyway. You might want to watch out if you have Doug Davis on your team as his only start of the week will probably come in Colorado. Tim Wakefield's first start of the season will likely be in hitting-friendly Texas.

Next week, once we have a bit of data in the books, I'll begin highlighting some specific players who are strong and weak percentage plays for the subsequent week, based on the schedule. For now, if you're a big believer in using last year's stats to estimate team strengths (I'm not), then Kansas City has an even tougher schedule than usual as they face Boston and Detroit this week. The Giants, especially the already limited offense, would likely have a tough go of it too as they've got games against the Padres and Dodgers, two of the top four pitching staffs last year. Atlanta pitchers would be up against two of the top three offenses in the NL from last year (the Phillies and Mets) and Tampa Bay pitchers will be contending with the Yankees and Blue Jays lineups this week.

Next Sunday, we'll have much more to say about the schedule but I did want to squeeze a few comments in today. It's hard to believe that another season is upon us. Best of luck to all of our readers this year!