Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • d4amenace
    Participant
    Post count: 4
    in reply to: v0.9 Released! #18885

    Tickstory still needs a lot of work. This update includes an error when downloading XAUUSD. Dukascopy data is 3 or 4 digits behind decimal. This version of tickstory doesn’t download it for your broker with the proper number of decimal places. And even if you try to set the decimal places with mt4 data editor, this creates zero divide errors.

    This update was premature. Can’t wait for the update to the update!

    d4amenace
    Participant
    Post count: 4

    [attachment=0:1gmo2f2q]ts1.png[/attachment:1gmo2f2q]

    1)The first box is the Tick Story EA provided broker data that I initially used for downloading tick data. The second box is the data editor opening of 15m on XAUUSD after download. I then open the TS Data Editor and change these incorrect values, in the second box, for what they should be in the first box. This causes the zero divide error.

    2) I have tried to run backtest opening using just birt’s TDS and Tick Story MT4 launcher with the same results.

    3) The symbol I am using is XAUUSD. I have 5 years of data (7/1/2008 to 7/1/2013) This must be where the problem is since dukascopy using a lot of decimal places in their prices for metals. I have not had this problem with currencies under the assumption that it is because typically most brokers use the same amount of decimal places for currency pairs. (The 5 digit brokers).

    4) I have not tried using MT4 432 because metaquotes has gotten very smart and forces you to upgrade any version you open to 509 regardless, since at some point you have to log on to an account to get broker feed. It immediately senses an old version and updates.

    *Note: The downloaded Dukascopy data has 3 or 4 decimal places worth of pricing in their ticks which is the reason why XAUUSD must be changed for my broker. (Downloaded Dukascopy sample price 1025.2632…. what is necessary for my broker 1025.26)

    Also very interesting is the fact that I can backtest with the downloaded incorrect decimal places feed of XAUUSD but of course the test is wrong since too many decimal places are used.

    d4amenace
    Participant
    Post count: 4

    The error happens only after I edit the data.

    d4amenace
    Participant
    Post count: 4

    I have tried the manual fix using the mt4 data editor….when I do this and use with birts backtester I get zero divide errors….my broker (profiforex) also uses a suffix (v).

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