Errors, bugs, questions - page 2223
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
Yes, I already gave this link to your implementation in post 22214. I'll say it again - I think this is the most sensible option so far. And it seems that there is no better implementation in terms of minimal CPU load and relevance of the moment of a new tick.
There will be normal functionality in Services.
In Services there will be normal functionality.
hopefully...
The terminal (1874) stops showing (chart or query) the bar history of the custom symbol when switching to another trading server. After Terminal restart the history is shown. As soon as you switch to another server again, the situation repeats.
Tick history does not suffer when switching trading server. This bug is not present there.
Is this how the ME is supposed to behave?
Error in FileLoad. If two local Agents with FILE_COMMON flag try to read data through FileLoad, one of the Agents fails.
It is possible to set appropriate flags in FileOpen, but not in FileLoad. Therefore, please allow access to the file via FileLoad if the other FileLoad reads it.
Forum on trading, automated trading systems and trading strategy testing
Not for MT Developers! What to replace INIT_PARAMETERS_INCORRECT with ?
fxsaber, 2018.07.10 20:16
Ancient bug.
Is it possible to keep tester_file in RAM to avoid HDD/SSD abuse? There are millions of passes and it's horrible to count the file so many times.
Such a "RAM-disk" would make it much more difficult for unauthorized transfer of personal data to third parties.
The new optimisation caches do not take into account changes to the tester_file and Common files before running Optimisation.
Here is an example of such an EA.
The new optimisation caches do not take into account changes to the tester_file and Common files before running Optimisation.
Here is an example of such an EA.
Have the old ones been taken into account or not?
Nothing has changed from "old" optimization caches.
If you slip a modified tester_file with the same file modification time, the file will be considered as unchanged.
Common files cannot be controlled in any way (and never have been), because it is unknown which of them you use in your Expert Advisor
If you slip a modified tester_file with the same file modification time, the file will be assumed to be unmodified.
The updated modification time has no effect on the result. Expert Advisor
Result of two consecutive runs
Marked in red, the second run corresponds exactly to the values of the first run, not the second (second line).
The log confirms it
If I reset the cache (recompile), the first run is fine, further on it is not.