That was the condition I was using for "no more often than" before i realized that "other" triggers could have fired much latter in the process getting bigger prices.
To be more precise.
What I am trying to evaluate more scientifically and statistically, is the how the prices rise and contract relative to the relationship between the Racing post forecast (RPFC) and the
BetFair f/c prices. (BFFC)
By having any kind of back matched restriction, this usually prohibits further bets being triggered if all triggers were to share a similar condition, unless of course the back matched was around £50 for £2 single bet. but then i would have a statement several thousand rows long each day and unnecessary bets at broadly similar prices as previously struck. The Excel sheet would quickly become overloaded and cumbersome.
"Once per selection" works great because the threshold relative to the RPFC AND BFFC grows with each trigger therefore after a few thousand bets we will better understand how the prices grow and the optimum thresholds etc.
The only problem with running 40 or so triggers on "once per selection" is the that the program slows to a virtual standstill.
Hence my desire for each trigger to have a turn in backing the same selection but only "once" at that particular triggers threshold, without the contraints operationally of the "once per selection" condition slowing the BOT to a crawl.
