How do I check whether 'Optimisation' or 'Forward Optimisation' is in progress? - page 4

New comment
 
Youri Tarshecki:
I do that 12 times in a whole volking-forward cycle. This is a minute loss at worst. Compared to the duration of testing itself, sometimes measured in hours, it's insignificant. At least I've got the full report pictures of both backing and forwarding and the terminal, by the way, does not get hung up because of the oversupply of charts, because I'm clearing them.

One pass in the tester for several hours?

 
Dmitry Fedoseev:

One pass in the tester for hours?

One pass is 12 back optimisations. That's minutes. The whole cycle is 12*5=60. But after each forward step I reload the terminal, copy the charts and get the forward profit.For this I do not run optimization, but a normal run - this is the moment when OnTester data can be processed.
 
Youri Tarshecki:
One pass is 12 back optimisations. That's minutes. The whole cycle is 12*5=60. But after each step of forward, I reload the terminal, copy charts and get forward profit .For this I do not start optimization, but a usual run - this is the moment when OnTester data can be processed.
I see, I get it.
 
Dmitry Fedoseev:
Got it, got it.

How much, by the way, could such a job in the marketplace cost - processing the results of a separate forward run and storing in a file, say, two parameters - linear balance regression and net profit?

In order to make the processing work at the right time - you can make some external flag or let it check the status of tetting in the ini-file every time and on the second initialization OnTester is triggered. Saw that optimization is disabled - counted, discounted.

 
And yet the question remains unanswered, how does one determine whether 'Optimisation' or 'Forward Optimisation' is in progress in the code?
 
Youri Tarshecki:

How much, by the way, could such a job in the marketplace cost - processing the results of a separate forward run and storing in a file, say, two parameters - linear balance regression and net profit?

In order to make the processing work at the right time - you can make some external flag or let it check the status of tetting in the ini-file every time and on the second initialization OnTester is triggered. Saw that optimization is disabled - counted, discounted.

Theoretically there could be one cost, but when closer to the case - another. On forward, the optimisation is also true.
 
Lilita Bogachkova:
And yet the question remains unanswered, how to determine in the code whether 'Optimisation' or 'Forward Optimisation' is in progress?
What do you mean? Is forward optimization running or simple optimization? Or when forward optimization is running, do you need to separate back and forward runs?
 
Dmitry Fedoseev:
What do you mean? Is forward optimisation running or simple optimisation? Or, during forward optimization, should we separate back and forward runs?
You need to determine when forward optimization starts and change calculations at this time OnTester().
 
Dmitry Fedoseev:
Theoretically there may be one value, but when we get closer, it may be a different one. On forward optimization is also true.

1.

Check Ini file. If Forward -Custom &&Optimization - Disabled, start counting for the second OnTester initialization

Other cases are ignored.

2-й

Write both first and second initialization. I will decide for myself which is even and which is not

3-й

We count and write everything in a row and find the result by the number of the line in the file N=number of all optimization frames + 1

 
Lilita Bogachkova:
We need to determine when forward optimization starts and at that time OnTester() change the calculations.
Apparently only by dates, as you have already done.
1234567891011
New comment