Forum Replies Created
-
AuthorPosts
-
in reply to: v1.0 Released! #19266
Hi JohnTiror – Thanks for your feedback. Please let us know how you go. We will be making an official v1.1 release of this change shortly.
Radu – thanks again for your updated translations. We are in the process of entirely replacing this chart so the options you mention will no longer exist in the same form. As such, hopefully you don’t mind if we defer the translations until the new version.
Thanks & regards.
in reply to: How to change MT4 leverage in strategies tester #19325Hi Janko,
Leverage is a setting that is used by EAs to make various determinations about lot-size, etc. It doesn’t at all affect the tick/pricing data.
Regards.
in reply to: MT4/tickstory/TDS #19389Hi Gabriele,
I’m not sure if your issue has something to do with Windows 7 file virtualisation? The first thing to do is identify exactly when your files are deleted so you can hone-in on the culprit.
Check the files just before shutdown/logout, then when you start up again, then when you start MT4 and then when you hit the ‘back-test’ button. Once you know the exact point at which your files are deleted you can most likely find out why this is occurring. As far as we’re aware, if the files are marked as read-only, MT4 cannot delete them.Hope this helps.
in reply to: compatible with Walk Forward Analyzer? #19398Hi Devonfgu,
At the moment Tickstory is not compatible with Walk Forward Analyser. Please see this discussion for more:
Thanks.
in reply to: Real and historical graphs are different.. spread? #19306Hi Gooly,
Re: your comments:
1) The spread is embedded by Tickstory during the export. It is whatever you specify in the “Metatrader Info” tab. The setting in MT4 is ignored.
2) Dukascopy data is in GMT and Tickstory performs the date shift from GMT into the time-zone you select in the ‘Export’ screen.
Hope this helps
in reply to: Real and historical graphs are different.. spread? #19304Hi Fdanilo,
We have done some further investigation on this – it appears Pepperstone is actually GMT +3 and when we select a GMT +3 timezone for the export (eg. Nairobi), we match the data you are showing.
Could you please confirm whether this works for you? Obviously it’s not intuitive to be selecting a time-zone like ‘Nairobi’, so we will look into adding some more identifiable time-zones. First step is to confirm this addresses your issue.Thanks.
in reply to: another suggestion #19382Hi Gooly,
We can never eliminate Case 2 unless MT4 decides to support the use of tick data. Until then, you need to launch the application via Tickstory because this step prevents MT4 from deleting the tick data files that Tickstory generates.
Hope this helps.
in reply to: MT4/tickstory/TDS #19387Hi Gabriele,
Here is a response to all your questions above:
So my first question is should I have a matching number of HST and FXT files?
A HST file is generated for every time-frame. If you have generated FXTs for every time-frame then yes, you will also have the same number of FXT files.
If so then, is there a known issue on why the HST files are downloaded but not the FXTs?
If you have exported from Tickstory you will automatically generate the FXT files.
Do I need to download the data again or can I extract them from my Ctickstory Lite folders?
You don’t need to touch the Dukascopy data files (*.bi5 files) in any way. These files are automatically downloaded and contain the tick data used by Tickstory to export to MT4. Once they are downloaded they do not get downloaded again.
Also, how can I make sure that once downloaded, the data stays on my pc? I have the feeling, but not the proof, that some of the files get deleted as I close my MT4 and shut down my pc.
– Data downloaded from Dukascopy is never deleted unless you explicitly choose to delete it.
– Data that you export for MT4 from Tickstory will reside in the Metatrader directory. Ensure you have selected ‘Mark files read-only’ when you do your export and always launch MT4 via the Tickstory ‘Launch’ feature (press F8 in the application). This will ensure MT4 cannot delete your FXT files. If you do not follow the ‘Launch’ procedure then yes, it is possible that MT4 will delete the FXT files when you try to back-test (and if these files are deleted then, yes, you will need to generate them again).Hope this answers your questions.
Regards.
in reply to: TickInfoExpert #18528Great to hear it works!
Regards.
in reply to: TickInfoExpert #18526Hi Emmarita,
First thing to check is which symbols you are getting a warning for. There are many symbols that Dukascopy supports which aren’t always available at other brokers – you will get the warning message for these symbols and you should not be concerned.
Obviously all major pairs should show up correctly (assuming your broker supports them all!). You can check to make sure all the major pairs have correct spread values (etc) by loading the config file into Tickstory and then viewing the details. If you do not have correct values (eg. spread=0), there is some sort of mismatch between the symbol that Tickstory is querying and the actual symbol name used by your broker and you will need to make sure this is resolved by adjusting the ‘Suffix’ parameter accordingly.
Hope this helps.
in reply to: another suggestion #19380Hi Gooly,
Not sure why MT4 cannot read the history files. Could you please explain further?
Thanks.
in reply to: MT4/tickstory/TDS #19385Hi Gabriele,
Given that you are just getting familiar with back-testing, we would recommend that you consult the Help guide to find out more about how MT4 databases work (and also Tickstory). You can go to the Help guide by going to this link: http://www.tickstory.com/help/tickstorylite/ or simply pressing F1 when you are using Tickstory. The section on “MT4 – A Quick Primer” will be useful for you to learn more about FXT & HST files. There is also a section in “The Basics”->”Downloading data” which also explains how data is retrieved from Dukascopy and stored on your local computer so it does not need to continually request this information over the Internet.
To address some of your other questions, note that MT4 databases (and therefore HST and FXT files) do not get generated until you perform an ‘Export’ from Tickstory (this is also explained in the Help guide). This may be why you are not seeing FXT files (and the existing HST files may already exist because they were downloaded from your broker).
As a starting point, have a look at our 5-step video guide for using Tickstory to back-test:
http://www.youtube.com/watch?v=R-rMOen4UHg
Hope this helps.
in reply to: Chinese Translate #19376Hi Madk,
Apologies for the delayed reply and thank you for the Chinese translation. We will be integrating this as soon as possible. We’re hoping it makes it into v1.2!
Many thanks for your help!
in reply to: Error inspecting data #19379Thanks for the further information, Sym. At the moment this lissue ooks related to memory limitations. If you are able to reduce your date range, this should eliminate the issue for the time being. We are planning to optimise this screen in the next version so you hopefully shouldn’t come across this issue.
Hope this helps.
in reply to: Tickstory Data On Live Account? #19351Hi Trader2384,
If you are collecting data ‘live’ as it occurs, then this is the most ‘faithful’ representation of what data your broker gives you. Of course, if you are back-filling data, then yes, it is possible that your broker can filter out any “anomalies” – or more importantly, if you are back-filling, you are at-best getting 1-minute data rather than tick-data.
Generally speaking, unless you are constantly keeping your MT4 running and collecting tick-data, you are much better off with the Dukascopy tick data to get an indicative idea of how your EA is performing.
Hope this helps.
-
AuthorPosts
