Also, before opening a fill-in, it should be checked to ensure that the fill-in will not result in a loss when the overall position is closed at stop loss.
Similar thoughts(#41) - see comment about Stop Loss. But I haven't made up my mind yet.
Version 1.002 can be optimised in "OHLC" mode - and the result you like can already be run in a single pass in either "All ticks" or"Every tick based on real ticks" mode.
Vladimir Karputov: Similar thoughts were(#41) - see comment about Stop Loss. But haven't decided exactly yet.
Didn't read that thought there, that's why I wrote.
Vladimir Karputov: I can optimize version 1.002 in "OHLC" mode - and the result you like may be run in a single pass in "All ticks" mode or in"Every tick based on real ticks".
CCI, as far as I know, is interesting when trading on the current bar - people usually catch signals there...
Didn't read that thought there, that's why I wrote.
CCI, as far as I know, is interesting when trading on the current bar - people usually catch signals there...
But you should try it in the tester. To avoid going too far, take the same pair USDJPY H4, from 2016.01.01 to today. I give for- 10% risk, stop loss 350.
Vladimir, tried this project in the tester and optimizer, not a single transaction, what am I doing wrong? Attached are the settings and test reports.
The interval of CCI values should be taken from "0" to "150". Time frame must be at least M15. This is not a scalper. It is not only EURUSD that needs to be tested.
Vladimir Karputov: The range of CCI values should be from "0" to "150". The timeframe is at least M15. This is not a scalper. And it is not only EURUSD that should be checked.
Ok, it would be good to attach a settings file to the zip for faster verification. Not everyone will be able to read the whole branch.
Alexey Volchanskiy: Ok, it would be nice to include a settings file in a zip, to speed up check. Because not everyone can read the whole branch.
No, I don't think that's a good approach: there are a lot of people, everyone likes different pairs and different timeframes. I'd rather prescribe it directly in the input parameters:
Ivan version "1.004":
entered variables
"Minimum distance from the price to stop loss (in pips)" - the minimum distance between the price and the Stop Loss level - if this distance is less, no position will be opened
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Also, before opening a fill-in, it should be checked to ensure that the fill-in will not result in a loss when the overall position is closed at stop loss.
Similar thoughts were(#41) - see comment about Stop Loss. But haven't decided exactly yet.
Didn't read that thought there, that's why I wrote.
I can optimize version 1.002 in "OHLC" mode - and the result you like may be run in a single pass in "All ticks" mode or in"Every tick based on real ticks".
CCI, as far as I know, is interesting when trading on the current bar - people usually catch signals there...
Didn't read that thought there, that's why I wrote.
CCI, as far as I know, is interesting when trading on the current bar - people usually catch signals there...
...
CCI, as far as I know, is interesting when trading on the current bar - people usually catch signals there...
Also, before opening a fill, I need to check if the fill will cause a loss when closing the overall position at stop loss.
I will do it like this for now:Ivan version "1.003":
I'll make it like this for now:Ivan version "1.003":
Vladimir, I have tried this project in the optimizer and tester, no deals, what am I doing wrong? Attached are the settings and test reports.
Vladimir, tried this project in the tester and optimizer, not a single transaction, what am I doing wrong? Attached are the settings and test reports.
The range of CCI values should be from "0" to "150". The timeframe is at least M15. This is not a scalper. And it is not only EURUSD that should be checked.
Ok, it would be nice to include a settings file in a zip, to speed up check. Because not everyone can read the whole branch.
No, I don't think that's a good approach: there are a lot of people, everyone likes different pairs and different timeframes. I'd rather prescribe it directly in the input parameters:
Ivan version "1.004":