Number of Selections as a Stored Value (Template) Guardian Automation Bot

[ubfxu]

Thanks for the prompt response Dallas,

Guess I should have made myself clearer. It's not the Fixed Odds Condition that I'm having a problem with - its the timing and the setting (and/or clearing) of the Stored Value ('selections').

The Guardian Automation File seems to have been set up for a standalone market on its own.

I'm trying to run it against a day's worth of Australian Racing loaded into Guardian (100+ races) and although it works fine on the first 1 or 2 races it seems to get stuck on a value of 2 and doesn't reset itself on any further races. For Example:

8/10/2022 13:21:35: [G_Auto 1] : Store Value (Shared) for market: selections = 1
8/10/2022 13:26:39: [G_Auto 1] : Store Value (Shared) for market: selections = 1 + 1 = 2
8/10/2022 13:46:54: [G_Auto 1] : Store Value (Shared) for market: selections = 1
8/10/2022 13:51:57: [G_Auto 1] : Store Value (Shared) for market: selections = 1
8/10/2022 14:02:01: [G_Auto 1] : Store Value (Shared) for market: selections = 1
8/10/2022 14:07:05: [G_Auto 1] : Store Value (Shared) for market: selections = 1 + 1 = 2
8/10/2022 14:37:18: [G_Auto 1] : Store Value (Shared) for market: selections = 1
8/10/2022 14:42:20: [G_Auto 1] : Store Value (Shared) for market: selections = 1

Is there some sort of Clearing or Resetting that needs to be done or is it related to the Guardian Advanced Settings Refresh Time?

The only change I've made to your original Automation Bot is the addition of the Fixed Odds Condition.

[ubfxu]

Seem to have partially solved part of the problem.
It's only the Increment SV Rule that needs to have the Fixed Odds Condition - not both.

There is still an issue with the Stored Value being updated with the new Count if a Selection hovers around the Odds of 20, ie sometimes it dips below or rises above. I just want to grab the exact count at 60 seconds prior to the event start time.

[Dallas]

Thanks for the prompt response Dallas,

Guess I should have made myself clearer. It's not the Fixed Odds Condition that I'm having a problem with - its the timing and the setting (and/or clearing) of the Stored Value ('selections').

The Guardian Automation File seems to have been set up for a standalone market on its own.

I'm trying to run it against a day's worth of Australian Racing loaded into Guardian (100+ races) and although it works fine on the first 1 or 2 races it seems to get stuck on a value of 2 and doesn't reset itself on any further races. For Example:

8/10/2022 13:21:35: [G_Auto 1] : Store Value (Shared) for market: selections = 1
8/10/2022 13:26:39: [G_Auto 1] : Store Value (Shared) for market: selections = 1 + 1 = 2
8/10/2022 13:46:54: [G_Auto 1] : Store Value (Shared) for market: selections = 1
8/10/2022 13:51:57: [G_Auto 1] : Store Value (Shared) for market: selections = 1
8/10/2022 14:02:01: [G_Auto 1] : Store Value (Shared) for market: selections = 1
8/10/2022 14:07:05: [G_Auto 1] : Store Value (Shared) for market: selections = 1 + 1 = 2
8/10/2022 14:37:18: [G_Auto 1] : Store Value (Shared) for market: selections = 1
8/10/2022 14:42:20: [G_Auto 1] : Store Value (Shared) for market: selections = 1

Is there some sort of Clearing or Resetting that needs to be done or is it related to the Guardian Advanced Settings Refresh Time?

The only change I've made to your original Automation Bot is the addition of the Fixed Odds Condition.

Its probably your Guardian refresh rate

You should be able to apply it to 100s of markets and it will trigger on them all independently

[Dallas]

Seem to have partially solved part of the problem.
It's only the Increment SV Rule that needs to have the Fixed Odds Condition - not both.

There is still an issue with the Stored Value being updated with the new Count if a Selection hovers around the Odds of 20, ie sometimes it dips below or rises above. I just want to grab the exact count at 60 seconds prior to the event start time.

For that you just need to set both rule to trigger from 00:01:00 till 00:00:59 before the start

Also if you change the second rule from ANY to Every (and set the number of triggers to 1) that will count them all at once without the need for it to rearm every 200ms

[ubfxu]

Thanks for that Dallas,

Its working well now.

[Dallas]

Thanks for that Dallas,

Its working well now.

No probs

[robbed]

Hope someone here can help.

Conditions
1. Count number of runners
2. Count number of automation nomination selections
3. Calculate number of automation nominated selections as a percentage of number of runners.
4. Place back bet if:
Number of runners is less than 11
AND
Number of automation nominated selections is greater than 1
AND
Percentage of of nominations to runners is less than 50%.

I'm completely lost after point 1. It will be very helpful if someone could create a rule for me. I can handle editing it to suit some different criteria from then on.

Thanks in advance.

[Dallas]

Hope someone here can help.

Conditions
1. Count number of runners
2. Count number of automation nomination selections
3. Calculate number of automation nominated selections as a percentage of number of runners.
4. Place back bet if number of runners is less than 11 AND percentage of of nominations to runners is less than 50%.

I'm completely lost after point 1. It will be very helpful if someone could create a rule for me. I can handle editing it to suit some different criteria from then on.

Thanks in advance.

2) Create a Set/Modify Stored Value rule applied to nominated selection 1, and on the stored value tab store a value named (what ever you want ie, you could name it 'nominated') and store 'An Entered Amount' and input the value of 1

Then add another this time applied to nominated selection 2 and change the input value on the stored value tab to 2
and repeat until you get 5 rules

3) Create another Set/Modify Stored value rule this time on the stored value tab store a value named (what ever you want ie, you could name this one 'percentage'' calculate the percentage using the stored value nuame from the template of this thread against the stored values named 'nominated' (or whatever you chose to call them in step 2)

4) Add a Stored value condition to your back bet rule to test if the stored value named 'percentage (or whatever you named it in step 3) is less than 50%

[robbed]

I'm not following step 3. I don't see any options for calculating a percentage based on another stored value.