I tried to form an array of time[] minute bars by ticks and compare it with the original one. I tried it on different brokers. The results are not ideal. For example, on broker "1" since JANUARY 2018, all bars match, but if I take previous years, there are a lot of "broken" bars. With broker "2" everything is OK. With MQ-Demo server also a lot of "broken" bars.
Whose fault is it? The broker? Why do the ticks not match the bars?
2019.07.2301:09:26.463 TestTicksVsBars (EURUSD,M1) ******************
2019.07.2301:09:28.217 TestTicksVsBars (EURUSD,M1) Время на загрузку 12478031 тиков = 1.635 секунд
2019.07.2301:09:28.217 TestTicksVsBars (EURUSD,M1) Время на формирование time[207157] = 119505 микросекунд
2019.07.2301:09:28.224 TestTicksVsBars (EURUSD,M1) сформировано бар с 2019.01.0206:00 - 2071572019.07.2301:09:28.225 TestTicksVsBars (EURUSD,M1) реальных баров - 2071552019.07.2301:09:28.226 TestTicksVsBars (EURUSD,M1) тики есть, бара нет. бар = 1908412019.07.0800:05:002019.07.0800:02:002019.07.2301:09:28.226 TestTicksVsBars (EURUSD,M1) тики есть, бара нет. бар = 1908412019.07.0800:05:002019.07.0800:03:002019.07.2301:09:28.226 TestTicksVsBars (EURUSD,M1) тики есть, бара нет. бар = 1908412019.07.0800:05:002019.07.0800:04:002019.07.2301:09:28.226 TestTicksVsBars (EURUSD,M1) бар есть, тиков нет. бар = 1908852019.07.0800:49:002019.07.0800:50:002019.07.2301:09:28.226 TestTicksVsBars (EURUSD,M1) ******************
2019.07.2301:11:21.408 TestTicksVsBars (EURUSD,M1) ******************
2019.07.2301:11:27.924 TestTicksVsBars (EURUSD,M1) Время на загрузку 39202241 тиков = 5.648 секунд
2019.07.2301:11:27.924 TestTicksVsBars (EURUSD,M1) Время на формирование time[578497] = 867958 микросекунд
2019.07.2301:11:27.929 TestTicksVsBars (EURUSD,M1) сформировано бар с 2018.01.0200:01 - 5784972019.07.2301:11:27.931 TestTicksVsBars (EURUSD,M1) реальных баров - 5784972019.07.2301:11:27.932 TestTicksVsBars (EURUSD,M1) Массивы равны
2019.07.2301:11:27.932 TestTicksVsBars (EURUSD,M1) ******************
Remember to put unlimited bar in the window for a proper test.
There's only one Agent enabled. 200 jobs in a full sweep.
2019.07.2420:35:37.739 Core 1 pass 191 returned result 1361.80in0:00:00.1112019.07.2420:35:37.739 Core 1 pass 192 returned result 1364.83in0:00:00.1102019.07.2420:35:37.739 Core 1 pass 193 returned result 1367.97in0:00:00.1272019.07.2420:35:37.739 Core 1 pass 194 returned result 1371.00in0:00:00.1172019.07.2420:35:38.615 Tester pass 195 not processed and added to task queue
2019.07.2420:35:38.615 Tester pass 196 not processed and added to task queue
2019.07.2420:35:38.615 Tester pass 197 not processed and added to task queue
2019.07.2420:35:38.615 Tester pass 198 not processed and added to task queue
2019.07.2420:35:38.615 Tester pass 199 not processed and added to task queue2019.07.2420:35:38.615 Core 1 pass 195 returned result 1373.83in0:00:00.1652019.07.2420:35:38.615 Core 1 pass 196 returned result 1376.71in0:00:00.2092019.07.2420:35:38.615 Core 1 pass 197 returned result 1379.64in0:00:00.1992019.07.2420:35:38.615 Core 1 pass 198 returned result 1382.55in0:00:00.1442019.07.2420:35:38.615 Core 1 pass 199 returned result 1385.43in0:00:00.1562019.07.2420:35:38.615 Core 1 pass 195 (batch of 5 tasks) started
2019.07.2420:35:38.615 Tester optimization finished, total passes 200
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Can we add sorting by number of votes in the kodobase?
Sorting by "best" is not clear at all how they are sorted and from when they became best
I tried to form an array of time[] minute bars by ticks and compare it with the original one.
I tried it on different brokers.
The results are not ideal.
For example, on broker "1" since JANUARY 2018, all bars match, but if I take previous years, there are a lot of "broken" bars.
With broker "2" everything is OK.
With MQ-Demo server also a lot of "broken" bars.
Whose fault is it? The broker? Why do the ticks not match the bars?
Remember to put unlimited bar in the window for a proper test.What has been going on with the tester for several builds in a row?
Why, after stopping debugging on historical data, there is no possibility to edit EA parameters,
and you can't start debugging again until you close the visual tester window.
Dear friends, why not add a tiny feature to the optimiser? Something like this:
Also. What is the correct way to check the delay when setting the Trade Mode?
Yesterday I set a delay of 50 ms. But TerminalInfoInteger(TERMINAL_PING_LAST) generates 0. What is wrong?
The full logs show this. Why did this occur?
How many times have I asked a question and there has been silence...
Either