Scripts: sHistoryExport - handy script to export the historical data in the МТ4 format

New comment
 

sHistoryExport - handy script to export the historical data in the МТ4 format:

Export of all necessary instruments and time frames in one click with load and checking history

Author: Andrey Khatimlianskii

 

why its not work!

 

 

Hello, your script writes off 1 year (370 000 minute bars) in 0.5 sec, but 370 001 already causes a slipson (on a 4-core i7 2600k 4GHz, 16Gb RAM) from the Alpari server, somewhere there is an error either in the script or in the data, because the CPU and memory when the script does not disturb at all (in the task manager), also Open Office programme with generated *.csv does not open correctly, although if you look with a text editor, everything is OK.

 
EvMir:

Hello, your script writes off 1 year (370,000 minute bars) in 0.5 seconds, but 370,001 already causes a hang (on a 4-core i7 2600k 4GHz, 16Gb RAM) from the Alpari server, somewhere there is an error either in the script or in the data, because the CPU and memory do not bother me at all when the script is running (in the task manager).

If you restart the terminal and run the script with 370,001 bar in the settings, does it hang?

Are the logs empty?

Is the script deleted from the chart?

What is in the terminal settings ("Bars in the window")?

 
Good stuff!
Could you also add the option to output to .hst at once
 
wlad:
Good stuff!
Could you add an option to output to .hst at once?

In principle, you could. To save the user from pressing 3 more buttons is a must.

I will try to do it soon.

 

Hi! But I have nothing else but M1 and M5, and I've been hanging for an hour with this one.

In the settings I set M1, M5, M15, H1.

What am I doing wrong?

2013.03.14 22:52:16 sHistoryExport (GBPUSD,H1) GBPUSD, PERIOD_M30: ERROR synchronizing history!!!
2013.03.14 22:52:16 sHistoryExport (GBPUSD,H1) GBPUSD, PERIOD_M15: ERROR synchronising history!!! 2013.03.14 22:52:16 sHistoryExport (GBPUSD,H1) GBPUSD, PERIOD_M15: ERROR synchronizing history!!!
2013.03.14 22:52:16 sHistoryExport (GBPUSD,H1) GBPUSD, PERIOD_M5: 1000000 bars have been written to "History (InstaForex-Server)\GBPUSDM5.csv" within 9.7 sec!
2013.03.14 22:52:06 sHistoryExport (GBPUSD,H1) GBPUSD, PERIOD_M1: 1000000 bars have been written to "History (InstaForex-Server)\GBPUSDM1.csv" within 9.8 sec!
2013.03.14 22:51:13 sHistoryExport (EURUSD,M15) C:\Users\villi\AppData\Roaming\MetaQuotes\Terminal\761EB886B0261916FE9EA8538D91CBC9\MQL5\Files\History (InstaForex-Server)\

 
villi311:

Hi! But I have nothing else but M1 and M5, and I've been hanging for an hour with this one.

In the settings I set M1, M5, M15, H1.

What am I doing wrong?

You are doing everything correctly, but there is not enough history on the server. M1 and M5 are recorded, but M15 and M30 are not.

I will try to make it so that in this case all available history is recorded (and not display an error as it is now).

As long as you can set a smaller number of bars, everything will work.

 
The new version has been sent for testing, will be available for download in the next 1-2 days.
 
wlad:
Good stuff!
Could you add the ability to output to .hst at once?
Done. The new version will be available for download after moderator check.
 

The whole depth of history is a bit of a MYTH ...


the thing is that for example I don't need even minutes to test a strategy - 1h and above is enough ...


Take the same usd/jpy - it seems that since 1980 there is data on h1 or even 1976 at fibo for example - they have the longest history on pairs for some reason ...


but if you look carefully, the HOUR candles go only from 2000, or even from 2001 ...

and anything earlier than that - they are daily bars embedded in the HOUR period ...


of course, it's a hell of a story, not history ...


The same method of ADDING day bars is used for all periods ... 5h, 6h, 8,12 ... 1,2ч ... etc. 30m. I think so too ...


Why I don't know... but it doesn't add any credibility to the story at all ... here ...


____

12345
New comment