PDA

View Full Version : Public Service Announcement: CAUTION: Twinspires displays incorrect tote data


highnote
07-15-2018, 10:42 PM
Caveat Emptor:

If you are using the Twinspires SUPERTOTE tote board to make wagering decisions be aware that it MAY contain errors.

It displayed the wrong win bet amounts on 8 horses in 6 races on July 15 at Sha Tin racetrack in Hong Kong. This also causes incorrect odds to be displayed.

This is of concern because it makes me wonder if this error happens at other tracks.

See this post #80 at this link for details:

http://www.paceadvantage.com/forum/showthread.php?p=2341918&posted=1#post2341918

I did a little digging and found the XML tote data for horses #13 and #14 in race #10:


<ProgramNumber>13</ProgramNumber>

<Win>8388607</Win>

<Place>0</Place>

<Show>5073214</Show>

<WinPct>20.2</WinPct>

<PlacePct>0.00</PlacePct>

<ShowPct>14.9</ShowPct>

</Entry>


-<Entry>

<ProgramNumber>14</ProgramNumber>

<Win>8388607</Win>

<Place>0</Place>

<Show>5973914</Show>

<WinPct>20.2</WinPct>

<PlacePct>0.00</PlacePct>

<ShowPct>17.5</ShowPct>

highnote
09-02-2018, 08:07 PM
Today is the first day of the new season for Hong Kong racing.

Unsurprisingly, twinspires did not fix the toteboard error that I have posted about over the past month or so.

At one point it was claimed by twinspire personnel that the error was on my end. When I pointed out that others spotted the same error there was only silence from twinspires.

I am waiting for an apology.

Today in races 5, 8, 9, and 10 certain horses have the amount 8388607 bet on them. This is the same amount that I have said previously is incorrect. This causes the sum of win pool total to be incorrect and therefore the odds are incorrect.

It's hard enough to beat this game, but when twinspires sends out incorrect pool data which causes incorrect odds to be displayed it makes super difficult to win.

twinspires, this is unacceptable.

You were notified over a month ago by me here on Paceadvantage.com, by others, as well, and you still let this happen again on the opening day of the Hong Kong meeting? This is unacceptable.

:ThmbDown: