![]() |
![]() |
![]() |
|
|
|
#1
|
||||
|
||||
|
Ouch. That's a sickening feeling when the will pays are already posted.
|
|
#2
|
||||
|
||||
|
Of course if they had info on a post time fave move for that other ticket they could have bet the 2nd choice into favoritism to make sure they had a single ticket...horse still needed to win of course. And did.
|
|
#3
|
|||
|
|||
|
I hit it on Friday for 850.. Didn't see the probables..thank god..probably would have had a heart attack for no reason
|
|
#4
|
||||
|
||||
|
Quote:
|
|
#5
|
||||
|
||||
|
The probable feed was actually never incorrect. It was based upon, at the time, the #11 being the favorite (which he was for a while in the early betting). For those who watch the races at Louisiana Downs, anytime an Al Stall ends-up the favorite is no surprise.
Obviously I would have never added the jackpot to my call nor would we have shown probables prior to the race if any of us had any idea this might have happened. The same set of probables were shown on every ADW out there because they all come from the same source. I feel bad about it all, but nobody did anything wrong... it's just, like I've said, an awful set of circumstances. |
|
#6
|
||||
|
||||
|
Quote:
|
|
#7
|
||||
|
||||
|
Quote:
My first thought it was to find-out whether or not tote can support updating those probables every x-seconds, similar to have the probables for Ex/DD are shown, but that is really just a band-aid. |
|
#8
|
||||
|
||||
|
It was correct data at the time of the posting and calculation of the probables. It's technically not a will pay... it's a probable. An additional scratch of any other horse live to the Jackpot between its initial cycle and race time would have had the same impact.
|
|
#9
|
||||
|
||||
|
Just one more note... this was all a nasty set of circumstances that I wish never would have happened. I know of partners who have six figures worth of reasons to agree and another who might not because he/she backed into a $12k payoff. That said, because it happened, we can now look to make adjustments going forward.
I do think there is a general public perception that those who run racing don't care. We see it all the time with the endless barrage of jabs toward NYRA and other racing entities. In reality, I have never met anyone who works at a racetrack that doesn't care about the sport or wants it to succeed, and the same applies here. I promise you that everyone in my office, in our racing office and beyond would have rather seen the Jackpot get distributed versus having to deal with what happened. But like I said, hopefully we can figure out the right solution and get it implemented as soon as possible. |
|
#10
|
||||
|
||||
|
Quote:
Although admittedly singling it would be somewhat suspicious. But just to add to the bizarre aspect of the bet, if this person had used 2 horses, and one was the winner, while the other was the 30-1 ML horse, who scratched, then he would have scratched into his own horse, thereby having it twice, and costing himself the entire pool?? Had there been no other tickets on the winner of course. |
|
#11
|
||||
|
||||
|
Quote:
|
|
#12
|
||||
|
||||
|
Quote:
But all this does go back to the problems of being put on the favorite in a scratch situation. There are times when a simulcast player won't even know who the favorite was until after the race, as the odds are available, but the pools aren't, and there could be multiple horses at the same odds. And the track announcer wouldn't even be able to tell everyone at post time, because we all know the money hasn't all been co-mingled at that point. Strange game we play. |
|
#13
|
||||
|
||||
|
Quick Pick on horses? Beyond bizarre
|
|
#14
|
||||
|
||||
|
I shouldn't say I "can't confirm" ... I was told that it was by someone who would know on Sunday morning as a follow-up to the gathering of info the night before. I was not made aware of it until I spoke with Andy Beyer, which is why he didn't mention it.
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|