Hey - back with another question which I think is particularly important. For some rules, it can be determined whether or not the rule will be triggered without even the event taking place. For example, imagine the rule:
back the 3rd fav IF
- Number of matched bets = 1
- race distance > 20f
Running this rule on a 7f race will mean that this rule will never be triggered. When Guardian evaluates this rule the first time, does it know it will always be false and not revaluate it ever again, even if other conditions may change? (e.g. number of matched bets may become 1 at some point).
I ask because if one has many rules of this nature for different race types then re-evaluating 20 rules, 19 of which will always be false continuously would be a waste of cpu cycles and perhaps throw the timing off a little?
disclaimer: the rule above is completely arbitrary and not reflective of a strategy, lol
Behaviour of guardian with rules that are not eligible
Guardian will check every rule of an automation file each time the market is refreshed and trigger a rule if all its conditions are met and their is any triggers remaining for that rule type. Its quiet capable of checking a hundred rules contained within an automation file (and all associated conditions for that rule)
Ok sweet thank you DallasDallas wrote: ↑Wed May 17, 2017 6:31 pmGuardian will check every rule of an automation file each time the market is refreshed and trigger a rule if all its conditions are met and their is any triggers remaining for that rule type. Its quiet capable of checking a hundred rules contained within an automation file (and all associated conditions for that rule)