I could finally made trailstop work. I was trying to use it with value of 9 pips (as commented on the first post). But changed to 19 and is now working.
Trail stops are only functional at a value of 15 pips or greater, a true shortcoming of the MetaTrader software, nor can one enter a trade using a Trail Stop. I'm sorry I don't see that you "commented on the first post" a value of 9, otherwise I would have spoken up to advise you.
Quote:
I'm attaching a chart, in which you can see many short trades right when the price is moving up. The DD so far is 12% of the equity. If we have that trade in place, and the EA can confirm that M5 and M30 stochs are going UP (going against the trade), and crossed 20, placing hedged long trades will reduce DD and probably profit more. Same thing if long trade in place and M5 and M30 go down and crossed 80.
Yes indeed, I saw the same type of trade entries on my charts that could have been made much better.
The very simple code modifications that I posted previously seem to solve the poor trade entry problem. On your image, notice if you will the value of the 5M Stoch(5,3,3) when the short trades were entered. This simply doesn't happen using my code modifications, which enter the short trades when the 5M Stoch(5.3.3) is greater than the (100 - stoch_threshold) value. This enters the trade with less risk, reduces the DD and makes for more profitable trading both long and short, I believe.
I'm "hedging" by having one window "short only" and another "long only" with different magic numbers. Using Roger's published input values, I've optimized (since 01 March 2008) different TrailStop and stoch_threshold values for the short and long windows.
Rather than increasing the complexity of the code by introducing hedging logic and increasing its optimization run-time, I'm devoting my humble efforts to improving the trade entry criteria to minimize risk and DD. This addresses both of the concerns displayed on your chart image, I believe.
Ok, here it is the optimization report that I was running for some days.
I think that there are several logic issues on the short entrys. And at this point I'm thinking on recoding the entire EA. So please post here any sugestions if possible with pieces of corrected code.
i tried setting up the EA as u've mentioned above....i.e having "short" on one window and "long" on the other with different magic but its working only in one direction.....
is there procedure i have to follow in setting different magic numbers?
i tried setting up the EA as u've mentioned above....i.e having "short" on one window and "long" on the other with different magic but its working only in one direction.....
is there procedure i have to follow in setting different magic numbers?
Different magic numbers in the two windows is all it takes. Don't expect to see trades in both directions very often, as the trade entry criteria favour one direction or the other. It's only at potential market turns when all the stochastics reverse that we'll see both directions simultaneously.
I really think the EA as written is a good one, and the small modifications I suggested will make fewer trades, but will be profitable with less drawdown (DD). The large figures generated with backtesting to 2006 seem to be what impresses the majority of people, but I really am scared with the DD of ~50% that those ancient curve-fits generate. One doesn't know in real-time when that 50% DD will occur.
It's much more difficult to use an EA in real-time than it is to generate glorious back-test results. One actually has to wait the 2 years to see if the optimization is valid in current market conditions. Optimizing over the past 2 months once every week makes it faster to see if any tweaks will improve the anticipated performance.
Ok, here it is the optimization report that I was running for some days.
I think that there are several logic issues on the short entrys. And at this point I'm thinking on recoding the entire EA. So please post here any sugestions if possible with pieces of corrected code.
DD is a big concern here. Results look good.
As per rewriting the EA, I would recomend:
- Trade either given lot value or % of balance
- Henrietta's entry filter
- Probably use fresh signals (not sure if Henrettas filter does this) and trade only when stochs are all alligned up and start ramping up or plummeting and crossing given stochs value for each case
- Be albe to trade both directions without favouring one - Hedge option when drawdown reaches given value or % per pair, with the capability of choosing between closing all pair trades when balances out, or close just negatives when balances out. This is the most important I believe
- ATR
If more ideas, let you know. With people contributions this can really be an amazing development. Thanks again for your hard work.
Trail stops are only functional at a value of 15 pips or greater, a true shortcoming of the MetaTrader software, nor can one enter a trade using a Trail Stop. I'm sorry I don't see that you "commented on the first post" a value of 9, otherwise I would have spoken up to advise you.
Yes indeed, I saw the same type of trade entries on my charts that could have been made much better.
The very simple code modifications that I posted previously seem to solve the poor trade entry problem. On your image, notice if you will the value of the 5M Stoch(5,3,3) when the short trades were entered. This simply doesn't happen using my code modifications, which enter the short trades when the 5M Stoch(5.3.3) is greater than the (100 - stoch_threshold) value. This enters the trade with less risk, reduces the DD and makes for more profitable trading both long and short, I believe.
I'm "hedging" by having one window "short only" and another "long only" with different magic numbers. Using Roger's published input values, I've optimized (since 01 March 2008) different TrailStop and stoch_threshold values for the short and long windows.
Rather than increasing the complexity of the code by introducing hedging logic and increasing its optimization run-time, I'm devoting my humble efforts to improving the trade entry criteria to minimize risk and DD. This addresses both of the concerns displayed on your chart image, I believe.
Thanks for your comments. You're right... I didn't comment before on trailing stop value of 9. I tried to say I red it, but was wrong too. On the very first post of this trade is quoted "the stoploss u need is extremely small (5-8pips)".
As per buy only and sell only charts, how do I do that? I cannot see that option on the settings.
On the very first post of this trade is quoted "the stoploss u need is extremely small (5-8pips)".
Yes, I read that also, and couldn't understand the reasoning behind the statement, especially when the published SL = 1800, an exorbitant amount of risk.
Quote:
As per buy only and sell only charts, how do I do that?
Select a chart, then: F7 -> "Common" tab -> "positions" pull-down menu -> Only Long || Only Short || Long & Short.
It's important to realize that to have *both* a "Long Only" and "Short Only" window for the same symbol requires a different magic number for each position bias, otherwise using the same magic number will cause the closing action in one window to affect all trades in both positions long & short, with potentially unexpected results.
Select a chart, then: F7 -> "Common" tab -> "positions" pull-down menu -> Only Long || Only Short || Long & Short.
It's important to realize that to have *both* a "Long Only" and "Short Only" window for the same symbol requires a different magic number for each position bias, otherwise using the same magic number will cause the closing action in one window to affect all trades in both positions long & short, with potentially unexpected results.
You're right, silly of me. Many times people try to make things more complex than they are.
Optimizing over the past 2 months once every week makes it faster to see if any tweaks will improve the anticipated performance.
Linear Mode
