Build a Better WAR Metric, Checkpoint

In trying to summarize the responses to the three questions, so far, what we have in terms of preference is:
– the event, regardless of the context
– the event, within the context of the whole game state (inning, score, base, out)
– the event, within the context of the base-out state
– and far down the list, the event as it ultimately affects the inning

What the responders therefore are gravitating toward is a purely
content-neutral metric. But, to the extent that we do want to measure the context-specific impact, that should be kept separate, and perhaps not even tied to the player at all. Just a general “timing” bucket.

If we take the case of the triple in the previous thread, in either case, Hamilton and Dyson will get +1 run, because that’s the context-neutral value of the triple, according to Linear Weights.

We immediately add a -0.1 runs because a triple with the bases empty and 0 outs is worth +0.9 runs. So, they don’t want to penalize either guy for getting the triple when they did, and so, to make things add up, we need “-0.1” runs for timing.

Then the three outs, they each get -0.25 runs, as is the standard weight.

So far, we have this:
+1.0 Hamilton
-0.1 timing: limited impact triple
-0.25 batter1
-0.25 batter2
-0.25 batter3

That’s a total of +0.15 runs. But since the inning started at +0.5 runs of expectancy, and we get 0 runs scored, the total has to be -0.5 runs. So, we add another item:
-0.65 bad timing: leaving runner on base

As for the other scenario:
+1.0 Dyson
-0.1 timing: limited impact triple
-0.25 batter1
-0.25 batter2
-0.25 batter3

But, since we actually scored a run, that should come in at +0.5 runs. We need another:
+0.35 good timing: scoring the runner

For a minority, a vocal minority, those “timing” impact runs should be given to the players involved. Looking at the Hamilton one, whereas a generic out is worth -0.25 runs, an out with a runner on third is more costly. So, that -0.65 runs has to be distributed to the three out-makers, for those readers part of the vocal minority. For the readers in the majority, those runs are an after-thought. Maybe they should be considered, so the thing adds up. But, it shouldn’t fall on the shoulders of the players involved. Just a general team bucket to capture the various plays affected by timing.

So, that’s how you build your WAR:

For each player, figure his context-neutral impact as one value, and his “timing” as another value.

Then, the reader can choose whether to include the timing value or not.

Now, on to the pitchers and fielders!


Build a Better WAR Metric, Part 3

Before we talk about baseball, let’s talk about the other three major sports. You’re on your own 20 yard line, you march down field on a series of plays, but ultimately, you punt. Or, you march down field and move far enough for a tough field goal that gets made. All those running and passing plays aren’t considered any differently based on the results. The RB got 25 yards on 4 running plays, and no one matches it up to the end result.

In hockey and basketball, a great pass that doesn’t ultimately lead to a goal or basket goes away like a fart in the wind. No one tracks it, and if they do, it’s not considered anything close to the impact of an assist that led to a score.

Why the difference? I think it’s because of the stop-start nature of football, that the “sequence” ends after each play, and the whole drive is 2-5 football minutes or 5-15 human minutes. In hockey and basketball, turnovers happen often enough and each drive lasts 10-30 seconds in sport or human minutes. I think that’s the reason.

So, let’s talk about the leadoff triple. Billy Hamilton gets on third base, and the next three batters strike out. He’s stranded there, no runs score. A fart in the wind triple? Or something much more tangible? Jarrod Dyson gets on third, the next batter hits a medium fly ball out, far enough to let Dyson score. The next two batters strike out. One run scores. That triple is obviously tangible.

How do you see these two triples?


Build a Better WAR Metric, Part 2

Ok, you guys have spoken, and you don’t want a bases loaded walk to count the same as a solo HR. That even though the base-out state before the event and after the event remain unchanged, and that the number of runs now in the bank are the same, the WAY it happened matters to most of you. Therefore, we are NOT trying to preserve the runs, we are not trying to make sure the runs add up. You have been clear on that.

Now, let’s talk about “preservation of wins”. It’s a 0-0 game, the bottom of the 9th, the bases are loaded with two outs. Historically, at this point in the game, the batting team would end up winning 68% of the time. It’s a high stakes situation, a Leverage Index of 6.4. And the batter walks. The batting team wins, game is over. Ooops, I meant the batter hit a single. No, wait, it was a Grand Slam. No, wait it should have been a Grand Slam, but Robin Ventura decided to abandon the bases after he reached first base. Regardless, the game is over, and the batting team won as soon as the batter touched first base.

Your question:


eBay’s Five Most Marvelous and Currently Available Ballcaps

It’s become a practice of the present author in recent years to begin in February a painstaking search for the new ballcap that will express his entire being. It’s also become a practice in recent years to parlay that search into web content so that the author might “remain” “employed.”

Two years ago, this pursuit yielded a Winston-Salem Spirits cap from 1994 with a weird red sun and melancholy eagle on it. Last year, I had the fortune of procuring a handsome Diablos Rojos cap from the actual team store at Parque Fray Nano in Mexico City. In each case, I have documented the relevant search for the benefit of posterity — even if posterity has failed to show any real interest in my work.

Last week, the author began this year’s edition of the search. What follows is the second installment of the newest volume.

To wit:

A Town

Atlanta Braves A-Town Corduroy 5-Panel Velcro Snapback (Link)
Style: Snapback
Time Left: 23 days, 5 hours
Cost: US $17.99 (Buy It Now)

While it’s difficult to conceive of a scenario in which one would voluntarily acknowledge any sort of affiliation with the city of Atlanta, this cap is almost certainly the best means by which to do it. The low crown preserves one from the awkward fit offered by other new caps. As for the corduroy, it’s the most expedient way to announce publicly that, regardless of what these so-called “credit reports” suggest, one has plans to acquire a sweet conversion van in the near future.

Read the rest of this entry »


Building a Better WAR Metric

Wins Above Replacement (WAR) has as its genesis Bill James, even if Bill might not necessarily take the credit (or blame based on some readers) for it. But make no mistake, Bill provided the plumbing for it. For those interested, you can read Brandon Heipp’s account on that backstory.

When you put all the plumbing together, you can create a framework. And that’s what WAR is, a framework to provide an estimate. Wins Above Replacement is an estimate of… something. What that something is is different for every person. While the currency is wins, it’s not clear what those wins represent. There are reasonable choices you can make along the way. And for every fork in the road you take, you may diverge yourself from the next guy. This is why WAR can never be one thing.

As a framework, WAR leaves little room for discussion. Whether it’s what you see at Baseball Reference or at FanGraphs or openWAR or (to some extent) at Baseball Prospectus, they have as their framework the WAR that was championed on my old blog, which culminated with this article. But a framework is not the same as an implementation. 95% of the cars on the road all follow the same core design. That’s the framework. But a Chevy is different from a Lexus. Those are implementations. And there are as many implementations of WAR as there are baseball fans. Whereas Baseball Reference and FanGraphs and the others provide a consistent, systematic implementation, most fans have their own personal mish-mash of arbitrary, biased, and capricious combination of stats, which can change as their mood fits.

This series of articles, of which there may be a dozen(*) is an effort to try to come up with a WAR metric that will satisfy the Straight Arrow readers.

(*) I have no idea. This is the first one I’ve written.

***

I’ll ask you a series of questions, starting now. The openWAR guys talk about “preservation of runs”. That is a good starting point, and a great way to describe the concept. So, the question centers around whether we want to make sure that everything adds up at the play level. If you get a bases-loaded walk, do we want to make sure that exactly one run is accounted for or not?

If you care about “talent”, you just want to account for around +.30 runs for offense (and -.30 runs for defense), because you don’t want to be concerned with the specific base-out state. (We’ll talk about “preservation of wins” in a later question.) Similarly, is a bases-empty walk and bases-empty single the same thing or not? And if you want to preserve runs, are you ready to accept a bases-loaded walk and a solo HR as being the exact same thing?

So, have a discussion, and then answer this poll question:

There are plenty of other discussion points that go into building an implementation of WAR, and we’ll get to those in the future. For this post, I’m interested to hear what you guys think about this issue specifically.


Job Posting: Miami Marlins Baseball Operations Data Architect

Position: Miami Marlins Baseball Operations Data Architect

Location: Miami

Description:

The Data Architect will assist in the modeling, housing, and integration of baseball data from a wide variety of sources. This position will be responsible for creating enterprise database systems and setting standards for operations, programming, security, and backup. It will involve construction of large relational databases, integrating new systems with existing applications, and refining system performance and functionality within the Microsoft SQL Server platform to enhance the information retrieval and analysis capabilities of the Baseball Operations department.

Responsibilities:

  • Perform data modeling and requirements gathering for Microsoft SQL Server database implementation.
  • Develop high-performing, scalable solutions including schema design, storage engines, indexing strategies, SQL tuning, ETL processes and Stored Procedures to integrate disparate data sources into a unified system.
  • Understand the format, definitions, limitations, and content of external and internal data feeds.
  • Reconcile differences across data sources and consolidate into a single master repository to ensure “single version of the truth” consistency across applications and reports.
  • Develop processes ensuring data standards, security, stewardship, lineage, and metadata management.
  • Develop and document database architectures, schemas, physical structure, functional capability, security, backup, and recovery specifications.
  • Support data and reporting requirements for a variety of applications, analysts, and end-users in the Baseball Operations department.
  • Provide technical and strategic advice for the creation and implementation of new data standards, databases, products, and vendors.

Qualifications:

  • Some familiarity with baseball and sabermetrics preferred.
  • Ability to communicate technical concepts to individuals with diverse and non-technical baseball background.
  • Knowledgeable about software development best practices and long-term maintainability of code.
  • Ability to effectively diagnose, isolate, and resolve complex problems pertaining to data infrastructure and integrity.
  • Strong work ethic, attention to detail, and ability to self-direct.
  • Ability to work evenings, weekends, and holidays during the season.
  • Bachelor’s degree in computer science, information technology, computer engineering, or equivalent professional experience required. Master’s degree a plus.
  • At least 5 years of experience required, with preferable experience with architecture and design responsibilities in a large and challenging database environment.
  • Extensive knowledge of Microsoft SQL Server (2005, 2008 with migration to 2012), Transact-SQL and third-party transformation middleware such as Scribe required.
  • Demonstrated data modeling ability required.
  • Experience designing, implementing, and managing large data warehouses and cubes in Microsoft SQL Server Analysis Services required.
  • Advanced knowledge in query development, including SQL, MDX, and stored procedures required.
  • Experience using XML and JSON formatted data strongly preferred.
  • Experience supporting or using statistical and/or data mining applications strongly preferred.
  • Business intelligence, data warehousing, or OLAP experience preferred.
  • Experience in a .NET programming language preferred.
  • Experience with a scripting language (Perl, Python, Ruby, etc.) a plus.
  • Knowledge of other database platforms (PostgreSQL, Oracle) a plus.
  • Familiarity with any application development and/or web technologies a plus.

Compensation:
This position is compensated.

To Apply:
Interested applicants can email their materials to marlinsbaseballjobs@gmail.com.


Reacquaint Yourself Now with LSU Righty Alex Lange’s Curve

Last year in these pages, the author — in an effort to justify his employment — published a pair of posts inviting the public to consider the virtues of LSU freshman Alex Lange’s curveball.

Lange is now an LSU sophomore and has recently recorded his first start of the season for Les Acadiens, during which he posted a 9:3 strikeout-to-walk ratio against 24 batters over 6.2 innings versus the University of Cincinnati (box). What else Lange did was to exhibit the breaking ball which scouts are calling “a good breaking ball” and “fine, yeah, a pretty strong breaking ball, now please stop bothering me, I’m with my kids.”

In any case, the following Betamax footage depicts examples of that same pitch from Lange’s season debut.

Like this footage, in which Lange records his first out of the season by means also of his first curveball of the season, against a Cincinnati batter (right fielder Vince Augustine) who appears to exhibit not no resignation while also swinging his bat:

Read the rest of this entry »


R.I.P. Tony Phillips

Tony Phillips passed away today, at the age of 56. Unlike some of the reporters sharing stories from their days covering him on Twitter — this one from Jeff Passan is great — I never had any interaction with him, and can’t share any personal stories in his memory. But what I can share is my memory of just how good Tony Phillips was at baseball.

Phillips really came into his own in 1990, when I was nine years old and getting seriously into baseball. And for the next decade, I must have watched Tony Phillips be the cause of my team losing on at least a half dozen occasions. He was never the other team’s best player, at least not according to the announcers, but he was one of those remarkably good role players that the good teams always seemed to have. And, with the benefit of some better ways of evaluating players these days, we can look back and say that Phillips just may have been his team’s best player on a number of occasions.

His peak ran about seven years, from 1990-1996. Here’s the position player leaderboard during that stretch.

Screen Shot 2016-02-19 at 2.04.14 PM

That’s a who’s-who of the best players of the 1990s, and Phillips is square in the middle of that class. For that seven year period, he was essentially the equal of Craig Biggio. As J.J. Cooper put it:

The comparison is apt, and if Phillips had played a couple of decades later, he’d be celebrated as one of the game’s most valuable players. While he wasn’t flashy, he didn’t hit a ton of home runs, and his positional versatility meant he was never considered an elite defender, his all-around game made Phillips a tremendous asset for his teams.

Rest in peace, Mr. Phillips.


eBay’s Five Most Marvelous and Currently Available Ballcaps

It’s become a practice of the present author in recent years to begin in February a painstaking search for the new ballcap that will express his entire being. It’s also become a practice in recent years to parlay that search into web content so that the author might “remain” “employed.”

Two years ago, this pursuit yielded a Winston-Salem Spirits cap from 1994 with a weird red sun and melancholy eagle on it. Last year, I had the fortune of procuring a handsome Diablos Rojos cap from the actual team store at Parque Fray Nano in Mexico City. In each case, I have documented the relevant search for the benefit of posterity — even if posterity has failed to show any real interest in my work.

In any case, what follows marks the beginning of this year’s search.

To wit:

Absolut

Absolut Vintage Strapback Cap (Link)
Style: Strapback
Time Left: 8 days, 2 hours
Cost: US $9.00 (Buy It Now)

Have you ever wanted to give the impression that you were a devotee of 80s sitcom Moonlighting without actually having to watch all 68 episodes of it? Have you ever wondered what a baseball uniform designed by Patrick Nagel might look like? This cap goes some way to addressing both of those concerns.

Read the rest of this entry »


Player Caps Now on the Player Pages

Short updates about over 1100 players are now on the player pages! As part of our new approach to membership, the player caps are free. Each player cap attempts to put the player in context by talking about recent career events and their outlook for the coming season — mostly with a fantasy slant. No matter your interest, however, you’ll find some nuggets in there, including Blake Murphy on Adam Rosales, Matt Klaassen on Alcides Escobar, Craig Edwards on Logan Schafer, and David Wiers on Chase Utley.

Thanks very much to our writers, listed below! They each worked hard to bring you insight.

The fantasy research pieces that used to be part of FG+ are now running over at The Hardball Times, with pieces about the following topics. Also free!

  • Mon., Feb. 15: Rylan Edwards, “Finding the Chacon Zone
  • Tue. Feb. 16: Mike Podhorzer, “xLOB%: Projecting a Pitcher’s Left On Base Percentage
  • Wed., Feb. 17: Alex Chamberlain, “On the Sustainability of Hitters’ Plate Discipline Gains”
  • Thu., Feb. 18: Tanner Bell, “Properly Valuing Hitters with Injury Risk”
  • Fri., Feb. 19: Jeff Zimmerman, “Comparing Pitcher First-Half and Second-Half Performances”
  • Thanks very much for your readership. I hope you enjoy these as you prepare for the upcoming season.

    Our writers:
    Adam McFadden
    Alex Chamberlain
    August Fagerstrom
    Ben Duronio
    Ben Pasinkoff
    Blake Murphy
    Brad Johnson
    Bradley Woodrum
    Brandon Warne
    Brett Talley
    Carson Cistulli
    Chad Young
    Chris Mitchell
    Colin Zarzycki
    Craig Edwards
    Darren Scheinbein
    David Temple
    David Wiers
    Dustin Nosler
    Dylan Higgins
    Eno Sarris
    Jeff Zimmerman
    Karl de Vries
    Matt Klaassen
    Michael Barr
    Mike Podhorzer
    Owen Watson
    Paul Sporer
    Paul Swydan
    Scott Spratt
    Scott Strandberg
    Zach Sanders