Deserved Run Average (DRA) is, as you know, the new pitcher-value metric here at Baseball Prospectus. DRA reflects our best estimate of the runs each pitcher “deserved” to allow in a given season. The number of deserved runs above or below average is used to calculate BP’s pitcher Wins Above Replacement Player (WARP).

By popular demand, we’ve now extracted the estimated effect, in runs, that various external factors have had on individual pitchers. You can get a direct link from the main site by clicking “DRA Run Values” from the Statistics pull-down menu, or by clicking here.

Overall feedback on DRA has been very positive, and we expect these run values will provide even more insight into the challenges various pitchers have faced. In other words, rather than simply knowing that DRA takes into account things like score differential and temperature, you can now see for yourself how those components have affected (or not affected) individual pitchers.

From the Run Values page, you’ll learn that Zack Greinke has benefited from terrific catcher framing, but also dealt with poor defense. You’ll see that his teammate, Clayton Kershaw, has lost about nine total runs from factors beyond his control, and that Dallas Keuchel has grabbed six free runs, largely from the parks in which he has pitched. You’ll also see a glossary on top of the entire table that briefly explains each column.

There are always caveats. Here are some.

First, this table does not contain *all* of the external factors that DRA considers, just the ones most likely to be of interest. The table is a bit crowded as it is, and we want to keep things readable. The “adjusted runs” column at the far right gives you the total effect of the factors in the other columns in the table. Are there other adjustments accounted for in the model? Yes. If one of them interests you particularly, feel free to ask below.

Second, don’t be surprised if some component run estimates diverge from other sites’ predictions. Remember that DRA calculates its own estimates for each factor, on a season-by-season basis, in light of the other considered factors. Thus, DRA doesn’t calculate generic park factors; rather, it calculates park factors that are adjusted for the temperature of the games played, the size of the strike zone there, and the quality of the teams that visited, among many other things. This doesn’t mean you can’t have your own opinion on these issues, or appreciate other perspectives, but it does mean that if DRA disagrees with somebody else about the effect of some component, it probably has a (uniquely) good reason for doing so.

Third, although we describe these figures as the “DRA Run Values,” they technically are the “value” mixed-model results from the first step of DRA. Those who enjoy the details may recall that we typically subject the value-model derivations to a second step, the MARS model, to give each season’s model the opportunity to consider basestealing prevention and other factors.

For this exercise, doing so is more trouble than it is worth, because the only factors DRA’s 2015 model selected as relevant were (1) pitcher value, (2) volume of batters faced, and (3) the starting-pitcher percentage. None of the baserunning stats were deemed relevant to assessing league-wide pitcher run prevention for 2015 (or 2014, for that matter). Thus, the MARS model in recent years largely just filters out the effects of plate appearances and converts the raw-value numbers to runs allowed per nine innings (RA/9). Those are both important, but neither is helpful when simply looking at total pitcher run value.

Lastly, for now we’ve posted run values for pitchers from the 1998 through 2015. We’ll push it back eventually to past seasons, and it’s not particularly difficult to do so, but we wanted to get you the most recent ones now.

As always, let us know what you think. *We* think you’ll have fun with these and get a much better sense of which areas constitute team strengths or weaknesses, and how it is that pitchers—even pitchers on the same team—can end up facing very different challenges.

#### Thank you for reading

This is a free article. If you enjoyed it, consider subscribing to Baseball Prospectus. Subscriptions support ongoing public baseball research and analysis in an increasingly proprietary environment.

Subscribe now
When I look at his player card, he is sitting at 6.1 WARP. This implies that a league-average pitcher with his number of innings is worth 3.6 wins (6.1 - 2.5 = 3.6). Is that accurate, or does the 10 runs = 1 win rule of thumb not apply here?

Using these two win values, a league-average starting pitcher throwing 172 innings is worth 3.5 wins (6.0 - 2.5 = 3.5). So my question is: is a league-average starting pitcher worth 3.5 WARP with a month to go in the season?

For now, WARP (taken from the sortable reports) is being displayed in place of RAA.

WARP is wins above replacement level; RAA is runs above average. So, it's a matter of a different reference point.

FRAA - The total runs lost from good or bad defense (created by averaging the total FRAA/PA of the defenders on the field for each play).

Is the FRAA that is being used generated specifically by the on field action during that PA or is it the general defensive performance for the 9 fielders over the course of the season scaled down to the specific PA?

DRA uses the defender's FRAA for the entire season divided by the number of events they've participate in. So, FRAA/PA.

As we learn more about the defender's play each year then the context of every event is adjusted accordingly.

I expected that meant that the DRA model is able to flesh out differences in the environment between the two pitchers such that Cole was either penalized more or helped less than Liriano. But looking at the breakdown of the DRA Run Values, Liriano has actually been penalized slightly more than Cole (-14.21 vs -13.52). So that seems to imply to me that they have different baselines from where the 'Adj Runs' is applied (and Liriano's baseline is higher than Cole's) in order for Liriano to have more value despite facing few batters and having worst adjustments.

I think it would be good to also publish the un-adjusted baseline runs number for each pitcher (which uses base-out run expectancy instead of raw runs, right?) to provide more context.

His DRA is 2.05, which is 2.92 runs per 9IP better than replacement. 2.92/9*172 = +56 runs better than average. Divide by 9.2, and you get 6.1 WARP.

But in no way is 2.05 only +23 runs better than average. 2.05 is 35 or 40 runs better than average. However, the hidden thing that no one is talking about is that the data is being regressed. This is huge. So, they are regressing someone with 700 or whatever PA at 30 or 40%, and so, bringing down the +35 down to +23.

The only reason I added the RAA column was as a means of sorting the pitchers by ultimate total value; essentially it was a proxy for PWARP ranking. But all it is doing is confusing people, so I expect we'll find some other means of sorting the table very shortly. I'll post another comment once we have done that. As I noted, the remainder of the columns are independent of the current "RAA" column and you can use them without regard to it.

Thanks to everybody for pointing this out. As usual, our readers are great.

The glossary at the top of the DRA Runs page has been updated accordingly.