A couple of general Automation questions

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
User avatar
firlandsfarm
Posts: 3384
Joined: Sat May 03, 2014 8:20 am

Just looking to see if anyone can help with these problems …

Is there a way to identify on which runner an unmatched bet may be still open. I don't want to close the bet, just identify if there is one. For example, suppose I want to place a bet on any runner that meets certain conditions but not if the runner already has an unmatched bet outstanding.

Is there a way to identify which team is batting in a cricket match so that if I want to place bets on the batting team the automation can be made to switch teams at the interval (other than guess the time).

Thanks for any contibutions.
User avatar
Dallas
Posts: 23599
Joined: Sun Aug 09, 2015 10:57 pm

There is an unmatched bet condition you can use, which could be set up as;
Number of unmatched bets on selection is equal to 0

No automation conditions to test who's batting on the cricket though
User avatar
firlandsfarm
Posts: 3384
Joined: Sat May 03, 2014 8:20 am

Thanks Dallas, I'll give that a try
User avatar
firlandsfarm
Posts: 3384
Joined: Sat May 03, 2014 8:20 am

Can I add another question to this … is there a way to record the time a bet is placed as an SV? What I want to achieve is that having placed a bet when conditions are met the rule stays active but doesn't trigger another bet until X time has passed since the previous bet was triggered.
User avatar
Dallas
Posts: 23599
Joined: Sun Aug 09, 2015 10:57 pm

firlandsfarm wrote:
Wed Jun 12, 2019 3:32 pm
Can I add another question to this … is there a way to record the time a bet is placed as an SV? What I want to achieve is that having placed a bet when conditions are met the rule stays active but doesn't trigger another bet until X time has passed since the previous bet was triggered.
There isn't an option to Store the time a rule triggered as a Stored Value
But you can do one of the following
1) Arm the second rule using the arm time 'After first rule as triggered'
2) set a signal when a rule triggers, then add a 'Signal changed' condition to a following to test how long it is since that signal was set/changed
User avatar
firlandsfarm
Posts: 3384
Joined: Sat May 03, 2014 8:20 am

Hi Dallas, it's a loop so there isn't really a 'second bet' as such (it's a scalping loop) so the first suggestion maybe wouldn't fit but please tell me if it could to help my learning! :)

The second suggestion looks good. :) Thanks.
User avatar
Dallas
Posts: 23599
Joined: Sun Aug 09, 2015 10:57 pm

firlandsfarm wrote:
Wed Jun 12, 2019 5:05 pm
Hi Dallas, it's a loop so there isn't really a 'second bet' as such (it's a scalping loop) so the first suggestion maybe wouldn't fit but please tell me if it could to help my learning! :)

The second suggestion looks good. :) Thanks.
If its a loop the first option won't work, but the second will.
If on your opening bet you use 'Increment signal value'
Then on your opposing bet use
Signal Changed condition
Has the signal named (whatever you called it)
Changed between 10 and 11 secs

that would basically allow the 2nd bet to only trigger 10 secs after the first so could be used on a loop
User avatar
firlandsfarm
Posts: 3384
Joined: Sat May 03, 2014 8:20 am

Yeah, that's basically what I concluded from your initial advice thanks. But, you are saying
Dallas wrote:
Wed Jun 12, 2019 5:39 pm
Then on your opposing bet use ...
so are you proposing two place bet rules? I'm not quite following that. I was looking to set the signal value at say "1" when the automation starts and have the place bet condition set to place a bet if the signal was increased between 10 seconds and 100000 seconds ago i.e. for practical purposes, 'at least 10 seconds ago' with Increment Signal chosen and the other conditions are met.
User avatar
Dallas
Posts: 23599
Joined: Sun Aug 09, 2015 10:57 pm

firlandsfarm wrote:
Thu Jun 13, 2019 5:47 am
Yeah, that's basically what I concluded from your initial advice thanks. But, you are saying
Dallas wrote:
Wed Jun 12, 2019 5:39 pm
Then on your opposing bet use ...
so are you proposing two place bet rules? I'm not quite following that. I was looking to set the signal value at say "1" when the automation starts and have the place bet condition set to place a bet if the signal was increased between 10 seconds and 100000 seconds ago i.e. for practical purposes, 'at least 10 seconds ago' with Increment Signal chosen and the other conditions are met.
I thought you were wanting to place a bet then a follow-up bet 'X' seconds after the first was placed?
User avatar
firlandsfarm
Posts: 3384
Joined: Sat May 03, 2014 8:20 am

Dallas wrote:
Thu Jun 13, 2019 12:01 pm
firlandsfarm wrote:
Thu Jun 13, 2019 5:47 am
Yeah, that's basically what I concluded from your initial advice thanks. But, you are saying
Dallas wrote:
Wed Jun 12, 2019 5:39 pm
Then on your opposing bet use ...
so are you proposing two place bet rules? I'm not quite following that. I was looking to set the signal value at say "1" when the automation starts and have the place bet condition set to place a bet if the signal was increased between 10 seconds and 100000 seconds ago i.e. for practical purposes, 'at least 10 seconds ago' with Increment Signal chosen and the other conditions are met.
I thought you were wanting to place a bet then a follow-up bet 'X' seconds after the first was placed?
The opposing bet will be placed with an 'offset with greening' parameter and Fill or Kill to delay the offset until the initial bet is filled. What I'm looking to do is for the loop to place another new bet if the conditions are satisfied again after a certain time delay.
Post Reply

Return to “Bet Angel - Automation”