Racing Software Inconsistencies
-
OK, so we've tracked down what's happening with Kortez Bay and Big Dream. Both part of the same issue.
It's to do with the price ranks getting messed up for some races which had reserve runners, when those runners became "active" due to other runners being removed.
The price ranks weren't being recalculated properly, so for example in Kortez Bay's race, there were 2 reserve runners which ended up running, and from the point when they became active, the ranks were shifted by 2, so Kortez Bay appeared to be the 3rd favourite (i.e. rank 3) when actually it was the favourite (rank 1).
This has been fixed already with regard to upcoming races. We now need to fix the historical records, which will probably take a while.
We'll start this in the early hours of tomorrow and once I've done the first batch, I'll have a better idea of how long the total job will take.
-
@Andrew-Gray great response from @Adam a little disappointed you didn't do this in support before doing this, next time please use the support form in the software: https://form.asana.com/?k=V4sICWddOgH3CMQ96g0XSA&d=1120854233877885
-
1. Max qualifiers issue
You seem to have a misunderstanding of how the "max qualifiers" feature works. The "max qualifiers" feature completely ignores races if there are more qualifiers than the specified number. Full explanation can be found in the help for that feature.Yes, the favourite setting does override this, because they're incompatible. If you say you want to bet on the 1st, 2nd and 3rd favourite, that implies you are happy with 3 bets on the market. If you then set max qualifiers to 1, that's a conflict, because it will be expecting to ignore the race if there is more than 1 bet in the market.
The favourite rule takes precedence and finds the first x trades based on the favourites specified.
This was discussed at length in the changelog thread here but I will also add a note to the help info for the "favourite" setting to clarify it.
2. Horses in the backtesting which you did not bet on
Havana Goldrush:- Appears in the backtesting because it became 3rd favourite at 2023-11-25 20:13:18.517 when its price came in from 8.4 to 8.2
- At the time, Girl From Italy was favourite (3.75) and Voltaic was 2nd fave (5.2)
- Havana Goldrush was fighting Rich Waters for 3rd fave position, as his price at the time was also hovering around 8.4 - 8.6
Kortez Bay:
- I'm still looking into this one. At the moment it looks like a possible gap in the price data for that market.
- I don't yet know if this was because of an issue with the Betfair API at that time or if it was an issue our end and I also want to see if any other runners are affected
- I will update shortly when I've had a chance to consult with Miklos
2. Horses you bet on which do not appear in the backtesting
I've only had time to fully review 2 of these so far, Muscika and Pulse Of Shanghai, however will continue investigating and update on Big Dream once I'm back at my desk after running an errand.
Muscika:
- Did not register within the top 3 during the specified betting window
- The top 3 were Waiting Game, Dickieburd and Clipsham La Habana, ranging from around 4.0-6.2. Muscika hovered around 8.6 during the betting window. It did come down to 7.6 briefly, but that wasn't enough to put it into 3rd position
Pulse Of Shanghai:
- Did not register within the top 3 during the specified betting window
- The top 3 were Half Nutz, Bold optimist and Sam's Express, ranging from around 5.1-6.8. Pulse of Shanghai hovered around 9.6 during the betting window, so I have no idea why you would have bet on that as it doesn't seem to have vied for 3rd fave at any point in the last 09:30 mins before the race
As I say, I will update you on any outstanding ones above shortly once I have had a chance to investigate the others fully. It would also be good to keep things in one thread (better still, a support ticket, because then we assign a ticket number and can track the necessary changes properly and add them to the public changelog).
Any genuine issues found will be rectified rapidly, reported extremely transparently as they always are, and cases added to our audit scripts to ensure they don't re-occur.
-
OK I've worked out the second bug already.
So the strategy was originally to be used for the 1st,2nd, and 3rd favourite in the filter settings.
But as we know this is not accurate as that takes the BSP 1/2/3 favs.
So I changed the filter to include 1/2/3 fav at time of bet - the new feature which should give more accurate back testing.
This however seems to have overriden the Max 1 selections per race rule I guess as it comes after it in the sequence of rules applied?
When I removed the 1/2/3 fav rule from that section, and put it back in the original BSP rule section, then only 1 bet per race appears in the individual selections.