Stored values comparison

[jimibt]

Ok, as promised, a quick 'n dirty example that tracks the high and low price of a runner and then places a back bet when there is a range of 10 ticks between the high and low and the LTP is closer to the high (i.e 2-3 ticks away)...

enjoy.

Another question. Why do you use "shared" when saving a variable? If you say that runnerHigh is automatically linked to each selection.

checking *shared* allows this variable to be used by other functions inside BA. For example, you could add a custom column to the one-click screen that showed the values of these variables (that's why i recommend using a single name per variable )

[ShaunWhite]

Shared also means that it's shared between markets on the same event.

Stored Values

[RedBrain]

I modified my rule to the following:

automation_pic6.png

And also added a column to one click screen (great idea:) ) and something strange. It triggers every single time and rewite the variable with higher value in spite it has a "less" rule. I also added extra rule to make the variable 100%, because it looks like it's 0 at default.


31.05.2018 14:26:38: [G_Auto] : Store Value: runnerHigh = 100
31.05.2018 14:26:38: [G_Auto] : Store Value: runnerHigh = 33.784
31.05.2018 14:27:21: [G_Auto] : Store Value: runnerHigh = 33.784
31.05.2018 14:28:05: [G_Auto] : Store Value: runnerHigh = 33.784
31.05.2018 14:28:48: [G_Auto] : Store Value: runnerHigh = 33.557
31.05.2018 14:29:31: [G_Auto] : Store Value: runnerHigh = 33.333
31.05.2018 14:30:15: [G_Auto] : Store Value: runnerHigh = 33.557

[jimibt]

I modified my rule to the following:
automation_pic6.png

And also added a column to one click screen (great idea:) ) and something strange. It triggers every single time and rewite the variable with higher value in spite it has a "less" rule. I also added extra rule to make the variable 100%, because it looks like it's 0 at default.


31.05.2018 14:26:38: [G_Auto] : Store Value: runnerHigh = 100
31.05.2018 14:26:38: [G_Auto] : Store Value: runnerHigh = 33.784
31.05.2018 14:27:21: [G_Auto] : Store Value: runnerHigh = 33.784
31.05.2018 14:28:05: [G_Auto] : Store Value: runnerHigh = 33.784
31.05.2018 14:28:48: [G_Auto] : Store Value: runnerHigh = 33.557
31.05.2018 14:29:31: [G_Auto] : Store Value: runnerHigh = 33.333
31.05.2018 14:30:15: [G_Auto] : Store Value: runnerHigh = 33.557

the reason for the value getting set all the time is because you've also added a condition whereby the old value must be less than the new value PLUS 0.1 %. if the value is unchanged, then it will of course update the stored value. I would remove that baggage as it is actually interfering with the clean execution of the intention of that little function.

[RedBrain]

Actually no. It does not affect. I added this +0.1 trying to stop trigger it every single time, because I thought since I compare book% - it can sligtly change every time without affecting the odds on the selection. But without it - it still triggered every single time.

I found out that problem was in second condition.

automation_pic7.PNG

But I thought that all these conditions must be true AND. This is just to cut out big odds.

But this fixed odd condition set the rule to fire up every time..

[RedBrain]

And why I see stored value for only one runner in one-click screen?

Your help is very appreciated!

[Dallas]

There is a few examples in this thread in the new 'tips and tricks' section which show how to use SV on the one click screen
viewtopic.php?f=61&t=16350

[RedBrain]

There is a few examples in this thread in the new 'tips and tricks' section which show how to use SV on the one click screen
viewtopic.php?f=61&t=16350

Thank you. This was a solution.

As for this strange behaviour of triggers. I just copied the ruleset and changed the book% to odds. It woks differently. It seems that book% as I supposed sligltly changes every time. But I don't understand why it rewrite the vvariable with greater value if condition is LESS ????

[jimibt]

There is a few examples in this thread in the new 'tips and tricks' section which show how to use SV on the one click screen
viewtopic.php?f=61&t=16350

Thank you. This was a solution.

As for this strange behaviour of triggers. I just copied the ruleset and changed the book% to odds. It woks differently. It seems that book% as I supposed sligltly changes every time. But I don't understand why it rewrite the vvariable with greater value if condition is LESS ????

whereas odds DECREASE in value, the associated book'% increases in value as the odds decrease - i.e. 2 odds = 50%, 5 odds = 20% etc...

[RedBrain]

Yes, and I store into variable increasing odds and decreasing book%, and I use less. But in any case this condition must work and make the rule record variable in ONE direction (always decreasing or increasing). but it record lower and greater values as I see..

[RedBrain]

automation_pic8.png

Finally I found a solution. This seems to be related to how these variables handled inside BA. Don't understand the difference between these two - current selection=nominated selection so it should apply to the same runner.

Anyway, now it works how it should. And summer is here...

[RedBrain]

automation_pic4.png

Unfortunately, ajustment in BA can't be relative - this make very hard to work with book% maybe it should be added. I will send them email on this.

Its there already 'amount'

Finally figured out how this works. And this is not I was talking about.
Right now I had a rule triggered by book% increase in 5%

book1.PNG

Actually book% was increased from 34% to 39% , but it's absolute increase while I was talking about relative. I was expecting rule to be triggered at 34*1,05=35,7%