Need help with stored values and signals

[Dabbla]

Heres an example, the description is as above.

This just looks at 1 range 1, 1-5 (range_1) ,if you wish to add more ranges, just do the same as range 1 but call it range_2 and change the relevant conditions.

The range total is SV = RANGE_1_SUM for the market (see log)

BET IN RANGE.baf

22/12/2024 08:32:07: [G_Auto 2] : Store (range calc) Value (Shared) for market: RANGE_1_SUM = 1
22/12/2024 08:32:08: [G_Auto 2] : Store (range calc) Value (Shared) for market: RANGE_1_SUM = 1
22/12/2024 08:32:08: [G_Auto 2] : Store (range calc) Value (Shared) for market: RANGE_1_SUM = 1
22/12/2024 08:32:08: [G_Auto 2] : Store (range calc) Value (Shared) for market: RANGE_1_SUM = 2
22/12/2024 08:32:08: [G_Auto 2] : Store (range calc) Value (Shared) for market: RANGE_1_SUM = 2

[Luke.B]

Great thanks dabbla will take a look. Can you tell me what version you are running. I get the attached message.
I'm on 1.62

[Dabbla]

I’m on 1.62.0 , check to make sure you’re not using 1.62 beta.

You can download the latest version here
https://www.betangel.com/download/?product=BetAngelPro

[Luke.B]

Ok thats great, i see how you have it, wasnt far off, but still slightly off. I had the store value as 0 element in the same rule and hoped to use heirachy to reset every runner and then re assess.

I have one other query, its not showing up in the one click like i had. I cant see the value 2 next to both runners that are in that range only.

[Luke.B]

this is what i had showing up , but wasnt refreshing

[Dabbla]

Because the Value 2 is set to Market, BA will display that value on all runners in the market.

[Luke.B]

Ok i tried to set for selection but that only showed for first one.
I'll have a play around.

[Luke.B]

I think i got it to work.
one question.
whats the benefit of using stored value condition when storing a value as opposed to just std condition
eg
i used fixed price - projected sp for SV condition
you used sv condition for projected sp

[Luke.B]

Nope no good, the sum rule doest refresh.
any wa to do your way and only have the sum next to the relevant range?

[Dabbla]

I think i got it to work.
one question.
whats the benefit of using stored value condition when storing a value as opposed to just std condition
eg
i used fixed price - projected sp for SV condition
you used sv condition for projected sp

The stores value conditions have a bit more flexibility.

For example with the SVC you can use the number 1 , whereas the fix odds only lets you use 1.01.

You can also use commands , e.g. greater or equals instead of just greater and equals.

[Luke.B]

Any ideas on how to make the sum only appear on the relevant selection only, if not show 0.

[Luke.B]

All good, got it. Thanks so much Dabbla for all your help and other posters. Appreciate it. Learnt alot. Also saw how and adopted your naming convention Dabbla.
Alot of counter intuitive elements. I had to do the same for the sum componant as the std sv, i had to force it to be a zero if outside range. Just hoping it would sum the range left incorrect values stored.
But it taught me for every value you want to store you need to store another when that is no longer the case.

[Luke.B]

One thing i noticed Dabbla was the use of group even though all conditions were true, is this habit or offers better efficiency. I imaging groups are great when only one needs to be true etc, just curious on why you use it if all elements true as that's default for conditions anyway