PDA

View Full Version : Put this spot play into your database


Frank N
2nd December 2001, 05:58.53 PM
A simple query for Access users to try on larger databases than Gramps has.

nDIST: 6 or 6.5 or 7
tSURF: "d"
nFAV: 0
tRS: ="*e"
nQPT: 3 or 4
F1: <=4
EP: <=4
ACL: <=5

The results in Gramps's database were

Plays: 347
Win%: 21.9%
ROI: 1.52

That is out of about 7200 total races at those distances, so it finds about one play per 20 such races.

I also found out that this worked well at 5 furlongs and shorter. However, it did very poorly at 5.5 furlongs. My own belief, based on the logic to be presented, is that it won't do as well at distances shorter than 6 furlongs as it does at sprints of 6, 6.5, and 7 furlongs. Maybe somebody else can test this on a larger database.

Here, factor by factor, is the logic behind the query:

The distance and surface are, of course, sprints of conventional distances raced everyday, and this is the basis of the other factors.

nFAV: Horses who were favored their last time tend to draw money today as well, whether they won or not. The public believes that the "smart money" was sent in then, and they react accordingly. Also, horses favored in their last race often get listed at lower morning line odds by the trackman, and this results in lower final odds. If we eliminate these horses, we eliminate, by and large, overbet undervalued types. So we set this to "0", which means we don't want horses who were favored in their last race.


tRS="*e": We're looking for the horse that is believed to be the early leader today. But we're also looking for something else, which will be discussed next. As you'll understand when you've read the next paragraph, we don't want a confirmed front runner (*f), nor do we want pressers, sustained, or rear-running horses.

nQPT=3 or 4: This is the key to the play. What we're looking for are horses who show some early foot, but not so much that everybody else sees it. The fact that the horse is considered to be the likely leader tells us that its early speed is good enough to get to the top of this field. But the fact that it doesn't ALWAYS run early means that the public won't be keying on an obvious front runner. Also, if the horse doesn't always get the lead, it suggests a horse that might be able to run flexibly and sit off of a hot pace today. We want a horse that figures to be ABLE to get to the lead, hence we don't use plain "e" horses (horses who run early but don't figure to get the early lead). But we also want some flexibility, so we don't include "*f" horses. a "*f" horse is both overbet and inflexible. If some jockey/trainer decides to send his/her horse to the lead today and contest a "*f" horse, it will hurt its chances. The fact that the horse figures to get the lead with only 3 or 4 Quirin points suggests that the race is fairly void of early speed, which gives the jockey of our horse more options to choose from as far as setting the pace or laying just off of a suicidal one.

In the database, QPT=2 also worked for a small profit, and perhaps somebody else can test that. QPT=5 did not, mainly because at 5-8 Quirin points, the fact that the horse can run early gets more and more obvious to the public. What's obvious to the public gets bet down.

F1<=4 and EP<=4: Simply, we want to be sure that the horse has enough early foot to the first and second calls to be within striking range, if not on the lead.

ACL<=5: We want to be sure that the horse has raced well against competition in the same ballpark as the other horses in the race.

Perhaps somebody would care to try this in a larger database and report the findings. I'm pretty sure that the ROI is a bit high in the small sample we have, and I'd think something like 1.30 (possibly a little lower) would be more in line with reality.
--------------
As an addendum, requiring minimum off-odds of at least 3-1 produces the following:

Plays: 208
Win%: 18.3%
ROI: 1.92

In this and the original sample were two $60 horses and a $112 horse. This isn't out of line with reality, in my opinion; however, a larger sample might show a lesser ROI.

MikeDee
3rd December 2001, 08:20.29 AM
Thanks Frank for sharing

Maybe someting wrong. I ran this on a 27000 race db and I only got 513 hits. Have checked and double checked but can't find anything wrong.

One item may be the problem. In Access if you put a *E in your query for tRS, Access reads this as like "*E" and then includes all E's, even those that do not have a * indicator. If I run it this way I get 1188 hits or about 1 out of 22 races which is in the rage you mentioned.

Here are my results on the 513 true *E runers

Trk nWin nBet Win% aMut aBet aWon aP/L ROI
AQU 7 34 21% $15 $68 $104 $36 53%
CRC 17 57 30% $16 $114 $280 $166 146%
DED 5 31 16% $13 $62 $67 $5 8%
HAW 11 71 15% $8 $142 $88 ($54) -38%
HOL 7 44 16% $7 $88 $49 ($39) -44%
HOO 8 27 30% $5 $54 $40 ($14) -26%
HOU 5 29 17% $7 $58 $34 ($24) -41%
MNR 4 27 15% $9 $54 $37 ($17) -31%
SUF 14 63 22% $7 $126 $103 ($23) -18%
TP 7 52 13% $13 $104 $88 ($16) -15%
TUP 19 78 24% $12 $156 $225 $69 44%
104 513 20% $1,026 $1,115 $89 9%


Here are all E and *E runners
Trk nWin nBet Win% aMut aBet aWon aP/L ROI
AQU 15 85 18% $11 $170 $169 ($1) -1%
CRC 23 113 20% $18 $226 $425 $199 88%
DED 11 58 19% $16 $116 $180 $64 55%
HAW 20 161 12% $10 $322 $202 ($120) -37%
HOL 14 97 14% $7 $194 $97 ($97) -50%
HOO 13 64 20% $9 $128 $117 ($11) -9%
HOU 10 72 14% $14 $144 $141 ($3) -2%
MNR 11 65 17% $12 $130 $133 $3 2%
SUF 27 167 16% $10 $334 $272 ($62) -19%
TP 20 129 16% $15 $258 $298 $40 16%
TUP 37 177 21% $10 $354 $365 $11 3%
Total 201 1188 17% $2,376 $2,399 $23 1%

Glen
3rd December 2001, 08:33.08 AM
Yeah, the *F, *E, *P, and *Anything will mess up a RS query. Best to use the Impact Export for RS queries. It solves the (*) problem by just using numbers to represent running styles.

Ex:

1=F
2=E
3=P
and so on...

Bernie
3rd December 2001, 10:36.43 AM
Mike,

If I use LDR=1 from Impact to give the * rating, I only get a handful of plays. What's wrong here?

Thanks to Frank for posting his logic. Even though this spot play fell short, I was able to use some of the ideas in my other spot plays.

hurrikane
3rd December 2001, 10:45.28 AM
Surprisingly I had a play like this for routes that worked quite well when I was doing spot plays. And now with the new contest comming up I suppose I'll be digging thorough all of that info.

Also...in impact there is a field for the likely * horse or horse likely to get the lead. Combine that with the nRS field and you got yourself a query. otherwise in ALL_MSA you need to do rs = *E and not like E. this will give you the "*E" front runner. :D

Juat a word of caution..you might like to play slow..especially with a small dataset. Spent a lot of money on education when I first stated db handicapping...test..test..test..equals..save.save .save...

have fun

Frank N
3rd December 2001, 11:42.55 AM
You can solve the "Like" parameters by using an equal sign. For example:

="*e" returns only exactly *e horses.

"*e" will be translated to 'Like "*e"' which will include all e and *e horses

e or =e will only return e horses and not *e horses.

In the sample, only *e horses are wanted, since we want the horse that is the likely leader today. Mike's sample for *e horses showed a 9 percent ROI, which isn't too bad for something as simple as this is. The sample which included both *e and e showed a 1% profit. however, if you took the *e horses out, the blank e horses would probably show a loss, which isn't surprising.