Data
“I’ve been developing my own handicapping software as a hobby since 2007, but the biggest problem I’ve faced is having enough data to properly calibrate and test the system,” said Ligett. “The data provided as part of the contest is just what I needed to move the idea forward.”
Lock up data, squelch innovation. Give developers data, spur innovation.
Dublin, dropped from my PDI top 10 after the Arkansas Derby, returns this week at #1, a move driven by Eskendereya’s withdrawal from the race and a few hours with the past performances. Last week, when the field was looking set, I was intent on figuring out who would run behind Eskendereya — I know, I should feel more embarrassed to admit that. Every wise guy out there has been complaining about how with the loss of Esky, all the odds on the horses they were really planning to play have plunged. Whatever. The colt had the two best Beyer speed figures of this bunch, a perfect prep season, a fitting pedigree. He’s also physically impressive — watching at Aqueduct on Wood Day, I was struck by how much more mature and robust he looked than the other starters (check out his chest and shoulders in this photo by Sarah K. Andrew). Watching the Wood replay, what grabbed my attention was how much he reminded me of Big Brown (and I wasn’t even a Big Brown fan), exhibiting a similar control and ease as he took the lead and drew away. I was going to bet the chalk on Saturday, and happily.
As for Dublin, I still have some concerns he won’t relish the Derby distance, but then, ten furlongs seem questionable for several of this year’s expected starters, who, for the most part, haven’t made much of an impression on me. His track work this weekend could also suggest problems: After attempting to bolt during a Saturday gallop, Dublin drifted out around the final turn in his Sunday work. What’s more, DRF clocker Mike Welsch noted, “the failure to gallop out with any serious energy cannot be taken as positive signs less than one week out from the big event.” A factor in his favor, though, is the relative toughness of the Oaklawn preps, in which Dublin ran well. Off a second in the Southwest, a third in the Rebel, and a fast-closing third in the Arkansas Derby,* he could be poised to move forward.
Devil May Care, coming into the Derby with a competitive profile and a slightly faster time in G2 Bonnie Miss Stakes than Ice Box in the G1 Florida Derby on the same day, moves to #2 and Sidney’s Candy to #3. Lookin at Lucky remains at #4, despite his exceptional qualities. I would rate him higher, but for his tendency to find trouble, and he’s only had two preps this year. There’s also the matter of blinkers-on, blinkers-off: Trainer Bob Baffert is still trying to figure out the colt, and he’s running out of time. But then, the new Derby favorite worked brilliantly this morning. (Trying to sort it all out this evening, Bill Finley’s see-no-works, hear-no-works approach to Derby week suddenly seems a very sensible one.)
PDI top 10 for 4/27/10: 1) Dublin 2) Devil May Care 3) Sidney’s Candy 4) Lookin at Lucky 5) Endorsement 6) Awesome Act 7) Jackson Bend 8) American Lion 9) Discreetly Mine 10) Stately Victor
Call it the Twerby? The 2009 Derby was the first in which Twitter played a real role, even if it was mostly to inspire an ongoing debate about the usefulness of the service. This year, however, Twitter has been a source of fast-changing news (see Ed DeRosa’s tweets Sunday on Eskendereya skipping work, doubtful for the Derby, out of the Derby), close-ups of contenders (see Frances J. Karon’s pictures of Dublin and Devil May Care), as well as workout times. Thanks to Dana Byerly of Green But Game for pointing out this Blood-Horse article on Monday’s Derby works, which cites tweets from Churchill’s media department. Observed Vic Zast, by tweet of course,
Not amazing that Esky out of Derby. Favs can drop out in last week. What’s amazing is how fast social networking sites passed news along.
How much a scene can change in just a year, and for the better.
*I was asked last week about column 15, “Key Derby Preps,” on the historical criteria spreadsheet. The numbers that appear there are simply how many such races a horse started in while prepping. Qualifying races were determined by the total number of Derby starters that emerged from each race, as well as the total number that finished ITM in the Derby, 1998-2008. A dozen races rated highly on both counts. It’s a quick measure of contenders’ preps, based on recent trends. Kevin Martin of Colin’s Ghost has done much deeper research on Derby preps: I recommend his work for more insight into using historical trends for judging prep races.
On first reading, I thought there was an error in the headline of the press release: “Equine Injury Database Statistic Released by The Jockey Club.” But no, the Jockey Club did release just one statistic, and it is a sobering figure:
Based upon a year’s worth of data beginning November 1, 2008, from 378,864 total starts in Thoroughbred flat races at 73 racetracks … 2.04 fatal injuries were recorded per 1,000 starts.
TJC did not report the actual number of deaths, but the Courier-Journal did the math, coming up with:
… about 773 horse deaths, or an average of nearly 15 fatal injuries a week.
For comparison, the New York Times offers:
In England, for example, the average risk of fatality ranges from 0.8 to 0.9 per 1,000 starts. In Victoria, Australia, studies reported the risk of fatality from 1989 to 2004 at 0.44 per 1,000 starts.
More detailed data, although not track-by-track stats, will be released at the Welfare and Safety of the Racehorse Summit in June.
Kentucky Derby 2009 bump chart, from Charts and Graphs:
Created with ggplot2 for R. More from Learning R on its construction.
Mine That Bird’s rail dash looks no less improbable graphed, while Pioneerof the Nile’s even run looks better. Too bad there’s no Trakus data, which would make for a busier, but surely richer and more revealing, chart.
Copyright © 2000-2023 by Jessica Chapel. All rights reserved.