Fill/kill timings

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
Sovereign
Posts: 39
Joined: Wed May 10, 2017 3:12 pm

Hello all,

I'm trying to make further progress with an in running horse market automation file. I have it working roughly how I want it to, but to make some improvements in trying to deal with bets that aren't matched (which happens occasionally), I'm trying to develop a fill/kill rule.

I want to ensure that if my bet isn't matched almost immediately, I want to cancel it and try again. I have set a fill/kill delay of 0.2 seconds, a trigger of up to 5 with a 1 second delay, and the following conditions:

Time since active fill or kill > 1 second
Matched bets on the market = 0
Lay bets matched = £0
Unmatched bets on the current selection = 0

Would this be suitable, or are my timings or conditions perhaps a bit off? Is the 'time since active fill or kill' condition necessary here or is that overkill? As you can see, I'm trying to make sure that my rule doesn't try and fire more than one bet at a time if there is a current one unmatched, especially with the small timings.

Thanks for your help guys.
Sovereign
Posts: 39
Joined: Wed May 10, 2017 3:12 pm

I will test the rule with the conditions above today and see how I get on. I'm hoping with the number of conditions I have that restrict a second bet being placed, it will be tight enough (even with the small timings) to work effectively without something peculiar happening (the main risk being it trying to place two bets at the same time.)
User avatar
Dallas
Posts: 23495
Joined: Sun Aug 09, 2015 10:57 pm

Is this a in-running or pre-race automation?
Sovereign
Posts: 39
Joined: Wed May 10, 2017 3:12 pm

Dallas wrote:
Mon Jun 26, 2017 10:09 am
Is this a in-running or pre-race automation?
Hi Dallas,

This is on an in running automation rule.
User avatar
Dallas
Posts: 23495
Joined: Sun Aug 09, 2015 10:57 pm

Firstly i'de recommend the fastest time for any fill/kill is 0.5 (to allow time for internet latency between you and BF) but i'de up this to 1sec for what your doing then the rest as follows

For the 4 conditions you listed
Time since active fill or kill > 1 second
is the most important and really all you need but i'de increase to 2 secs for in-running markets to be absolutely sure another bet is not triggere during offsetting

Matched bets on the market = 0
Lay bets matched = £0

both these will stop your rule triggering once one has been matched - i assume your wanting to place multiple bets if so these need to be removed

Unmatched bets on the current selection = 0
this is fine and a good safety option to go with your time since fill/kill cond
Sovereign
Posts: 39
Joined: Wed May 10, 2017 3:12 pm

Dallas wrote:
Mon Jun 26, 2017 10:31 am
Firstly i'de recommend the fastest time for any fill/kill is 0.5 (to allow time for internet latency between you and BF) but i'de up this to 1sec for what your doing then the rest as follows

For the 4 conditions you listed
Time since active fill or kill > 1 second
is the most important and really all you need but i'de increase to 2 secs for in-running markets to be absolutely sure another bet is not triggere during offsetting

Matched bets on the market = 0
Lay bets matched = £0

both these will stop your rule triggering once one has been matched - i assume your wanting to place multiple bets if so these need to be removed

Unmatched bets on the current selection = 0
this is fine and a good safety option to go with your time since fill/kill cond
Dallas,

I hadn't even thought about the latency issue! Thanks very much for your comprehensive advice once again, I'll make the changes and test it this afternoon.

Out of curiosity (and if I were to remove the Lay bets matched =£0 and Matched bets on the market =0 conditions) if a lay bet is only partially matched before its cancelled, if another lay bet is placed, is that lay liability the remaining amount, minus the original liability of the partially matched bet?

So say I have a liability of £20 here, and my lay is matched with a liability of say £2, would any future lay stakes only be up to a liability of £18?
User avatar
Dallas
Posts: 23495
Joined: Sun Aug 09, 2015 10:57 pm

Sovereign wrote:
Mon Jun 26, 2017 10:46 am

Out of curiosity (and if I were to remove the Lay bets matched =£0 and Matched bets on the market =0 conditions) if a lay bet is only partially matched before its cancelled, if another lay bet is placed, is that lay liability the remaining amount, minus the original liability of the partially matched bet?

So say I have a liability of £20 here, and my lay is matched with a liability of say £2, would any future lay stakes only be up to a liability of £18?
No it will place the full £20 liability stake again, so if you use Lay bets matched =£0 once any amount of lay bet is matched no further lays bets will trigger

But when using fill/kill only the amount of the lay (or any opening bet) that is matched will be offset
Sovereign
Posts: 39
Joined: Wed May 10, 2017 3:12 pm

Dallas wrote:
Mon Jun 26, 2017 10:53 am
Sovereign wrote:
Mon Jun 26, 2017 10:46 am

Out of curiosity (and if I were to remove the Lay bets matched =£0 and Matched bets on the market =0 conditions) if a lay bet is only partially matched before its cancelled, if another lay bet is placed, is that lay liability the remaining amount, minus the original liability of the partially matched bet?

So say I have a liability of £20 here, and my lay is matched with a liability of say £2, would any future lay stakes only be up to a liability of £18?
No it will place the full £20 liability stake again, so if you use Lay bets matched =£0 once any amount of lay bet is matched no further lays bets will trigger

But when using fill/kill only the amount of the lay (or any opening bet) that is matched will be offset
That's as I thought, but glad to have some confirmation.

Thanks for all your help once again, Dallas! Massively appreciated.
Sovereign
Posts: 39
Joined: Wed May 10, 2017 3:12 pm

Dallas wrote:
Mon Jun 26, 2017 10:31 am
Firstly i'de recommend the fastest time for any fill/kill is 0.5 (to allow time for internet latency between you and BF) but i'de up this to 1sec for what your doing then the rest as follows

For the 4 conditions you listed
Time since active fill or kill > 1 second
is the most important and really all you need but i'de increase to 2 secs for in-running markets to be absolutely sure another bet is not triggere during offsetting

Matched bets on the market = 0
Lay bets matched = £0

both these will stop your rule triggering once one has been matched - i assume your wanting to place multiple bets if so these need to be removed

Unmatched bets on the current selection = 0
this is fine and a good safety option to go with your time since fill/kill cond
Hi Dallas,

Tried this on a few races so far this afternoon and I'm finding that, even with these timings and conditions, I'm having two bets placed.

Any ideas on how to resolve this?

Here's a partial example from my log:

26/06/2017 14:46:15: [G_Auto] : £ 2.22 Lay bet placed on Mr Skinnylegs at x. Fully matched at x. Ref: 96045104342 ( Fill or kill bet with 1 seconds delay. )
26/06/2017 14:46:16: [G_Auto] : £ 2.22 Lay bet placed on Mr Skinnylegs at x. Fully matched at x. Ref: 96045104884 ( Fill or kill bet with 1 seconds delay. )
26/06/2017 14:46:36: Guardian has detected that the market is suspended
cybernet69

I have found that you need to set it at least 1 second higher than the in-play delay.

Horses is 2 seconds + 1 = 3 seconds.

But even then sometimes BF queue transactions especially on fast in-play events.

So, setting it to 4 seconds would be better.
Sovereign
Posts: 39
Joined: Wed May 10, 2017 3:12 pm

cybernet69 wrote:
Mon Jun 26, 2017 2:58 pm
I have found that you need to set it at least 1 second higher than the in-play delay.

Horses is 2 seconds + 1 = 3 seconds.

But even then sometimes BF queue transactions especially on fast in-play events.

So, setting it to 4 seconds would be better.
Hi there,

If I set my rearm delay to 4 seconds, my fill/kill rate to 2 seconds, and then 'Time since active kill/fill' to >4, would this be enough to cover all of this, do you reckon?
cybernet69

Sovereign wrote:
Mon Jun 26, 2017 3:06 pm
cybernet69 wrote:
Mon Jun 26, 2017 2:58 pm
I have found that you need to set it at least 1 second higher than the in-play delay.

Horses is 2 seconds + 1 = 3 seconds.

But even then sometimes BF queue transactions especially on fast in-play events.

So, setting it to 4 seconds would be better.
Hi there,

If I set my rearm delay to 4 seconds, my fill/kill rate to 2 seconds, and then 'Time since active kill/fill' to >4, would this be enough to cover all of this, do you reckon?
Set the rearm to 3, fill/kill to 0.5, Time since active fill/kill to > 2.

Should be ok
Sovereign
Posts: 39
Joined: Wed May 10, 2017 3:12 pm

cybernet69 wrote:
Mon Jun 26, 2017 3:16 pm
Sovereign wrote:
Mon Jun 26, 2017 3:06 pm
cybernet69 wrote:
Mon Jun 26, 2017 2:58 pm
I have found that you need to set it at least 1 second higher than the in-play delay.

Horses is 2 seconds + 1 = 3 seconds.

But even then sometimes BF queue transactions especially on fast in-play events.

So, setting it to 4 seconds would be better.
Hi there,

If I set my rearm delay to 4 seconds, my fill/kill rate to 2 seconds, and then 'Time since active kill/fill' to >4, would this be enough to cover all of this, do you reckon?
Set the rearm to 3, fill/kill to 0.5, Time since active fill/kill to > 2.

Should be ok

I shall give these timings a go, thanks for your help!
Post Reply

Return to “Bet Angel - Automation”