The tester tries to retrieve the history of an unrelated currency pair.
- problem with history center on MQL4 --> losing data for 4 days
- mt5 history for pairs calculation
- BACKTESTING ISSUE - please help
The... target currency pair is XAUUSD, but the operation log shows it's also trying to download historical data for XAUJPY, which is unrelated.
99% of the time, problems such as this are proverbially "your code." Inspect your symbol calling code for accuracy. To avoid any doubt whatsoever about your code, consider hardcoding all instances of symbol calls as "XAUUSD."
in my experiences, this happens when there are gaps in the history of the symbol you are testing. This has result of mt5 to make fake history to fill those gaps. These can be easily detected at the start of your backtest log in the journal. Post the start of the journal, before the 2nd trade is opened and we will point it out to you.
but this also happens if the margin currency is not the same as your account's deposit currency. This has result of mt5 to retrieve a similar symbol with the margin currency so that it can convert between the 2 currencies.
Maybe your account currency is jpy, in that case strategy tester downloads the additional pair in order to be able to convert profits to your account currency.
I.e. if you test USDJPY on an EUR Account, also EURJPY is downloaded and so on...
My account currency is JPY.
I tried replacing the _Symbol variable with "XAUUSD", but the same problem occurs.
Since the current source code works without problems on other brokers, I have requested an investigation into whether there is a problem on the broker's end and am currently awaiting the results.
The broker experiencing this issue released XAUJPY a few days ago, so I suspect the problem may have occurred during that process.
My account currency is JPY.
I tried replacing the _Symbol variable with "XAUUSD", but the same problem occurs.
Since the current source code works without problems on other brokers, I have requested an investigation into whether there is a problem on the broker's end and am currently awaiting the results.
The broker experiencing this issue released XAUJPY a few days ago, so I suspect the problem may have occurred during that process.
My account currency is JPY.
I tried replacing the _Symbol variable with "XAUUSD", but the same problem occurs.
Since the current source code works without problems on other brokers, I have requested an investigation into whether there is a problem on the broker's end and am currently awaiting the results.
The broker experiencing this issue released XAUJPY a few days ago, so I suspect the problem may have occurred during that process.
my account currency is AUD, so i have similar behaviour as you, cept mt5 downloads XAUAUD and XAUUSD to "fill" the missing gaps. These gaps are easily detected by looking at top part of your backtest log and seeing lines "missing ticks". These fake ticks are often accurate, however, they are also often "not".
ryans solution is how i get my ticks as close to 100% as i can, that is, before starting my backtests and optimisations, however, it is still, never perfect.
Have you tried forcibly downloading All historic tick data for both XAUUSD and XAUJPY? Michael Charles Schefe's experienced and posted cause makes me think that those two instruments could be related to Yen account currency. This could be a strange 1% likely cause.
I tried forcibly downloading the tick data for XAUUSD and XAUJPY and testing again, but the problem persists.
I will wait for the broker's investigation results.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use