Hey, I know this post is old, but I found a simple solution which I want to share - If you want to prevent trading on the non-farm payroll day, or first Friday of the month, use these two time filters together:
Time filter, specify day start and finish, AND weekday filter, allow Friday. So if both these conditions are true, then you can link them to exclude from trading. It should only exclude Friday which falls on day 1 to 7 of the month.
I'm pretty sure this is working now
Hi support,
Tried multiple computers and the builder page seems to be offline? Reside in Australia, thanks
@roar No, if you use fixed SL and TP the robot is still profitable. The win rate is between 60-65% and that's with some TP's on trades being higher than SL. Hey, I tried to do backtest using MT5 but I can't seem to get the tester working. Can anyone backtest on MT5 for me?
Yes this is great jstap.
I am finding success with timing the trade exits, more so than relying just on stop losses. Particularly when it comes to trading multiple currency pairs in the account. I can monitor the equity swings closely and I'm recording when the equity highs occur to help refine the strategy
@TipsyWisdom When backtesting on M1 bar data, the ticks generated to build that candle are interpolated. That means, there are ticks that make up the OHLC of the candle, but everything in between is made up of random ticks that travel somewhat up and down.
Therefore, let's assume a candle has a high and low wick. Has it reached the high first before the close, or the low? This question is the key and holds a critical answer, at which most scalpers will be given false hopes that their system will yield real results after the backtesting looks good.
The only real way to test your strategy properly is forward testing, on a demo account. This will be very accurate and will be as close to live trading results as you're likely to get
@roar One week forward test results. Too many trades to print so here's just the details. Ended the week up just under 1,045 pips. It's taken me a whole week to figure out how to get certain variables to modify themselves under special conditions. Work in progress
So I have been stewing over this for a while and finally found a solution - How to use 2 different ATR trailing stops based on where profit is, without having them conflict.
Let's say I want to use an ATR trailing stop (x2) and have it trigger at the ATR level itself. In this case I use a variable ts_atr_mult with value of 2. I find on backtesting it triggers at the perfect time, giving the trade enough room to move into profit first. However as the trade goes further into profit, the TS is too wide to capture good profit.
Now, when profit moves let's say 85% of TP level, I want to trigger a second trailing stop that tightens from 2 x ATR to 1 x ATR. Simply having 2 trailing stops connected creates a conflict, therefore the stops jump around all over the place and it jams the testing.
How to solve this problem??
I use a condition block to check if profit is below 85% of TP, and I use 'Set Flag' true/false to fix this issue. I have the 'check flag' T/F block set to false before the condition. I have the 'set flag' to true after the negative output and below the second trailing stop. Thus, once the profit goes above 85% for the first time, the second stop is triggered and the flag is set true. Then check flag block bypasses the condition and stays on the tighter stop. Just remember to reset the flag when trades have closed. Works well to capture more profit
I don't want to sound like a wet blanket but binary options just seem like a major rip off to the trader. You're paying a 10% royalty to the broker every time you trade. You get better odds at the casino. I think you would be best just developing a tidy forex trading strategy