Laying the lowest priced horse in an odds range

[GBob76]

I've got the following automation set up:

Rule type: Place Lay Bet
In-play time:
Arm at 00:00:01
until 00:00:02
1 trigger
Applies to:Any selection

Parameters:
Custometicks above Actual SP - Ticks = 0
Fixed Amount £

Conditions:
Fixed Odds Condition - Back price > 3.45 (on current selection)
Fixed Odd Condition - Back price < 4.6 (on current selection)

This works on laying the horses with odds in the range but I want to limit it to laying only the lowest priced horse in the range. I'm struggling to find a way to get this to work.

[tommyc333]

This seems like it should be really easy, but I had a look out of interest and couldn't find an easy way.

One method I have found that works, but is a little convoluted, is to use a 'Store a value calculated from a range of values' SV, to identify the lowest price based on SV's you'd need to apply to each selection.

Once you've identified the lowest price, you could then append the SelectionID to it, and then use a 'Stored Value condition' on the Lay bet rule to only trigger if the appended value with the SelectionID matched the original stored price and SelectionID.

Convoluted, although it does work. Most likely there will be a better way!

[GBob76]

Thanks.

Your response got me looking at Custom rankings too and i think I've come up with another solution:

Rule 1
General:
Rule type: Update Custom Ranking of Selections
Always Armed
Unlimited triggers
Rearm every refresh
Selection _ In position 1 (sorted in order of favouritism)
Parameters:
Asign ranking to: Custom ranking 1
Rank by: Back price - Ascending order
Conditions:
Group
Back price > 3.45 (Selection - Current)
Back price < 4.6 (Selection - Current)
End Group

Rule 2
Rule type: Place Lay Bet
In-play time:
Arm at 00:00:01
until 00:00:02
1 trigger
Applies to: rank 1 in Custom Ranking 1

Parameters:
Custom ticks above Actual SP - Ticks = 0
Fixed Amount £

Cheers.

[tommyc333]

I don't think that will work, the custom ranking rule would only fire if the current fav was in that price band, and if it was, it would just rank every selection in ascending order so you'd always just end up laying the fav, regardless of price.

Custom Ranking is good for when you want to rank Any (which in effect is Every) selection according to a criteria, eg. if you wanted to know the runner which had drifted the most over the last x period of time.

[jamesedwards]

I would do it like this. Starts with 1st fav then works it's way up until it finds a selection with the desired odds criteria, then stops.

test 3.baf

[Dabbla]

Here’s another approach, True or false is it within the price range.

LOW_ODDS.baf

NOT tested.

[jtrader]

Jamesedwards and Dabbla as usually provided quite effective and clear logic .baf files and you could try in practice mode that file too.

If you change times to 'event start time' it's almost sure that it couldn't be triggered as should,cause of events delay or starts earlier.

I set the time 'in-play' ,but it's not any guarantee that bet will be matched too,cause of SP fast move.And you could try in practice mode

LAY_LOWPR_RANGE.baf

Not tested too..