A global history list ? how ?

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
User avatar
decomez6
Posts: 695
Joined: Mon Oct 07, 2019 5:26 pm

how does one populate a single list of stored values ,all from different selections ?

- the plan is to nominate different stored values from different selections and compile a list to allow calculations.



stored values calculated from a range of values.PNG

much thanks.
You do not have the required permissions to view the files attached to this post.
User avatar
Dabbla
Posts: 827
Joined: Wed Apr 15, 2009 1:50 pm

In the General tab select (Applies to Selection) Select Every.
Then store a value as current selection. That will give you one list for all runners.
User avatar
decomez6
Posts: 695
Joined: Mon Oct 07, 2019 5:26 pm

Dabbla wrote:
Wed Sep 15, 2021 11:30 am
In the General tab select (Applies to Selection) Select Every.
Then store a value as current selection. That will give you one list for all runners.
thanks Dabbla ,
yes that will store a stored value with a similar name across all selections and i can perform calculations using this option:

c) named Stored Value (across all selections) : builds the set by looking for the same named value stored against each selection in the market.

-could also go further and isolate or nominate the selections i need to capture using this condition:

isolation _nomination condition.PNG


and its all very well but

?
lets say you want to store value X for selection A
value Y for selection B

value X is not the same name as value Y this will make a global list of mixed values with different names from different sources.
would like to compile a list of the above and perform caculations using #
Store Value calculated from a Range of Values .
You do not have the required permissions to view the files attached to this post.
User avatar
Dabbla
Posts: 827
Joined: Wed Apr 15, 2009 1:50 pm

You would need to add some conditions to filter what data your looking for.
For example rule 1 is the selection over 10 = yes > Store a value called XXX1 with the data you want, lets say the back price.
You would now do the same for rule 2 but is under 10 = YES > Store a value called XXX1 with the data you want, now you can store the lay price.
You may also what to add a filter to set a 0 on an unwanted stored value. If the selection = 10 it won’t meet either criteria. Store a value called XXX1 with a 0.
You would then use the SV XXX1 to do your range calculations.
Be careful with range calculations as there is a bug in it but an easy work around.
viewtopic.php?f=37&t=24317

You may also need to add a rule at the start that sets XXX1 to 0.
Otherwise it don’t think it will calculate the rang if any of the selections are blank / cleared.
User avatar
decomez6
Posts: 695
Joined: Mon Oct 07, 2019 5:26 pm

Dabbla wrote:
Wed Sep 15, 2021 1:56 pm

rule 1 is the selection over 10 = yes > Store a value called XXX1 back price.

for rule 2 but is under 10 = YES > Store a value called XXX1 store the lay price.

If the selection = 10 it won’t meet either criteria. Store a value called XXX1 with a 0.

use the SV XXX1 to do your range calculations
.
You may also need to add a rule at the start that sets XXX1 to 0.
aha ! ok :)


- keep the same SV name XXX1 {global name}

- only change/filter the contents as required

appreciate your help Dabbla ,

much thanks
Post Reply

Return to “Bet Angel - Automation”