The natural logarithm of value in case of success. If val is negative, the function returns NaN (undefined value). If value is 0, the functionreturns INF (infinity).
This result means: the code has an error in the algorithm of value calculation (e.g. we forget to initialize variables - we just hope we will get lucky, in division operations we don't think ...).
Поиск выполняется с учетом морфологии и без учета регистра. Все буквы, независимо от того, как они введены, будут рассматриваться как строчные. По умолчанию наш поиск показывает страницы...
The natural logarithm of value in case of success. If val is negative, the function returns NaN (undefined value). If value is 0, the function returns INF (infinity).
This result means: the code contains an error in the algorithm of value calculation (e.g. we forget to initialize variables - we hope for the worst, in division operations we don't think ...).
That's all I've found in search >>> documentation (but I didn't read every description, I always find it by title - habit)
About initialization of variables (I either misunderstood you or heard about it for the first time), for example:
double a = 0, b;
... Isn't it enough? I usually declare variables and use
What can the 'inf' in the indicator on the MLQ5 mean?
This is the first time I've encountered this and I couldn't find anything in the documentation search
I figured out what the problem is!
If you have initialised the buffers EMPTY_VALUE
ArrayInitialize(Bufer,EMPTY_VALUE);
... then you copied or calculated insufficient number of timeseries in further calculations and then multiply any value by EMPTY_VALUE from the buffer - you get inf
Here I just alerited, and only multiplying by EMPTY_VALUE results in inf
... then in further calculations you have copied or calculated insufficient number of timeseries and then multiply any value by EMPTY_VALUE from buffer - then you get inf
Here I have just alerated, and only when multiplying by EMPTY_VALUE does it get inf
It looks like you found the reason. So when initializing a buffer with EMPTY_VALUE, during arithmetic operations we should first check "is EMPTY_VALUE accidentally present in the buffer at this index?
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Hello. Please show me where the error is.
Hello. Could you please show me where the error is?
somewhere in the code
somewhere in the code.
Hilarious.
This is BuySellVolume. The total volume is not equal to the sum of Buy and Sell, but only slightly more.
What can the 'inf' in the indicator on the MLQ5 mean?
This is the first time I have encountered this and I have not found anything in the documentation search
What can the 'inf' in the indicator on the MLQ5 mean?
This is the first time I've encountered this and I couldn't find anything in the documentation search
Not a good search: an INF search produces several results.
For example look in MathLog
The natural logarithm of value in case of success. If val is negative, the function returns NaN (undefined value). If value is 0, the functionreturns INF (infinity).
This result means: the code has an error in the algorithm of value calculation (e.g. we forget to initialize variables - we just hope we will get lucky, in division operations we don't think ...).
Not a good search: an INF search produces several results.
For example look in MathLog
The natural logarithm of value in case of success. If val is negative, the function returns NaN (undefined value). If value is 0, the function returns INF (infinity).
This result means: the code contains an error in the algorithm of value calculation (e.g. we forget to initialize variables - we hope for the worst, in division operations we don't think ...).
That's all I've found in search >>> documentation (but I didn't read every description, I always find it by title - habit)
About initialization of variables (I either misunderstood you or heard about it for the first time), for example:
... Isn't it enough? I usually declare variables and use
Here's everything I saw in my search >>> documentation (but I didn't read the description of each one, I always find it by the title - habit)
***
Bad habit.
... isn't that enough? I usually declare variables and use
And here comes the "black swan" - the b variable is not initialised, it can contain any rubbish.
What can the 'inf' in the indicator on the MLQ5 mean?
This is the first time I've encountered this and I couldn't find anything in the documentation search
I figured out what the problem is!
If you have initialised the buffers EMPTY_VALUE
... then you copied or calculated insufficient number of timeseries in further calculations and then multiply any value by EMPTY_VALUE from the buffer - you get inf
Here I just alerited, and only multiplying by EMPTY_VALUE results in inf
Thank you
I see what the problem is!
If you have initialised the EMPTY_VALUE buffers
... then in further calculations you have copied or calculated insufficient number of timeseries and then multiply any value by EMPTY_VALUE from buffer - then you get inf
Here I have just alerated, and only when multiplying by EMPTY_VALUE does it get inf
It looks like you found the reason. So when initializing a buffer with EMPTY_VALUE, during arithmetic operations we should first check "is EMPTY_VALUE accidentally present in the buffer at this index?