Errors, bugs, questions - page 1988
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
That's right, there are, here they are:
2017.09.05
2017.09.05 11:42:04:04 Logger log was cleaned
2017.09.05 2017.09.05 00:00:00.000 Server MetaTester 5 stopped
There's nothing else out there.
So why is there no complete Print() information in the tester logs?
Free up disk space. The logs are cleared if the disk space is less than 500 meg
How are they cleaned? Where can I find out about the cleaning algorithm? Where is the message that the logs have been cleaned?
How to work with the programme if it does not do what is expected of it? - We are talking about MT5 as well, not only about Expert Advisor.
In my specific example we can see in the logs that the ticks are skipped. What is a user to think in this case? What bright pure thoughts can arise unclouded by foul language?
In the tester visual mode, the speed slider position is memorised. I set it to maximum once. Then I run a heavy EA - the visualizer hangs.
I have to make a dummy EA and run it in the visualizer and move the slider back a bit. A heavy EA does not hang after that.
Is it possible to set the slider position in advance (as it is in MT4)?
During a single run without visualization, I run an Expert Advisor that performs many trades, clogging the log with appropriate messages (the tester itself likes to output them). After the backtest (or immediately after pressing Stop) I switch to the Log tab and see the logs continue to be displayed. This is the first nonsense, since the backtest is over, why not show the end of the logs?
I'm not interested in the logs and click "Delete logs". After which the log is cleared and... continues to fill up with old records!
How are they cleaned? Where can I find out about the cleaning algorithm? Where is the message that the logs have been cleaned?
How to work with the programme if it does not do what is expected of it? - We are talking about MT5 as well, not only about Expert Advisor.
In my particular example, you can see in the logs that ticks are skipped. What is a user to think in this case? What bright pure thoughts may arise unclouded by foul language?
You've never looked at the tester agent logs before.
The message about clearing the logs is the one you showed yourself.
If you analyze the logs of the tester, then you are a priori considered a skilled user. A wizard must always keep an eye on his tool. Windows Explorer always shows a drive with little free space in red
BTW even if your dashboard has a tyre pressure indicator, this in no way cancels a visual inspection of the vehicle before driving
During a single run without visualization, I run an Expert Advisor that performs many trades, clogging the log with appropriate messages (the tester itself likes to output them). After the backtest (or immediately after pressing Stop) I switch to the Log tab and see the logs continue to be displayed. This is the first nonsense, since the backtest is over, why not show the end of the logs?
I'm not interested in the logs and click "Delete logs". After which the log is cleared and... continues to fill up with old records!
Yes, it's a good idea to disable the output to the log during a test without visualisation. More often you just want to see the final result (profit, test time, etc.), which is displayed at the very end.
Details during the test can be viewed in the visualisation mode. There is no point in reactively dumping this "pile" without visualization.
Here's the test code if you're interested.
I think I've found the cause and a temporary solution to this problem. It's hard for me to explain how it happens, but it seems that the colour buffer interferes and messes everything up.
Here's what I changed in the source code and the problem disappeared
Why does the tester do this?
1. You have never looked at the tester agent logs before.
The message about clearing the log is the one you showed yourself.
2. If you are analysing the tester logs, you are a priori considered a skilled user. A wizard must always keep an eye on his tool. Windows Explorer always shows a drive with little free space in red
BTW even if your dashboard has a tyre pressure indicator, it by no means cancels a visual inspection of the vehicle before driving
1. I've never had to do this because it wasn't necessary - the tester logs always showed what was expected.
2. Who cares what windows explorer shows? We work in MT5 and it just has to tell the user that there is not enough memory (or any other reason not allowing to work normally).
Yes, the reason was that the free space was less than 500mb and not only logs were printed completely without any skips, but the lags disappeared during the test (it is unclear why any lags occur at all if logs are printed anyway regardless of the test). But how does the user know that we need at least 500Mb? Why not 2Mb, 100Mb, 100500Gb? - The agent/tester should display messages about problems interfering with normal operation.
And, there just needs to be a choice of what to output to the log.
I think I've found the cause and a temporary solution to this problem. It's hard for me to explain how this happens, but it seems that the colour buffer is interfering and messing everything up.
Here's what I changed in the source code and the problem disappeared