[imported_tickstoryParticipant February 3, 2015 at 12:09 am Post count: 1479]

in reply to: Help setting up ASX Index #20489

Hi Danny,

All I can suggest at this point is to try export a small sample of data to analyse what the differences are. In the next major upgrade of Tickstory we will be offering a viewer that can browse the MT4 FXT files which may make it easier to see if there are any differences in the two data sets you are exporting. Until then, it may be necessary to just manually export them (to Excel for example) and see if its the actual bar formations that are causing your differences or some specific setting (such as “Filter weekends”). This is of course assuming that your Metatrader Info/FXT Headers are now the same.

Do note that as long as you see no errors appear in the Tickstory “Log” window during your export/download process you can expect the data is complete and matches what Dukascopy have on their servers.

Regards.

[imported_tickstoryParticipant February 2, 2015 at 11:53 pm Post count: 1479]

in reply to: Metatrader data disappearing #20528

Hi Jollydragon,

Glad to hear you resolved the issue!

P.S. Your post title has been changed to more accurately describe the issue as it may assist others.

[imported_tickstoryParticipant January 31, 2015 at 11:55 am Post count: 1479]

in reply to: Application Error on View #20521

Thanks for your update, DerkWehler. MT4 has a few limitations on how large their data files can be, although this usually affects back-testing and not display of charts. If you have managed to use the “Download” option for the date range you need (with no errors reported), then it should indicate all is well in terms of having the tick data on disk. After that, it is just a matter of finding out why MT4 hasn’t got the data you exported. Make sure you try viewing Metatrader’s “History Center” to see if the data exists for the date range you exported. If not, it is possible that you can exported to the incorrect directory and/or server.

Hope this helps.

[imported_tickstoryParticipant January 31, 2015 at 11:40 am Post count: 1479]

in reply to: Metatrader data disappearing #20527

Hi Jollydragon,

The manual outlines how you need to not be logged into your MT4 terminal as the broker will potentially override the historical data you have exported with Tickstory. This is different to ensuring your MT4 terminal is closed during the export process. Please ensure you do not log in to MT4 and see if this resolves your problem.

Thanks.

[imported_tickstoryParticipant January 30, 2015 at 9:35 am Post count: 1479]

in reply to: Metatrader data disappearing #20524

Hi Jollydragon – are you connected to your broker? If so, it is possible that your data is being refreshed from your broker’s server again. Make sure you are disconnected and try the export again.

Thanks.

[imported_tickstoryParticipant January 30, 2015 at 9:32 am Post count: 1479]

in reply to: Application Error on View #20519

Hi DerkWehler,

Thanks for the problem report – we are aware there are a few problems with the beta data viewer & charts and they will be addressed in the next major version. These errors should not affect the export process – only the viewing of data.

As for your data issue, you should have data going back to 2003 for AUDJPY. What does your ‘earliest’ date read when looking at the main Tickstory screen? If you don’t have the date you downloaded from, please explicitly try the ‘Download’ option and ensure you get no errors during the process.

Hope this helps.

[imported_tickstoryParticipant January 29, 2015 at 9:44 am Post count: 1479]

in reply to: Help setting up ASX Index #20487

Hi Danny,

The only thing I can suggest is to take the first trade as an example and see why the EA takes it in one case but not the other. Is it due to an indicator? In the most base case it would be worthwhile checking the two sets of data have the same candles and/or indicators at that given period. If there is something notable we might be able to assist further.

Regards.

[imported_tickstoryParticipant January 29, 2015 at 2:19 am Post count: 1479]

in reply to: Accuracy of TickData Testing #20514

Hi Fiverr,

If the two extracts were produced from CSV files, there could potentially be the following differences:

1) The CSV tick data from SQL Downloader vs Tickstory is different (this should not be the case as you mention since both are sourced from Dukascopy).
2) The import process into CSV2FXT has been incorrect. Check that each file was loaded correctly into CSV2FXT and that the fields were correctly detected.
3) If there were any changes to the CSV2FXT parameters then this will cause back-test differences. Step 4) mentioned above will help identify if there are any such differences in the “Metatrader Info” information.

Hope this helps.

[imported_tickstoryParticipant January 29, 2015 at 1:09 am Post count: 1479]

in reply to: Help setting up ASX Index #20485

Hi Danny,

Thanks for the information – it looks like you have got the correct base-line for the Metatrader Info/FXT header information which is a good start. From here you need to identify any differences in your back-testing setup. For one, I can see that you have different export dates. You will note that in each back-test you have a different date for your first trade. Depending on how your EA is designed, it could mean dramatically different results. For example, if you happen to be in the midst of a trade in one back-test vs the other, it may mean you miss out on a number of profitable trades that the other is taking. Or if you happen to be relying on a certain time/date/indicator/money management, this condition could be different in each case (also indicating that your EA could be vulnerable to different start times). To eliminate some of these variables, make sure you export the same date range for both back-tests. Of course, if you see any discrepancies with the data that Tickstory is producing, we will investigate further.

Hope this helps.

[imported_tickstoryParticipant January 28, 2015 at 9:34 pm Post count: 1479]

in reply to: Accuracy of TickData Testing #20511

Hi Fiverr,

Looking at the results it appears you are using CSV2FXT to generate your back-test databases. We don’t support this script since Tickstory already has a feature to output HST/FXT data, but I suggest doing the following to trouble-shoot:

1) Copy the HST/FXT files across the two machines. Do you still get different results? If so, something odd is happening. Otherwise;
2) Copy the CSV data to the other machine and re-generate your HST/FXT files with CSV2FXT. If there are differences in the back-test, then make sure your CSV2FXT parameters machine between machines. Create a .set file on the originating machine and load it on the other.
3) If there are still differences, check your CSV2FXT versions are the same.
4) Open the FXT file in Tickstory->MT4 FXT Editor and compare the two sets of information to make sure they match on both machines.

I would recommend that you use Tickstory’s ‘Export To MT4’ function if there is not a good reason to do so. You can save your settings in an .mt4config file which can be shared between machines (similar to the .set file) and should ensure all the important broker information is the same across the two machines.

Hope this helps.

[imported_tickstoryParticipant January 28, 2015 at 11:55 am Post count: 1479]

in reply to: widows 8 tickstory #20502

Hi Alasdeaguila,

Errors like this usually mean that something has corrupted. I would recommend re-downloading the installation and trying it on another machine if it still gives you problems.

Hope this helps.

[imported_tickstoryParticipant January 27, 2015 at 11:57 pm Post count: 1479]

in reply to: Status Field should show date as yyyy/mm/dd #20447

Thanks for your feedback, Sryoung. We’re considering something a bit more visual such as a progress bar which will hopefully help.

[imported_tickstoryParticipant January 27, 2015 at 11:55 pm Post count: 1479]

in reply to: Help setting up ASX Index #20483

Hi Danny,

Comparing the FXT headers of your CSV2FXT vs Tickstory export, there are the following differences:

Spread=2 (in Tickstory you have exported a spread of 3).
Digits=0 (in Tickstory you have it set to 1)
Margin Init=0 (in Tickstory you have a value of 10000)
GTC Pending=Yes (In Tickstory you have it unchecked)

Could you please try re-export to match the changes described above? You will need to manually change the respective Metatrader Info fields and then “Save as default”.
Then try your back-test again and see if starts to match up with what you expect.

Regards.

[imported_tickstoryParticipant January 27, 2015 at 9:38 pm Post count: 1479]

in reply to: Tick history and Ctrade #20505

Hi Nonciazzecco,

Are you attempting to export tick data or M1 data from Tickstory? Depending on this, you will need to select the “Tick” or “1-Minute” time-frame, respectively.

Hope this helps.

[imported_tickstoryParticipant January 27, 2015 at 11:52 am Post count: 1479]

in reply to: Tick history and Ctrade #20503

Hi ,

The posts don’t seem to have specified the format for the tick data. If it is expecting the format outlined below:

Date
Time
Open Price
High Price
Low Price
Close Price
Volume (Integer only)
Example:

2003.06.18,16:01,1.11423,1.11428,1.11332,1.11374,19
2003.06.18,16:02,1.11364,1.11436,1.11361,1.11405,7
2003.06.18,16:03,1.11402,1.11455,1.11400,1.11440,5
2003.06.18,16:04,1.11446,1.11461,1.11401,1.11447,14

Then try this custom format while ensuring you have specified the “Tick” timeframe in the File Export dialog box:

{BarBeginTime:yyyy.MM.dd},{BarBeginTime:HH:mm},{BidPrice},{BidPrice},{BidPrice},{BidPrice},{Volume:F0}

If the tick data requires the ‘seconds’ component in the time specification, then you can simply add the seconds like so:

{BarBeginTime:yyyy.MM.dd},{BarBeginTime:HH:mm:ss},{BidPrice},{BidPrice},{BidPrice},{BidPrice},{Volume:F0}

Note how the Bid price is being output as the Open, High, Low and Close. The Volume is being forced to be rounded as an integer through specifying “F0”.
More information on this topic is available in the manual.

Hope this helps.

[Author]

Posts