I have recently returned to Bet Angel automation after taking a long break due to the frustration of not being able to fully control the automation.
The introduction of the signals facility is a great improvement and has helped me move much closer to what I am trying to achieve.
But I still have the problem of bets being triggered on a horse when it already has a bet associated with that horse.
Basically my programme seeks to place a bet if certain circumstances apply and if those circumstances don't apply then place a bet if other similar but slightly different circumstances apply. But I only want one bet per horse.
I thought that as long as matched bets on selection = 0 and unmatched bets on selection = 0 then I would be safe but I am still finding that 2 bets are placed on the same horse simultaneously or within a second of each other.
Sometimes this results in double the winnings and sometimes it turns a winning race into a losing race as a horse has been over layed.
I have a programme that is only triggering bets a few times a day but the majority of those races produce a profit. If only I can stop the double bet problem I think I may be onto something good.
I have considered lowering the refresh rate so that the automation recognises the first bet before placing the second bet but think I need the refresh rate to be fast in order to place any bets at all, currently using 200ms. Perhaps I should go the other way and speed up the refresh rate.
Controlling Automation
it may be a case of ensuring that the re-arm of the rule is set to > 5 seconds, just to ensure that you don't encounter a double trigger before the bet is placed on the market. you could also use the bet triggers option (set to equal 0) as this will effectively ensure that the rule is only triggered the one time irrespective of the re-arm timings. as ever, Dallas will probably have a few other little tricks to impart.
Guy,
I find the simplest approach for these scenarios is to set a selection level signal, combined with a condition that the signal is not set with a value. This ensures that if the rules has passed the conditions and fired once, the signal will be set, and will therefore fail any subsequent evaluations, and not fire.
Doing it this way ensures that any subsequent rules in the sequence will not fire, irrespective of in play delays, refresh rates etc. Also, by doing it with a selection level signal, you can duplicate it for multiple selections if required.
Cheers
Steve
I find the simplest approach for these scenarios is to set a selection level signal, combined with a condition that the signal is not set with a value. This ensures that if the rules has passed the conditions and fired once, the signal will be set, and will therefore fail any subsequent evaluations, and not fire.
Doing it this way ensures that any subsequent rules in the sequence will not fire, irrespective of in play delays, refresh rates etc. Also, by doing it with a selection level signal, you can duplicate it for multiple selections if required.
Cheers
Steve