Apologies for the delayed response - I agree something very strange happened and I have reached out to the Team responsible for the US data and they are doing some analysis.jamesedwards wrote: ↑Tue Feb 01, 2022 7:14 pmAny update on what went wrong with Angelus Diamond data from Tampa Bay 19:13 race 5 on Sunday please?
TPD Feedback and Issues
Regarding Angelus Diamond data from Tampa Bay 19:13 race 5, Sunday last. The Team have looked into this and unfortunately there is no unequivocal answer. At this track, two GPS trackers are always fitted to each horse and we can say with certainty that one of the two trackers "dropped out" at about the half way mark.
This should not matter as one tracker will "do the job" absolutely fine. And indeed we are not quite there yet with rolling out two trackers per horse in all UK and US tracks, which is being done to improve overall resilience. Having said that the second tracker then did not drop out as such, but obviously transmitted some very spurious data towards the end of the race. This does happen very occasionally and the most common reason for this is what we term "whipstrike".
It is highlighted that all trackers are thoroughly checked out prior to being placed in the saddle by a suitably qualified on-site operator and hopefully instances such as this will be very few and far between. Sorry we can't be more specific on this occasion.
This should not matter as one tracker will "do the job" absolutely fine. And indeed we are not quite there yet with rolling out two trackers per horse in all UK and US tracks, which is being done to improve overall resilience. Having said that the second tracker then did not drop out as such, but obviously transmitted some very spurious data towards the end of the race. This does happen very occasionally and the most common reason for this is what we term "whipstrike".
It is highlighted that all trackers are thoroughly checked out prior to being placed in the saddle by a suitably qualified on-site operator and hopefully instances such as this will be very few and far between. Sorry we can't be more specific on this occasion.
We just thought that we would post this - not sure if it will affect anyone's set-up, either with or without TPD data, but useful information of which to be aware I would think.
From now until 1st April all Class 5 &6 races at all ARC All Weather tracks will have 1 yard added to their race descriptions…. So a class 3 sprint at Southwell will be described as 6f 16 yards but a class 5 sprint will be described as 6f 17 yards.
However – the race distances aren’t actually changing!!
The reasoning behind this which we have so far been able to elicit from ARC/BHA is that in their systems they need to differentiate between classes 5 & 6 and the rest, so they chose to add a yard to the distances. And if you are thinking that being called class 5 and Class 6 in the system would be differential enough, then that is likewise our thinking.
The affected races today Fri 4 Feb:
Lingfield races 2,5 & 6
Newcastle races 1,2,3,4,6,7
From now until 1st April all Class 5 &6 races at all ARC All Weather tracks will have 1 yard added to their race descriptions…. So a class 3 sprint at Southwell will be described as 6f 16 yards but a class 5 sprint will be described as 6f 17 yards.
However – the race distances aren’t actually changing!!
The reasoning behind this which we have so far been able to elicit from ARC/BHA is that in their systems they need to differentiate between classes 5 & 6 and the rest, so they chose to add a yard to the distances. And if you are thinking that being called class 5 and Class 6 in the system would be differential enough, then that is likewise our thinking.
The affected races today Fri 4 Feb:
Lingfield races 2,5 & 6
Newcastle races 1,2,3,4,6,7
Have alerted the Developers re Chepstow.
Looks like a server websocket problem re the issues at the moment. Developers hope to have this fixed very soon. Apologies.
That was working fine for me, I've been creating an example so been grabbing screenshots all afternoon - only the first has had any data missing for me
- Attachments
-
-
jamesedwards
- Posts: 3933
- Joined: Wed Nov 21, 2018 6:16 pm
Thanks for this info. It helps us to understand how this technology works and what can go wrong in order to build in stop-checks into our programming.TPD-Zone wrote: ↑Fri Feb 04, 2022 10:42 amRegarding Angelus Diamond data from Tampa Bay 19:13 race 5, Sunday last. The Team have looked into this and unfortunately there is no unequivocal answer. At this track, two GPS trackers are always fitted to each horse and we can say with certainty that one of the two trackers "dropped out" at about the half way mark.
This should not matter as one tracker will "do the job" absolutely fine. And indeed we are not quite there yet with rolling out two trackers per horse in all UK and US tracks, which is being done to improve overall resilience. Having said that the second tracker then did not drop out as such, but obviously transmitted some very spurious data towards the end of the race. This does happen very occasionally and the most common reason for this is what we term "whipstrike".
It is highlighted that all trackers are thoroughly checked out prior to being placed in the saddle by a suitably qualified on-site operator and hopefully instances such as this will be very few and far between. Sorry we can't be more specific on this occasion.
-
jamesedwards
- Posts: 3933
- Joined: Wed Nov 21, 2018 6:16 pm
Gulfstream R2 17:59: Adios Dixie no GPS data throughout the race.
-
jamesedwards
- Posts: 3933
- Joined: Wed Nov 21, 2018 6:16 pm
Tampa Bay R2: Almost no data throughout the race.
Tampa Bay R3: Strange goings on with the data from Van which looked incorrect for much of the race eg skipped straight from last and 65m behind the leader, to 1st and 10m clear at about 1250 metres out.
Tampa Bay R3: Strange goings on with the data from Van which looked incorrect for much of the race eg skipped straight from last and 65m behind the leader, to 1st and 10m clear at about 1250 metres out.
Last edited by jamesedwards on Fri Feb 04, 2022 8:16 pm, edited 2 times in total.