I tried the above trigger point logic with the above parameter in GBPUSD 15 minsTF Live this week i.e Nov 21 to 25,2022. i can see buy on entering OB and sell on Entering OS seems more fruitful.. p.s. i did not check on all 28 pairs and also not on any history data. Just one pair and understood that the trigger logics need to be changed dynamically w.r.t pairs and current behavious and also of our individual logics and filtering.. Thanks a lot Martin for all of the interesting work, research and time you are putting.. :)
Hello Martyn. I think it has processed OS on the trade shown at 15:10 because you are processing the current candlestick on H1 that hasn't closed yet. If you processed the last completed candle, you would not have taken that trade close into account. What do you think about processing current candle or last closed candle? Thank you for your generosity in sharing content.
I use both techniques in different strategies. The really important thing though is that you use the same technique in live as you do in backtest. So if you backtest using candle 1 (the most recent closed candle), then you should also do that in live. Hope that makes sense
When testing visually I just use one single pair. But after confirming the logic is correct I will be using 28 pairs for the actual analysis and results
Hi Martyn, I didn't understand the last part- are you running the test on H1 or M5? I get the part where you say you're processing per-min instead of per-tick. BTW- I ran on EURUSD for the same time period- I'm not getting profitable results at M5, only higher time-frames M30, H1 etc. Could be because of my commissions(7$/lot). Also- can you please do one tutorial on how to export and analyze your test results?
Hi. I am testing using indicators on the H1 timeframe. I am assuming you ask the question because I am running the backrest on an M5 chart in the strategy tester settings tab. This setting is analogous to the chart that the EA is being run on. In my code I never rely on the chart timeframe (or the chart symbol). I always have timeframe and symbols as variables and then pass these values to indicators etc. So the symbol and timeframe on the settings tab are irrelevant to the way my EA operates. So yes H1, and yes I agree with your conclusion that charges will be too large in comparison to the edge in lower timeframes. I have added your final request to my list of future videos. Thanks, Martyn
@@Darwinexchange Wow! Thanks for taking time and replying. Another minor future request: how to sanitise and verify your historical data. I'm using Dukascopy data and I'm getting wild results(could be a bug with downloading software). Is the data available with Darwinex sanitized?
Great way of exposing the concepts. I look forward to the next ones! 💪🏽
Thanks Xavier. Martyn
Good sir, the quality of your content made a very big impact on my career as an Algo developer.
Happy to hear that! Martyn
I tried the above trigger point logic with the above parameter in GBPUSD 15 minsTF Live this week i.e Nov 21 to 25,2022. i can see buy on entering OB and sell on Entering OS seems more fruitful.. p.s. i did not check on all 28 pairs and also not on any history data. Just one pair and understood that the trigger logics need to be changed dynamically w.r.t pairs and current behavious and also of our individual logics and filtering.. Thanks a lot Martin for all of the interesting work, research and time you are putting.. :)
Nice content. Thank you for sharing this playlist(spotlight on indicators). Have gained good insight on indicators
Thanks for the feedback. Martyn
Hello Martyn.
I think it has processed OS on the trade shown at 15:10 because you are processing the current candlestick on H1 that hasn't closed yet. If you processed the last completed candle, you would not have taken that trade close into account.
What do you think about processing current candle or last closed candle?
Thank you for your generosity in sharing content.
I use both techniques in different strategies. The really important thing though is that you use the same technique in live as you do in backtest. So if you backtest using candle 1 (the most recent closed candle), then you should also do that in live. Hope that makes sense
In that test you ran, was it just on UJ, GJ and GU or all 28 pairs?
When testing visually I just use one single pair. But after confirming the logic is correct I will be using 28 pairs for the actual analysis and results
Really great series of videos. thank you so much. I've learned so much from these videos. and is it possible to share the code?
Code coming soon (in a couple of episode's time).. cheers, Martyn
Hi Martyn,
I didn't understand the last part- are you running the test on H1 or M5?
I get the part where you say you're processing per-min instead of per-tick.
BTW- I ran on EURUSD for the same time period- I'm not getting profitable results at M5, only higher time-frames M30, H1 etc.
Could be because of my commissions(7$/lot).
Also- can you please do one tutorial on how to export and analyze your test results?
Hi. I am testing using indicators on the H1 timeframe. I am assuming you ask the question because I am running the backrest on an M5 chart in the strategy tester settings tab. This setting is analogous to the chart that the EA is being run on. In my code I never rely on the chart timeframe (or the chart symbol). I always have timeframe and symbols as variables and then pass these values to indicators etc. So the symbol and timeframe on the settings tab are irrelevant to the way my EA operates. So yes H1, and yes I agree with your conclusion that charges will be too large in comparison to the edge in lower timeframes. I have added your final request to my list of future videos. Thanks, Martyn
@@Darwinexchange Wow! Thanks for taking time and replying. Another minor future request: how to sanitise and verify your historical data. I'm using Dukascopy data and I'm getting wild results(could be a bug with downloading software).
Is the data available with Darwinex sanitized?
I really want to see the results!!
They'll be out 19th November Leon.... Cheers, Martyn