Auto in-play loss limitation

[rayhigh]

Hi all, I’m struggling with automation that I’ve been trying to work out over the last week.

The strategy is I expect the 2nd fav to lose (in certain races) so lay before the off… if the 1st & 2nd favs are certain prices etc. Then, in play, if it looks like the 2nd fav could win (odds less than 2 for example) , reduce losses etc. and red up. If a loss, the 3rd part is to set a trigger to remind me to read aloud from a list of pre-prepared swear words.

The lay part is straight forward so I think I’ve got that cracked. When the 2nd fav is a genuine donkey the price never gets low enough to go to the loss limitation part so all good in that scenario.

The loss limitation part is what I’m struggling with. I’ve tried setting an in play back bet using a trigger based on the ‘back the likely winner’ baf file but sometimes it works, sometimes it doesn’t. Then redding???

I'm also covered on part 3!

Can you help?

Thanks in advance… Ray

[Dallas]

If i understand correctly you just want to close and exit the trade if the horse you have backed (2nd fav) looks like its going to win?

If so you could use the 'Green All Selections' rule type
trigger 2-3 times with a 2-3 sec re-arm
and use the conditions

'Number of Matched bets Condition'
On 'Selection'
is 'Greater' than 0

and

'Fixed odds condition'
Last traded price
'By poisiton (sorted in order of favourtism) 1
Is 'Less' than 2.0 (or whatever odds you want to exit at

That should do it

[rayhigh]

Thanks Dallas, I'll give it a try.

I have to set things up early doors as I have other stuff to do during the day so will look at the results later.

I'm also going to trigger the initial lay bet only if certain odds & # runners conditions are met so I think I have to apply number of matched bets = 1 for the green up to trigger.

Is that right?

Thanks... Ray

[Dallas]

If you use = to 1 then the green up rule will only trigger the once (afterwhich there will be more than 1 matched bet to prevent it) so if it does not fully green up equally first time it cant fire again.

Using greater than 0 the green can trigger multiple times on a selection providing its had more than one matched bet (your initial lay bet).

[rayhigh]

Look at the results from yesterday... the trigger worked 2/3 of the time, is that what you would expect?

Do I need to change the refresh rate?

Any other changes I should make?

Many thanks... Ray

[Dallas]

It should be working all of the time, but if you left it as one trigger it may only get a very small part matched before the price moved but this would count as a matched bet and therefore not trigger anymore.

The refresh rates are very important especially in-running, you should be refreshing at 200ms and only the one market (2 at the most).
This thread explains how the refresh rates and cycling of markets in guardian works.

viewtopic.php?f=37&t=11491

[rayhigh]

Hi Dallas

Yes, the refresh rate solved the issue and it was firing on four cylinders. The trick now is to suss out the lowest traded value I can get away!

As I can't watch the action live in the afternoon I'm thinking of installing a screen recorder so I can replay in the evening and see what happened when and how etc... however that'll slow my laptop down!

Regards... Ray

[rayhigh]

I'm further developing the strategy and trying to solve this -

If I decide to auto lay the 2nd fav (for example) regardless of which bf row it's in and I do that via the the 'sort via order of favourite'... how do I handle the green up element as I want Guardian to track that selection and if it goes down to 1.5, red up.

When the 2nd fav happens to be in row 2 In conditions I've been using the same row selection for green up which seems to work ok.

The 2nd fav may not be in row 2.

Hope that makes sense?

Thanks.. Ray

[Dallas]

When the 2nd fav happens to be in row 2 In conditions I've been using the same row selection for green up which seems to work ok.

If you have used the green up rule as detailed above there is no need to make any changes or apply it to any particular row, the matched bets condition will ensure its only triggers on a selection that has been backed.