RR Community Project: Calculating Defense
I embarked upon an intriguing idea but several minutes ago. Because many defensive statistics are highly debated among the sabermetric and scouting communities alike, and many statistics have been proven to be some degree of inaccurate or faulty, I would like to begin a season-long community project where we estimate - "scientifically" - exactly how many runs Royals defenders cost or help the team for this year. I would like to see how these statistics compare to the various metrics out there (UZR, +/- system, and more). This system would be a rough estimate, basically.
It might require some effort and debating on our parts - but it's an interesting idea, nonetheless. Does someone who has watched every game, or at least paid close attention to them in some form, want to volunteer to begin our contest, calculating +/- totals for the first six games? In other words, for example, Bloomquist's gaffe yesterday cost the Royals....how many runs, total? Who has helped save a run - in estimation - on defense?
Food for thought. Unfortunately, I won't be able to watch every inning of every Royals game this year, so let's make this a 'community' effort.
2 recs |
25 comments
Comments
I'l post what I recall...
Game 5 – Bloomquist 1 run RF
Game 4 – Aviles 2 runs @ SS (the play he threw behind Swisher @ 2B and Swisher subsequently scored w/ 2 outs, and the laser hit to him in the 1st inning that he tried to play off his hip)
Game 4 – Jacobs 1 run the laser he ole’d
Game 6 – This is debateable…I think the runs score w/ or w/o Jacob’s error in the 7th, but it is possible that he gets an out there, and Aviles plays in w/ 1 out and either cuts down (I think it was Matsui) the runner on 3rd, or holds him there alltogether…either way, I guess the play should have been made by Jacobs, whether or not it cost a run is debateable…
As for runs saved…
DeJesus’s diving catch in Left on opening day – did it save a run or not? I can’t recall…
Coco’s long run & catch in game 2 (or was that game 3) in deep right center saved I think 2 runs
BOOM! ROASTED!
by GoBabies!! on Apr 12, 2009 7:18 PM EDT reply actions 0 recs
Bloomy was actually more than 1 run...
It was 2 runs on the play in the 1st (which was a tough play, but an experienced, mobile OF’er gets there) and I believe 2 more runs on the ‘near miss’ dive. By near miss of course I mean 3 feet short.
BOOM! ROASTED!
by GoBabies!! on Apr 12, 2009 7:21 PM EDT up reply actions 0 recs
Yeah,
and the runner on 3rd was going to score anyway. But Swisher getting to 3rd on that one should go against Bloomy. Right?
If you were thinking, you wouldn't have thought that.
by Warden11 on Apr 12, 2009 10:12 PM EDT up reply actions 0 recs
Those on this board argue that Bloomquist saved runs with those erros
Guillen would have done much much worse according to NYRoyals
by GobbleforCyoung on Apr 13, 2009 10:21 AM EDT up reply actions 0 recs
I'd be surprised if you got that argument.
Most likely it would be that Guillen wasn’t with 15 feet of the ball as it hit, so the run from 3rd scores easily and Guillen holds Swisher to a single.
If you were thinking, you wouldn't have thought that.
by Warden11 on Apr 13, 2009 12:37 PM EDT up reply actions 1 recs
Either way
they both are under par.
Bloomy definitely cost 3, as the runner on 3rd would have scored regardless because he either tags when he catches it on the dive, or he scores when he misses. Bloomy can’t make the throw home.
I think Jacobs should have made at least 1 of the plays hit hard at him. So maybe -.5 for each?
Aviles, should get dinged a run too.
by AxDxMx on Apr 13, 2009 12:53 PM EDT up reply actions 0 recs
I like the idea of this (obviously) but I think we need some more ground rules...
i.e. I’m not counting Alex Gordon’s diving play in game 4 because it opened up the inning…Now we all know that runner on 1st and nobody out is a markedly different situation than none on & 1 out, but since it didn’t DIRECTLY take away a run…..should it count, or count in a seperate ‘baserunner saved’ category?
BOOM! ROASTED!
by GoBabies!! on Apr 12, 2009 7:25 PM EDT reply actions 0 recs
We could use for each play the expected run between the two plays
Such as in Gordon’s case, it would have been .90 expected runs in the batter reached first or .33 since he made the out. Gordon saved on average .57 runs on the play. This could be used with each error.
by Jeff Zimmerman (TucsonRoyal) on Apr 12, 2009 8:49 PM EDT up reply actions 0 recs
That is the way it should be done.
That takes the majority of the objectivity out of it, making it more scientific and believable, I guess.
by rockchalk on Apr 12, 2009 11:46 PM EDT up reply actions 0 recs
Obviously, this would be extremely subjective
We just need to use our sensibilities collectively, I think, to get the most “accurate” result. I think we need to take into consideration range and arm, as well. Not necessarily just diving for plays, assists – but making reasonably difficult plays look easy. I hope that makes sense.
by Royals Nation on Apr 12, 2009 9:00 PM EDT reply actions 0 recs
there are better ways to do this
scenario: jacobs is playing first. bases are loaded with 2 outs. batter hits a scorcher down the line, jacobs makes a brilliant diving stab and ends the inning. had jacobs not made the catch, 3 runs would have scored and the batter would have wound up at 2nd, so the result of the catch is maybe about 3.5 runs better than the double would have been.
do we credit jacobs with 3.5 runs saved? no, we’re comparing jacobs to the average first baseman, and although we know jacobs made the play, we don’t know how likely it would have been that an average first baseman would have made that play. If an average first baseman would have made it 50% of the time, we should only credit Jacobs with 1.75 runs saved. Trouble is, we’ll never know.
by kcdc1 on Apr 12, 2009 10:33 PM EDT reply actions 0 recs
d'oh
I just hit “post” right after you and made the same point, but not as clearly.
Bringing you more-or-less replacement level analysis and commentary to Driveline Mechanics and elsewhere since sometime in 2008.
by devil_fingers on Apr 12, 2009 10:34 PM EDT up reply actions 0 recs
better way:
i believe someone (maybe dewan or tango) collected data for the team each batted ball is in the air. there is also data for where each batted ball lands. if you ignore wind, spin, and assume average air resistance in all cases, you can calculate rough ball flight trajectories. they won’t be great because they’ll neglect most of the forces applied to the ball once it leaves the bat, but it should give you an idea of where each ball travels and how fast it gets there. using this rough where/when data, you could look at each player and determine how effective they are at producing outs for balls hit x distance away with t seconds to get there. you could group batted balls by velocity, and chart a player’s range for balls at each velocity grouping. you could compare these charts to those of other players.
by kcdc1 on Apr 12, 2009 11:19 PM EDT up reply actions 0 recs
ONe additional idea
would be to participate in Tango’s Fan Scouting Report if/when he gets it going this season. It sounds like this gets more at what you want, and doesn’t mess with trying to convert to runs, which, for reasons I’ll allude to below, will be extremely difficult by just watching.
I’m not sure how this is going to work — it sounds like you’re grading the defense by how many runs it actually costs in the game, which makes some sense intuitively, except that doesn’t really necessarily judge how good a defender is, just how “clutch” he is. If Mike Jacobs fails to field 5 grounders that an average 1B would get to gets on first, but each time the pitcher strikes out everyone else and it costs no runs, but (for example) Billy Butler has to make plays on 5 similar grounders and makes for of them, but the one guy who gets to first gets driven on a jack, does that mean Billy Butler is one run “worse” than Mike Jacobs over those 5 grounders each had to deal with?
Maybe I’m misunderstanding what you’re doing. Defense metrics may be far from perfect (although they seem to have a better scouting eye than the geniuses who want Jacobs to play first everyday), but if this is how you are doing it… well, I’d advise reading a bit more. This is not how they work, nor should they. Doing it by how many runs (the observers think) each play actually cost on the scoreboard is to defensive metrics is like judging a players offense by his RBI. Which is about as genius as judging a player solely by what he did in 2005.
If you just judge by the plays guys “should” or “shouldn’t” be able to make, you need to have some sense of average — otherwise, errors will be total negatives, etc. Every player makes errors, fails to make plays, etc. at some point. The point of a plus/minus runs system is to compare to average.
Having said that, the idea is intriguing if you get past that. Some suggestions
The BIg One: Deciding what you are going to do and not do.1. Don’t deal with the “Run value” of events at all — just deal with the plays made/not made. I’d deal with range, mainly, as that’s the greater bulk of defense (unless you think that all the best sabermetricians are totally wrong about that, and that, e.g., the 3-1 is worth 2 runs a game or something).
2. Range is the toughest thing to judge, anyway, and the one the metrics were designed for. I’m not sure quantifying it will be that easy — one has to have a sense of what “average” is, and if you’re just watching the same guys every day (as Royals fans, that makes sense), well… that’s how people come to believe Derek Jeter, Ross Gload, etc. are good defenders. A “subjective” baseline is a tough thing to do…. Maybe instead of dealing with runs, just give each player a 1-10 or 1-100 rating or something,. but that gets more to the subjective nature of a scouting report, which I guess you don’t want to do…
3. Contrary to some, OF “arm” ratings (not as a subjective judge of strength of arm, but rather whether an OF holds/throws out baserunners) is relatively easy to calculate, but the “subjective” side of it, at least quantifying it, will be harder by just watching, since it’s hard to tell when the guy is holding the runner or not.
4. Double plays are easy enough, I guess. Again, you have to have a baseline. If you don’ t have a sense of “average” rate, almost everyone’s going to end up negative.
5. Errors are also relatively small part of defense, believe it or not, relative to range.
ONE VERY IMPORTANT POINT: No matter how you decide to work it out, the “scouts” engaged in this must not look at other defensive statistics (and who would, right? They’re all totally flawed anyway!) or read scouts opinions of these players during the season. I’m serious. You don’t want to be biased by metrics or other scouts opinions. Tango says somewhere he wouldn’t want his scouts looking at defensive numbers, since the scouts job is to see other things, and heck, one of the premises of this idea, as I understand it, is that defenisive metrics are too flawed and the fans need to correct them — so don’t be contaminated.
All kidding aside, this is a cool idea. These are just some suggestions off the top of my head. I’ll be interested to see where it leads.
Bringing you more-or-less replacement level analysis and commentary to Driveline Mechanics and elsewhere since sometime in 2008.
by devil_fingers on Apr 12, 2009 10:33 PM EDT reply actions 0 recs
I agree that that would be the best, BUT
way tooooo difficult to follow. It needs to be simple.
1. Expect outcome (1 out, no one on)
2. Actual outcome (0 outs, one on)
3. What was the cause (no range, arm, error). — (range)
4. What is cost us expected (.57 runs)
We could set it up Google Docs and people could add as they like.
by Jeff Zimmerman (TucsonRoyal) on Apr 12, 2009 11:19 PM EDT up reply actions 0 recs
of course, that's better
I wasn’t offering a method, just making suggestions.
I really do think that people doing this should be avoiding looking at defensive stats (“faulty!”) or scouting reports (probably biased against Royals like David Cameron! just kidding, but this is the whole point of doing a separate exercise).
Not sure why individuals need to be calculating the run value of each individual play — I’m pretty comfortable saying that is something the defensive metrics have down.
I will say that if people aren’t doing a scouting “reports,” but an actual “what this cost us” thing, and they aren’t comparing to average, then this is likely to be pretty worthless.
Bringing you more-or-less replacement level analysis and commentary to Driveline Mechanics and elsewhere since sometime in 2008.
by devil_fingers on Apr 12, 2009 11:32 PM EDT up reply actions 0 recs
let me rephrase that last sentece
what is this supposed to be?
1. A scouting report on player defensive tools? That’s probably what would make he most immediate sense. But then give up the notion of measuring plus/minus plays/runs.
2. A “defensive statistic?” Fine —but this won’t really show anything unless there’s some sort of baseline, whether it’s average, runs above Ross Gload (as if anyone could be better than Gload, really, he’s a Gold Glove-lever defender! Otherwise, a GM would have to be a dumbass to extend him!), or whatever.
Bringing you more-or-less replacement level analysis and commentary to Driveline Mechanics and elsewhere since sometime in 2008.
by devil_fingers on Apr 12, 2009 11:35 PM EDT up reply actions 0 recs
We could base on the number of curse words we say on the plays
I think it does need to be based on runs since that is what defensive are based on.
At the end of the season, we could see that Jacobs cost us X number of runs and compare it to the final numbers.
The survey would be great, but with ~50% turnover on all positions, we should set up a survey about 1/2 the way through the season. In the meantime, keep track of how much everyone messes up. We can argue the methods, but should keep track of the mistakes so we don’t forget them.
by Jeff Zimmerman (TucsonRoyal) on Apr 12, 2009 11:51 PM EDT up reply actions 0 recs
I agree on numbers
I’m just saying have the “scouts” mark down/keep track of what they thought the problem was, and keep the run calculation separate.
But if they want to individually decide on the run value, that’s cool. It’s just a suggestion.
Bringing you more-or-less replacement level analysis and commentary to Driveline Mechanics and elsewhere since sometime in 2008.
by devil_fingers on Apr 13, 2009 12:15 AM EDT up reply actions 0 recs
what it would be
is something similar to a great play/terrible play counter with situational leverage mixed in. i think dewan actually does something similar already without the leverage.
by kcdc1 on Apr 13, 2009 12:51 AM EDT up reply actions 0 recs
I'd have to check it out
I understand the appeal of leverage, but I still think it only applies to relievers, because they are the only players who are on the roster and earn their leverage playing time (in any significant sense) according to their skill. Defenders are always out there.
There’s a good chance I’m misunderstanding all this, I’m pretty dumb.
Bringing you more-or-less replacement level analysis and commentary to Driveline Mechanics and elsewhere since sometime in 2008.
by devil_fingers on Apr 13, 2009 1:15 PM EDT up reply actions 0 recs
no, i'm not saying the leverage component would be a plus
i’m just saying it would be in there—according the proposed system, a ground ball through the legs for a single wouldn’t count against the defender nearly as much with no one on and 2 outs as the same play with the bases loaded and two outs. like you said, the leverage component wouldn’t have anything to do with the quality of play though. unless you think clutchness is a big component in defense i guess.
by kcdc1 on Apr 14, 2009 2:02 AM EDT up reply actions 0 recs
I think we're in agreement
Bringing you more-or-less replacement level analysis and commentary to Driveline Mechanics and elsewhere since sometime in 2008.
by devil_fingers on Apr 14, 2009 1:29 PM EDT up reply actions 0 recs

by 












