Ian Worthington / Publications
Forum
Bar exists when backtested, but not on real charts
Left is my EURUSD 1H chart, right is the backtester during a test around the same time. I noticed this because I use the Python API to get data, and as on the left, the 6th hour bar does not exist, but it was traded on. Can anyone explain this
Could be one of 2 functions.....
I am trying to use CArrayList with a custom class, but when I try to Add to it, it doesn't seem to know which function to use - is this a bug in the platform? How can I specify? class EntryLevel { public : void EntryLevel( double p, bool d) : price(p), direction(d) {} double price;
Wrong example in docs.
https://www.mql5.com/en/docs/series/ispread The example is not an example of ispread
[Another BUG] Symbol_trade_tick_value not accurate in backtester.
Screenshot is a printout of SYMBOL_TRADE_TICK_VALUE using a script on US30 symbol, and then run as part of an EA (exact same calling code). My account is in JPY, so the script is correctly showing that the value of one tick is about 10 yen. But in the backtester, this is just ignored, and is
[Bug] secondary charts in strategy tester don't use tester template
Please make all of the symbols used in the strategy tester use the tester template file, instead of just the first one
ChartScreenShot not working as expected
https://www.mql5.com/en/docs/chart_operations/chartscreenshot align_mode= ALIGN_LEFT works as expected, it takes data from the left side of the chart window as much WIDTH as it can but this is not what I want because it misaligns the end of the charts (weekends etc). So I tried A LIGN_RIGHT (the
Bug in debugger watch window?
Why is the value 1 when i multiply by (1) in brackets?? Am I missing something here? size*(2) = 2 But it seems those are the not values actually used in the code. In the watch window, multiplying by something in (brackets) causes the value to appear as whatever is in the brackets
timegmt() in tester is rubbish
In live I can use timegmt vs timecurrent to get the offset of the data, which means all my code can correctly use UTC times everywhere and be corrected regardless of the datasource. How are we supposed to do any kind of time related testing when there seems to be NO way to get the UTC offset of the
python api does not return UTC times
https://www.mql5.com/en/docs/integration/python_metatrader5/mt5copyticksfrom_py Looking at the Note section of this page, it says that the returned data is in UTC. But it is not, it is in the brokers defined timezone (for me, moscow time +3). (the same as the charts) it is exactly 7am UTC right now