Suggestions : %age of BSP Facility

Help improve Bet Angel.
Post Reply
firlandsfarm
Posts: 274
Joined: Sat May 03, 2014 8:20 am

Sun Apr 14, 2019 5:36 pm

Can we please either have a rethink of the formula used for this or can we have a way to calculate the 'correct' odd. At present if I wanted to place a bet at 50% of BSP the formula is BSP/2 which seems correct to how the facility is worded but is not mathmatically correct for what the user is probably trying to achieve. If BSP is say 5.00 then to bet at half that is not to bet at 2.50, it is to bet at 3.00 ((BSP-1)/2+1). The current formula halves the stake as well as the odd. Half of 4/1 is not 3/2 it is 2/1. To see the error in the current formula please explain how I can place a bet at odds of 0.90? If BSP is 1.80 and I want to bet at half BSP it cannot be 0.90, an impossible odd ... it is 1.40.

User avatar
Dallas
Posts: 10896
Joined: Sun Aug 09, 2015 10:57 pm
Contact:

Sun Apr 14, 2019 6:28 pm

I'm not sure I follow the first part of your question, it sounds like you want it to use fractional odds rather than the decimal odds it currently uses?
If so the problem is it would only be able to trigger when the BSP lands on a fraction price ie, if its 5.8 then the closest fractional odds is either 6.0 (5/1) or 5.5 (9/2) so which would it use?

For the last half ie, if the decimal odds are below 2.0 then you can use stored values and adjust by using percentage price -1
But if using fractional odds I don't think you would be able to do anything when below Evens

firlandsfarm
Posts: 274
Joined: Sat May 03, 2014 8:20 am

Mon Apr 15, 2019 8:39 am

Dallas wrote:
Sun Apr 14, 2019 6:28 pm
I'm not sure I follow the first part of your question, it sounds like you want it to use fractional odds rather than the decimal odds it currently uses?
Sorry if I was not clear Dallas, I was only using fractional odds to demonstrate the error in the current formula … I fully understand how odds are presented and the inter-relationship between decimal, fractional and American odds.
Dallas wrote:
Sun Apr 14, 2019 6:28 pm
For the last half ie, if the decimal odds are below 2.0 then you can use stored values and adjust by using percentage price -1
... and it is when the BSP is below 2 that the current error is fully exposed. I have tried to work around this bug by exploring Stored Values but I cannot see an option for a Stored Value to equal the BSP of a runner. I must be doing something wrong but I can only see this …

Under the "General" tab
"Set/Modify a Stored Value Only"
"Any Selection"
then under the "Stored Values" tab
"New"
"Store a value"
"the Current Selection"
"Any Selection"
"with" (a whole list of selections but not one mentions BSP … options of "Back", "Lay" or "Last Traded" come the closest)

If I can get the BSP for all selections into stored values per selection then yes, I can do the calculation and work around the bug.

firlandsfarm
Posts: 274
Joined: Sat May 03, 2014 8:20 am

Mon Apr 15, 2019 1:37 pm

firlandsfarm wrote:
Mon Apr 15, 2019 8:39 am
… I cannot see an option for a Stored Value to equal the BSP of a runner … If I can get the BSP for all selections into stored values per selection then yes, I can do the calculation and work around the bug.
I'm thinking the new Beta release may solve it. The notes say … "Automation Rules Editor changes … On the Parameters page, bets can now be staked using an amount held in a Stored Value … On the Stored Values page, more price options are available so the SP … can be assigned to a Stored Value." I'll give it a go. :)

firlandsfarm
Posts: 274
Joined: Sat May 03, 2014 8:20 am

Tue Apr 16, 2019 4:41 pm

firlandsfarm wrote:
Mon Apr 15, 2019 1:37 pm
I'm thinking the new Beta release may solve it. The notes say … "Automation Rules Editor changes … On the Parameters page, bets can now be staked using an amount held in a Stored Value … On the Stored Values page, more price options are available so the SP … can be assigned to a Stored Value." I'll give it a go. :)
Well I gave it a go but it's not going, well not going fast enough! :(

I want to calculate odds of 50% BSP (the proper way! :) (BSP-1)*0.50 +1) for each runner and then place a bet on each. I couldn't get it to work except by experimenting to find the problem I discovered it's a matter of time … it was taking too long! The 16:50 today at Newmarket was a typical example. Here is an extract from the log …

16/04/2019 16:10:55: Guardian has detected that the market is in-play
16/04/2019 16:10:58: [G_Auto] : Store Value for Chasing Dreams: BSP-1 = 1.43 - 1 = 0.43
16/04/2019 16:10:58: [G_Auto] : Store Value for Chasing Dreams: (BSP-1)*0.50 = 0.43 * 0.5 = 0.215
16/04/2019 16:10:58: [G_Auto] : Store Value for Chasing Dreams: 50%BSP = 0.215 + 1 = 1.22
16/04/2019 16:10:58: [G_Auto] : Automation Signal for Chasing Dreams: 50%BSPCalculated = 1
16/04/2019 16:10:58: Guardian has detected that the market is now unsuspended
16/04/2019 16:11:02: [G_Auto] : Store Value for Kemble: BSP-1 = 5.769 - 1 = 4.769
16/04/2019 16:11:02: [G_Auto] : Store Value for Kemble: (BSP-1)*0.50 = 4.769 * 0.5 = 2.385
16/04/2019 16:11:02: [G_Auto] : Store Value for Kemble: 50%BSP = 2.385 + 1 = 3.4
16/04/2019 16:11:02: [G_Auto] : Automation Signal for Kemble: 50%BSPCalculated = 1
16/04/2019 16:11:06: [G_Auto] : Store Value for Bartat: BSP-1 = 17.757 - 1 = 16.757
16/04/2019 16:11:06: [G_Auto] : Store Value for Bartat: (BSP-1)*0.50 = 16.757 * 0.5 = 8.379
16/04/2019 16:11:06: [G_Auto] : Store Value for Bartat: 50%BSP = 8.379 + 1 = 9.4
16/04/2019 16:11:06: [G_Auto] : Automation Signal for Bartat: 50%BSPCalculated = 1
16/04/2019 16:11:09: [G_Auto] : Store Value for Good Vibes: BSP-1 = 19.442 - 1 = 18.442
16/04/2019 16:11:09: [G_Auto] : Store Value for Good Vibes: (BSP-1)*0.50 = 18.442 * 0.5 = 9.221
16/04/2019 16:11:09: [G_Auto] : Store Value for Good Vibes: 50%BSP = 9.221 + 1 = 10
16/04/2019 16:11:09: [G_Auto] : Automation Signal for Good Vibes: 50%BSPCalculated = 1
16/04/2019 16:11:13: [G_Auto] : Automation Signal for Chasing Dreams: Layed = 1
16/04/2019 16:11:14: [G_Auto] : £ 2.00 Lay bet placed on Chasing Dreams at 1.22. Entirely unmatched when it initially reached the market. Ref: 10040
16/04/2019 16:11:16: [G_Auto] : Automation Signal for Kemble: Layed = 1
16/04/2019 16:11:17: [G_Auto] : £ 2.00 Lay bet placed on Kemble at 3.4. Entirely unmatched when it initially reached the market. Ref: 10041
16/04/2019 16:11:20: [G_Auto] : Automation Signal for Bartat: Layed = 1
16/04/2019 16:11:21: [G_Auto] : £ 2.00 Lay bet placed on Bartat at 9.4. Entirely unmatched when it initially reached the market. Ref: 10042
16/04/2019 16:11:24: [G_Auto] : Automation Signal for Good Vibes: Layed = 1
16/04/2019 16:11:25: [G_Auto] : £ 2.00 Lay bet placed on Good Vibes at 10. Fully matched at 4.1. Ref: 10043
16/04/2019 16:11:38: [G_Auto] : Cancelling bets 10041
16/04/2019 16:11:53: Guardian has detected that the market is suspended

As you can see it's taking 4 seconds just to calculate the 50%BSP formula! (I extended the time for the rule to complete to 15 seconds when I got a hunch this was the problem but even then it only managed 4 runners.) Why is it taking so long? The rule is set to fire 50 times at 0.1 seconds rearm (I need to process this part ASAP) but it only managed to fire 4 times in the 15 seconds as shown in the log above. I can confirm no other rule is due to run in this period … all other rules either cease at the scheduled off or start at 15 seconds after the race goes in-play (the bet placer). I can't believe it's the increased flow of traffic as soon as the market goes in play because by the time it gets to the second runner it's already 7 seconds after going in-play! Am I doing something wrong because the Grand National would take 2 mins 40 seconds before a bet is placed at that rate!

BTW the Stored Value calculations are stacked within one rule, just in case it makes a difference.

Bet Angel
Bet Angel
Bet Angel
Posts: 3627
Joined: Tue Apr 14, 2009 3:47 pm

Tue Apr 16, 2019 4:52 pm

Have a look at how often you are allowing the market to refresh.
For top speed, use Streaming and use the 'auto switch Bet Angel market' option in Guardian to put the market into the main trading window. If not, use restricted refresh option in Guardian to optimise the refresh.

https://www.betangel.com/user-guide/upd ... cling.html

firlandsfarm
Posts: 274
Joined: Sat May 03, 2014 8:20 am

Wed Apr 17, 2019 10:12 am

I think it would be better to switch this to the Beta 1.52 topic (viewtopic.php?f=46&t=18643&p=185113&p185113) so will respond there.

firlandsfarm
Posts: 274
Joined: Sat May 03, 2014 8:20 am

Wed Apr 17, 2019 10:19 am

wrong posting location! :(
Last edited by firlandsfarm on Wed Apr 17, 2019 10:40 am, edited 3 times in total.

User avatar
Dallas
Posts: 10896
Joined: Sun Aug 09, 2015 10:57 pm
Contact:

Wed Apr 17, 2019 10:19 am

It's not related to the new beta version, Stored values have been around for a few versions and as it was pointed out in the beta thread they are capable of 100s of calculations per second (several of the example files I have uploaded in the shared files section use several stored values in a rule and all trigger fine) so as per what was said to you in the beta thread the issue will be down to your Guardian settings and refreshing rates or perhaps the way you have the rules set up and the rearm times etc.

If you want to upload the rules file here i'll check it for you

firlandsfarm
Posts: 274
Joined: Sat May 03, 2014 8:20 am

Wed Apr 17, 2019 10:39 am

Bet Angel wrote:
Tue Apr 16, 2019 4:52 pm
Have a look at how often you are allowing the market to refresh.
For top speed, use Streaming and use the 'auto switch Bet Angel market' option in Guardian to put the market into the main trading window. If not, use restricted refresh option in Guardian to optimise the refresh.

https://www.betangel.com/user-guide/upd ... cling.html
Bet Angel wrote:
Tue Apr 16, 2019 5:48 pm
Bet Angel can process hundreds of Automation stored values per second, so as we posted on the other thread, it looks like you're just not refreshing that market quickly enough. The market is probably just running in a refresh cycle with many other markets in Guardian without any optimisation.
The suggestions I made in the other thread should help and the link to the user guide fully explains about Guardian's cycling.
Thanks for the input. I can't say now what the settings were because I closed BA down overnight but I will monitor today. But, I have just opened BA in response to your reply and the Settings I was using reloaded as streaming (I always Stream the data) … refresh rate was set to 20ms (again as I always use that speed except in exceptional circumstances if I am testing a lot of options at the same time) but the Settings files doesn't seem to be setting the Restrict Refresh period nor the Export Reports. I just copied the required settings file from the previous release and would have assumed they would all be working but I admit I don't recall checking. Dallas also asked about the trigger rate, that is 50 times for this rule at 0.1 of a second interval. So it's probably the refresh period, I will make sure I set it properly for start 150 seconds before and end 1,500 seconds after today's racing and report back later.

Post Reply

Return to “Suggestions”

  • Information
  • Who is online

    Users browsing this forum: No registered users and 4 guests