You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
....
Tester mode includes optimisation mode, but not vice versa.
No. On the contrary.
I'm afraid I do not understand.
If MQL_OPTIMIZATION is included in MQL_TESTER, why check it too?
I'm afraid I don't understand.
If MQL_OPTIMIZATION is included in MQL_TESTER, why check it too?
Exactly right. If not a tester or optimiser, you don't get in here at all )))
Artem, if I understood correctly, then my such construction
is superfluous?
It will be enough
?
We know that we are working in the tester, but we don't know if it is a single pass or optimization, so we have to check the optimization flag
Yes, Andrew, I understand that.
But this is a general question. If I'm optimizing or testing, some statistics is being collected for using in OnTester().
Therefore, my question is whether it is sufficient to writeif(MQLInfoInteger(MQL_TESTER)) orif(MQLInfoInteger(MQL_OPTIMIZATION) || MQLInfoInteger(MQL_TESTER))?
If the optimization is part of the test, then checking for the optimization mode seems to be unnecessary...
But this is a general question. If I'm optimizing or testing, some statistics is being collected for using in OnTester().
Therefore, my question is whether it is sufficient to writeif(MQLInfoInteger(MQL_TESTER)) orif(MQLInfoInteger(MQL_OPTIMIZATION) || MQLInfoInteger(MQL_TESTER))?
If the optimization is part of the test, then checking for the optimization mode seems unnecessary...
Why complicate the construction?
Looks like you have files for the real, for tester and optimizer.
In that case - yours:
you could write it this way:
and that's it -- all your files will be clearly distinguishable by tester, optimizer and real
why complicate the design?
It looks like you have files for the real, for the tester and for the optimiser.
In that case, they're yours:
you could write it this way:
and that's it -- all your files will be distinguishable by tester, optimizer and real
Is this check really necessary?
Is this test necessary?
you need to start with -- what is the purpose of the distinction between tester, optimiser and real in your system?
why can't you do without these checks?
you have to start with -- what is the purpose of the distinction between tester, optimiser and real in your system?
Why can't you do without them?
Forum on trading, automated trading systems and strategy testing
What the hell is going on?
Sergey Tabolin, 2020.05.20 15:11
Yes, Andrey, I understand it.
But it is a general question. If I'm optimizing or testing, I collect some statistics for using in OnTester().
Therefore, my question is whether it is sufficient to writeif(MQLInfoInteger(MQL_TESTER)) orif(MQLInfoInteger(MQL_OPTIMIZATION) || MQLInfoInteger(MQL_TESTER))?
If the optimization is part of the test, then checking for the optimization mode seems to be unnecessary...
Why are you asking anyone?
CheckMQLInfoInteger(MQL_TESTER) andMQLInfoInteger(MQL_OPTIMIZATION) values in tester and optimizer
and you will see for yourself.