Greyhounds - A stall number selection from one rule file to Dutch Forecast Market Choices in another

[smgreyuk]

Hi,

I am wanting to see how the following could be done.

1. A rule outputs a stall number from a selection being made (this bit I am fairly confident with)

2. Then, in a separate rule the stall number is used to select multiple Forecast markets to back in which it's designated to 2nd place in the market in a dutch.

- For example, the stall number of the dog is lets say 2 (in my current rule, it's basically deemed the favourite 10 seconds before the off in the Win Market for the Event)

- I want a new rule to then use the number 2 to dutch all forecast markets in where it's covering the dog in stall 2 for all of the 2nd place markets for dog 2 as back bets in the forecast event, so if it were a 6 dog race (with al stalls being used), it would dutch:
1 - 2
3 - 2
4 - 2
5 - 2
6 - 2

Or if the dog were in stall 4 for a 5 dog race (Only stalls 1,2,3,4 and 5 being used) it would dutch :
1 - 4
2 - 4
3 - 4
5 - 4
(6 - 4 doesn't exist)

Or if the dog was in stall 6 for a 5 dog race (Only stalls 1,3,4,5,6 being used) it would dutch :
1 - 6
3 - 6
4 - 6
5 - 6
(2 - 6 doesn't exist)

So it's using the Stall number SV in the original rule to select the 2nd integer where a Forecast Market exists in the new rule.

I know how to set a condition on a number of selections in a race, for me it's just understanding how the stall number integer being used can select a variable amount of forecast markets

I know row number can be selected but there seems to be too many possibilities for what row numbers would be in play

Can this be done and if so how should I approach it?

Thank you

[jamesedwards]

You can use a 'text comparison condition' that the selection must contain the relevant text, eg " - 2".

[smgreyuk]

Ah I see. So an ANY selection but coupled with the text comparison condition (which in essence filters it down to the targeted forecast selections)?

I would imagine I would need 6 back bet rules to cover each stall number possibility

Not too sure about the dutching side of that yet, but I could give this a whirl for now and work it out from there, thanks jamesedwards

[jamesedwards]

Ah I see. So an ANY selection but coupled with the text comparison condition (which in essence filters it down to the targeted forecast selections)?

I would imagine I would need 6 back bet rules to cover each stall number possibility

Not too sure about the dutching side of that yet, but I could give this a whirl for now and work it out from there, thanks jamesedwards

You would need to use EVERY selection. ANY would only trigger the first selection that satisfies the conditions. EVERY will trigger all selections that satisfy.

[smgreyuk]

Ahh, good to know. You're a fountain of Bet Angel knowledge jamesedwards, thank you yet again

[smgreyuk]

Hi There,

I have revisited this but I cannot seem to get it work and it selects all of the FC selections, rather than the ones I am trying to focus on:

Here is where I am storing the SV Number on the Win Market (Bet Angel Level as I know you cannot communicate Event SVs between The Win Market and the Forecast Market):

A.png

I added in the suffix <space>dash which should in my mind make number "X -" , looking at the log, it has done this
21/05/2025 16:52:54: [G_Auto 1] : Store Text Value (Shared) for Bet Angel: Number = 2 -
Then for the rule assigned to the Forecast Market I am putting in 6 different back rules that each with a condition on them to that are there to try and dutch all of the selections:

B.png

C.png

But all Forecast options get selected, "Dutch FC Selections if Number 1" is always triggered, regardless what the number is, and every forecast options gets backed - it seems to ignore the text condition I am putting in. Any ideas?

[jamesedwards]

It's too complicated for me to get my head around from just these images. You could attach the whole rule and someone might be able to find the issue?

[smgreyuk]

Of course:

00001 - Lay Fave Dog.baf

00002 - Dutch Fave Dog in FC.baf

00003 - Calculate Total.baf

Rules 1 and 2 above are the most important in solving this issue, but I have included file 3 in there for a complete overview.

Basically Rule 1 has the original Lay bet that stores the Stall Number (that lay fires off successfully, as does storing the number in "X -" format) - so I think the issue lies with file 2, in how the dutching conditions work.

It could be how the selection is made, I set it to EVERY like jamesedwards instructed in an earlier post

[jamesedwards]

You're not checking the selection description so it's triggering against every selection. Need a condition that checks the Number stored value AND the selection name.

z143.jpg

[smgreyuk]

Ah, okay I shall give that a go. Thanks jamesedwards

[tootall]

You need 6 rules in your F/C to check if your stored fav condition and that stored number contains - x
example if fav was Trap 1 do a text comparison on F/C selection name to exactly match one of the following
2 - 1
3 - 1
4 - 1
5 -1
6- 1

[eatyourgreens]

Hi smgreyuk

I did the attached rules file last night, I think it does all you were looking for??? I have only tested on the 4 races so far this morning and it worked fine on all of them.

It will place a £5 book% back bet on all f/c with the favourite to be in 2nd place, I am not too sure how the book % works out when there are only 5 runners, but nothing drastic happened, I only tried it in practice mode and the liability was just over £1 for each race.

Anyhow try it in practice mode and see if it does what you want.

You will need to load both the win and f/c markets into guardian and apply the rules file to both of them.

good luck!

doggy f_c fav to be 2nd.baf

[smgreyuk]

Hi eatyourgreens,

Wow, that's brilliant. Just had a look at your file, you've basically combined two of the rules into one eloquently there, by pointing it at both markets and having the fix order not to look at forecast, it's clever.

I have slightly changed my approach on this since the first post, I now want this to apply to the fave to be selected for the 1st place forecast selections and I can see how easy it would be to change that in your file you have provided.

Now this is where it will get a bit more tricky

To add a further stipulation to this, now, rather than it applying to all of the dogs that would fit the 1st fave in 1st place selections - I wanted it to apply to a subset of these based on the top two faves

So say Dog is 1 is fave from the Win Market, then I want it to only dutch two of the of the F/C selections and these selections to be ranked 1st and 2nd in back price where Dog 1 is selected to win.

For example

1 - 2 is at 10
1 - 3 is at 7
1 - 4 is at 8
1 - 5 is at 6.8
and 1-6 is at 22

I would only want it to put 1 - 5 and 1 - 3 into the dutch (bearing in mind that the actual 1st and 2nd overall faves in the full F/C selection list may not start with Dog 1)

I was looking into how to this with my approach before seeing your brilliant file.

I was going down the line of a custom rank list at first but got lost

But looking at your file, I think I'd know exactly what to do.

I'd rename the betangel sv to ba1 in the first 6 rules after fix order, then create another 6 but set to fave 2 storing in ba2

Then add a further condition to each of the back rules to satisfy both the 1st (ba1) and 2nd fave (ba2) so only these were dutched, in my mind that should work.

Finally I can easily add the original lay bet I had on the fave in my approach in this file, that should be straight forward (this went in tandem with the dutch bets).

Thank you eatyourgreens - I shall let you know how I get on with all of that

[smgreyuk]

Hi eatyourgreens,

Just to note, before I use your file out of the box today (just to get a feel for it), I see the following pop up message:

1.png

Also I have noticed that the selection part of the back rules is blank, so I have a feeling that currently won't select anything in it's current state:

2.png

My gut tells me to go with EVERY (to satisfy the condition stated), is that correct?

[smgreyuk]

Hi again, the more I look at it, I have an inkling it needs a "Text Comparison" Condition that hones in on the selection, is that right?

3.png