Forum Replies Created

Viewing 15 posts - 676 through 690 (of 1,458 total)
  • Author
    Posts
  • imported_tickstory
    Participant
    Post count: 1479

    Hi Matdust,

    Firstly check that you have configured Tickstory correctly by going to File->Settings. In the ‘MT4 Settings’ section, select the “MT4 Installation Folder”. Then select the correct “MT4 Data folder” which should match the folder you see when you select File->Open Data Folder in MT4.

    If you continue to get the launcher error, please advise which MT4 Build you are using (listed in File->About).

    Thanks.

    imported_tickstory
    Participant
    Post count: 1479

    Hi Matdust,

    Translating the error message to English seems to indicate that you are getting an “access denied” error (something like “Error occurred during download: Access to the path is denied“).
    Windows 7 and above introduce a protection measure to prevent applications from writing data to the “Program Files” folder. As such, you will need to specify an alternate location for your tick data to be stored. To do this, go to File->Settings and select a folder for your “Dukascopy Store location” that isn’t in ‘”Program Files” (eg. C:Users[UserName]DocumentsTick data). You will obviously need to create the directory if it doesnt currently exist.

    Hope this helps.

    imported_tickstory
    Participant
    Post count: 1479
    in reply to: TickInfoExpert #18534

    Hi Mmsk,

    It doesn’t appear that the EA has run correctly. If you are attaching it to a live chart, you will need to wait for a single tick to occur before it runs. Otherwise just use the Tester function to run the EA. You should see lots of logging information appear and if you don’t, it means the EA has not executed.

    Regards.

    imported_tickstory
    Participant
    Post count: 1479

    Hi Snejkane,

    Thank you for the additional information – it helped us to quickly reproduce the issue you’re having.

    We have cross-checked the information from the export with that of Dukascopy’s official export (from http://www.dukascopy.com/swiss/english/marketwatch/historical) and it also has the same negative ‘Ask volumes’. Given that the issue appears to be with the Dukascopy data, we will have to assume that there is some anomaly that perhaps they will correct in the future. Until then, the best way forward may be to filter the negative volumes in Excel.

    Hope this helps.

    imported_tickstory
    Participant
    Post count: 1479
    in reply to: 2012-2013 Data #19938

    Apologies, the terminology “filter weekend” was used to explain the behaviour of the function (we have corrected the original post to avoid any other users getting confused). The option is called ‘Include weekend’ and if it is checked it will include all the data. If it is unchecked (default), it will apply the filter.

    Hope this clarifies.

    imported_tickstory
    Participant
    Post count: 1479

    Hi – we have done the following and see no negative numbers:

    1) Right-click EURJPY->Export to File with settings:
    Date: 8 Feb 2008
    Timezone: UTC
    Timeframe=Tick
    Format=Pre-defined Generic tick format

    2) Loaded the data into Excel and checked for negative bid/ask volumes. None can be found for that day.

    Please note there are many options to export and view volume information and it would help us answer your question more promptly if you provided more details including:

    a) What specific options are you selecting in Tickstory (eg. Export to MT4? Export to File? View data?)
    b) What specific parameters are you using to export/view data – date range, time-frame, etc?
    c) Which application you are using to see this negative volume data – MT4? Excel? A screenshot would be very helpful.
    d) At least two specific times where this negative volume occurs (for eg. if you are referring to specific tick, the specific timestamp could be “20080208 18:56:06:949”).

    Thanks.

    imported_tickstory
    Participant
    Post count: 1479
    in reply to: 2012-2013 Data #19936

    Hi – unchecking the ‘include weekend’ option will yield a slightly different result as it will filter data outside “normal” weekday trading hours. With the filter enabled you will not get bars being constructed during that period, otherwise you would get bars late Friday and early Sunday (try this in a 1-minute timeframe to see the difference). Traders don’t typically include weekend data since the market is illiquid at this time and using the information will affect things like moving averages.

    Hope this helps.

    imported_tickstory
    Participant
    Post count: 1479

    Hi Snejkane,

    Please provide the symbol and dates that you are seeing these negative volumes for and any other information relevant to reproducing the issue.

    Thanks.

    imported_tickstory
    Participant
    Post count: 1479

    No – Just bear in mind that the Tickstory is not specifically targeted to Metatrader or Metatrader Back-testing. We are interested in allowing all traders to store quality data and back-test their systems efficiently and as accurately as possible – regardless of what trading application they use. Our development still continues to focus on improving the way Tickstory can acquire market data from various sources, store and analyse this data and also deliver it to various trading systems. Having a good, manageable set of market data is the pinnacle of a profitable trading system yet few have access to it (unless they’re willing to invest many (hundreds of) thousands of dollars).

    Metatrader 4 obviously have their own specific list of development priorities and tick-level back-testing has been requested by many of their customers. If this ever comes to fruition then we will continue to support it as one of the many third-party trading applications that can utilise the Tickstory database.

    imported_tickstory
    Participant
    Post count: 1479

    That’s a good question and is best answered by MT4 developers. You could ask the question on MT4 forums, however given that this method of tick-quality back-testing is not officially supported, I’m not sure whether you’ll get an official answer. There may be other users who have worked around the issue so perhaps it’s worth asking the question.

    imported_tickstory
    Participant
    Post count: 1479

    Hi Vinisius,

    If you are using Birt’s CSV2FXT, you should be using the accompanying file format.

    Hope this answers the question.

    imported_tickstory
    Participant
    Post count: 1479

    Sounds like the only way forward is to reduce your export range a bit more and see how things go!

    imported_tickstory
    Participant
    Post count: 1479

    No it doesn’t. It only writes HST and FXT files specific to the symbol being exported. If you believe that something is changing in-between exports, why not try exporting both symbols before commencing the back-tests?

    imported_tickstory
    Participant
    Post count: 1479

    Understand your predicament, however unfortunately we can only work within the limitations of MT4. We’re already stretching them by allowing back-testing with tick data, so there will be other compromises. I would recommend at least finding the maximum date boundaries and make sure this issue is resolved first (you will need to give some slack as tick data volume will obviously vary from day to day, month to month). It’s seems odd that a restart doesn’t fix things and implies that something else could have changed in-between your back-tests.

    imported_tickstory
    Participant
    Post count: 1479

    Does it work again if you restart MT4? If so, it sounds like something odd is happening within MT4. I’m guessing that your FXT files are under 4gb? You might need to try reducing the file size further to get some consistency.

Viewing 15 posts - 676 through 690 (of 1,458 total)