Scripts: ThirdPartyTicks - page 15

New comment
 
Sergey Demidov #:

Installed it, nothing shows up in the terminal in any folder and in the tester too.

The script log starts with such lines.

2023.01.07 11:59:56.060 ThirdPartyTicks (CADCHF,M1)     Downloading https://rannforex.com/static/ticks_archive/
2023.01.07 11:59:59.932 ThirdPartyTicks (CADCHF,M1)     Done! - 13549596 bytes (3496 Kb/s.)

If there is nothing like this (for example, the number of bytes is less), you should look for a reason outside the script.

 
Forester #:

https://www.mql5.com/ru/forum/232030/page2#comment_7069847

I wanted to try to run this Expert Advisor, but I get an error when compiling.
The error is caused by the line
this.Add(this.MinMax, RESERVE);

How can I fix it?

Remove the word RESERVE.

Describe briefly how the profit is calculated in this script? The code doesn't make any sense.

It's a ZigZag algorithm with a minimum knee. The rest is written in the link in the comment.

 
fxsaber #:

Remove the word RESERVE.

This is a ZigZag algorithm with minimal knee. The rest is written in the link in the comment.

Yes, I had already figured it out, that's why I deleted the questions. Strange that you saw them)
 
Forester #:
deleted the questions. I'm surprised you saw them)

When there were questions, I left the tabs open so I'd remember to answer when I had a chance.

 

It's not a quick fix? I can't figure it out myself, older versions of MT won't run

 
Rorschach #:

It's not a quick fix? I can't figure it out myself, older versions of MT won't run

Most likely, there is not enough memory. You can make sure of it by looking in the second Journal of the terminal.

 
fxsaber #:

Most likely, there is not enough memory. You can verify this by looking in the second Journal of the terminal.

Yes it is. Is it related to reserve_size in ArrayResize(), if yes, in which file can it be corrected?


 
Rorschach #:

Yes it is. This is related to reserve_size in ArrayResize(), if yes in which file can I tweak it?

This is not a one-two punch. It is supposed to allocate memory for the entire length of the history. And this is indeed a lot.

All for the reason that when the tool was written, copying historical ticks in parts into a custom symbol, not at once, worked crookedly (MQ did not correct their errors for a long time).

Now you can probably convert to piecewise writing ticks to a custom symbol. But I won't even take a look at it.

1...89101112131415
New comment