Hello all...
I'm wondering if anyone here has come up with an elegant solution for filtering out unwanted trades in a mean-reversion automated strategy.
For example, I use 6 range bars in my trading. I'm in the process of developing an automated strategy around them. One thing I'm having difficulty with, on the creative side, is coming up with an elegant way of filtering out counter-trend trades without killing all the other trades in that direction. I'll explain...
Let's say I have a fast-flush down trend (morning session on the YM).
This particular strategy I'm designing, which is written using NinjaScript for NinjaTrader, is designed to trade the reversion to the mean. So it is designed to focus on weakness in peaks and troughs.
The problem is, when a fast-flush down occurs and you quickly get six red bars, and then there is a one-bar pullback in that flush (as so often happens), the strategy attempts to buy that one bar, only to have the market continue its flush on the next six to eight bars... followed by another one-bar pullback, each time canceling the short position (causing me to have to re-enter), and triggering the stop loss multiple times on the way down.
Many times, this can result in 6 to 8 stopouts in a row. It's not the end of the world, and I can disengage the strategy during these periods, which are pretty easy to see coming, but I would be interested to find a way to programmatically "edit" these trades out, so I don't have to intervene in the running of the strategy.
I'm wondering if anyone has come up with a way to deal with these fast-flush situations without killing the other mean reversion trades in their system.
Any creative ideas and input would be much appreciate. (I've considered MA crossovers, slope calculations, etc., but I haven't come up with anything yet which works well... and I'm open to hear ideas regarding MA crossovers, falling or rising MA's, oscillator tricks, etc.).
Thank you in advance.
-PD
I'm wondering if anyone here has come up with an elegant solution for filtering out unwanted trades in a mean-reversion automated strategy.
For example, I use 6 range bars in my trading. I'm in the process of developing an automated strategy around them. One thing I'm having difficulty with, on the creative side, is coming up with an elegant way of filtering out counter-trend trades without killing all the other trades in that direction. I'll explain...
Let's say I have a fast-flush down trend (morning session on the YM).
This particular strategy I'm designing, which is written using NinjaScript for NinjaTrader, is designed to trade the reversion to the mean. So it is designed to focus on weakness in peaks and troughs.
The problem is, when a fast-flush down occurs and you quickly get six red bars, and then there is a one-bar pullback in that flush (as so often happens), the strategy attempts to buy that one bar, only to have the market continue its flush on the next six to eight bars... followed by another one-bar pullback, each time canceling the short position (causing me to have to re-enter), and triggering the stop loss multiple times on the way down.
Many times, this can result in 6 to 8 stopouts in a row. It's not the end of the world, and I can disengage the strategy during these periods, which are pretty easy to see coming, but I would be interested to find a way to programmatically "edit" these trades out, so I don't have to intervene in the running of the strategy.
I'm wondering if anyone has come up with a way to deal with these fast-flush situations without killing the other mean reversion trades in their system.
Any creative ideas and input would be much appreciate. (I've considered MA crossovers, slope calculations, etc., but I haven't come up with anything yet which works well... and I'm open to hear ideas regarding MA crossovers, falling or rising MA's, oscillator tricks, etc.).
Thank you in advance.
-PD
