MetaTrader 5 Strategy Tester: bugs, bugs, suggestions for improvement - page 29

[fxsaber]

If you import a cache and then export it, it will not be the imported cache, but the last counted in the optimiser.

[fxsaber]

After importing the cache, there is no mention anywhere that a cache taken from there is in front of you. So sometimes you don't know if you are looking at your own opt-file or some regular one.

You have to double-check all the time that the correct file is shown.

[Slava]

fxsaber:

Wait, so this is initial_deposit - initial deposit. It has nothing to do with optimization criterion.

When you do classic optimization (not by all symbols), this field is filled with initial deposit.

There is another field for optimization criterion - custom_fitness.

custom_fitness contains the result of the OnTester

[fxsaber]

It used to be very convenient to work with optimisation results. You select an interesting pass, then do sorting by some column, and the selected pass remains selected and visible.

Now, after sorting, just the top row is highlighted, the pass before that is completely lost from visibility.

Is it possible to bring back the old behaviour?

[Slava]

fxsaber:

It used to be very convenient to work with optimisation results. You select an interesting pass, then do sorting by some column, and the selected pass remains selected and visible.

Now, after sorting, just the top row is highlighted, the pass before that is completely lost from visibility.

Is it possible to get the old behaviour back?

Nothing has been changed in this place. Maybe it was accidentally broken off.

Let's see

[Ivan Titov]

Why does the OrderCalcMargin() function return one value in the visual testing, but actually an open order with the same parameters uses a different value? Because of this, it is impossible to calculate the maximum order volume for a guaranteed opening.

[Vladimir Karputov]

Ivan Titov:
Why does the OrderCalcMargin() function return one value in a visual testing, but actually an open order with the same parameters uses a different value? Because of this, we cannot calculate the volume of the order for a guaranteed opening.

OrderCalcMargin-Calculates the amount of margin required for the specified order type in the current account and in the current market environment, excluding current pending orders and open positions. Allows you to estimate the amount of margin for the planned trade. The value is returned in the currency of the account.

And in the trade request you send the volume, which you have specified yourself.

That is carefully:OrderCalcMargin-calculates the amount of margin, and in the trade request you send the volume that you have specified

[Ivan Titov]

I send the same volume in both trade request and function call (other parameters are also the same). But the function returns one value, and the free margin decreases by another value after the trade request is executed. There are no other pending orders or open positions.

[zevs1980]

Good afternoon. Built an owl on 5 TS and 5 pairs, input parameters only 670 (less than maximum 1024). Attempting to run optimisation it gives out 2019.11.21 09:19:11.249 Tester no optimised parameter selected, please check input(s) to be optimised and set start, step and stop values. All checkboxes checked, all intervals set, number of options per parameter from 3 to 40. When I run it by one tool (134 parameters), optimization works, when I run it by two. When I run it by three (402 parameters), I get the same message again. Each character separately is not an option, I want to optimize it all together (that's what I created the owl for). Where to dig, who knows?

[Andrey Dik]

zevs1980:
Good afternoon. Built an owl on 5 TS and 5 pairs, input parameters only 670 (less than maximum 1024). Attempting to run optimisation it gives out 2019.11.21 09:19:11.249 Tester no optimised parameter selected, please check input(s) to be optimised and set start, step and stop values. All checkboxes checked, all intervals set, number of options per parameter from 3 to 40. When I run it by one tool (134 parameters), optimization works, when I run it by two. When I run it by three (402 parameters), I get the same message again. Each character separately is not an option, I want to optimize it all together (that's what I created the owl for). Where to dig, who knows?

message me in pseudo