Forum Replies Created
-
AuthorPosts
-
Hi jinxbhoy,
This sounds like an issue with your EA. Have a look at this thread and see if it resolves your problem:
http://www.forexfactory.com/showthread.php?t=395149
Regards.
in reply to: Modeling quality n/a #18486Hi Yarosvet,
“Real spread” is essentially variable spread and this is undoubtedly why you are seeing some differences in your results. Variable spread additions in Tickstory are pending and will let you know when they are available.
Regards.
in reply to: Modeling quality n/a #18484Hi Yarosvet,
Glad to hear you’ve got it working.
1) The Order Send 134 error is because you don’t “have enough money” which means you should increase your initial deposit for back-testing or get a more profitable EA 😉 See here for more: http://www.earnforex.com/blog/2010/11/ordersend-error-134-no-enough-money/
As for your results, I would need to know more before being able to say why the different results. If you are using variable spreads, this is more than likely the issue – Tickstory does not currently support this.
2) You should use Build 432 which is supported by the Tickstory launcher (F8). If you are using TDS then I believe that supports all versions.
Regards.
This issue should now be resolved in v0.6b.
in reply to: Modeling quality n/a #18487Hi Yarosvet,
You should be getting a back-test quality of 99.9% if everything has been followed. Usually the n/a will appear if you have not launched MT4 from Tickstory or your MT4 build is not currently supported, although the launcher should advise you of any such issue. Also make sure that the MT4 is not connected to any broker.
After that, could you please try these steps:
– Select your MT4 folder location in the File->Settings->MT4 setup.
– Export your data to your MT4 directory using any time period and instrument.
– Go to the MT4 tester/history directory and make all your FXT files ”read-only”.
– Launch MT4 by pressing ‘F8’ in Tickstory.
– Select the instrument you exported and “Start” a back-test (of any EA).Does this give you any errors? If it does, then it seems likely that the patch hasn’t been applied correctly. If you don’t get any errors but still get the “n/a” quality, I’d appreciate if you could give the full details to see if it can be reproduced.
Thanks.
The issue has been corrected and will be released in the upcoming version (0.6b). The issue only affects the “begin time” of MT4 bars and would affect any strategies relying on specific bar times.
Regards.
in reply to: Bid/Ask Spread #18462Hi jinxbhoy,
Can you please confirm that you are not connected to your broker while doing the back-test? Otherwise your spreads will be overridden by your broker.
Regarding the “60” pips – if you are using the MT4 functionMarketInfo(Symbol(),MODE_SPREAD);It will return a value of 60 which denotes a 6 pip spread on a 5-digit broker.
Regarding Commission Types, essentially this is the way that the commissions are calculated by the broker. A brief description taken from the FXT file format taken from http://codebase.mql4.com/source/2684:
//—- commission calculation
//—- basic commission type
COMM_TYPE_MONEY 0
COMM_TYPE_PIPS 1
COMM_TYPE_PERCENT 2//—- commission per lot or per deal
COMMISSION_PER_LOT 0
COMMISSION_PER_DEAL 1Generally speaking you should not need to change any of these values that have been acquired from your broker.
Regards.
Not sure what the error may have been, but hopefully you agree that the Tickstory export looks correct compared to the other export.
Regards.
in reply to: Accuracy of Data #18471Hi 50pips,
Can you please provide more details.
– You mentioned in another forum that there are file size discrepancies compared to Birt’s scripts. Can you please outline what “file size” are you comparing?
Folder size of a particular month? Specific date/time/hour file size? What is the size/contents of the folder? Did you know that Dukascopy changed their file format at the start of the year to a much smaller format? Are you sure you’re not comparing files of the old format with the new smaller format? Also note that Tickstory does not download the Dukascopy candle data but instead generates its own candles “on-the-fly”.– What EA are you getting different results for? What options did you use produce the FXT file in the CSV2FXT scripts vs Tickstory? Are you using variable spreads (which Tickstory does not yet support)?
Any additional information that will help identify the issue you’re having would be much appreciated.
Thanks.
Hi Carioca,
Did you have any filters on your export such as remiving duplicate ticks?
Thanks.
in reply to: Quick export to file, without missing data check #18439Hi jfroth,
The main feedback around this seems to be to speed up response times in the export process. There will be some improvement on this front in the next version.
As far as skipping data goes, I think this feature would cause some confusion to a majority of users. It would be better to focus on enhancing the export process instead.
Regards.
Hi jfroth – thanks. This is on the list of enhancements.
Regards.
in reply to: Specify folder for exported files #18441Hi jfroth,
The store location in the Dukascopy is specifically the location of where Dukascopy data files will be stored/cached. When you export a file, you should be able to specify the full path name of where you wish to store your exported files. For eg:
C:exportedfiles{Symbol}.csv
Will output all files to that directory.
Regards.
Hi Jfroth,
I have PM’d you. Can you please try again. Some topics go for approval before appearing on the site.
This thread will be removed shortly.
Regards.
Hi Carioca,
Comparing with the historical prices on this site:
http://aud.fx-exchange.com/usd/exchange-rates-history.html
It seems to me that the Tickstory version is alot closer to the file you are comparing with on the right.
I would be checking your source and method for obtaining your other set of CSV data.Regards
-
AuthorPosts