I have been messing about and i think i have found a bug.
Using a simple rule guardian appers to send 2 signals when only 1 shounld be sent.
Using historic relative odds to check if the lay price on the fav is lower than it was a second ago,thats works fine.
The problemm is when the guardian market is open in BA and BA is refreshing faster than a second and guadian is faster than 750ms.The allow rule to trigger wait was a second.
I was testing this in a dead market by placing bets in front of one another.when Ba was to fast double signals were being sent.
Am I using it wrong or is this a bug ?
double signal bug ?
Not quiet sure what you mean here, unless your running more than one rule type which is triggering a signal then the most signals that it should be possible to set is 1 per sec.
If you want to upload the file i can check see if its working as it should be
If you want to upload the file i can check see if its working as it should be
Hi Dallas
Sorry for the slow response. Here is the file i was testing. I have adapted it so it bets automatically for demonstration purpose.
This should be opened in a market that has no activity. I tested it in a Australian market. Pick a horse were the lay price is close to 1000 and back price is alot lower. Just make sure there is a nice big gap.
Here are the results I got testing at different refresh rates. The refresh rates refer to guardian, the main BA refresh rate was turned off. The results show the number of signals recorded at different refresh rates. I tested each refresh rate 3 times. The results I expected are the results I got at 1 second. All other refresh rates are all wide of the mark.
I can sort of see why I’m getting these results but don’t believe I should be getting them. I don’t believe I should be getting them due to the rearm wait time.
I guess it’s happening because the seconds are over lapping.
I do have the logs for both test but there’s about 40 pages in total .So I wont post them here.
Sorry for the slow response. Here is the file i was testing. I have adapted it so it bets automatically for demonstration purpose.
This should be opened in a market that has no activity. I tested it in a Australian market. Pick a horse were the lay price is close to 1000 and back price is alot lower. Just make sure there is a nice big gap.
Here are the results I got testing at different refresh rates. The refresh rates refer to guardian, the main BA refresh rate was turned off. The results show the number of signals recorded at different refresh rates. I tested each refresh rate 3 times. The results I expected are the results I got at 1 second. All other refresh rates are all wide of the mark.
I can sort of see why I’m getting these results but don’t believe I should be getting them. I don’t believe I should be getting them due to the rearm wait time.
I guess it’s happening because the seconds are over lapping.
I do have the logs for both test but there’s about 40 pages in total .So I wont post them here.
You do not have the required permissions to view the files attached to this post.
I've tested the rule as it was then also removed the back part and left just the signal's set on both times signals where setting just fine at exactly 1 per sec intervals (as per the re-arm time) and 5 secs for the back bets as per the re-arm time.
I tried several refresh settings and got the same results everytime, the log below shows when it was on main screen at 40ms and guardian at 20ms
Bottom image - no back bets
Top image - original rule
I tried several refresh settings and got the same results everytime, the log below shows when it was on main screen at 40ms and guardian at 20ms
Bottom image - no back bets
Top image - original rule
You do not have the required permissions to view the files attached to this post.