"Fix the Order of the MarketSelections" not in order!

[firlandsfarm]

I'm wanting to fix the order by favouritism and then assign a Stored Value to each so the 3rd Favourite will have a Stored Value of "Favourite"=3 … the 5th favourite would be "5" etc. The values are being assigned no problem but in Bf order, not favouritism. I am attaching the baf but basically here's what I am doing …

Rule 1: Fix Favourite Order
Fix the Order of the Market Selections: Selection box defaulted to "in row 1 (Betfair order)". I have tried other options but with no effect. In "Settings" the order for Favouritism is based upon Back Price.
No other action with this rule.

Rule 2: Assign Stored Values and Signals
Set/Modify a Signal Only: Any Selection
Conditions: Check "Favourite" Signal NOT set with a value for Current selection then assign the signal a value of 1
Stored Values:
1. Store a value "Runners" for the Market and increment value by 1 as selections are cycled through
2. Store a value "Favourite" for the Current Selection equal to the value of "Runners" as the selections are cycled through

Everything works fine in assigning values except that the order of the runners is as the Bf order and not in favourite order.

ListByFavouritism.baf

[Dallas]

I've only looked at it briefly in notepad but from what I can see you're just storing value and setting a signal (which you've named favourite) on ANY selection
Then repeating that every half second on ANY other selection you've not yet set a signal on, so eventually, they'll all have a signal named fav on them regardless of there position

Try applying the rule SV and signal rule to the favourite

[firlandsfarm]

I've only looked at it briefly in notepad but from what I can see you're just storing value and setting a signal (which you've named favourite) on ANY selection

Yes because at this stage that's all I want. I will add the bet trigger rules later but there's no point if I cannot have an identifiable order of favouritism. The Signal "Favourite" is simply to record that that runner has been 'processed'. The Stored Value "Favourite" would hold the runner's actual position in order of favouritism if the runners were being processed in order of favouritism as I had expected.

Then repeating that every half second on ANY other selection you've not yet set a signal on, so eventually, they'll all have a signal named fav on them regardless of there position

Yes but the Signal is simply to prevent a runner being processed more than once ... and by the time every runner has been processed they will all also have a Stored Value "Favourite" that should be their position in order of favouritism. The problem is not the setting of the number, the problem is that the Fix Order of the Market is not fixing in order of favouritism, it is in Betfair Order. Maybe you will see it better if you apply it to a US or AUS race as favouritism and Betfair Order are usually the same for UK/IRE races.

Try applying the rule SV and signal rule to the favourite

Sorry Dallas but I don't know what you mean but as I have said the problem in the result is not that the values are being incorrectly applied it is that the runners are in the wrong order.

The 17:25 at Tampa is timely. I am attaching screen grabs of the Odds and the Log ...

odds.JPG

log.JPG

... from which you will notice that the clear second favourite is "Dig In" who is last in the Betfair order but unfortunately remains last despite the Fix in Order of Favouritism rule.

I'm open to achieving this another way but when I posted the problem I didn't receive any responses so this is my attempt to do it. I want to be able to identify which runner is where in the order of favouritism so that my bet trigger can say … fire a bet on the runner if the SV "Favourite" for that runner = N. I can think of a possible alternative but more complicated way of doing it but thought I would try and find out why the Fix Order rule does not seem to be working.

[firlandsfarm]

Dallas, one thought that has just crossed my mind and may explain the cause of the problem is could the "Fix the Order of the Market Selections" (by favouritism) only fix for the purposes of the "by Position (Sorted in Order of Favouritism)" option in the "Selection (conditions only)" box and not for any other actions? Just a thought.

[Dallas]

When you apply a rule (any rule) to ANY selection by default it starts with the selection in row 1 then works its way through triggering on whatever selection meets its criteria first
Whether you have fixed the order of market selection or not won't have any effect on this, a rule applied to ANY will still start checking from BF row 1 upwards.

When you do fix the order it remembers both the Betfair row index and Betfair order of favouritism (so no matter how the prices change or if a runner is withdrawn it will still remember that order until the market closes or you run a unfix market order rule) you can then apply any rule to either a selection in Betfair row index OR Betfair order of favouritism and know its order won't have changed since it was fixed

[firlandsfarm]

When you apply a rule (any rule) to ANY selection by default it starts with the selection in row 1 then works its way through triggering on whatever selection meets its criteria first
Whether you have fixed the order of market selection or not won't have any effect on this, a rule applied to ANY will still start checking from BF row 1 upwards.

So the Fix Order rule does only fix it for the Selection box and no other actions as I thought. That is not what I was expecting from it's definition but I now know it is of no help to achieve my task of an identifiable favouritism order.

When you do fix the order it remembers both the Betfair row index and Betfair order of favouritism (so no matter how the prices change or if a runner is withdrawn it will still remember that order until the market closes or you run a unfix market order rule) you can then apply any rule to either a selection in Betfair row index OR Betfair order of favouritism and know its order won't have changed since it was fixed

Yes, it's great that it remembers that order but the disappointment is that it is only for the purposes of Selection of a runner and no other purpose. The 'favorite' I want to place the bet on is a function of many things ... number of runners, odds distibution etc so will vary from race to race ... this is why I need to be able to indentify which runner is the Nth favourite.

Is BA able to identify and store/use the favouritism order of the runners ... the 'selection by favoritism' is not viable in this instance because I cannot link it to a calculated SV. Is there a way to achieve that? My thought was to place a bet on a runner where the Favourite SV equals the required favourite. The enhancement of the Stored Value feature is great but I'm thinking some other aspects of BA now need to catch up with some of the things the SV facility can do.

[sa7med]

Does this get fixed in excel also? Will non runners be left as blank instead of moving each runner up 1? If so this would make my sheet a lot simpler.