agree that a analysis feature for highlighting gaps will be very useful. I've been using the "export to mt4" in tickstory and what what i missed (comparing it to csv2fxt) is that there's no logs telling me if there are any gaps in the generated fxt/hst. Also, may i know how to use the &quo...
Hi admin, Yes, it's only for information purpose to know how often gaps happen in the tickdata. For me, it was useful when deciding which data source to use. For example, I had given truefx tickdata a try and used birt's approach to get the fxt/hst. What I found out was that it too has gaps and it h...
Thanks, admin. birt's approach is download tickdata from dukascopy > merge data into csv > build fxt/hst using csv2fxt tickstory approach is download tickdata from dukascopy > build fxt/hst directly using tickdata I like the approach that tickstory has taken as it takes out the effort of combining/g...
Thanks for the reply, admin. That's much clearer now. I have also previously used Birt's csv2fxt and one thing that i like in in that's missing in tickstory is this: csv2fxt shows an alert telling me where there's a gap in the tickdata. but since tickstory convert tick data to fxt/hst without needin...
Hi admin, I have data downloaded from dukascopy using jforex from 2007 to july 2012 just getting back into tickdata testing and updating + reusing my existing jforex dukascopy data to build the fxt + hst files (export to mt4 files...) the logs shows lots of: "Error occured processing file ...pa...