New beta version of Bet Angel v1.55.0 - now on general release

[mcgoo]

Was just thinking is there a way to tap into/record the average $ matched per second as displayed at top of the ladder screen, via automation.? Be great to leverage that as a liquidity ratio..i.e. average matched is above $x00 per second. Thanks

You could just store the Volume amount every second and subtract the difference

Good idea. I'm always looking 4 the easy..lazy.. way I would then have to total and/or average it.. Will give it a go
Cheers

[Dr Ginhog]

Hi Team,
Simply the best. None even close. My head is spinning with so many brilliant updates (Or maybe its too much exorcising)
As my aunt gertrude used to say methinks you should keep your mouth shut when you have nothing good to say and keep focused on the big picture. I failed miserably in that respect needless to say. If I begin to open my Gob just ignore me,thats the best policy overall. I used to wonder is anything worse than being ignored. Now Im thinking is anything worse than not being ignored.My posting days are done! apart from nice words of congratulations
Congrats on great work.

[sniffer66]

Is anyone else having any issues with Restricted Refresh in Guardian ?

I've been having intermittent issues for a few days with automation not trading and think it's down to the restricted refresh. I had it set this morning and applied an automation file to all todays ATP Challenger tennis matches. There were 2 matches at 11:00, one set nothing in the log (as expected), the other launched immediately.
Unticking the refresh immediately launched the automation on the one that hadn't started, as expected. I can't see why the other one started when they both have the same start time

Same for the rest of the days matches - some on, some off

Example here. Turned restricted refresh back on and no updates since 07:52. But then 2 matches have updated at 08:19. Same settings, same automation file
Export Reports turned off as I know that forces a constant refresh

Capture.JPG

Capture1.JPG

[Bet Angel]

Restricted Refresh tells Guardian not to request a refresh of that market, but other screens may have needed an update.
i.e. Did you have the market open on any other screen that would have required a refresh, like the main trading screen or in a popup ladder?
If the markets were visible on a watchlist then depending on 'Options' the market under the mouse cursor can get a refresh.

There are also situations where betfair change the version number of the market and trigger the need for an update; in that situation it would only update a few times and then stop again rather than constantly refreshing.

[sniffer66]

Restricted Refresh tells Guardian not to request a refresh of that market, but other screens may have needed an update.
i.e. Did you have the market open on any other screen that would have required a refresh, like the main trading screen or in a popup ladder?
If the markets were visible on a watchlist then depending on 'Options' the market under the mouse cursor can get a refresh.

There are also situations where betfair change the version number of the market and trigger the need for an update; in that situation it would only update a few times and then stop again rather than constantly refreshing.

Thanks, I didnt realise re the mouse over option. Will keep an eye on it and check if something like that is the cause.
Pretty sure I had neither of the 11 am markets open anywhere else. Literally applied the automation and checked the logs. Did nothing else

[Kirneh74365]

Just upgrated to v1.55.0

The charts candles look strange the is no vertical lines in the candle chart

[Dallas]

Just upgrated to v1.55.0

The charts candles look strange the is no vertical lines in the candle chart

In your chart editor there is an option to enable/disable the vertical lines on a chart

[BetWin]

Not sure I'm in the right place here but have been wanting to get data out of BetAngel and this new update looks great ( I'm still a newbie and thought I might be better collating some data first before jumping in with both feet).
I've managed to build two automation rules, using Dallas' step by step guide, for back price and Traded vol as a %- but I can't get both of them to record at the same time. I either get back price every refresh or traded volume %, not both?
Is it possible to record two rules at the same time or am I looking for something that doesn't exist?

[StevieB]

V.1.55.0 is a NIGHTMARE!! So many things now do not work and I want to go back to the previous version. Every attempt so far just re-loads V1.55 ........... any ideas??

[Dallas]

V.1.55.0 is a NIGHTMARE!! So many things now do not work and I want to go back to the previous version. Every attempt so far just re-loads V1.55 ........... any ideas??

What specifcally isn't working?

It been working fine for everyone else using it apart from the two minor bug fixes below both found and fixed several weeks ago
ladder cells were not changing colour as mouse tracked over them
matched bets not showing in Guardian if you navigate the markets in a certain way

[jimibt]

V.1.55.0 is a NIGHTMARE!! So many things now do not work and I want to go back to the previous version. Every attempt so far just re-loads V1.55 ........... any ideas??

i've not experienced any issues tbh. maybe as Dallas mentions, just pop a list of the issues into a message and maybe it will shed light on a potential fix (if it exists).

I found that i had to perform a reboot on one of the previous installs as it actually couldn'r get it to update.

[Vovsen]

There seems to be an issue when storing the VWAP Book % of a selection, it does not return correct values when using "ANY":

VWAP.PNG

I have not used it before this version of BA.

In this rule I am already storing the back and lay book %, for every selection row, which is working as it should.

But if I try to store the VWAP%, it gives the same value for every selection, instead of just one value for a certain row, that I have defined for the stored values.

If I use "EVERY" selection the other prices do not work, but they do work when I use "ANY", VWAP however does not.

[Dallas]

There seems to be an issue when storing the VWAP Book % of a selection, it does not return correct values when using "ANY":

VWAP.PNG

I have not used it before this version of BA.

In this rule I am already storing the back and lay book %, for every selection row, which is working as it should.

But if I try to store the VWAP%, it gives the same value for every selection, instead of just one value for a certain row, that I have defined for the stored values.

If I use "EVERY" selection the other prices do not work, but they do work when I use "ANY", VWAP however does not.

Can you post the rule file or log from it if its set up correctly there should be no problems?

There are several example rules i put on the forum in the last few weeks that use applied to 'EVERY' selection and even some also store the VWAP% so know I thats always worked exactly as it should, but just ran a test rule to show it below anyway.

When applying a rule to ANY selection it will always start by looking at the selection in betfair row 1, then row 2, then row 3, and so on, and will always trigger on the first selection to meet its criteria,so if using no conditions it will just continullly trigger on Row1
Again thats the way applying a rule to 'ANY' selection should and always has worked.

Log.jpg

[Vovsen]

There seems to be an issue when storing the VWAP Book % of a selection, it does not return correct values when using "ANY":

VWAP.PNG

I have not used it before this version of BA.

In this rule I am already storing the back and lay book %, for every selection row, which is working as it should.

But if I try to store the VWAP%, it gives the same value for every selection, instead of just one value for a certain row, that I have defined for the stored values.

If I use "EVERY" selection the other prices do not work, but they do work when I use "ANY", VWAP however does not.

Can you post the rule file or log from it if its set up correctly there should be no problems?

There are several example rules i put on the forum in the last few weeks that use applied to 'EVERY' selection and even some also store the VWAP% so know I thats always worked exactly as it should, but just ran a test rule to show it below anyway.

When applying a rule to ANY selection it will always start by looking at the selection in betfair row 1, then row 2, then row 3, and so on, and will always trigger on the first selection to meet its criteria,so if using no conditions it will just continullly trigger on Row1
Again thats the way applying a rule to 'ANY' selection should and always has worked.


Log.jpg

Thanks Dallas for the quick response. I will try to upload more info going forward instead of typing so much as I am not very good with words.

Here is the log where you can see that Lay and Back % is working fine, but VWAP is not.

VWAPnotWorking.PNG

And here is example rule file, it uses the Condition of text "Match Odds":

VWAPtest.baf

[Dallas]

There seems to be an issue when storing the VWAP Book % of a selection, it does not return correct values when using "ANY":

VWAP.PNG

I have not used it before this version of BA.

In this rule I am already storing the back and lay book %, for every selection row, which is working as it should.

But if I try to store the VWAP%, it gives the same value for every selection, instead of just one value for a certain row, that I have defined for the stored values.

If I use "EVERY" selection the other prices do not work, but they do work when I use "ANY", VWAP however does not.

Can you post the rule file or log from it if its set up correctly there should be no problems?

There are several example rules i put on the forum in the last few weeks that use applied to 'EVERY' selection and even some also store the VWAP% so know I thats always worked exactly as it should, but just ran a test rule to show it below anyway.

When applying a rule to ANY selection it will always start by looking at the selection in betfair row 1, then row 2, then row 3, and so on, and will always trigger on the first selection to meet its criteria,so if using no conditions it will just continullly trigger on Row1
Again thats the way applying a rule to 'ANY' selection should and always has worked.


Log.jpg

Thanks Dallas for the quick response. I will try to upload more info going forward instead of typing so much as I am not very good with words.

Here is the log where you can see that Lay and Back % is working fine, but VWAP is not.
VWAPnotWorking.PNG

And here is example rule file, it uses the Condition of text "Match Odds":
VWAPtest.baf

Thanks for the rules file, and for flagging this up.

After looking into we can confirm that is a genuine bug you've found caused when using the combination of applying a rule to 'ANY' selection, and using 'Nominated' selection on the SV tab, to store the VWAP%, we also found it also the same when storing just the VWAP (all others work fine).

The build is due to go on general release shortly so we'll get that fixed before then.

In the mean time using the 'Every' selection you should be able to work around what you need to do, if not if you start a new thread we details of exactly what you want to achieve i'll take a look and see what can be advised