Hi folks, i've been trialing an automation for a few days which places a back bet 1 hr before the off. It backs the favourite and then lays within the last hour. It generally works fine but yesterday 1 bet was different. It backed Veronicas Napkin at 1.75.
According to another site i use @ 1hr before the off Veronicas Napkin was priced at 60.00 and the lowest price it got to was 38.00, 15 mins before the off.
Anybody any ideas why this might happen and/or what i can do to prevent it happening again
Regards
Al
Not sure what happened
Veronicas Napkin was racing at an irish meeting where liquidity is low an hour before the off however looking at the form beaten 67l unseated rider and beaten 26l in this 3 starts this is a poor horse and no wonder was sent off as a 60/1 outsider I am shocked that it was matched at 1.75 it was the lay of the century.
Sometimes you get strange matched bets as soon after the market has been suspended for a non runner and in your race Miro was a declared a non runner (according to bet365 the rule 4 was 10p) at 5:09 if you were placing your bet an hour before ie 5:30 I am shocked the market was showing Veronicas Napkin at 1.70 fav
So what should you do ? Perhaps avoid Irish Racing and maybe look how your bot operates I presume you are selecting your bet by position sorted by favourtism that should work perhaps dallas could confirm ? I know nothing about the new signals feature and perhaps you could improve your bot with this feature ??? and if you have time dallas i think this would be a good idea for a bot
Sometimes you get strange matched bets as soon after the market has been suspended for a non runner and in your race Miro was a declared a non runner (according to bet365 the rule 4 was 10p) at 5:09 if you were placing your bet an hour before ie 5:30 I am shocked the market was showing Veronicas Napkin at 1.70 fav
So what should you do ? Perhaps avoid Irish Racing and maybe look how your bot operates I presume you are selecting your bet by position sorted by favourtism that should work perhaps dallas could confirm ? I know nothing about the new signals feature and perhaps you could improve your bot with this feature ??? and if you have time dallas i think this would be a good idea for a bot
The order of favoritism is determined by the selection with the lowest back price.
Suppose runner A had these odds
.......2.80
2.64
and your selection had
.......42.0
1.75
The automation would see this selection as fav due to having the lowest back price
so if a runner was withdrawn shortly before and the market had poor liquidity to start with its highly likely there was large gaps on all sections especially on the true outsiders which your bot just happened to then fire on at just the wrong time.
As linusP has said using LTP would be the better option but had someones else bot done something similar to yours 1.75 would of become the LTP and yours could still of triggered immediately after but the combination of the above scenario then another bot triggering on a false fav would be very very rare.
If you really wanted to be super cautious you could use a 'Historic relative odds condition' and set the number of ticks between a selections back any lay price is 0 or no more than a few ticks that will definitely prevent it triggering accidentally while a market is reforming.
Suppose runner A had these odds
.......2.80
2.64
and your selection had
.......42.0
1.75
The automation would see this selection as fav due to having the lowest back price
so if a runner was withdrawn shortly before and the market had poor liquidity to start with its highly likely there was large gaps on all sections especially on the true outsiders which your bot just happened to then fire on at just the wrong time.
As linusP has said using LTP would be the better option but had someones else bot done something similar to yours 1.75 would of become the LTP and yours could still of triggered immediately after but the combination of the above scenario then another bot triggering on a false fav would be very very rare.
If you really wanted to be super cautious you could use a 'Historic relative odds condition' and set the number of ticks between a selections back any lay price is 0 or no more than a few ticks that will definitely prevent it triggering accidentally while a market is reforming.
-
shakespeare
- Posts: 113
- Joined: Sat May 21, 2016 1:43 pm
I'm no expert but I agree with Dallas. I've had similar problems in automations I've written for tennis, even in-play. I now add a condition that a bet shall be placed only if the back and lay prices are within 3 or 5 ticks of each other (depending on the market).
-
halfagallon
- Posts: 13
- Joined: Tue Nov 03, 2015 8:43 pm
Many thanks for all your replies.
It's not so straight forward just making an automation and expecting it to work perfect without taking every eventuality into consideration. It's good we have practice mode to try these things out.
thanks once again
Al
It's not so straight forward just making an automation and expecting it to work perfect without taking every eventuality into consideration. It's good we have practice mode to try these things out.
thanks once again
Al
now, if only we could replay historic markets to iron out issues like this in a structured and methodical fashion. oh, wait a minute, maybe we could if we had this: viewtopic.php?f=20&t=11983halfagallon wrote:Many thanks for all your replies.
It's not so straight forward just making an automation and expecting it to work perfect without taking every eventuality into consideration. It's good we have practice mode to try these things out.
thanks once again
Al
