PLACING LAY BET WITHIN % OF BACK PRICE

[airtomoreira]

Hi, occasional Bet Angel user here…..

Hoping someone can point me in the right direction. I’ve looked through the automation guidelines but can’t see anything that solves the following problem (though I’m far from an expert on how things like Servants, Stored Values etc work, so there may well be an easy answer….)

I have automated a system whereby I lay US races, either 2 or 3 horses in each race, by placing lay bets 30 seconds before the advertised off. Having been running it for two months now (in live mode), it would seem to be profitable (so far), there being far more positive days that negative ones. The one problem being of course, that at some tracks, the advertised off time bears no resemblance to the actual race time start. This means that there can be occasions where, 30 seconds before the advertised off time, the market is showing a significant difference between the back and lay prices of runners, and as a result my lay bet is being placed outside of a range that I would be happy with, so I'd like to set some parameters.

I’d like to instruct Guardian to place a lay bet only if the lay price is within a set % of the back price (let’s say theoretically 10%, so that if the back price was 5.0, the lay would only be placed if the lay price was no greater than 5.5). However, the only “condition” I can see that I could apply is based not on a % variance, but on the number of ticks. So, again for example, if I set a maximum gap of 10 ticks, I’d be happy to place a lay bet at anything up to 2.20 if the back price was 2.00. but I’d not be happy to do so at 15.0 if the back price is 10.0 – the tick range in both of the above examples being 10. The exposure in the latter example is far too great to be acceptable.

Is there a tool I could use to achieve this % based rule? Thanks in advance to anyone who can advise.....

[Derek27]

Hi, occasional Bet Angel user here…..

Hoping someone can point me in the right direction. I’ve looked through the automation guidelines but can’t see anything that solves the following problem (though I’m far from an expert on how things like Servants, Stored Values etc work, so there may well be an easy answer….)

I have automated a system whereby I lay US races, either 2 or 3 horses in each race, by placing lay bets 30 seconds before the advertised off. Having been running it for two months now (in live mode), it would seem to be profitable (so far), there being far more positive days that negative ones. The one problem being of course, that at some tracks, the advertised off time bears no resemblance to the actual race time start. This means that there can be occasions where, 30 seconds before the advertised off time, the market is showing a significant difference between the back and lay prices of runners, and as a result my lay bet is being placed outside of a range that I would be happy with, so I'd like to set some parameters.

I’d like to instruct Guardian to place a lay bet only if the lay price is within a set % of the back price (let’s say theoretically 10%, so that if the back price was 5.0, the lay would only be placed if the lay price was no greater than 5.5). However, the only “condition” I can see that I could apply is based not on a % variance, but on the number of ticks. So, again for example, if I set a maximum gap of 10 ticks, I’d be happy to place a lay bet at anything up to 2.20 if the back price was 2.00. but I’d not be happy to do so at 15.0 if the back price is 10.0 – the tick range in both of the above examples being 10. The exposure in the latter example is far too great to be acceptable.

Is there a tool I could use to achieve this % based rule? Thanks in advance to anyone who can advise.....

You can create a stored value (Spread in the example) by dividing the lay price by the back price.

Screenshot 2023-08-29 121955.gif

Then you simply subtract 1 from it to get a fraction, obviously multiply by 100 if you want a percentage.

[jimibt]

Hi, occasional Bet Angel user here…..

Hoping someone can point me in the right direction. I’ve looked through the automation guidelines but can’t see anything that solves the following problem (though I’m far from an expert on how things like Servants, Stored Values etc work, so there may well be an easy answer….)

I have automated a system whereby I lay US races, either 2 or 3 horses in each race, by placing lay bets 30 seconds before the advertised off. Having been running it for two months now (in live mode), it would seem to be profitable (so far), there being far more positive days that negative ones. The one problem being of course, that at some tracks, the advertised off time bears no resemblance to the actual race time start. This means that there can be occasions where, 30 seconds before the advertised off time, the market is showing a significant difference between the back and lay prices of runners, and as a result my lay bet is being placed outside of a range that I would be happy with, so I'd like to set some parameters.

I’d like to instruct Guardian to place a lay bet only if the lay price is within a set % of the back price (let’s say theoretically 10%, so that if the back price was 5.0, the lay would only be placed if the lay price was no greater than 5.5). However, the only “condition” I can see that I could apply is based not on a % variance, but on the number of ticks. So, again for example, if I set a maximum gap of 10 ticks, I’d be happy to place a lay bet at anything up to 2.20 if the back price was 2.00. but I’d not be happy to do so at 15.0 if the back price is 10.0 – the tick range in both of the above examples being 10. The exposure in the latter example is far too great to be acceptable.

Is there a tool I could use to achieve this % based rule? Thanks in advance to anyone who can advise.....

You can create a stored value (Spread in the example) by dividing the lay price by the back price.


Screenshot 2023-08-29 121955.gif


Then you simply subtract 1 from it to get a fraction, obviously multiply by 100 if you want a percentage.

i would do it the other way around (back/lay) *100 as you will always have the lay > back, therefore you need to understand the back as a %age of the lay.

[Derek27]

i would do it the other way around (back/lay) *100 as you will always have the lay > back, therefore you need to understand the back as a %age of the lay.

Yeah, that would be easier.

[airtomoreira]

Thank you!