Forum Replies Created

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • rpg
    Participant
    Post count: 13

    I think you need M15 HST file to be present.

    rpg
    Participant
    Post count: 13

    If MT4 does not ask you before updating itself, the probably you have disabled User Account Control Settings (UAC) on your Windows. So whenever another MT4 installation downloads new updates, all your MT4 installations will be updated automatically when you launch them. To prevent this, you have to enable UAC. Open up start menu and search for UAC, go to “Change User Account Control Settings” and set the slider on “Default”; so when you launch MT4, you’ll be notified if it wants to update itself and prevent it.

    rpg
    Participant
    Post count: 13

    Do not connect to MetaQuotes server; or even if it downloads the new version and prompts to restart MT4, click cancel.

    rpg
    Participant
    Post count: 13
    in reply to: v1.5 Released! #20066

    Hello Tick
    Will there be a new version coming?

    Thanks

    rpg
    Participant
    Post count: 13
    in reply to: Different results #20544

    What issue? which one?

    rpg
    Participant
    Post count: 13

    As far as I know, there’s no MT4 version for MAC. is there? And if you are using 3rd party softwares to run MT4 on your MAC, then I guess it’s possible to do the same for Tickstory.

    rpg
    Participant
    Post count: 13
    in reply to: Tick-Volume #19104

    Mar 27, 2014
    @tickstory wrote:

    Hi Berty,
    The tick volume that is published is still as described above – that is, it uses the volume traded as oppose to the number of ticks. All data originates from Dukascopy.
    We still have an open enhancement item to change the MT4 export so it exports the tick activity rather than volume.
    Hope this helps.

    Almost 11 months have passed since this post. Will we see tick-count in Tickstory any soon?

    rpg
    Participant
    Post count: 13
    in reply to: Different results #20542

    Thanks for your great support. I got all my answers 🙂

    rpg
    Participant
    Post count: 13
    in reply to: Different results #20540

    Dear ticktory
    Dukascopy’s data timestamp is in GMT, and the broker which I export the data into, uses GMT +2. So if last bar of Dukascopy is 21:00 the exported bar should be 23:00. And those bars 22:00 and 23:00 in dukascopy data which are empty, are shifted into Saturday 00:00 and 01:00, when the market is closed, so they are empty.
    Here I compare three different charts for 2014 November 28th. First chart shows the exported data using tickstory; second one shows CSV2TXT generated export and last one shows the broker’s own data.

    1. Tickstory
    [attachment=2:17ebw33g]tickstory.png[/attachment:17ebw33g]

    2. CSV2FXT (I used a CSV file generated by tickstory and then exported it into Metatrader using CSV2TXT)
    [attachment=1:17ebw33g]CSV2FXT.png[/attachment:17ebw33g]

    3. FxPro’s own data
    [attachment=0:17ebw33g]FxPro.png[/attachment:17ebw33g]

    As you can see, in all 3 charts all other bars are the same, except for last two bars of Friday, which tickstory misses to export.

    rpg
    Participant
    Post count: 13
    in reply to: Different results #20537

    Okay, finally I figured out how to get rid of Sunday bars. EST +7 is the key (using UTC +2 with London DST results Sunday data in March and October); but couldn’t find an answer for my last two questions:
    1. Tick volumes: why they don’t match the number of ticks in source data?
    2. Why last two hours of Fridays are missed?

    I gave CSV2FXT a try; apparently it generates exact tick volume and also full Friday bars.

    rpg
    Participant
    Post count: 13
    in reply to: Different results #20536

    Hi tickstory and thanks for your useful replies. I’ve sorted out mismatched charts errors and modeling quality issues; but still struggling with time shift and daylight saving time problems. I checked the “timezone info” for “UTC+2 with european/london DST”:

    [attachment=0:1usw01ms]timeinfo.png[/attachment:1usw01ms]
    I’m not sure what 1/Mar and 1/Oct mean (maybe 1st Sunday of the month?), but I still think those shifts that happen on my charts are based on U.S. DST shift, not London. I really need help to get rid of those Sunday bars 🙁

    I have also a couple of more questions:
    1. Number of ticks in Dukascopy data do not match to exported data. Please see attached below:

    [attachment=2:1usw01ms]ticks.png[/attachment:1usw01ms]

    2. I searched on the forum for this one, but didn’t get a clear answer. And the problem is why last 2 hours of Fridays are missed? Here I quote your own words:
    @tickstory wrote:

    The ‘filter weekend’ option will filter all tick data that occurs after Friday 22:00 hrs (UTC) and before Sunday 21:00hrs (UTC). It will then perform the time-shift to the selected time-zone and create bar data from this. This means that if the converted times fall between Monday 00:00-23:59hrs, then yes, everything will be seen on that bar.

    [attachment=1:1usw01ms]friday_close.png[/attachment:1usw01ms]
    Seems that “filter weekend” filters data after Friday 20:00? If not what could have caused the missing?

    rpg
    Participant
    Post count: 13
    in reply to: Different results #20534

    @tickstory wrote:

    Please make sure that you are launching MT4 via Tickstory’s “Launch MT4” button prior to backtesting. Failure to do so will result in the problems you’re describing. If your results do not show 99.9% modelling quality then you have missed a step somewhere.

    Launching MT4 via tickstry works fine with 99.9% modeling quality. But what I wanted to do was just exporting HST files into MT4 and let metatrader build its own FXT files. I mean just using exported data like any other sources (similar to MT4’s own history center data). Do I still need to launch MT4 thru tockstory even if I don’t want real tick modeling?

    As for the Sunday data, Tickstory will filter all the data from weekends in the data’s original timezone and then subsequently perform the time-shift. I imagine that this time-shift could be causing the data to move into the weekend.

    I checked it closely and I found there are four Sunday data appearances on my chart during 2014. Three in March and one in October.
    And I think I’ve found why this happens. You probably have defined wrong DST switching dates for London (which are 30 March and 26 October in 2014), seems that you have used those dates of the United States (9 March, 2 November). That’s why Sunday bars appear 3 weeks in March and once in the last week of October.

Viewing 12 posts - 1 through 12 (of 12 total)