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
Latest figures
https://www.mql5.com/ru/forum/381623#comment_25821280
Latest figures
https://www.mql5.com/ru/forum/381623#comment_25821280
No one is going to look at it and take it apart. Until there is a comparative analysis of exchange ticks and MT5, the conversation is empty. Because it can always be said that it is the exchange that is broadcasting crooked data to the broker.
No one is going to look at it and take it apart. Until there is a comparative analysis of exchange ticks and MT5, the conversation is empty. Because it can always be said that it is the stock exchange that is broadcasting crooked data to the broker.
There are some things that don't require external confirmation if you just look closely...
There are some things that don't require external validation if you just look closely...
Forum on trading, automated trading systems and trading strategy testing
Testing 'CopyTicks'
fxsaber, 2021.11.12 08:05
You can always say that it's the exchange that is broadcasting crooked data to the broker.
More
https://www.mql5.com/ru/forum/381623/page2#comment_25871123
Watch the video step by step
https://www.mql5.com/ru/forum/381623/page2#comment_25878109
And finally
https://www.mql5.com/ru/forum/381623/page4#comment_25943280
Do I understand correctly that finding out the actual tick at a certain point in time is a difficult task?
For example, you need to find out which tick was actual 2022.04.29 23:00:00.000. In the screenshot it is highlighted.
The only solution that came to mind.
Do I understand correctly that finding out the actual tick at a certain point in time is a difficult task?
For example, you need to find out which tick was actual 2022.04.29 23:00:00.000. In the screenshot it is highlighted.
The only solution that came to mind.
Beautifully done, it never occurred to me before that it could be done that way.
I would have corrected it in such a way, the meaning is the same, only in 1 time.
I faced such a task only when synchronizing >=2 tick arrays and here. But in both cases, synchronization is performed using the ready arrays unloaded at once. Both there and there, I synchronized by shifting the indexes one by one. I see what time (in future) is nearest and shift the index by this tool ++.
I would correct it like this - the meaning is the same, only in 1 time.
Unfortunately, it is impossible to guess the interval between adjacent ticks. Sometimes well over half a minute.