But have tried modifying it! It obviously reads the consistent backing, in my case the current favorite but it also (well I'm trying) looks at the the current 2nd Favorite which is pushing out (increasing). If you take a look at my file, I'm doing this correctly or I am going wrong somewhere? So, the favorite is still leading and the horse behind gradually moving backwards, if you understand me!
Another InPlay Strategy I'm trying to work out!
Its based on Dallas's Consistance IR Backing Post viewtopic.php?f=52&t=14957
But have tried modifying it! It obviously reads the consistent backing, in my case the current favorite but it also (well I'm trying) looks at the the current 2nd Favorite which is pushing out (increasing). If you take a look at my file, I'm doing this correctly or I am going wrong somewhere? So, the favorite is still leading and the horse behind gradually moving backwards, if you understand me!
But have tried modifying it! It obviously reads the consistent backing, in my case the current favorite but it also (well I'm trying) looks at the the current 2nd Favorite which is pushing out (increasing). If you take a look at my file, I'm doing this correctly or I am going wrong somewhere? So, the favorite is still leading and the horse behind gradually moving backwards, if you understand me!
You do not have the required permissions to view the files attached to this post.
The problem is likely coming from the 2nd fav changing places
ie, 1 or 2 signals maybe getting set then its becoming 3rd, 4th, 5th fav etc and new selections become the 2nd fav momentarily,this same thing will stop the resetting of the signals correctly to
ie, 1 or 2 signals maybe getting set then its becoming 3rd, 4th, 5th fav etc and new selections become the 2nd fav momentarily,this same thing will stop the resetting of the signals correctly to
Its impossible to do it in this way (setting multiple signals) as each time the 2nd fav changes those signals are lost.
What you could do is add a 'Set/Modify signal' rule using an 'historic relative odds condition' to test the 2nd fav LTP (or back price) is now greater than 'X' seconds ago
no matter how the order changes the 2nd fav must be on the drift for the rule to trigger (if something steams in from the page then the above condition won't be true)
If you then add a 'signal changed' condition to your back rule to test that signal above has been set within 'X' seconds that should achieve what you want
What you could do is add a 'Set/Modify signal' rule using an 'historic relative odds condition' to test the 2nd fav LTP (or back price) is now greater than 'X' seconds ago
no matter how the order changes the 2nd fav must be on the drift for the rule to trigger (if something steams in from the page then the above condition won't be true)
If you then add a 'signal changed' condition to your back rule to test that signal above has been set within 'X' seconds that should achieve what you want
-
mickypaul72
- Posts: 116
- Joined: Tue May 15, 2018 1:52 pm
Hi might it be just as easy to reconfigure this baf file
You do not have the required permissions to view the files attached to this post.
