[imported_tickstoryParticipant February 16, 2014 at 10:40 pm Post count: 1479]

in reply to: Data consistency issue: changing history #19748

Hi Tickster,

Tickstory intentionally doesn’t try re-check the data if it already exists since this would obviously increase download times and bandwidth. Unfortunately there is no option to simply perform a “checksum”check and retrieve the data only if it has changed.

Hope this helps.

[imported_tickstoryParticipant February 15, 2014 at 2:54 am Post count: 1479]

in reply to: Data consistency issue: changing history #19746

Hi Tickster,

Note that all the data is provided as-is from Dukascopy – we do not alter it any way nor have the scope to alter the original data files (*.bi5). Another user recently reported the issue of different data (see viewtopic.php?f=4&t=385) and we are unsure of why it was revised, however we do know there was an update to the Dukascopy data format circa Jan 2012.

In later versions of Tickstory, we plan to have a data comparison feature which may help you resolve this issue.

Regards.

[imported_tickstoryParticipant February 13, 2014 at 11:23 pm Post count: 1479]

in reply to: Problem when exporting data to MT4 #19725

Hi Jim777,

Have a look at this step-by-step instructional video of how to back-test with Tickstory & MT4:

https://www.youtube.com/watch?v=R-rMOen4UHg

If you are still having errors, please check out the forum to see if your error has already been discussed. Otherwise, post the details here so we can assist.

Thanks.

[imported_tickstoryParticipant February 13, 2014 at 10:43 pm Post count: 1479]

in reply to: v1.3 bar data problem? #19742

Interesting, Juhaszb. Thanks for letting us know. It was the case that Dukascopy updated their data format over a year ago – perhaps there were some other changes in the process.

Regards.

[imported_tickstoryParticipant February 13, 2014 at 10:59 am Post count: 1479]

in reply to: Modelling quality – n/a #19745

Great to hear – thanks letting us know!

[imported_tickstoryParticipant February 13, 2014 at 12:06 am Post count: 1479]

in reply to: v1.3 bar data problem? #19740

Hi Juhaszb,

Could you please do us a favour and:

1) Go to the store directories for both JForex and Dukascopy and find the file in [StoreLocation]EURUSD201301013h_ticks*.*
Are the file names & file sizes the same? When was the file downloaded?

2) Set the Dukascopy folder to be your ‘Store location’ in Tickstory (go to File->Settings and specify the JForex store folder). Start up Tickstory and ‘View data’ for the day you mention. Does the pricing now match the JForex export?

If you find that in Step 2 that the data is now the same as the JForex export, it is possible that Dukascopy have revised their historical data since the time it was originally downloaded.

Hope this helps.

[imported_tickstoryParticipant February 12, 2014 at 10:38 pm Post count: 1479]

in reply to: v1.3 Release Candidate to support MT4 Build 545, 574+ #19672

Hi 4EverMaAT,

I’m not sure why you would not want to use TDS if it’s there, but what you can do is rename ‘tds.exe’ to something like ‘tds1.exe’ so Tickstory will not launch it.
If there were developers interesting in maintaining the launcher we would work to expose and enhance this feature, however after posing the question around a year back there hasn’t been too much interest. We’ll focus on more ‘value-add’ features for the moment.

Regards.

[imported_tickstoryParticipant February 12, 2014 at 12:14 pm Post count: 1479]

in reply to: v1.3 bar data problem? #19738

Hi Juhaszb,

I wouldn’t have thought the JForex platform changed the data in any way before it exported it. Are you pointing your Tickstory configuration to the same location where JForex stores its data? Did you cross-check that the raw data in Tickstory corresponds to the open/close prices I mentioned?

Thanks.

[imported_tickstoryParticipant February 12, 2014 at 4:43 am Post count: 1479]

in reply to: v1.3 bar data problem? #19736

Hi Juhaszb,

Thanks for your problem report. We have investigated the issue and it does appear that there is an issue when generating the open price of a candle in specific circumstances. The issue only affects the MT4 Export and we plan that this will be addressed as part of v1.3.

Regarding the actual prices between Dukascopy export vs the Tickstory one, we are not so sure. We have downloaded the latest copy of the data for the dates you mention at the first and last prices for the minute 13:51 are 1.31758 and 1.31757, respectively. You can browse the raw tick data by using the “Show data” option in Tickstory. Have you exported the Dukascopy data from JForex or from their website?

Thanks.

[imported_tickstoryParticipant February 12, 2014 at 12:40 am Post count: 1479]

in reply to: MAYDAY – Does not work with Build 600 #19707

Hi Jockey,

All communcations regarding v1.3RC are being discussed here:

viewtopic.php?f=2&t=376&start=20

We believe the latest RC2 should address your issue.

Thanks.

[imported_tickstoryParticipant February 12, 2014 at 12:37 am Post count: 1479]

in reply to: Modelling quality – n/a #19743

Hi experienced_tester,

MT4 are currently releasing a flurry of updates that we are trying to keep up with. FYI, All communications regarding the 1.3RC are being discussed in a single post in order to address any issues prior to the official release:

viewtopic.php?f=2&t=376&start=20

RC2 has just been released which will hopefully resolve your issue.

Thanks.

[imported_tickstoryParticipant February 12, 2014 at 12:29 am Post count: 1479]

in reply to: Some suggestion to put you put you head and shoulders above. #19645

Hi TickTester,

I believe Birt’s Tick Data Suite (TDS) by-passes the 4GB limitation. You read more here: http://17293gp5li0a4xdimxo5gkiy0k.hop.clickbank.net/.

Hope this helps.

[imported_tickstoryParticipant February 12, 2014 at 12:20 am Post count: 1479]

in reply to: v1.3 Release Candidate to support MT4 Build 545, 574+ #19669

Hi Alextc,

That doesn’t sound right – if you exported from Tickstory and launched via Tickstory (by pressing F8), you should be getting a 99.9% modelling quality. Please check you are exporting to the correct MT4 Data folder. In MT4 go to the File->Open Data Folder option and ensure this directory is the one you are exporting to. Also make sure that your FXT files (in tester/history) are marked read-only.

Hope this helps.

[imported_tickstoryParticipant February 12, 2014 at 12:08 am Post count: 1479]

in reply to: TestGenerator: deficient data #19719

Hi Trader2345,

We have tried the following zipped directory structure and it seems to work fine for us even after a restart:

http://www.tickstory.com/files/MetaTrader 509 Full.zip

If that still updates automatically, check our some discussions on the some of the other MT4 forums – the suggestion is to rename/protect the C:ProgramDataMetaQuotesWebInstall directory .

Also note that the latest RC2 to support Build 600+ is now available.

Thanks.

[imported_tickstoryParticipant February 11, 2014 at 10:13 pm Post count: 1479]

in reply to: Bactest multiple timeframe #19539

Hi Experienced_tester,

Put the code into the main start() block of your EA.

Thanks.

[Author]

Posts