Back The Losing Fave in 2nd Set (Combined With Serve Stats and BP's) Bot

Post Reply
sniffer66
Posts: 658
Joined: Thu May 02, 2019 8:37 am

I posted a bot earlier on in the year that utilised Stored Values and Signals to record break points - for, against, saved and converted.
The aim was to build a little intelligence into the betting conditions using stats you would use when trading manually.
At the same time I also started looking at recording service stats via a similar mechanism. The process is unfortunately long winded, as you need to record each possible score, the outcome and then store the values to add to a running total. The only real alternative currently is to screen scrape and use Excel to pass the data to your Guardian Stored Values.

One real shame is that you can't detect 1st and 2nd serve or I would be able to break the stats down further. At least I can now get a fully automated bot to make a trade decision with some idea of how the favourite is performing, as opposed to backing blind when the fave is having a nightmare with no signs of threatening the dog. Of course, this won't cater for the fave having a 100% turnaround in set 2 :)

Anyway, this is what I've come up with and run from the start against a match it will sort the favourite into position 1 and calc the following SV's

BPConverted - Number of BP's Converted by the fave
ServeBrokenCount - Number of games the fave lost on serve.
BPAgainstTotal - Number of BP's against the fave.
BPForTotal - Number of BP's earned by the fave.
BPSavedTotal - Number of BP's saved by the fave.

PercentWonOnServe - Percentage of points won by fave when serving (1st and 2nd serve combined)
PercentReceivingOnServe - Percentage of points won by fave when receiving (1st and 2nd serve combined)

As a demo, I've taken one of Dallas' bots (Back Fav if Lose 1st Set and Green up in Stages.baf) and included it in the baf below to show how the stats might be used to make a decision to back the fave after losing the first set. Numbers in the conditions are pulled purely from my head and I have no idea how they will work in practice.
Unfortunately there are no matches currently where BF are including the score in the API so will need to wait until ATP\WTF start up again.

Easy enough to copy rules from your own strats into the lines I've marked in the attached baf file

Back Condition:
Capture.JPG
Looking forward to the restart of the season proper so I can put this properly to the test using my own strats.

Feel free to fire any questions or improvement suggestions.






Back The Losing Fave in 2nd Set (Combined With Serve Stats and BP's).baf
You do not have the required permissions to view the files attached to this post.
sgeorgepa62
Posts: 19
Joined: Sun Apr 05, 2020 3:59 pm

Good day there, have been interested in looking at tennis market so downloaded this bot to take a look, i loaded up on multiple matches and it didnt take a trade at all, could see it sorted order of fav but nothing more, its got quite deep rules set but looks promising if can get to fire. Let me know if you want a tester to try out?
sniffer66
Posts: 658
Joined: Thu May 02, 2019 8:37 am

sgeorgepa62 wrote:
Tue Jun 16, 2020 11:39 am
Good day there, have been interested in looking at tennis market so downloaded this bot to take a look, i loaded up on multiple matches and it didnt take a trade at all, could see it sorted order of fav but nothing more, its got quite deep rules set but looks promising if can get to fire. Let me know if you want a tester to try out?

Hi, as per my original post it's only going to work for matches where BF is sending the score in the API i.e WTA and ATP. At the moment it's only exhibition and practice matches so will not fire. Unfortunately you'll have to wait :)

For info I've provided this as a data plugin for your own automation. It's using a Back the losing fave in the 2nd set automation that Dallas posted, but purely to demo how it could be used
alldaygreen
Posts: 32
Joined: Mon May 18, 2015 10:50 am

I am getting a lot of invalid values using this file....

18/11/2020 13:33:53: [G_Auto] : Unable to : Store: 'BPAgainstTotal' for current selection. First value invalid.
18/11/2020 13:33:53: [G_Auto] : Unable to : Store: 'BPSavedTotal' for current selection. First value invalid.
18/11/2020 13:33:54: [G_Auto] : Unable to : Store: 'ServeBrokenCount' for current selection. First value invalid.
18/11/2020 13:34:01: [G_Auto] : Unable to : Store: 'BPSavedTotal%' for current selection. First value invalid.
18/11/2020 13:34:01: [G_Auto] : Unable to : Store: 'BPSavedTotal%' for current selection. First value invalid.
18/11/2020 13:36:23: [G_Auto] : Store Value for Granollers/Zeballos: TempBPCount = 2
18/11/2020 13:37:16: [G_Auto] : Unable to : Store: 'BPForTotal' for current selection. First value invalid.
18/11/2020 13:37:16: [G_Auto] : Unable to : Store: 'BPConverted' for current selection. First value invalid.
18/11/2020 13:40:23: [G_Auto] : Store Value for Granollers/Zeballos: TempBPCountAgainst = 3
18/11/2020 13:40:55: [G_Auto] : Unable to : Store: 'BPAgainstTotal' for current selection. First value invalid.
18/11/2020 13:40:55: [G_Auto] : Unable to : Store: 'BPSavedTotal' for current selection. First value invalid.
18/11/2020 13:40:56: [G_Auto] : Unable to : Store: 'ServeBrokenCount' for current selection. First value invalid.
18/11/2020 13:41:03: [G_Auto] : Unable to : Store: 'BPSavedTotal%' for current selection. First value invalid.
18/11/2020 13:41:03: [G_Auto] : Unable to : Store: 'BPSavedTotal%' for current selection. First value invalid.
18/11/2020 13:44:43: [G_Auto] : Store Value for Granollers/Zeballos: TempBPCount = 1
18/11/2020 13:45:38: [G_Auto] : Unable to : Store: 'BPForTotal' for current selection. First value invalid.




This is just using the .baf as is without any changes...... is this right?
sniffer66
Posts: 658
Joined: Thu May 02, 2019 8:37 am

alldaygreen wrote:
Wed Nov 18, 2020 1:58 pm
I am getting a lot of invalid values using this file....

18/11/2020 13:33:53: [G_Auto] : Unable to : Store: 'BPAgainstTotal' for current selection. First value invalid.
18/11/2020 13:33:53: [G_Auto] : Unable to : Store: 'BPSavedTotal' for current selection. First value invalid.
18/11/2020 13:33:54: [G_Auto] : Unable to : Store: 'ServeBrokenCount' for current selection. First value invalid.
18/11/2020 13:34:01: [G_Auto] : Unable to : Store: 'BPSavedTotal%' for current selection. First value invalid.
18/11/2020 13:34:01: [G_Auto] : Unable to : Store: 'BPSavedTotal%' for current selection. First value invalid.
18/11/2020 13:36:23: [G_Auto] : Store Value for Granollers/Zeballos: TempBPCount = 2
18/11/2020 13:37:16: [G_Auto] : Unable to : Store: 'BPForTotal' for current selection. First value invalid.
18/11/2020 13:37:16: [G_Auto] : Unable to : Store: 'BPConverted' for current selection. First value invalid.
18/11/2020 13:40:23: [G_Auto] : Store Value for Granollers/Zeballos: TempBPCountAgainst = 3
18/11/2020 13:40:55: [G_Auto] : Unable to : Store: 'BPAgainstTotal' for current selection. First value invalid.
18/11/2020 13:40:55: [G_Auto] : Unable to : Store: 'BPSavedTotal' for current selection. First value invalid.
18/11/2020 13:40:56: [G_Auto] : Unable to : Store: 'ServeBrokenCount' for current selection. First value invalid.
18/11/2020 13:41:03: [G_Auto] : Unable to : Store: 'BPSavedTotal%' for current selection. First value invalid.
18/11/2020 13:41:03: [G_Auto] : Unable to : Store: 'BPSavedTotal%' for current selection. First value invalid.
18/11/2020 13:44:43: [G_Auto] : Store Value for Granollers/Zeballos: TempBPCount = 1
18/11/2020 13:45:38: [G_Auto] : Unable to : Store: 'BPForTotal' for current selection. First value invalid.




This is just using the .baf as is without any changes...... is this right?
I think an update to BA broke the Stored Values. Previously an unset SV was assumed to have a value of 0, now they need to be set as 0 at the start of the automation

If you look at my later Tennis framework file here, I've fixed that issue since the update

viewtopic.php?f=51&t=21870

If you download the above and open you will see a rule that sets the starting SV's - should all be to a 0 value. Copy that rule to the older file and it should fix it

Alternatively, and probably better, copy the trading strat lines from the old file and insert in the new where I've marked the strat to go.

That strat was only put there to demo how the stats can be used by the way. I've no idea if the numbers used for the stats work in practice
alldaygreen
Posts: 32
Joined: Mon May 18, 2015 10:50 am

Thanks for the reply.......

the problem is the baf file you directed to was made with an older version so will not import. :(

I'm using 1.55ob2
sniffer66
Posts: 658
Joined: Thu May 02, 2019 8:37 am

alldaygreen wrote:
Wed Nov 18, 2020 8:41 pm
Thanks for the reply.......

the problem is the baf file you directed to was made with an older version so will not import. :(

I'm using 1.55ob2
I'm using a version of this in 1.55.0.b3 so think you need to update. They should be backward compatible but not forward
User avatar
Dallas
Posts: 16310
Joined: Sun Aug 09, 2015 10:57 pm
Contact:

sniffer66 wrote:
Wed Nov 18, 2020 9:04 pm
alldaygreen wrote:
Wed Nov 18, 2020 8:41 pm
Thanks for the reply.......

the problem is the baf file you directed to was made with an older version so will not import. :(

I'm using 1.55ob2
I'm using a version of this in 1.55.0.b3 so think you need to update. They should be backward compatible but not forward
They are both beta versions, the latest has now been formally released and can now be downloaded from the website
The version number has been reset back to V1.55.0
https://www.betangel.com/download/?product=BetAngelPro
alldaygreen
Posts: 32
Joined: Mon May 18, 2015 10:50 am

:D Cheers Dallas
Post Reply

Return to “Bet Angel Automation - Tennis”