TPD Feedback and Issues

[parrettt]

just happened again
1625 laurel park
Hazelmoor beach won and was never the fastest in the race

[jamesedwards]

Santa Anita working fine yesterday, but today "Unable to connect Santa Anita Park (US) 29th Oct - 20:30 R2 1m Allw Claim to Total Performance Data. The race is not supported by their service"

[jamesedwards]

29-Oct-23 00:41 29-Oct-23 00:50
Horse Racing / Santa Anita Park (US) 28th Oct : R7 1m Allw Claim

First race I checked, first bit of the race I checked, with 338.1m to finish; eventual winner (yerwanthere) was running at the fastest speed of all selections.

Gimme Mo Baby: MPS 16.89
Luminiferous: MPS 16.82
Rose Barton: MPS 16.48
Grace Period: MPS 16.81
Myfavoritedaughter: MPS 16.87
With Love: MPS 17.32
Yerwanthere: MPS 17.38


It is of course possible to win a horse race without ever being the fastest horse at any given moment. But perhaps looking at a 5 sec average is too long?

In my automations I use speed data up to half a second average at most.

[jamesedwards]

just happened again
1625 laurel park
Hazelmoor beach won and was never the fastest in the race

With 249.0m left to run;

Singalong: MPS 16.75
Spirit Of Power: MPS 16.19
Reveille Song: MPS 15.64
Stage Call: MPS 16.81
Hazelmoor Beach: MPS 16.96
Boardwalk Fries: MPS 16.25
Newtons Star: MPS 15.59
Peace Fire: MPS 16.55
Satisfied: MPS 16.41
Bessie Blue: MPS 16.29

[parrettt]

OK thanks for looking
i used live speeds as well as 5 and 10 seconds and horses streaking away to win in the last 15 seconds were supposedly going at slower speeds than the horses behind them.
The mystery is that the English races showed figures that tallied with what we could see on the feed. I looked through your old posts and the theme that kept coming through was do not solely rely on TPD and I think that is the answer!

[sIGNAL]

OK thanks for looking
i used live speeds as well as 5 and 10 seconds and horses streaking away to win in the last 15 seconds were supposedly going at slower speeds than the horses behind them.
The mystery is that the English races showed figures that tallied with what we could see on the feed. I looked through your old posts and the theme that kept coming through was do not solely rely on TPD and I think that is the answer!

I would agree that TPD shouldn't be used 100% solely on its own . I've used it solidly on its own for a month, over 500 races with mixed results. I have now gone back to using a live racing feed where I can read a race quite well, actually seeing the horses run ratherr than just a blip on the screen is far more reliable. using the live betfair feed and the TPD live metrics mixed in and not relying on the tracking map so much, this seems to be working better for me and my strategy.

[parrettt]

Yes you see more with a decent feed but there are feeds and feeds. The coverage at S Anita last night was perfect while the map was a bit slow on the uptake. Also the pre-race analysis was worth listening to which is not always the case.
I just wish they would stop the long slow march to the stalls. It looks like Napoleon on his way back from Moscow

[parrettt]

in the 1430 at ncl which was well won by 4, the map showed 11 leading all the way across the finishing line from a furlong out.
the map was useful until then as it covered 4 coming from the back to the front but then dried up. Bet angel were well across this on the ipt and it was clear on the feed. I have a feeling looking at other software that tpd lost connection towards the end

[Dinyal]

I signed up to TPD today, admittedly only the initial £10 a month 20 races trial.

Chepstow is the meeting today and from the first few races it seems that the TPD feed (horses moving on the map) is almost identical to the Betfair live video, which obviously other than the mph figures doesn't really give any advantage.

Is this usual for Chepstow or is it the fact I'm on the lowest tier of subscription?

[jamesedwards]

I signed up to TPD today, admittedly only the initial £10 a month 20 races trial.

Chepstow is the meeting today and from the first few races it seems that the TPD feed (horses moving on the map) is almost identical to the Betfair live video, which obviously other than the mph figures doesn't really give any advantage.

Is this usual for Chepstow or is it the fact I'm on the lowest tier of subscription?

In my experience these are roughly the typical delays behind live;
TPD 0.5 secs
BFL (RTV tracks) 1 sec
BFL (ATR tracks) 1.5 secs

As you are on the 'trialist' package, you also only get TPD updates every 0.8 secs, compared with 'standard' and better packages will get updates every 0.2 secs.

Easiest way to compare is at the start of a flat race when you can check movement on the map vs the stalls opening.

[jamesedwards]

I signed up to TPD today, admittedly only the initial £10 a month 20 races trial.

Chepstow is the meeting today and from the first few races it seems that the TPD feed (horses moving on the map) is almost identical to the Betfair live video, which obviously other than the mph figures doesn't really give any advantage.

Is this usual for Chepstow or is it the fact I'm on the lowest tier of subscription?

I should add, the TPD edge is not really in latency, it's in the power of information in number format. It is NOT accurate enough to try and beat 1.01 on the reported leader at the finish.

[Dinyal]

I signed up to TPD today, admittedly only the initial £10 a month 20 races trial.

Chepstow is the meeting today and from the first few races it seems that the TPD feed (horses moving on the map) is almost identical to the Betfair live video, which obviously other than the mph figures doesn't really give any advantage.

Is this usual for Chepstow or is it the fact I'm on the lowest tier of subscription?

I should add, the TPD edge is not really in latency, it's in the power of information in number format. It is NOT accurate enough to try and beat 1.01 on the reported leader at the finish.

Thanks for the replies! I guess it was because i'd seen some videos where the video feed was a few seconds behind (I was timing from the time the horses were jumping the fence on each platform) and it looked intriguing! Good to know its not something wrong with what I was doing! I'll have a look through the things in the emails they sent me and have some fun with it

[sIGNAL]

I signed up to TPD today, admittedly only the initial £10 a month 20 races trial.

Chepstow is the meeting today and from the first few races it seems that the TPD feed (horses moving on the map) is almost identical to the Betfair live video, which obviously other than the mph figures doesn't really give any advantage.

Is this usual for Chepstow or is it the fact I'm on the lowest tier of subscription?

I should add, the TPD edge is not really in latency, it's in the power of information in number format. It is NOT accurate enough to try and beat 1.01 on the reported leader at the finish.

Thanks for the replies! I guess it was because i'd seen some videos where the video feed was a few seconds behind (I was timing from the time the horses were jumping the fence on each platform) and it looked intriguing! Good to know its not something wrong with what I was doing! I'll have a look through the things in the emails they sent me and have some fun with it

I have noticed that the delays do vary from track to track. Some days and some tracks TPD can be a good few seconds ahead, and sometimes it's minimal as already mentioned. Be careful with betting at the last minute as its not accurate enough to do that and sometimes even the horses seem to be the wrong way round. I found a good starting point with all the data was using the Pars to see if the horses were running under or over. You can get some decent lay to backs on there using that data.
Good luck

[jamesedwards]

Golden Gate race 6. Transponder swap between 4) Coral Cat and 5) It Aint Over.

[jamesedwards]

I've noticed a bug which feels like is slowly growing in frequency. I have a back-up physical PC that I leave on 24/7 purely to run TPD automations.

I'm finding that every few days TPD data on this back-up PC stops flowing and remains stuck until I restart Bet Angel. It feels like this has been occurring for several weeks now.

TPD is connected ok on the affected machine but the 'last update' window in settings sticks on 'heartbeat' and no data will flow.

Example diagnostics of affected PC:
17/11/2023 17:00:05.695:Stream_149: Status Response:{"status":"heartbeat","id":"14b886a852590cc022244bdcb8d2d9bd","date_time":"2023-11-17T17:00:06.005Z"}
17/11/2023 17:00:11.693:Stream_149: Status Response:{"status":"heartbeat","id":"14b886a852590cc022244bdcb8d2d9bd","date_time":"2023-11-17T17:00:12.005Z"}
17/11/2023 17:00:17.695:Stream_149: Status Response:{"status":"heartbeat","id":"14b886a852590cc022244bdcb8d2d9bd","date_time":"2023-11-17T17:00:18.006Z"}
17/11/2023 17:00:23.693:Stream_149: Status Response:{"status":"heartbeat","id":"14b886a852590cc022244bdcb8d2d9bd","date_time":"2023-11-17T17:00:24.005Z"}

At the same time my main PC is also running TPD on the same races with no issues.
Example diagnostics of main PC for the same time:
17/11/2023 17:00:05.000:Stream_110: Race Info Received (58202311171700)
17/11/2023 17:00:05.001:Stream_110: Race Info Received (35202311171720)
17/11/2023 17:00:05.175:Stream_110: Race Info Received (58202311171700)
17/11/2023 17:00:05.205:Stream_110: Race Info Received (35202311171720)
17/11/2023 17:00:05.410:Stream_110: Race Info Received (35202311171720)
17/11/2023 17:00:05.412:Stream_110: Race Info Received (58202311171700)
17/11/2023 17:00:05.612:Stream_110: Race Info Received (58202311171700)
17/11/2023 17:00:05.612:Stream_110: Race Info Received (35202311171720)
17/11/2023 17:00:05.783:Stream_110: Race Info Received (35202311171720)
17/11/2023 17:00:05.791:Stream_110: Race Info Received (58202311171700)
17/11/2023 17:00:05.982:Stream_110: Race Info Received (35202311171720)
17/11/2023 17:00:05.986:Stream_110: Race Info Received (58202311171700)