LifeHack for trader: one back-test is good, but four is better:
Author: Karputov Vladimir
Useful article, like almost everything is known, but collected in one pile. I didn't know about origin.txt. Do I understand correctly that on 4 cores I can run only 4 terminals for testing with only local agents, according to the number of these agents?
And it's not very clear with point 4.3
UseLocal=1 //enable/disable the ability to use local agents for testing
And how to enable/disable agents in the cloud?
Useful article, it seems that almost everything is known, but it is collected in one pile. I didn't know about origin.txt. 1. Do I understand correctly that on 4 cores I can run only 4 terminals for testing with only local agents, according to the number of these agents?
And it's not very clear with point 4.3.
2- And how to enable/disable agents in the cloud?
1. Not really: you can run one agent on one core.
2. UseCloud - enable/disable the possibility of using agents of the MQL5 Cloud Network (0 - disable, 1 - enable). If this parameter is absent, the current platform settings are used.
1. Not exactly: you can run one agent on one core.
2. UseCloud - enable/disable the possibility of using agents of the MQL5 Cloud Network (0 - disable, 1 - enable). If this parameter is absent, the current platform settings are used.
I see. Why is portable mode so bad? I don't think there are any restrictions there compared to the normal mode. I don't write to Program Files, because everything is located in the c:\forex\*** folders. Yes, it is a violation of Windows security rules, but it is convenient to access MQL4/5 folders. And while you are roaming in this roaming you will have to figure out which terminal is where...it's a pity for time.
UAC should always be enabled.
All of the above and below applies to Windows 10 - previous operating systems are not even discussed or considered.
Because of conflicts with operating system security, a user (or a programme running under him) has no rights to write to Program Files, but there are no prohibitions in AppData. What happens when the terminal is installed without the \Portable key and when UAC is enabled? Right, it is STANDARD installation and then there are no problems with writing files.
In general, you should use standard programmes and installations as much as possible - much less problems and conflicts.
UAC should always be enabled.
All of the above and below applies to Windows 10 - previous operating systems are not even discussed or considered.
Due to conflicts with operating system security, a user (or a programme running under him) has no rights to write to Program Files, but there are no prohibitions in AppData. What happens when the terminal is installed without the \Portable key and when UAC is enabled? Right, it is STANDARD installation and then there are no problems with writing files.
In general you should use standard programmes and installations as much as possible - much less problems and conflicts.
I have Win 10 x64, UAC is enabled. I wrote that I do not put terminals in Program Files, everything is in c:\forex and its subfolders. You can write there safely.
In general, it's a matter of religion, I try to live as it is more convenient, often breaking regulations, and you - as the rules are written down. This is neither good nor bad, just different characters ))
Great article.
I think it can be used as a basis for automatic launch of optimisations using the Walking Forward method (by shifting the dates of optimisations).
Is it possible to see somewhere all variants of variables and their values that can be applied in the configuration ini-file?
I am interested in running optimisations with forward. Also need to connect local agents from agents from local network and from cloud. I hope all this can be controlled from ini file?
Great article.
I think it can be used to make automatic launch of optimisations using the valking forward method (by shifting the dates of optimisations).
Is it possible to see somewhere all variants of variables and their values that can be applied in the configuration ini-file?
I am interested in running optimisations with forward. Also need to connect local agents from agents from local network and from cloud. Hope all this can be controlled from ini file?
Running with your own configuration file - here is the description of the common.ini file
Interested in running optimisation with forward. Also need to connect local agents from agents from local network and from cloud. I hope all this can be controlled from ini file?
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
New article LifeHack for trader: four backtests are better than one has been published:
Before the first single test, every trader faces the same question — "Which of the four modes to use?" Each of the provided modes has its advantages and features, so we will do it the easy way - run all four modes at once with a single button! The article shows how to use the Win API and a little magic to see all four testing chart at the same time.
Why did it happen? Imagine that the file consists of a set of cells that are following each other. Each cell contains one character. So, when something is written into the file staring from its middle, the cells are in fact overwritten. If more characters are added than there were originally (as in the example above: originally there was "df=12", and then two more characters were written - "df=1256"), then the additional characters simply corrupt the further code. That's how it looks like:
Fig. 10. Information corruption.
Author: Karputov Vladimir