It excludes the pre-off favreids wrote: ↑Thu Nov 12, 2020 7:33 pmActually - does this exclude the favourite or just not a place a bet on the race as a whole if the favourite is below the set price?Dallas wrote: ↑Thu Nov 12, 2020 1:38 pmYes, you need to add a 'Set/Modify signal rule' applied to the fav (armed around post time)
and on the signal tab set a signal on the selection (give it any name and value)
Then on the conditions tab add a 'Fixed Odds Condition'
Selections back price
is greater than
(whatever odds you want to set)
Next on the existing back bet rule add a 'Signal Set Condition'
to test the signal named (whatever you called it) is NOT set with a value
Back the Likely Winner Automation Bot for Horse Racing
Hmmm, something seems to be off. So using the 14.15 at Southall as an example - Hooper was the favourite and went off around the evens mark - Wargrave was the winner.Dallas wrote: ↑Thu Nov 12, 2020 8:04 pmIt excludes the pre-off favreids wrote: ↑Thu Nov 12, 2020 7:33 pmActually - does this exclude the favourite or just not a place a bet on the race as a whole if the favourite is below the set price?Dallas wrote: ↑Thu Nov 12, 2020 1:38 pm
Yes, you need to add a 'Set/Modify signal rule' applied to the fav (armed around post time)
and on the signal tab set a signal on the selection (give it any name and value)
Then on the conditions tab add a 'Fixed Odds Condition'
Selections back price
is greater than
(whatever odds you want to set)
Next on the existing back bet rule add a 'Signal Set Condition'
to test the signal named (whatever you called it) is NOT set with a value
The signal didn't fire due to it rightly excluding the favourite, but then it didn't try to place a bet once the conditions had been met. Looking at the log it seems to have then applied the signal 4 mins later to the second favourite but then didn't fire off the bet. However it seems to work fine if the favourite is above the price set with the signal firing at the beginning of the race
13/11/2020 14:15:54: Guardian has detected that the market is suspended
13/11/2020 14:15:55: Guardian has detected that the market is in-play
13/11/2020 14:15:56: Guardian has detected that the market is now unsuspended
13/11/2020 14:19:22: [G_Auto] : Automation Signal for Wargrave: SET = 1
13/11/2020 14:20:02: Guardian has detected that the market is suspended
I've attached my rules file - does this all look ok?
Last edited by reids on Fri Nov 13, 2020 4:04 pm, edited 1 time in total.
You've armed the signal rule for 10secs after the race has startedreids wrote: ↑Fri Nov 13, 2020 2:38 pmHmmm, something seems to be off. So using the 14.15 at Southall as an example - Hooper was the favourite and went off around the evens mark - Wargrave was the winner.
The signal didn't fire due to it rightly excluding the favourite, but then it didn't try to place a bet once the conditions had been met. Looking at the log it seems to have then applied the signal 4 mins later to the second favourite but then didn't fire off the bet. However it seems to work fine if the favourite is above the price set with the signal firing at the beginning of the race
13/11/2020 14:15:54: Guardian has detected that the market is suspended
13/11/2020 14:15:55: Guardian has detected that the market is in-play
13/11/2020 14:15:56: Guardian has detected that the market is now unsuspended
13/11/2020 14:19:22: [G_Auto] : Automation Signal for Wargrave: SET = 1
13/11/2020 14:20:02: Guardian has detected that the market is suspended
I've attached my rules file - does this all look ok?
This should be done sometime before they go in-play
Thanks, now amended, however something still isn't right. For instance at the 12.35 Punchestown - Latest Exhibition went off at 1.78 - no signal was correctly set, however it still placed a bet on it.Dallas wrote: ↑Fri Nov 13, 2020 3:07 pmYou've armed the signal rule for 10secs after the race has startedreids wrote: ↑Fri Nov 13, 2020 2:38 pmHmmm, something seems to be off. So using the 14.15 at Southall as an example - Hooper was the favourite and went off around the evens mark - Wargrave was the winner.
The signal didn't fire due to it rightly excluding the favourite, but then it didn't try to place a bet once the conditions had been met. Looking at the log it seems to have then applied the signal 4 mins later to the second favourite but then didn't fire off the bet. However it seems to work fine if the favourite is above the price set with the signal firing at the beginning of the race
13/11/2020 14:15:54: Guardian has detected that the market is suspended
13/11/2020 14:15:55: Guardian has detected that the market is in-play
13/11/2020 14:15:56: Guardian has detected that the market is now unsuspended
13/11/2020 14:19:22: [G_Auto] : Automation Signal for Wargrave: SET = 1
13/11/2020 14:20:02: Guardian has detected that the market is suspended
I've attached my rules file - does this all look ok?
This should be done sometime before they go in-play
15/11/2020 12:36:41: Guardian has detected that the market is suspended
15/11/2020 12:36:41: Guardian has detected that the market is in-play
15/11/2020 12:36:41: Guardian has detected that the market is now unsuspended
15/11/2020 12:41:29: [G_Auto] : £ 2.00 Back bet placed on Latest Exhibition at 1.26. Fully matched at 1.33. Ref: 216782719674
I've attached the latest version of my rule as I can't see where I'm going wrong!
Last edited by reids on Sun Nov 15, 2020 4:05 pm, edited 1 time in total.
What refresh rate are you using in Guardian ?reids wrote: ↑Sun Nov 15, 2020 12:43 pmThanks, now amended, however something still isn't right. For instance at the 12.35 Punchestown - Latest Exhibition went off at 1.78 - no signal was correctly set, however it still placed a bet on it.Dallas wrote: ↑Fri Nov 13, 2020 3:07 pmYou've armed the signal rule for 10secs after the race has startedreids wrote: ↑Fri Nov 13, 2020 2:38 pm
Hmmm, something seems to be off. So using the 14.15 at Southall as an example - Hooper was the favourite and went off around the evens mark - Wargrave was the winner.
The signal didn't fire due to it rightly excluding the favourite, but then it didn't try to place a bet once the conditions had been met. Looking at the log it seems to have then applied the signal 4 mins later to the second favourite but then didn't fire off the bet. However it seems to work fine if the favourite is above the price set with the signal firing at the beginning of the race
13/11/2020 14:15:54: Guardian has detected that the market is suspended
13/11/2020 14:15:55: Guardian has detected that the market is in-play
13/11/2020 14:15:56: Guardian has detected that the market is now unsuspended
13/11/2020 14:19:22: [G_Auto] : Automation Signal for Wargrave: SET = 1
13/11/2020 14:20:02: Guardian has detected that the market is suspended
I've attached my rules file - does this all look ok?
This should be done sometime before they go in-play
15/11/2020 12:36:41: Guardian has detected that the market is suspended
15/11/2020 12:36:41: Guardian has detected that the market is in-play
15/11/2020 12:36:41: Guardian has detected that the market is now unsuspended
15/11/2020 12:41:29: [G_Auto] : £ 2.00 Back bet placed on Latest Exhibition at 1.26. Fully matched at 1.33. Ref: 216782719674
I've attached the latest version of my rule as I can't see where I'm going wrong!
If its still at the default setting of 1 second and you had more than 5 markets in guardian at the time then the market hasn't been refreshed to allow the rule to trigger.
This post explains how Guardian cycles and refreshes markets and how you can configure it optimally
viewtopic.php?f=37&t=11491
200 milliseconds but I have restrict refresh on to limit the effects of that. Am I right in thinking that the rule was right not to trigger though? The issue is that it placed the bet when it shouldn't have as the favourite didn't meet the criteria.Dallas wrote: ↑Sun Nov 15, 2020 1:08 pmWhat refresh rate are you using in Guardian ?reids wrote: ↑Sun Nov 15, 2020 12:43 pmThanks, now amended, however something still isn't right. For instance at the 12.35 Punchestown - Latest Exhibition went off at 1.78 - no signal was correctly set, however it still placed a bet on it.
15/11/2020 12:36:41: Guardian has detected that the market is suspended
15/11/2020 12:36:41: Guardian has detected that the market is in-play
15/11/2020 12:36:41: Guardian has detected that the market is now unsuspended
15/11/2020 12:41:29: [G_Auto] : £ 2.00 Back bet placed on Latest Exhibition at 1.26. Fully matched at 1.33. Ref: 216782719674
I've attached the latest version of my rule as I can't see where I'm going wrong!
If its still at the default setting of 1 second and you had more than 5 markets in guardian at the time then the market hasn't been refreshed to allow the rule to trigger.
This post explains how Guardian cycles and refreshes markets and how you can configure it optimally
viewtopic.php?f=37&t=11491
Yes the rule is set up right, and the only reason for the signal not setting is the market not being refreshed in that time but your Guardian settings should certainly allowed that to happenreids wrote: ↑Sun Nov 15, 2020 1:31 pm200 milliseconds but I have restrict refresh on to limit the effects of that. Am I right in thinking that the rule was right not to trigger though? The issue is that it placed the bet when it shouldn't have as the favourite didn't meet the criteria.Dallas wrote: ↑Sun Nov 15, 2020 1:08 pmWhat refresh rate are you using in Guardian ?reids wrote: ↑Sun Nov 15, 2020 12:43 pm
Thanks, now amended, however something still isn't right. For instance at the 12.35 Punchestown - Latest Exhibition went off at 1.78 - no signal was correctly set, however it still placed a bet on it.
15/11/2020 12:36:41: Guardian has detected that the market is suspended
15/11/2020 12:36:41: Guardian has detected that the market is in-play
15/11/2020 12:36:41: Guardian has detected that the market is now unsuspended
15/11/2020 12:41:29: [G_Auto] : £ 2.00 Back bet placed on Latest Exhibition at 1.26. Fully matched at 1.33. Ref: 216782719674
I've attached the latest version of my rule as I can't see where I'm going wrong!
If its still at the default setting of 1 second and you had more than 5 markets in guardian at the time then the market hasn't been refreshed to allow the rule to trigger.
This post explains how Guardian cycles and refreshes markets and how you can configure it optimally
viewtopic.php?f=37&t=11491
There has since been another post on the forum for the same race, runner and who's rule was armed at a similar time to yours so 'im not exactly sure what could of happened at the moment just trying to piece it together
Interesting. I've just done another test with the 14.40 at Fontwell. I cleared all other markets out just to completely eliminate the possibility of the refresh causing the issue. Nassalam was the favourite and went off at 2.06. No signal was again correctly set, but again it placed the bet when it shouldn't have...Dallas wrote: ↑Sun Nov 15, 2020 1:59 pmYes the rule is set up right, and the only reason for the signal not setting is the market not being refreshed in that time but your Guardian settings should certainly allowed that to happenreids wrote: ↑Sun Nov 15, 2020 1:31 pm200 milliseconds but I have restrict refresh on to limit the effects of that. Am I right in thinking that the rule was right not to trigger though? The issue is that it placed the bet when it shouldn't have as the favourite didn't meet the criteria.Dallas wrote: ↑Sun Nov 15, 2020 1:08 pm
What refresh rate are you using in Guardian ?
If its still at the default setting of 1 second and you had more than 5 markets in guardian at the time then the market hasn't been refreshed to allow the rule to trigger.
This post explains how Guardian cycles and refreshes markets and how you can configure it optimally
viewtopic.php?f=37&t=11491
There has since been another post on the forum for the same race, runner and who's rule was armed at a similar time to yours so 'im not exactly sure what could of happened at the moment just trying to piece it together
15/11/2020 14:40:30: Guardian has detected that the market is suspended
15/11/2020 14:40:31: Guardian has detected that the market is in-play
15/11/2020 14:40:31: Guardian has detected that the market is now unsuspended
15/11/2020 14:44:25: [G_Auto] : £ 2.00 Back bet placed on Nassalam at 1.28. Entirely unmatched when it initially reached the market. Ref: 216794611969
Have you checked your PC clock is synced?reids wrote: ↑Sun Nov 15, 2020 2:45 pmInteresting. I've just done another test with the 14.40 at Fontwell. I cleared all other markets out just to completely eliminate the possibility of the refresh causing the issue. Nassalam was the favourite and went off at 2.06. No signal was again correctly set, but again it placed the bet...Dallas wrote: ↑Sun Nov 15, 2020 1:59 pmYes the rule is set up right, and the only reason for the signal not setting is the market not being refreshed in that time but your Guardian settings should certainly allowed that to happen
There has since been another post on the forum for the same race, runner and who's rule was armed at a similar time to yours so 'im not exactly sure what could of happened at the moment just trying to piece it together
15/11/2020 14:40:30: Guardian has detected that the market is suspended
15/11/2020 14:40:31: Guardian has detected that the market is in-play
15/11/2020 14:40:31: Guardian has detected that the market is now unsuspended
15/11/2020 14:44:25: [G_Auto] : £ 2.00 Back bet placed on Nassalam at 1.28. Entirely unmatched when it initially reached the market. Ref: 216794611969
If this is out by just a few seconds it could mess up your triggers.
I've just ran it on several markets here including some Greyhounds and its triggered and set the signal fine every time it should have done
I've synced it to double check, there's a few low price favourites in the next hour or so, so will see if that changes anything. It does correctly set and fire for races where the favourite is above 2.2 (such as the below 15.00 at Cheltenham), just doesn't seem to be excluding the favourite if it's below 2.2Dallas wrote: ↑Sun Nov 15, 2020 2:56 pmHave you checked your PC clock is synced?reids wrote: ↑Sun Nov 15, 2020 2:45 pmInteresting. I've just done another test with the 14.40 at Fontwell. I cleared all other markets out just to completely eliminate the possibility of the refresh causing the issue. Nassalam was the favourite and went off at 2.06. No signal was again correctly set, but again it placed the bet...Dallas wrote: ↑Sun Nov 15, 2020 1:59 pm
Yes the rule is set up right, and the only reason for the signal not setting is the market not being refreshed in that time but your Guardian settings should certainly allowed that to happen
There has since been another post on the forum for the same race, runner and who's rule was armed at a similar time to yours so 'im not exactly sure what could of happened at the moment just trying to piece it together
15/11/2020 14:40:30: Guardian has detected that the market is suspended
15/11/2020 14:40:31: Guardian has detected that the market is in-play
15/11/2020 14:40:31: Guardian has detected that the market is now unsuspended
15/11/2020 14:44:25: [G_Auto] : £ 2.00 Back bet placed on Nassalam at 1.28. Entirely unmatched when it initially reached the market. Ref: 216794611969
If this is out by just a few seconds it could mess up your triggers.
I've just ran it on several markets here including some Greyhounds and its triggered and set the signal fine every time it should have done
15/11/2020 14:59:55: [G_Auto] : Automation Signal for Tegerek: SET = 1
15/11/2020 15:02:14: Guardian has detected that the market is suspended
15/11/2020 15:02:16: Guardian has detected that the market is in-play
15/11/2020 15:02:16: Guardian has detected that the market is now unsuspended
15/11/2020 15:06:14: [G_Auto] : £ 2.00 Back bet placed on The Shunter at 1.28. Fully matched at 1.28. Ref: 216796845650
15/11/2020 15:06:28: Guardian has detected that the market is suspended
15/11/2020 15:37:53: Guardian has detected that the market is suspended
15/11/2020 15:37:54: Guardian has detected that the market is in-play
15/11/2020 15:37:54: Guardian has detected that the market is now unsuspended
15/11/2020 15:41:34: [G_Auto] : £ 2.00 Back bet placed on Third Time Lucki at 1.2. Fully matched at 1.2. Ref: 216800586206
15/11/2020 15:42:12: Guardian has detected that the market is suspended
Signal again correctly didn't fire as Third Time Lucki was below the conditions set, yet it still didn't exclude Third Time Lucki and placed the bet when it shouldn't have. Baffling! Should the signal be set for selection or the market?
15/11/2020 15:37:54: Guardian has detected that the market is in-play
15/11/2020 15:37:54: Guardian has detected that the market is now unsuspended
15/11/2020 15:41:34: [G_Auto] : £ 2.00 Back bet placed on Third Time Lucki at 1.2. Fully matched at 1.2. Ref: 216800586206
15/11/2020 15:42:12: Guardian has detected that the market is suspended
Signal again correctly didn't fire as Third Time Lucki was below the conditions set, yet it still didn't exclude Third Time Lucki and placed the bet when it shouldn't have. Baffling! Should the signal be set for selection or the market?
You currently have it to test if the price is greater than 2.2, and that's what I was checking workedreids wrote: ↑Sun Nov 15, 2020 3:10 pm
I've synced it to double check, there's a few low price favourites in the next hour or so, so will see if that changes anything. It does correctly set and fire for races where the favourite is above 2.2 (such as the below 15.00 at Cheltenham), just doesn't seem to be excluding the favourite if it's below 2.2
If you want it to exclude runners where the fav is below 2.2 the condition needs changing to;
Less than 2.22
Aha! Perfect, knew I messed it up somehow and that looks like the answer! Many thanks!Dallas wrote: ↑Sun Nov 15, 2020 4:02 pmYou currently have it to test if the price is greater than 2.2, and that's what I was checking workedreids wrote: ↑Sun Nov 15, 2020 3:10 pm
I've synced it to double check, there's a few low price favourites in the next hour or so, so will see if that changes anything. It does correctly set and fire for races where the favourite is above 2.2 (such as the below 15.00 at Cheltenham), just doesn't seem to be excluding the favourite if it's below 2.2
If you want it to exclude runners where the fav is below 2.2 the condition needs changing to;
Less than 2.22
-
- Posts: 2
- Joined: Wed Dec 02, 2020 7:51 am
Hi,
For me this bot works well even with the "time" condition.
So I would like to know how it is possible to change the stake depending if the last bet with the bot is win or loose.
Thanks by advance.
Lucien
For me this bot works well even with the "time" condition.
So I would like to know how it is possible to change the stake depending if the last bet with the bot is win or loose.
Thanks by advance.
Lucien
- wearthefoxhat
- Posts: 3207
- Joined: Sun Feb 18, 2018 9:55 am
@Dallas,
I'm testing out the original bot settings on page 1, by nominating a selection to be backed in-play. (not just anything)
The test includes, backing In-Play with 2 (fixed odds conditions) one for the Actual BSP to be in certain range and one for the Lay Price trigger as per the original bot.
The reasoning is the selection, although fancied to win, needs to be a value BSP and be confirmed to be running well In-Play.
I'm testing out the original bot settings on page 1, by nominating a selection to be backed in-play. (not just anything)
The test includes, backing In-Play with 2 (fixed odds conditions) one for the Actual BSP to be in certain range and one for the Lay Price trigger as per the original bot.
The reasoning is the selection, although fancied to win, needs to be a value BSP and be confirmed to be running well In-Play.