This is part 3 of an 8 part series.Editor's note...There was a prior error in this that was discovered through conversation on slack. Basically RC/27 is a “lineup stat” so ZR needed to be multiplied by 9 as well. So here we are at new numbers and a new analysis!
Why not one more today?
In case you haven’t read Part 1 (Catcher’s Edition) or Part 2(First Baseman Edition) there is a recap of what exactly I am doing and why at the bottom of this post.
This will be the last one released today, so we are going to move right around the diamond and take a look at the second baseman. All second basemen who are qualified batters, meaning 3.1 at-bats per team game are going to be included in this analysis. If you are a team who has a platoon, you are likely out of luck and will have to do the math yourself as you won’t find your players on this list. If there is a 2B who is playing an easier position and the game recognizes him as a second baseman, that will also skew this a bit but you can still use RC/27 to do your own math.
Anyhow…Second baseman. An interesting trend here as maybe 2nd base isn’t a very important position, as 7 of the 8 teams that are currently in the playoff hunt find themselves with a below-average second baseman this season.
Averages for the second baseman:
The Best: Pepe Espinosa (Edmonton).
The first time we did this, we had Rocky Wattson as the best second baseman. Well after taking Pepe Espinosa’s ZR into account, that quickly bumped Espinosa up the charts from being middle of the pack up to the very top! Espinosa would have an 81.9 lineup ZR giving him 76 Net Runs Created when you factor in his -5.85 over the course of the season.
Rocky Wattson, for what it is worth still comes screaming into second place with just 6 runs less than Wattson.
Players from Atlantic City, Twin Cities, and Rockville round out the top 5, just as they did in the previous calculations.
The Worst: Reece Wareham
Sean Macquire(YS9) & Lloyd Braun(Boise) both wind up saved using these calculations, as Reece Wareham and his -91.8 lineup ZR take over the bottom spot giving him a negative 97 runs created against the average second baseman, nearly 30 less than the next worst guy.
Anyhow, the link for the spreadsheet to see the report is below, feel free to take a look and I will be adding new positions each day this week as we attempt to analyze offense vs defense from this point of view. I hope everyone enjoys this, and if not, then tough shit I guess because I am going to be doing it for the next 7 days.
https://docs.google.com/spreadsheets/d/ ... p=sharing
For those wondering, I used 7 games for the average amount of games it takes a good hitter to get 27 outs. 162 divided by7 games is roughly 23 games per season. I took the runs created per 27 outs and multiplied by 23 to get the average season runs created.
When looking at offensive stats for players, the greenest of fans look at batting average, home runs, and runs batted in. These stats are typically used because that is what people are used to seeing when watching ESPN or looking at the box scores in the newspaper. However, as we know these are far from even being important and most are reliant on other members of your team to accomplish. For instance, you can’t have a ton of RBI if your teammates aren’t getting on base, likewise, you can’t score 100 runs if your teammates can’t hit you around.
In comes the stats of on-base percentage, slugging percentage, and for pitchers FIP. I am going to dive a bit further after doing some reading on one stat that caught my eye and specifically made me question a few things.
That stat is Runs Created. My first thought was simply what the hell is that? Ron did a good job of explaining it on slack the other day to the group who didn’t know (which was basically just me), as there were some debates over the “who is more valuable” type guys which I appreciate as much as anyone.
So just what is a run created?
Basically it looks at the following linear weights (relative to outs)
It takes all of these and basically accounts for how many runs did that player truly produce during the season with no other factors attributing to it such as teammates' performance. It is a pretty accurate measure, as if you take your entire team’s RC, it typically hits the number within 5% of your runs scored during the season.
So now here is where it gets a bit interesting and what had me thinking.
Obviously a great defensive glove in the league is a coveted thing for many people, but at what point does the defensive player actually hurt that team based on his batting ability? The same goes for offense, how well does an offensive bat have to be in order to deal with poor defense? If a player has as a -10 ZR but is generating 45 more runs that season than the average at that position, then that is a player who obviously is very valuable despite his glove.
This feature is going to take a look day by day at each position showcasing who truly has been the top player at each position, all the way down to the worst player for that position. In order to qualify as a position player, you must be a qualified batter, meaning 3.1 at-bats per game. The only exception to this is going to be the catcher position because of obvious reasons. For the catcher position, I will grab anybody who has at least 200 at-bats this season.
For those who have played multiple positions, it is going to be the cumulative ZR, and they will be grouped by their natural position (whatever they are set at in the game).
