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
I'll let you in on a big secret. At maximum test speed (32) there is no lag. The vice maximum speed (31) has ::Sleep(0). Simply switching the threads gives this difference
But I don't want to use empty loops for delay - other users will get angry: "Why the fuck did I get a 100% CPU load on nothing!"
If Sleep() is not called on every tick?
For example: Optimization is done from 2015.01.01 till 2015.12.31 = 259 days of optimization with coefficient "1" equal to 259 (minimum amount of "Total trades") or with "0.5" coefficient equal to ~129 (minimum amount of "Total trades").
For example: Optimization is done from 2015.01.01 till 2015.12.31 = 259 days of optimization with coefficient "1" equal to 259 (minimum amount of "Total trades") or with "0.5" coefficient equal to ~129 (minimum amount of "Total trades").
+1
All current criteria for the genetic optimizer are 'unrobust', i.e. the result is too overoptimized and unprofitable in the fronttest. In EAs which are available to me I am solving such problems with my own code, checking the minimum number of deals per week etc. In Expert Advisors from the Market I simply do the fullest possible test for all parameters and then process the results in excel.
Many problems would be solved if we could add the possibility to write our own code for ontester() of any EA. It probably will not have access to the EA's global variables, of course, but all data from TesterStatistics() should be readable.
Finished it later:
I thought so, it would be even better if the scripts could call optimisation. Call parameters - date, EA name and its own parameters, etc. Full functionality of the usual strategy tester. At the end of the test, the script could get all the results with full access to TesterStatistics() of each.
2. Make normal versions for Mac and Lin, so that there are no vinyls. Works in it every once in a while.
How many percent are trading under them? 1% or 1.5% ? No need to spread it around.
3. Make it possible not only to "fix" EAs with indicators, but also to update the interface.
I think the implementation of the last point will speed up the development of MT)).
What interface should I update for my trader? Please write clearer.
I'll let you in on a big secret. At maximum test speed (32) there is no lag. The vice maximum speed (31) has ::Sleep(0). Simply switching the threads makes the difference
But I don't want to use empty loops for delay - other users will get angry: "Why the fuck did I get a 100% CPU load on nothing!"
If Sleep() is not called on every tick?
Forum on trading, automated trading systems and trading strategy testing
New version of MetaTrader 4 build 950: Embedded videos and improved performance
Ramiz Mavludov, 2016.01.16 08:53
What's missing is the ability to visually test multiple TFs at the same time.