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

[Korattt]

is there any way of displaying traded volume across all cells & not just in one column?

Not quite sure what you mean here, can you post an screenshot example?

Dallas, from 8.4 down to 6 across all 7 cells, basically stretch the traded volume across all cells?

[Bet Angel]

from 8.4 down to 6 across all 7 cells, basically stretch the traded volume across all cells?

No that isn't possible and wouldn't be easy to do either because each column is separate from each other and is only positioned & sized based on the current column order & settings.

[Bet Angel]

I am not talking about storing the values, that is fine.

It's ok, I know what you mean. We saw this once during Development and thought it was resolved as it never happened again. We'll try again to recreate it. The screen used to configure the history list is reused from one condition to the next and the data should be saved as you edit, but I think what you've seen is that although you change the values it doesn't actually save internally, so when you click on another condition you end up corrupting the data held in the first one. You might be able to resolve it just by restarting Bet Angel and starting the creation of the rule from scratch again, but we'll know more when/if we recreate it. I'm thinking that there's probably some specific order of edits that triggers the corruption and once it's in that state it stays there.

[Vovsen]

I am not talking about storing the values, that is fine.

It's ok, I know what you mean. We saw this once during Development and thought it was resolved as it never happened again. We'll try again to recreate it. The screen used to configure the history list is reused from one condition to the next and the data should be saved as you edit, but I think what you've seen is that although you change the values it doesn't actually save internally, so when you click on another condition you end up corrupting the data held in the first one. You might be able to resolve it just by restarting Bet Angel and starting the creation of the rule from scratch again, but we'll know more when/if we recreate it. I'm thinking that there's probably some specific order of edits that triggers the corruption and once it's in that state it stays there.

Yes exactly

Using the Historical Stored Values as conditions corrupts the conditions, when using several groups of them and having different settings, even though the preview shows it correctly, the settings gets changed.

I also updated my other posts with more details, a similar thing happens the History List when you have several rules like this, all using their own History list 1 2 3 etc. Saving one of them will put all rules to History list 1 1 1 for instance

Thank you!

[Bet Angel]

Yes exactly

Using the Historical Stored Values as conditions corrupts the conditions, when using several groups of them and having different settings, even though the preview shows it correctly, the settings gets changed.

I also updated my other posts with more details, a similar thing happens the History List when you have several rules like this, all using their own History list 1 2 3 etc. Saving one of them will put all rules to History list 1 1 1 for instance

Thank you!

Typically our first attempt to recreate following your instructions has ended with no bug found and a fully functional editor! I'm not that surprised as we tested this to death, but there must be a certain order of edits that breaks it.
Could you export the rules file that isn't editing properly and upload it here or send it into support and we'll see if the file itself contains the corruption.
Once you've exported it and therefore have a safe copy, you could also try opening it in a new session of Bet Angel just to see if the edit problem remains or whether the restart mends it.

[Vovsen]

Yes exactly

Using the Historical Stored Values as conditions corrupts the conditions, when using several groups of them and having different settings, even though the preview shows it correctly, the settings gets changed.

I also updated my other posts with more details, a similar thing happens the History List when you have several rules like this, all using their own History list 1 2 3 etc. Saving one of them will put all rules to History list 1 1 1 for instance

Thank you!

Typically our first attempt to recreate following your instructions has ended with no bug found and a fully functional editor! I'm not that surprised as we tested this to death, but there must be a certain order of edits that breaks it.
Could you export the rules file that isn't editing properly and upload it here or send it into support and we'll see if the file itself contains the corruption.
Once you've exported it and therefore have a safe copy, you could also try opening it in a new session of Bet Angel just to see if the edit problem remains or whether the restart mends it.

I tried different instances of BA, export and import, new rules, separate rules in the same file, it keeps happening every try. I will try to test it on another computer

[Vovsen]

I have now installed BA on another computer, that have never had BA installed before and quickly tested it:

I created a new rule, and go to the "Conditions" tab

New condition: Stored Value Condition
Value A: VWAP
Value B: Historical List 1 30 seconds ago

Another condition: Stored Value Condition
Value A: VWAP
Value B: Historical List 1 2 seconds ago

When I click Apply and then Save, there is a brief blue marker flash over the text of both of these and the 30 seconds become 2 seconds. like this:

Value B: Historical List 1 2 seconds ago
Value B: Historical List 1 2 seconds ago

Not in the preview but in the setting for seconds where you manually input the number of seconds

Please try this, grouping them does not help.

Splitting them into two separate rules, the same thing occurs when you save, after changing the seconds. But also the Historical list gets changed in some scenarios, which I cant pinpoint exactly yet.

[Bet Angel]

Please try this, grouping them does not help.

Splitting them into two separate rules, the same thing occurs when you save, after changing the seconds. But also the Historical list gets changed in some scenarios, which I cant pinpoint exactly yet.

Yes we can see that now. It seems to be the History List in Value B that's causing the issue. We'll look to fix that tomorrow.... if betfair don't sort out the charts they broke this afternoon then we'll need to issue a build anyway!

For now, swap the comparison round so that VWAP is in Value B and the History List is Value A. Changing the greater than to less than comparison as required.

Have you only seen the issue in the Stored Value condition or have you ever seen it occur on the Stored Values tab using the 'Store a value in a history list' command?

[Vovsen]

Yes this workaround solves the issue with Seconds Ago looks like, thank you so much!

[/quote]

Have you only seen the issue in the Stored Value condition or have you ever seen it occur on the Stored Values tab using the 'Store a value in a history list' command?

[/quote]

I have only noticed issues when using Historical List's as conditions where I compare them to another stored value.

Right now it only seems to happen sometimes, that Historical lists 1 2 3 and in 3 different rule conditions, all 3 rules get changed to Historical list 2 in the conditions comparing stored values, if thats the last one i have edited.

Edit:

I can recreate the issue now it seems.

1st rule, with 1 Stored Value Condition History list 1 in value B
2nd rule, with 1 Stored Value Condition History list 2 in value B

Changing the History list in one of these and saving the file, will change the History list to the same across all of them like this:

1st rule, with 1 Stored Value Condition History list 2 in value B
2nd rule, with 1 Stored Value Condition History list 2 in value B

[convoysur-2]

Hi Betangel.
I downloaded 1.55.0 - and restarted my pc,
But when i tried to log into betangel i get a pop up that i have a pasword change pending ,but i didnt change password,bit freaked so i withdrew my balance as precaution,maybe it has nothing to do with the upgrade?

[jimibt]

I have now installed BA on another computer, that have never had BA installed before and quickly tested it:

I created a new rule, and go to the "Conditions" tab

New condition: Stored Value Condition
Value A: VWAP
Value B: Historical List 1 30 seconds ago

Another condition: Stored Value Condition
Value A: VWAP
Value B: Historical List 1 2 seconds ago

When I click Apply and then Save, there is a brief blue marker flash over the text of both of these and the 30 seconds become 2 seconds. like this:

Value B: Historical List 1 2 seconds ago
Value B: Historical List 1 2 seconds ago

Not in the preview but in the setting for seconds where you manually input the number of seconds

Please try this, grouping them does not help.

Splitting them into two separate rules, the same thing occurs when you save, after changing the seconds. But also the Historical list gets changed in some scenarios, which I cant pinpoint exactly yet.

very nice analysis of the problem and breakdown of the issue... hadn't seen it myself but can foresee that i would have used it in a similar way moving fwd.

thanks for highlighting this

[Anbell]

i'm SOO enjoying these History Lists. Started off testing them doing different things on the Ladder and quickly had an epiphany - this is a GREAT way to visualize how an automation rule will function using the same History List(x) logic... mind blown....

jimibt - could you please expand on what you're saying here to help me understand a bit better? How does this help visualize?

Cheers

[tricola]

Does anyone have problems with charts not loading properly?

[mcgoo]

Does anyone have problems with charts not loading properly?

viewtopic.php?f=5&t=21556

[gutuami]

just finished setup for tomorrows session. Amazing features. thank you BA. Thinking, what would be version 1.100 like?