Is anyone having a problem with storing a value from a range in a history list using version 1.57.0.b1?
When trying to do so, I can't get the drop down labelled "selection holding the values" to stick on my selection. Whichever selection I choose, the drop down reverts to blank.
I have dozens of stored values from history list ranges in many baf files developed with earlier versions without spotting this error.
If I try to edit an old automation by changing the selection holding the values the drop down will refuse the change.
This behaviour exhibits on two different pcs and on my BA VPS so I suspect it's not just a corrupted file.
Appreciate your thoughts/observations.
Cheers
Store Value (range calc) issue
-
AngelsWithDirtyFaces
- Posts: 56
- Joined: Tue Jul 05, 2011 12:08 am
So this is a quick knock up file created just now using 1.57.0.b1 to illustrate.
You'll note that the drop down for selection holding the values displays "market" (which just happens to be the last use of that drop down in another file). Every time I change it to "selection" and click the apply button it reverts to market.
Hope you can replicate this because it happens on two home pcs and my vps.
Thanks for looking into this.
You'll note that the drop down for selection holding the values displays "market" (which just happens to be the last use of that drop down in another file). Every time I change it to "selection" and click the apply button it reverts to market.
Hope you can replicate this because it happens on two home pcs and my vps.
Thanks for looking into this.
You do not have the required permissions to view the files attached to this post.
-
AngelsWithDirtyFaces
- Posts: 56
- Joined: Tue Jul 05, 2011 12:08 am
Hi Dallas,
Further to my opening post, I uninstalled v1.57.0.b1 and installed v1.56. The selection drop down problem disappeared.
I reinstalled v1.57.0.b1 and the problem reappeared.
To clarify.
>Load a fresh instance of BA which hasn't yet been used for editing a guardian rules file and create a new rules file.
>Create a rule to store a value using a range of values from a history list
>Click the selection drop down "selection holding the values" and make a choice.
> Click "Apply" and the drop down "Selection holding the values" reverts to blank.
If the instance of guardian has previously has a rues file loaded, the behaviour appears to change because the drop down will have a preloaded selection which cannot be changed.
If you could take another look to try to replicate this behaviour or suggest what I might be doing wrong, I'd appreciate you input.
Is anyone else seeing this problem?
Cheers.
Further to my opening post, I uninstalled v1.57.0.b1 and installed v1.56. The selection drop down problem disappeared.
I reinstalled v1.57.0.b1 and the problem reappeared.
To clarify.
>Load a fresh instance of BA which hasn't yet been used for editing a guardian rules file and create a new rules file.
>Create a rule to store a value using a range of values from a history list
>Click the selection drop down "selection holding the values" and make a choice.
> Click "Apply" and the drop down "Selection holding the values" reverts to blank.
If the instance of guardian has previously has a rues file loaded, the behaviour appears to change because the drop down will have a preloaded selection which cannot be changed.
If you could take another look to try to replicate this behaviour or suggest what I might be doing wrong, I'd appreciate you input.
Is anyone else seeing this problem?
Cheers.
-
AngelsWithDirtyFaces
- Posts: 56
- Joined: Tue Jul 05, 2011 12:08 am
Here’s a possible work around.
Change the drop down menu to what you want.
Then tick/untick the (Note value assignments to log ) tick box at the bottom of the screen. It shouldn't change after that.
I just had the same thing with the (stored value> value name) box. It kept changing back to the old name.
Change the drop down menu to what you want.
Then tick/untick the (Note value assignments to log ) tick box at the bottom of the screen. It shouldn't change after that.
I just had the same thing with the (stored value> value name) box. It kept changing back to the old name.
-
AngelsWithDirtyFaces
- Posts: 56
- Joined: Tue Jul 05, 2011 12:08 am
Cheers for that. I can confirm that the chosen selection "sticks" after the tick/untick maneuver.Dabbla wrote: ↑Mon Sep 13, 2021 11:04 pmHere’s a possible work around.
Change the drop down menu to what you want.
Then tick/untick the (Note value assignments to log ) tick box at the bottom of the screen. It shouldn't change after that.
I just had the same thing with the (stored value> value name) box. It kept changing back to the old name.
-
AngelsWithDirtyFaces
- Posts: 56
- Joined: Tue Jul 05, 2011 12:08 am
I've noticed another issue with range calcs which may or may not be related to the problem already outlined above but I'm adding it to this thread just in case.
The steps I'm performing (every refresh) are:
Store a value into a market history list (HL1) In this case it happens to be the back book % of the market.
Store a value (Avg) for the market being the average of a set of values from a range of values in a history list (HL1). Sampling every second from 10 seconds ago to now.
I'm displaying the two values (HL1 NOW AND stored value "Avg") side by side in two custom columns on the one click screen. At all times the two values appear to be in absolute lockstep and there is never any difference between the two. It appears that stored value "Avg" is not calculating an average but just storing the most recent value in the history list. I've rechecked the the custom columns are correctly displaying the two discrete variables and not the same variable by accident.
Even in a frantic pre off racing market in the final few seconds these two variables never get out of sync.
I've tried changing both the sampling frequency and the sampling period and nothing solves the problem.
Having a single market loaded into guardian to avoid any refresh/recycling issues also doesn't make a difference.
As ever, grateful for your observations.
Cheers
The steps I'm performing (every refresh) are:
Store a value into a market history list (HL1) In this case it happens to be the back book % of the market.
Store a value (Avg) for the market being the average of a set of values from a range of values in a history list (HL1). Sampling every second from 10 seconds ago to now.
I'm displaying the two values (HL1 NOW AND stored value "Avg") side by side in two custom columns on the one click screen. At all times the two values appear to be in absolute lockstep and there is never any difference between the two. It appears that stored value "Avg" is not calculating an average but just storing the most recent value in the history list. I've rechecked the the custom columns are correctly displaying the two discrete variables and not the same variable by accident.
Even in a frantic pre off racing market in the final few seconds these two variables never get out of sync.
I've tried changing both the sampling frequency and the sampling period and nothing solves the problem.
Having a single market loaded into guardian to avoid any refresh/recycling issues also doesn't make a difference.
As ever, grateful for your observations.
Cheers
I've just tried it using the settings you gave above and got this log, it was about 15mins out so there wasn't a great deal of movement but I've highlighted the area it changed once there was movementAngelsWithDirtyFaces wrote: ↑Sat Sep 25, 2021 11:37 amI've noticed another issue with range calcs which may or may not be related to the problem already outlined above but I'm adding it to this thread just in case.
The steps I'm performing (every refresh) are:
Store a value into a market history list (HL1) In this case it happens to be the back book % of the market.
Store a value (Avg) for the market being the average of a set of values from a range of values in a history list (HL1). Sampling every second from 10 seconds ago to now.
I'm displaying the two values (HL1 NOW AND stored value "Avg") side by side in two custom columns on the one click screen. At all times the two values appear to be in absolute lockstep and there is never any difference between the two. It appears that stored value "Avg" is not calculating an average but just storing the most recent value in the history list. I've rechecked the the custom columns are correctly displaying the two discrete variables and not the same variable by accident.
Even in a frantic pre off racing market in the final few seconds these two variables never get out of sync.
I've tried changing both the sampling frequency and the sampling period and nothing solves the problem.
Having a single market loaded into guardian to avoid any refresh/recycling issues also doesn't make a difference.
As ever, grateful for your observations.
Cheers
This was the file I used
You do not have the required permissions to view the files attached to this post.
-
AngelsWithDirtyFaces
- Posts: 56
- Joined: Tue Jul 05, 2011 12:08 am
Dallas wrote: ↑Sat Sep 25, 2021 1:20 pmI've just tried it using the settings you gave above and got this log, it was about 15mins out so there wasn't a great deal of movement but I've highlighted the area it changed once there was movementAngelsWithDirtyFaces wrote: ↑Sat Sep 25, 2021 11:37 amI've noticed another issue with range calcs which may or may not be related to the problem already outlined above but I'm adding it to this thread just in case.
The steps I'm performing (every refresh) are:
Store a value into a market history list (HL1) In this case it happens to be the back book % of the market.
Store a value (Avg) for the market being the average of a set of values from a range of values in a history list (HL1). Sampling every second from 10 seconds ago to now.
I'm displaying the two values (HL1 NOW AND stored value "Avg") side by side in two custom columns on the one click screen. At all times the two values appear to be in absolute lockstep and there is never any difference between the two. It appears that stored value "Avg" is not calculating an average but just storing the most recent value in the history list. I've rechecked the the custom columns are correctly displaying the two discrete variables and not the same variable by accident.
Even in a frantic pre off racing market in the final few seconds these two variables never get out of sync.
I've tried changing both the sampling frequency and the sampling period and nothing solves the problem.
Having a single market loaded into guardian to avoid any refresh/recycling issues also doesn't make a difference.
As ever, grateful for your observations.
Cheers
Capture.JPG
This was the file I used
HL Avg.baf
Thanks Dalllas
I've used the logic in your file HL Avg in one of my own with the following changed parameters:
Store Market Volume in MARKET HL 1 and Store Value test-avg as a MARKET level value being the average of MARKET HL 1 for the last 10 seconds sampling every second. I've chosen Market Volume to test as this I know will constantly change.
I've set the rule to trigger100 times and rearm on every refresh
The end of my log output looks like this:
25.09.2021 14:08:54: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 136676.54
25.09.2021 14:08:54: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 136676.54
25.09.2021 14:08:55: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 137182
25.09.2021 14:08:55: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 137182
25.09.2021 14:08:55: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 137215.71
25.09.2021 14:08:55: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 137215.71
25.09.2021 14:08:55: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 137585.44
25.09.2021 14:08:55: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 137585.44
25.09.2021 14:08:56: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 137796.75
25.09.2021 14:08:56: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 137796.75
25.09.2021 14:08:56: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 137975.13
25.09.2021 14:08:56: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 137975.13
25.09.2021 14:08:56: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 137979.13
25.09.2021 14:08:56: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 137979.13
25.09.2021 14:08:56: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 139333.46
25.09.2021 14:08:56: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 139333.46
25.09.2021 14:08:57: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 139468.74
25.09.2021 14:08:57: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 139468.74
25.09.2021 14:08:57: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 139469.72
25.09.2021 14:08:57: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 139469.72
25.09.2021 14:08:57: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 139554.63
25.09.2021 14:08:57: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 139554.63
25.09.2021 14:08:58: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 139642.91
25.09.2021 14:08:58: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 139642.91
25.09.2021 14:08:58: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 139709.9
25.09.2021 14:08:58: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 139709.9
25.09.2021 14:08:58: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 139947.09
25.09.2021 14:08:58: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 139947.09
25.09.2021 14:08:59: [G_Auto 2] : Store Value (Shared) in History List 1 for market = 140204.35
25.09.2021 14:08:59: [G_Auto 2] : Store (range calc) Value (Shared) for market: test_avg = 140204.35
This rule was applied to the 14:10 at Market Rasen so was only a minute from the off time. I had this market loaded on the one-click screen to ensure constant refreshing. As you can see, the test-avg variable returns the same value as the latest value in HL1?
So I'm puzzled. Is the problem only apparent in MARKET level values and lists? Or is it because I've got the rearm set to every refresh combined with the one second sampling of the data which is out of sync?
Here is my file
You do not have the required permissions to view the files attached to this post.
The second rule in the file you uploaded was armed to trigger 50 times and rearm every refresh - so when I ran it it was out of triggers in under 2 secs
So I've edited mine to Store the Value on the market and this was the log I got
So I've edited mine to Store the Value on the market and this was the log I got
You do not have the required permissions to view the files attached to this post.
-
AngelsWithDirtyFaces
- Posts: 56
- Joined: Tue Jul 05, 2011 12:08 am
This is getting interesting.
I noted your point about the refresh time and only 50 triggers but my one-click screen was refreshing at 200m and the particular instance of guardian I ran it on had all the days uk racing markets loaded with a 20ms refresh. Anyway I edited the rule to trigger 300 times with a one second rearm and applied it to the 15:40 at Newmarket in the few minutes before the off.
Again, I am logging market volume which I know will almost certainly increase every second. So I would expect the average of the last 10 seconds to always be lower than the latest value in Market HL1.
The log which I have attached here shows 600 lines of output (2 lines per each iteration of the rule) in just over five minutes. So that seems to be fine. But when you look at the log, the overwhelming number of the outputs of test_avg are identical to the latest value in Market HL 1. But here is where it gets a bit weird. Just occasionally the test_avg output will show a different value compared to Market HL1.
By way of an example from my log. Row 300 of the log with a time stamp of 15:36:41 shows test_avg < Market HL 1. Within a few seconds, however, the two values are back in lockstep.
When you only look at the end of a log and see identical outputs, you don't realise that some further up might be different.
I feel I must be missing something obvious but for the life of me I can't see why the average keeps reporting the latest HL value.
My log:
I noted your point about the refresh time and only 50 triggers but my one-click screen was refreshing at 200m and the particular instance of guardian I ran it on had all the days uk racing markets loaded with a 20ms refresh. Anyway I edited the rule to trigger 300 times with a one second rearm and applied it to the 15:40 at Newmarket in the few minutes before the off.
Again, I am logging market volume which I know will almost certainly increase every second. So I would expect the average of the last 10 seconds to always be lower than the latest value in Market HL1.
The log which I have attached here shows 600 lines of output (2 lines per each iteration of the rule) in just over five minutes. So that seems to be fine. But when you look at the log, the overwhelming number of the outputs of test_avg are identical to the latest value in Market HL 1. But here is where it gets a bit weird. Just occasionally the test_avg output will show a different value compared to Market HL1.
By way of an example from my log. Row 300 of the log with a time stamp of 15:36:41 shows test_avg < Market HL 1. Within a few seconds, however, the two values are back in lockstep.
When you only look at the end of a log and see identical outputs, you don't realise that some further up might be different.
I feel I must be missing something obvious but for the life of me I can't see why the average keeps reporting the latest HL value.
My log:
You do not have the required permissions to view the files attached to this post.
I've just shut my BA down for the night so can't check the file till morning
Just to answer this part though from the end of your post
When you only look at the end of a log and see identical outputs, you don't realise that some further up might be different.
The SV is showing the average just from now till 10 secs (or at least that's what the earlier files where doing), so the average could be different anywhere within the log and return back to same values several times
ie, if you get a lull in activity then that's going to cause the average value get closer to the latest stored value and after 10 secs (at the most) it will be back to exactly the same as the latest stored value
Just to answer this part though from the end of your post
When you only look at the end of a log and see identical outputs, you don't realise that some further up might be different.
The SV is showing the average just from now till 10 secs (or at least that's what the earlier files where doing), so the average could be different anywhere within the log and return back to same values several times
ie, if you get a lull in activity then that's going to cause the average value get closer to the latest stored value and after 10 secs (at the most) it will be back to exactly the same as the latest stored value