Help filtering out sideways odds movement

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
superalf
Posts: 2
Joined: Fri Feb 07, 2020 2:36 pm

Hello,

Sorry if this has been covered before, but I am having trouble finding this info. I have created a rule to alert me to shortening prices on football markets. I have assigned this rule to the matches on my watchlist that I way I don't miss downward odds movements.

The basic condition I have setup is if the price on the selection drops by one tick to send out the alert. It works great for what I need when the price is going down steadily over time or even quickly dropping.

But the problem I'm encountering is that it alerts me when the price is basically moving sideways. By that I mean, say the price is at 2, goes up to 2.02, then drops back down to 2, I get an alert. If it repeats this cycle I get another alert. I don't want to get notified of this "market noise", I'm only interested in knowing when the price breaks through the historic/relative minimum odd the market has reached.

So I tried filtering this out by adding another condition to check the current lay price vs the lay price 5 seconds ago. If the current price is less than the one 5 seconds ago, then trigger the alert, but this did not get the intended effect. What I essentially wanted is condition to check that the current price is NOT equal to the price 5 seconds ago, but there is no negation test that I'm aware of. My rules currently look like this:

https://snipboard.io/Y9Upda.jpg

I'm thinking I could also do it using a stored value, to hold the lowest low reached, and only alert when that value is penetrated but that seems more complicated, as I would need a way to reset it from time to time, if the market drifts a lot, I would need to set a new minimum to again capture the odds shortening from a new high.

Is there a way to filter out this noise just using conditions? Thanks in advance for the help.
Jukebox
Posts: 1576
Joined: Thu Sep 06, 2012 8:07 pm

Just a suggestion for a quick fix for your alert
Add the same condition for the back price - that way you know that the market has properly shifted as both prices have moved and its not just the lay money thats appearing and disappearing from the price.
You might consider adding a relative odds condition that the back price is equal to the lay price minus 1 tick (I notice your file might be active 12hrs out when it might be a bit gappy)

You can have the same sound alert triggered by two rules: one rule with conditions detecting that prices have risen and another with conditions detecting when prices have shortened - this will give the effect of the alert sounding if prices NOT the same.
superalf
Posts: 2
Joined: Fri Feb 07, 2020 2:36 pm

Jukebox wrote:
Fri Feb 07, 2020 4:13 pm
Just a suggestion for a quick fix for your alert
Add the same condition for the back price - that way you know that the market has properly shifted as both prices have moved and its not just the lay money thats appearing and disappearing from the price.
You might consider adding a relative odds condition that the back price is equal to the lay price minus 1 tick (I notice your file might be active 12hrs out when it might be a bit gappy)

You can have the same sound alert triggered by two rules: one rule with conditions detecting that prices have risen and another with conditions detecting when prices have shortened - this will give the effect of the alert sounding if prices NOT the same.
Ok thanks. I will try this out and see if it helps.
Anbell
Posts: 2383
Joined: Fri Apr 05, 2019 2:31 am

How about this one:

Bet Angel - Servants - Shared files : Alert to a Steamer or Drifter Servant
viewtopic.php?t=15214
Post Reply

Return to “Bet Angel - Automation”