Fix Order by BSP Workaround

[simonv74]

The latest updates are superb.

However, I would still like to see an 'fix market order by BSP' option to fully utilise the option now BSP can be stored as a value.

There is a workaround you can do for this already,
If you go into Settings > Edit Settings > Automation and change the 'Favouritism sort uses' to 'Last Traded Price'

Then on your fix order rule set it to trigger at 00:00:00 in-play

I have tested with this exhaustively, LTP does not = BSP therefore when a few runners are very closely priced at the off the LTP 'fix' isn't a true reflection of BSP order.

[simonv74]

For example, in the 13.50 at Chester:

10/05/2019 13:51:19: [G_Auto] : Store Value for Another Batt: BSP = 10.528
10/05/2019 13:51:19: [G_Auto] : Store Value for Another Batt: LTP = 11
10/05/2019 13:51:19: [G_Auto] : Store Value for Dragons Tail: BSP = 13.186
10/05/2019 13:51:19: [G_Auto] : Store Value for Dragons Tail: LTP = 13.5
10/05/2019 13:51:19: [G_Auto] : Store Value for Gabrial The Saint: BSP = 12.5
10/05/2019 13:51:19: [G_Auto] : Store Value for Gabrial The Saint: LTP = 12

These were 3/5/4 in the BSP order but were 2/6/4 in the fixed order at the off time.

[Dallas]

Following on from a post on the release thread I've just done some tests on over a dozen of this afternoons races and so far the method of fixing the order @ 00:00:00 using LTP has been identical to the BSP order, the closest it came to a false trigger was in the 4th image were two had a BSP 32

Depending on how accurate you need it and the runners your targeting it does offer a decent workaround if you want to fix the BSP order

1.JPG

2.JPG

3.JPG

4.JPG

5.JPG

[jimibt]

Following on from a post on the release thread I've just done some tests on over a dozen of this afternoons races and so far the method of fixing the order @ 00:00:00 using LTP has been identical to the BSP order, the closest it came to a false trigger was in the 4th image were two had a BSP 32

Depending on how accurate you need it and the runners your targeting it does offer a decent workaround if you want to fix the BSP order

1.JPG

2.JPG

3.JPG

4.JPG

5.JPG

nice one as ever -any chance of adding the workaround steps??

[Dallas]

nice one as ever -any chance of adding the workaround steps??

That would help wouldn't it

If you go into;
Settings > Edit Settings > Automation
and change the 'Favouritism sort uses' to 'Last Traded Price'

Then on your 'fix market order' rule set it to trigger at 00:00:00 in-play

Remaining rules can then be applied to 'Selection by Betfair order of favouritism'
and that will be identical to there BSP order

(Just to clarify the logs and the storing of values are not required they were just for purposes of demonstrating how close the LTP is to the BSP)

[jimibt]

nice one as ever -any chance of adding the workaround steps??

That would help wouldn't it

If you go into;
Settings > Edit Settings > Automation
and change the 'Favouritism sort uses' to 'Last Traded Price'

Then on your 'fix market order' rule set it to trigger at 00:00:00 in-play

Remaining rules can then be applied to 'Selection by Betfair order of favouritism'
and that will be identical to there BSP order

(Just to clarify the logs and the storing of values are not required they were just for purposes of demonstrating how close the LTP is to the BSP)

perfect!!

[simonv74]

And again.

10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: BSP = 11.5
10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: LTP = 10

I ended up backing the 4th placed BSP and missed the 3rd placed winner (who I wanted to automatically back).

[jimibt]

And again.

10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: BSP = 11.5
10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: LTP = 10

I ended up backing the 4th placed BSP and missed the 3rd placed winner (who I wanted to automatically back).

unless you're privvy to how BSP is calculated at BF's end, I think that trying to preemptively coorce LTP->BSP will have shortcomings. I also (imho) don't pay much store in positions (i.e. back pos 3 if the odds are 10 etc) and prefer to think of those as randomly arbitary...

that said, it is a tad annoying if you have a rule that TRIES to use BSP and doesn't play ball...

[Dallas]

And again.

10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: BSP = 11.5
10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: LTP = 10

I ended up backing the 4th placed BSP and missed the 3rd placed winner (who I wanted to automatically back).

Did you also change the fav sort in the automation settings as advised?
If this is still set to the default 'back price' then your likely to get more wrong than right as there be gaps all over at the time your fixing the order

[simonv74]

And again.

10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: BSP = 11.5
10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: LTP = 10

I ended up backing the 4th placed BSP and missed the 3rd placed winner (who I wanted to automatically back).

Did you also change the fav sort in the automation settings as advised?
If this is still set to the default 'back price' then your likely to get more wrong than right as there be gaps all over at the time your fixing the order

Yes, I did.

It would just be easy if the software could sort by BSP! The 'workaround' is flawed...

Can it be implemented? I will put it in feature requests, for what it's worth.

[simonv74]

And again.

10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: BSP = 11.5
10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: LTP = 10

I ended up backing the 4th placed BSP and missed the 3rd placed winner (who I wanted to automatically back).

unless you're privvy to how BSP is calculated at BF's end, I think that trying to preemptively coorce LTP->BSP will have shortcomings. I also (imho) don't pay much store in positions (i.e. back pos 3 if the odds are 10 etc) and prefer to think of those as randomly arbitary...

that said, it is a tad annoying if you have a rule that TRIES to use BSP and doesn't play ball...

I am just storing the values to show how there's a disparity between LTP and BSP at off time hence wrong horses are getting backed.

[Dallas]

And again.

10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: BSP = 11.5
10/05/2019 17:22:53: [G_Auto] : Store Value for Callipygian: LTP = 10

I ended up backing the 4th placed BSP and missed the 3rd placed winner (who I wanted to automatically back).

Did you also change the fav sort in the automation settings as advised?
If this is still set to the default 'back price' then your likely to get more wrong than right as there be gaps all over at the time your fixing the order

Yes, I did.

It would just be easy if the software could sort by BSP! The 'workaround' is flawed...

Can it be implemented? I will put it in feature requests, for what it's worth.

The suggestion is still on the release thread so developers will see it and if there's enough support for it then no reason why it can't be added in a future update.

It's odd that the workaround is not working for you though, I've suggested it to many other people over the years and its worked for all them

[simonv74]

It's accurate to a certain degree but in the 1% of cases where it doesn't work then it's costly!

I am having to make rules like this to try and catch ones that move in position from LTP to BSP but there are still some that get missed.



If there was one rule just to be able to fix the order by BSP then I wouldn't need a whole array of extra rules, that may or may not work.

[Dallas]

What sort of refresh rate are you using?

I was doing 1 market only at 20ms

[simonv74]

All markets are in Guardian, refresh restricted to 10 seconds before the off (so Guardian only processing one market at a time), streaming with 20ms refresh on a quad core VPS with 40Gbit network speed and sub 10ms ping.

Automation favouritism ordering is by LTP and fixing the order of selections is at 00:00:00 in-play.

It's as optimal as I can manage it but it still won't solve the fact that LTP order is not the same as BSP order in every race, some will still slip through.