[adminParticipant December 31, 2012 at 6:38 am Post count: 92]

in reply to: 7 digits instead of 5 #18494

Hi offgridforex, that sounds positive from a Tickstory perspective. At the moment there is plan to support TDS, however for the moment the system only supports the launching of a single instance of MT4.
Kind regards.

[adminParticipant December 31, 2012 at 6:31 am Post count: 92]

in reply to: Accuracy of Data #18475

Hi mainw,

Thanks for the info. We’ll put the “gap detection” feature towards when new data sources are available. As for the duplicate tick filter, we’ll try to get this out in the next version or the one after.

Hope you have a great 2013 as well – happy trading!

Regards.

[adminParticipant December 30, 2012 at 12:10 pm Post count: 92]

in reply to: Accuracy of Data #18473

Hi mainw,

I can see the reasoning for having this integrity check but interested to know how it would be useful across Dukascopy data? After all, if there is a gap this is essentially the “raw” data that is being used for all Dukascopy & Jforex back-tests. I assume you just want to know for informational purposes?

Regarding the size of the FXT, this should not be dependent on the size of the Dukascopy data files as the FXT format remains the same. The only thing I can think of that would reduce the size of your FXT file is by filtering duplicate ticks (or any other data filter). At the moment, Tickstory does not provide this functionality.

Hope this helps.

[adminParticipant December 30, 2012 at 11:59 am Post count: 92]

in reply to: 7 digits instead of 5 #18492

Hi offgridforex,

Thanks for the further detail. Will look into this shortly, however could you please clarify your final post? Are you having similar issues with TDS? Also, are you generating the FXT file directly via Tickstory or firstly generating a CSV file that you are then processing with CSV2FXT?

Thanks.

[adminParticipant December 30, 2012 at 1:53 am Post count: 92]

in reply to: Accuracy of Data #18479

Hi mainw,

Thanks for the suggestion. At the moment since Tickstory sources its information only from Dukascopy, there is no need to perform integrity checks since the data is assumed to be complete. When Tickstory provides other datasources such as a CSV import, this feature will definitely come in handy. Consider it on the todo list.

Regards.

[adminParticipant December 29, 2012 at 10:48 pm Post count: 92]

in reply to: 7 digits instead of 5 #18495

Hi offgridforex,

Could you please give further details where you are seeing these 7 digits? Are you seeing them in an exported CSV or your back-test results? Also, could you please provide the symbol and date range where you see this happen so it can be investigated?

Thanks.

[adminParticipant December 29, 2012 at 11:24 am Post count: 92]

in reply to: CONGRATULATIONS #18427

Hi tcferreira,

Thanks for your post. Yes, Tickstory does provide end-to-end functionality to allow users to create MT4 databases with quality tick data from Dukascopy and then launch MT4 to allow you to perform 99% back-tests. This said, the intention is not to specialise in MT4 as TDS does (and I believe it does it well).
There are many additional features planned to assist traders manage their data – Metatrader being just one of the many platforms Tickstory intends to support.

Regards.

[adminParticipant December 29, 2012 at 5:28 am Post count: 92]

in reply to: Accuracy of Data #18477

Hi mainw,

Dukascopy have changed their file format at some stage this year and this is why you are seeing this error. Tickstory only supports the latest format which have significantly smaller sizes. When you see this error, it simply means that the older file format is being replaced with the newer. Once all your data has been updated to the latest format, you should not see this error again.

With regards to the candle data, Dukascopy also allow you to download candle information however rather than using and storing this data, Tickstory produces the same candle information by using the tick data. This way, it can support construction of bar information that Dukascopy may not have, not to mention there is no disk space overhead.

Hope this helps.

[adminParticipant December 29, 2012 at 1:36 am Post count: 92]

in reply to: Difference between download historical data JForex and Ticks #18502

Hi tcferreira,

The Dukascopy download feature in Tickstory utilises the same data that the Jforex platform uses so there should be no difference in the tick data that is acquired.

Regards

[adminParticipant December 19, 2012 at 10:27 pm Post count: 92]

in reply to: WEEKENDS #18450

Hi annobln,

Thanks for the feedback. The feature has been implemented and will be released in the next version (soon!).

Regards.

[adminParticipant December 19, 2012 at 1:18 am Post count: 92]

in reply to: WEEKENDS #18448

Hi annobln,

Thanks for the feedback. Compliments are always a good way to get your requests ahead in the queue 😉

To ensure everyone’s understanding is the same, a “weekend” will be considered to be “After Friday 22:00 GMT and before Sunday 21:00 GMT“.

This will ensure it captures the entire trading session inside and outside of daylight savings time (but also causing a flat bar to be generated when daylight savings is not in-effect).

Does everyone agree with this interpretation?

Regards.

[adminParticipant December 17, 2012 at 8:50 pm Post count: 92]

in reply to: Error "executable file is corrupted. Please recompile it." #18455

Great to hear! Thanks for letting us know.

[adminParticipant December 17, 2012 at 10:16 am Post count: 92]

in reply to: WEEKENDS #18445

Thanks for the further information, topgun.

A new feature needs to be added to eliminate weekend information (the system currently does not suppress any information it gets from Dukascopy).
A tracking item has been logged for this request and it will be added in the next release.

As a side note, it might be worthwhile highlighting that you do not necessarily need to “import” your data via MT4 History Center. Tickstory has the ability to create the entire MT4 history for you by simply pointing to your MT4 installation folder (just bear in mind that it will delete all existing history, so back it up if it is of any value).

To do this:

1) Select File->Settings and set your MT4 installation directory. Press OK.
2) Select the symbol you wish to export in the ‘Instrument View‘ and right-click on it and select Export To MT4.
3) Select the date range for your exported database. Ensure Generate HST files is selected. This will ensure all HST time frames are exported.
NOTE: Make sure you have closed your MT4 terminal as it could have a lock on the files and the export will fail.
4) Once the export is complete, start your MT4 terminal (it is not necessary to use the launcher since you are not back-testing, however you may want to do this for completeness).
5) In MT4, select File->New Chart->Symbol and view your exported data.

Hope this helps.

Regards.

[adminParticipant December 17, 2012 at 3:16 am Post count: 92]

in reply to: Error "executable file is corrupted. Please recompile it." #18453

Hi – you can find a MT4 Build 432 at this link:

http://www.multiupload.nl/2AB9S9505T

Regards.

[adminParticipant December 16, 2012 at 1:25 am Post count: 92]

in reply to: WEEKENDS #18443

Hi topgun,

Can you please provide a zoomed in screenshot on the 5 days around a weekend including the chart axis and title? What symbol are you using? Are you viewing the symbol in offline mode (i.e. File->Open Offline->,H1?

Thanks.

[Author]

Posts