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
Today I was also dealing with this script and I still as well as traveller00 2 have an understanding that there is a double check for the presence of refresh: suppose that Sync = t rue(i.e. there is a need to make Refresh).
- first we run Refresh() - in the section of all symbols we have determined whether there are updates on the server,
We got the list of Online and Offline files.
- then run Update(false) - download new zip files on a particular symbol, false prevents repeated Refresh,
Download the difference in the lists.
- then execute ToCustomSymbol(Sync, false, MinPips) - here we rebuild the custom symbol, but if initially Sync = t rue, there is a repeated call of Refresh(true) .
Since there was synchronisation, after uploading we need to refresh the Offline list to start parsing the quotes from it.
I checked. Sometimes even the candles on M15 don't match.
They don't have to match. Shift ticks by one millisecond and you will see how even H1 bars have changed.
The source of ticks for the script now has MT5. So it is possible (haven't tried it) to use it directly.
Either I'm unlucky or it's better not to use directly. Ran for the last 3 months
Either I'm unlucky or it's better not to use direct. I've been running it for the last three months
I was talking about the tick source, not the backtest on the original symbol.
MT5 Tester prioritises M1 bars over ticks. That's why there are so many errors in the log.
it is better not to test directly on the symbol.
Forum on trading, automated trading systems and testing trading strategies
Libraries: Symbol
fxsaber, 2020.03.26 08:02
If we open a demo account on Swissquote-Server and run this script, we will get the following line.
It means that in the tick history Bid/Ask prices differ by 5 pips from those broadcasted in the Market Watch (there are better prices there than in the history).
Accordingly, in the Tester you cannot recreate what you see in the Terminal on the original symbol.
The only solution is to use a custom symbol, which is based on the corresponding demarcap of the tick history.
I.e. Tester on the original symbol can produce fully synchronised tick and bar histories - no errors in the logs. Only the result will be bullshit.
I don't know if it's a bug or a feature, but it can cause errors. In unfiltered quote the instrument type remains forex.