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
Units.
Probably so, but it is still a basic function and if the terminal itself uses it, at least to export data, it undermines the credibility of the terminal as well
Promised error examples in the attached file. Surprisingly, Err_SymbolInfoTick2() worked correctly for a while, but then started to return null date as well. There are explanatory comments in the code.
Log:
Fun for a snack: if you watch the ticks with the terminal tools, you can get more ticks than were recorded. (see picture ). And if the "before" date is reduced to 2021.09.18 then there are less of them recorded.
Promised error examples
Unfortunately, there is no access to these characters to reproduce.
Unfortunately, no access to these symbols to reproduce.
it's the micex. ok, i'll try the forex.
it's the MICEX. OK, I'll try the forex.
1. There is no "@BR" symbol on MICEX.
You seem to be using a custom symbol.
And there might be an error in creating it.
I use CopyTicks and CopyTicksRange functions a lot on original MICEX symbols - haven't noticed any errors.
2. The terminal doesn't store the whole tick history and the first function call may return ticks not for the whole requested period.
Added
Here is an example of an indicator, where I load ticks using the CopyTicksRange function
And everything loads fine, but not always the first time.1. There is no "@BR" symbol on MICEX
Here is an example of indicator, where I load ticks using CopyTicksRange function
And everything loads fine, but not always the first time.This is a glue of oil futures. Broker BCS. It may be called differently at different brokers. But exactly the same problems will be on other symbols.
In your example it works, because calling conditions are different - start time is always equal to start of existing bar (i.e. ticks are known to exist) and you read all tick history of the last bar at once.
By the way, one of my crutches works similar to yours. I also get the times of existing bars at first, and then break them into maximal continuous segments and get the ticks. But another problem occurs - if there's not enough of receiving array for data, the rest resuming is a tambourine dance (about which I've talked above).
And working with dynamic arrays is much slower and you have to consider possible memory fragmentation.
2. The terminal does not store the entire tick history and the first call to the function may not return ticks for the entire period requested.
There is no problem if not the whole period is returned, the problem is when another period is returned instead of the requested one. Or, even worse, when it returns the requested one and some other ticks, not included into the range
I replaced the symbol in my example with "SILV-12.21" I got the same error, and what's interesting, SymbolInfoTick returned the right answer in the last test :) but how do I guess, when it's wrong and when it's wrong?
К сожалению, нет доступа к этим символам, чтобы воспроизвести.
On forex, the same mistakes. Alpari broker, test account. EURUSD symbol
Custom symbol made on the basis of EURUSD, just left the name too