[mainwParticipant February 12, 2015 at 1:06 pm Post count: 6]

in reply to: Data gaps and bad ticks – error source? #20461

thanks for the reply.

How about the “include weekends” option? I still don’t quite understand what it does even after reading the faq

appending to an existing FXT file will be superb, can’t wait 🙂

[mainwParticipant February 10, 2015 at 12:13 pm Post count: 6]

in reply to: Data gaps and bad ticks – error source? #20459

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 “include weekends” option when exporting to mt4? My broker is aligned with “5pm New York market close”, so for me that means:

1. inlcude weekends – unchecked
2. timezone – leave it at UTC
3. daylight savings – unchecked

Is my understanding correct?

Also, is it possible to append to fxt/hst? Am asking because it seems each time (say every month) i need to backtest with the latest data, I have to build the fxt/hst from the start all over again. There must be a better way?

[mainwParticipant December 31, 2012 at 5:29 am Post count: 6]

in reply to: Accuracy of Data #18474

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 happened more often compared to dukascopy tickdata for the same pair. So in the end, I opt for dukascopy tickdata as it has less gap and happen less often.
Without knowing this “information”, users won’t know about gap and how accurate their data is…

Yup, birt’s csv2fxt has a check for duplicate ticks. Will that be released in the next version of tickstory?

BTW, happy new year 2013!

[mainwParticipant December 30, 2012 at 10:56 am Post count: 6]

in reply to: Accuracy of Data #18472

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/generating csv from tickdata

BUT, here’s the big BUT…
There are still gaps in dukascopy data (not a lot, but it’s there. They are still the best though when compared to other data sources)

I’m not actually suggesting for the feature – “provides other datasources such as a CSV import”
But am suggesting that tickstory perform some integrity check when building the mt4 fxt/hst and report if there are any gaps.

Another observation:
The tickstory built fxt are much bigger in file size compared to those i generated back in july 2012 using csv2fxt
That certainly sounds strange since i take it that with smaller bi5 introduced from dukascopy “sometime this year”, I would assume that the generated fxt would also be smaller?

[mainwParticipant December 29, 2012 at 5:53 pm Post count: 6]

in reply to: Accuracy of Data #18478

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 needing a csv, i wonder how does that work?
can tickstory generate a report showing if there are any gaps after finishing building fxt/hst?

[mainwParticipant December 28, 2012 at 5:47 am Post count: 6]

in reply to: Accuracy of Data #18476

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 …pathTojforex.cachepair….bi5. Attempting redownload

Is that normal or what?

Note that all existing data were downloaded back in July 2012, it was valid and i was able to do 99% backtest with it. Why is tickstory now saying “error occured processing file …bi5 and have to redownload again?

Please advise.

* btw, what is this “on the fly” candle that you mentioned previously?

* you have my email, email me and i can send you some sample *.bi5 file between now and then which are both different, for your comparison

[Author]

Posts