Take SP (Greater Than Price Parameter)

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

Instead of cancelling unmatched bets less than a fixed price, I am using a Stored Value Price called high-2 (highest matched price minus 2 ticks). In this example "Kens Laser" was matched at 6.6. My requirement for taking SP was therefore 6.2. However, the price I got was 5.4. (This is Greyhound). Any advice is appreciated!
You do not have the required permissions to view the files attached to this post.
User avatar
Dallas
Posts: 23597
Joined: Sun Aug 09, 2015 10:57 pm

It looks like your bet was matched or was in the process of being matched when trying to cancel it
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

Dallas wrote:
Tue Nov 02, 2021 12:59 pm
It looks like your bet was matched or was in the process of being matched when trying to cancel it
That makes no sense to me because it was placed at 6.4 (as you can see from the log), but then matched at 5.4...? It has to be another explanation, right? Anyway, I have stop it from happening again. What could/should I do?
User avatar
Dallas
Posts: 23597
Joined: Sun Aug 09, 2015 10:57 pm

lotora wrote:
Tue Nov 02, 2021 1:08 pm
Dallas wrote:
Tue Nov 02, 2021 12:59 pm
It looks like your bet was matched or was in the process of being matched when trying to cancel it
That makes no sense to me because it was placed at 6.4 (as you can see from the log), but then matched at 5.4...? It has to be another explanation, right? Anyway, I have stop it from happening again. What could/should I do?
Actually yes, I can see from the matched bet screenshot it was matched as an SP bet

Something else I did notice on a closer look was your stored value name on the parameters tab is 'high-2'
But in the log the Stored value being set is just named 'high'
Unless the SV named 'high-2' has not been told to write to the log?
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

The SV named 'high-2' is not part of the log, and that was also my intention. I am storing highest and lowest prices continually, as "high" and "low".
You do not have the required permissions to view the files attached to this post.
Last edited by lotora on Tue Nov 02, 2021 2:23 pm, edited 2 times in total.
User avatar
Dallas
Posts: 23597
Joined: Sun Aug 09, 2015 10:57 pm

lotora wrote:
Tue Nov 02, 2021 2:06 pm
The SV named 'high-2' is not part of the log, and that was also my intention. I am storing highest and lowest prices continually, as "high" and "low".
I'd suggest enabling the logging for that high-2 SV to ensure thats triggering correctly and storing the right price
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

Dallas wrote:
Tue Nov 02, 2021 2:23 pm
lotora wrote:
Tue Nov 02, 2021 2:06 pm
The SV named 'high-2' is not part of the log, and that was also my intention. I am storing highest and lowest prices continually, as "high" and "low".
I'd suggest enabling the logging for that high-2 SV to ensure thats triggering correctly and storing the right price
Anything else I should do? (attachments)
You do not have the required permissions to view the files attached to this post.
User avatar
Dallas
Posts: 23597
Joined: Sun Aug 09, 2015 10:57 pm

lotora wrote:
Tue Nov 02, 2021 2:42 pm
Dallas wrote:
Tue Nov 02, 2021 2:23 pm
lotora wrote:
Tue Nov 02, 2021 2:06 pm
The SV named 'high-2' is not part of the log, and that was also my intention. I am storing highest and lowest prices continually, as "high" and "low".
I'd suggest enabling the logging for that high-2 SV to ensure thats triggering correctly and storing the right price
Anything else I should do? (attachments)
Thats a signal, its your rule that setting the Stored Value named 'high-2' you need to check the log for to see if its working correctly
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

Okay! Will see how it goes
You do not have the required permissions to view the files attached to this post.
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

Here's another one. As you can see from the log, the SP price should have been 5.9 at a minimum.
You do not have the required permissions to view the files attached to this post.
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

Dallas wrote:
Tue Nov 02, 2021 2:49 pm
lotora wrote:
Tue Nov 02, 2021 2:42 pm
Dallas wrote:
Tue Nov 02, 2021 2:23 pm


I'd suggest enabling the logging for that high-2 SV to ensure thats triggering correctly and storing the right price
Anything else I should do? (attachments)
Thats a signal, its your rule that setting the Stored Value named 'high-2' you need to check the log for to see if its working correctly
Hey! If you need any more information, just tell me!
User avatar
Dallas
Posts: 23597
Joined: Sun Aug 09, 2015 10:57 pm

lotora wrote:
Wed Nov 03, 2021 2:53 am
Dallas wrote:
Tue Nov 02, 2021 2:49 pm
lotora wrote:
Tue Nov 02, 2021 2:42 pm


Anything else I should do? (attachments)
Thats a signal, its your rule that setting the Stored Value named 'high-2' you need to check the log for to see if its working correctly
Hey! If you need any more information, just tell me!
Your high-2 SV in that last market was 5.9
The back bet was at 6.2 and therefore satisfied your Take SP parameter of being >high-2
So the bet was marked as take SP

What you are asking for in those screenshots is for the bets above your high-2 SV to be taken as SP - but that still means they can be matched at whatever the returned SP is, ie, your not setting a minimum SP

For that you'd need to use the rule 'place back SP bet' (with the same parameters)
and that will allow you to set a minimum limit the same way as you do on Betfair
User avatar
lotora
Posts: 754
Joined: Thu Dec 24, 2009 9:20 am

Dallas wrote:
Wed Nov 03, 2021 4:19 pm
lotora wrote:
Wed Nov 03, 2021 2:53 am
Dallas wrote:
Tue Nov 02, 2021 2:49 pm


Thats a signal, its your rule that setting the Stored Value named 'high-2' you need to check the log for to see if its working correctly
Hey! If you need any more information, just tell me!
Your high-2 SV in that last market was 5.9
The back bet was at 6.2 and therefore satisfied your Take SP parameter of being >high-2
So the bet was marked as take SP

What you are asking for in those screenshots is for the bets above your high-2 SV to be taken as SP - but that still means they can be matched at whatever the returned SP is, ie, your not setting a minimum SP

For that you'd need to use the rule 'place back SP bet' (with the same parameters)
and that will allow you to set a minimum limit the same way as you do on Betfair
That's working, thanks a bunch! Really hoping that the upcoming version of BA includes the staking method "By liability using Stored Value Stake", for "Place Back SP Bet".
Post Reply

Return to “Bet Angel - Automation”