automation advice please

Advanced automation available in Guardian - Chat with others and share files here.
User avatar
melvidge
Posts: 16
Joined: Wed Sep 06, 2017 11:48 am

Dallas wrote:
Sun Dec 03, 2017 12:13 pm

Finally When greening all to a profit or loss you only need the one rule for each (otherwise if one is reached at the moment it will fire 3 green up orders simultaneously)


Would I be correct in suggesting (a method I use) as an alternative to having separate 'green up' or 'close selection..' rules for each runner - especially useful if needed for many runners, or the field?..

I use a single rule, but set a signal, under the Signals tab (for example named 'greened') 'for the selection', and then add the rule 'signal set condition' (for the selection) -> 'named - "greened"' -> 'for the selection' -> 'NOT set with a value', and then 'Allow rule to trigger' in the general tab, can be set to whatever, obviously the same or more than, and in the original example, of at least 3. This would then just trigger once for each selection/runner.

If I wanted to allow the rule to trigger, say just 3 times only on per selection, then would instead, 'increment' the signal (named 'greened') for the Selection (starting at '0') then have the rule in conditions: 'Signal Value Condition' -> 'The Value of The Signal Named' (in this case, 'greened') -> 'For - The Selection' -> 'Is Less Than: 4' (to allow it to trigger 3 times) -> 'Current (any selection)'.
stefan084
Posts: 111
Joined: Tue Oct 31, 2017 5:52 pm

ok dallas, here is the lay bet part I talked about.
dallas1.png
dallas2.png
dallas3.png
You do not have the required permissions to view the files attached to this post.
stefan084
Posts: 111
Joined: Tue Oct 31, 2017 5:52 pm

dallas4.png
You do not have the required permissions to view the files attached to this post.
User avatar
Dallas
Posts: 22674
Joined: Sun Aug 09, 2015 10:57 pm
Location: Working From Home

That all looks fine also Stefan0084
From what i can see there it should work for you?
User avatar
Kafkaesque
Posts: 886
Joined: Fri Oct 06, 2017 10:20 am

Dallas wrote:
Sun Dec 03, 2017 12:17 pm
Kafkaesque wrote:
Sun Dec 03, 2017 1:50 am
I've often found that automation fires in a second bet at the same as the first bet is matched. It seems to fire in that second bet, before the offset is placed, as there's a temporary gap with the unmatched bets on the selection being zero. I've worked with various settings and the refresh rates, but have been unable to come up with solution which works anywhere close to all the time.
When trading in-play to account for the delay time If you use a 'fill or kill bet time condition' is greater than 2 secs (or any time longer than the IP delay) that will avoid any bets being triggered whilst waiting for the offset being placed
Hijacking a bit here :)

Cheers Dallas. As I mentioned, i don't do much in-play, but it's duly noted for later use :) Any ideas towards how to set the automation so that it doesn't do it pre?
User avatar
cmuddle
Posts: 160
Joined: Tue Apr 18, 2017 7:12 pm

Dallas wrote:
Sun Dec 03, 2017 12:17 pm
Kafkaesque wrote:
Sun Dec 03, 2017 1:50 am
I've often found that automation fires in a second bet at the same as the first bet is matched. It seems to fire in that second bet, before the offset is placed, as there's a temporary gap with the unmatched bets on the selection being zero. I've worked with various settings and the refresh rates, but have been unable to come up with solution which works anywhere close to all the time.
When trading in-play to account for the delay time If you use a 'fill or kill bet time condition' is greater than 2 secs (or any time longer than the IP delay) that will avoid any bets being triggered whilst waiting for the offset being placed


I have problems trading with back and lay in-play with guardian offset bets which do not trigger. The bet is placed but the offset bet either does not trigger or disappears.
Does it have to do also with the 2 secs fill or kill ? My automation is set to 2 secs fill or kill.
Or is it something else?
User avatar
ShaunWhite
Posts: 9731
Joined: Sat Sep 03, 2016 3:42 am

If you're backing pre and you need your offset to remain in-play. You'll need to have a rule that changes the status of your unmatched trades to 'Keep' otherwise BF will cancel them.

And yes, 2s fill/kill is not enough as bets are delayed by at least 2s in-play by BF
Dipstick
Posts: 116
Joined: Tue Feb 17, 2015 10:08 pm

Have had an issue twice with an automation rule this morning, Can anyone help please - possibly Dallas, but trying to see if anyone else has seen the same issue.

I have a green up rule which has a "Not in play" indicator as well as a "don't fire until 30 secs after unsuspension" condition. But twice today, the rule has kicked in immediately after going in play (and its related suspension). It kicks in 1 second after and I think it might be a timing issue on the telecomms that I can do nothing about. Can anyone help me stop this please. Log details below:

15/12/2017 08:38:20: Guardian has detected that the market is in-play
15/12/2017 08:38:20: Guardian has detected that the market is suspended
15/12/2017 08:38:21: Guardian has detected that the market is now unsuspended
15/12/2017 08:38:21: [G_Auto] : Greened up 3. Backbench Blues by Laying 1.76 at 24
15/12/2017 08:38:21: [G_Auto] : Greened up 6. Toni May by Laying 13.39 at 3.95
15/12/2017 08:38:22: [G_Auto] : Greened up 2. Dharmony by Backing 0.73 at 3.25
15/12/2017 08:40:08: Guardian has detected that the market is suspended

Thanks

Dipstick
User avatar
Dallas
Posts: 22674
Joined: Sun Aug 09, 2015 10:57 pm
Location: Working From Home

Dipstick wrote:
Fri Dec 15, 2017 8:51 am
Have had an issue twice with an automation rule this morning, Can anyone help please - possibly Dallas, but trying to see if anyone else has seen the same issue.

I have a green up rule which has a "Not in play" indicator as well as a "don't fire until 30 secs after unsuspension" condition. But twice today, the rule has kicked in immediately after going in play (and its related suspension). It kicks in 1 second after and I think it might be a timing issue on the telecomms that I can do nothing about. Can anyone help me stop this please. Log details below:

15/12/2017 08:38:20: Guardian has detected that the market is in-play
15/12/2017 08:38:20: Guardian has detected that the market is suspended
15/12/2017 08:38:21: Guardian has detected that the market is now unsuspended
15/12/2017 08:38:21: [G_Auto] : Greened up 3. Backbench Blues by Laying 1.76 at 24
15/12/2017 08:38:21: [G_Auto] : Greened up 6. Toni May by Laying 13.39 at 3.95
15/12/2017 08:38:22: [G_Auto] : Greened up 2. Dharmony by Backing 0.73 at 3.25
15/12/2017 08:40:08: Guardian has detected that the market is suspended

Thanks

Dipstick
Except for timing issues i cant see anything else that would cause it. Can you post some screenshots of the green up rule settings you were using, (general and conditions tabs etc)
Post Reply

Return to “Bet Angel - Automation”