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
It should not logically be equal to zero at all - it is not clear why this is the case!
It shouldn't be zero by logic at all - I don't understand why it does that!
Run in debugger on Si-9.18. Time in rates is 2016 for some reason. Although the value of i is 2189. Accordingly, it starts the calculation at the beginning of the chart, where there is no liquidity. Initial time between start and stop is 1 hour. But for that hour, there is only one time value. It finds it with both the start and the stop variable. As a result, start = stop. Of course, if you subtract them, you get zero. I haven't figured out the rest yet.
You have d1 with tiny numbers, I avoid such problems converting price to int, i.e. for example int bid=int((tick_array[0].bid+_Point/10)/_Point); for sure, sometimes it returns 0 if calculations are performed in double
Let's not discuss d1 - if it's necessary, then it's necessary, everything is counted correctly there. The question is, why do we get the same value for start_time and stop_time, as well as start_index and stop_index?
Let's not discuss d1 - if it's necessary, then it's necessary, everything is counted correctly there. The question is why do we get the same value for start_time and stop_time as for start_index and stop_index ?
After another hang-up, the terminal stops working.... How do I resurrect it without reinstalling?
Turned out to be hanging in memory - forcibly killed the process - it started.
How is it possible that the time becomes equal? Everything has been working correctly for half a year...
Run in debugger on Si-9.18. Time in rates is 2016 for some reason. Although the value of i is 2189. Accordingly, it starts calculation at the beginning of the chart where there is no liquidity. Initial time between start and stop is 1 hour. But for that hour, there is only one time value. It finds it with both the start and the stop variable. As a result, start = stop. Of course, if you subtract them, you get zero. I haven't figured out the rest yet.
Put BarsUsed=100 in the incoming parameters.
Put BarsUsed=100 in the incoming parameters.
Yes, this way no errors occur. But if you get into some illiquid instrument or illiquid time - evening session, for example, then you can easily get 1 low bar within an hour. Thus, the limit = 0 is guaranteed for you! And if the quote is 2 - then the limit/2 will still give 0 when rounded.
Yes, that's not an error. But if you get into some illiquid instrument or illiquid time - for example, during the evening session, there might be 1 low bar in an hour. Thus, the limit = 0 is guaranteed for you! And if the quote is 2 - then the limit/2 will still be 0 when rounded.
Perhaps, I will think about it, thank you. But the global problem is something else.... The problem is that it's not stable.
It's up to you, try dividing 0.0000099999 by 2, for example
Printed d1 - for my purposes it's
Anyway, that's not the point, thanks.