Quote:
Originally Posted by AltonKelsey
ts provides data for dozens of tracks , hundreds of pools daily, and I have never noticed a pool error. I'd say the accuracy rate is close to 99.99% on a daily basis.
|
You are probably correct that the pools are correct most of the time. I have never seen a problem in their domestic pools, but I have never thought to look for the specific kinds of errors I saw recently. The reason I brought this up in the first place was to remind handicappers to not become complacent and just assume the data is always correct.
It might be worth it to me to write additional code for my software that checks for certain kinds of tote errors. I have some error checking code in my software already, but not for the kind of errors I saw recently. Maybe it is possible to cross-check the pools with other sites or to look for win bet amounts that are repeated over and over?
I have always assumed the liability for any betting errors that happen to me -- even if the fault is not mine. That's part of the game. Things happen that are out of anyone's control. I have probably benefitted from errors that were outside of my control. In the end it all evens out.
Quote:
|
You're distracting from the issue of management priority of a software fix.
|
It sounds like you are saying it is more of a priority to fix batch wagering than to track down the bug that displays incorrect tote data.
I respectfully disagree. Odds are the lifeblood of bettors. If a horse is listed at 4/1 and it's really 4/5 that is a big difference to a bettor. And it could be the difference between making or not making a bet.
If the horse is 4/5 and you think it is 4/1 and send in a big bet because you think you are getting value, then you're in for a rude surprise if the horse wins. People would be screaming about past posting. I can hear them now, "It was 4/1 when I bet at a minute to post and it only paid 4/5!"
Or vice versa, "I would have bet if I would have known it was 4/1. No way would I bet it at 4/5!"
