Forum Replies Created

Viewing 15 posts - 16 through 30 (of 53 total)
  • Author
    Posts
  • Trader2384
    Participant
    Post count: 75
    in reply to: 2012-2013 Data #19937

    thanks for the information. Just to clarify, is the “filter weekend” the same as “include weekend”?

    Trader2384
    Participant
    Post count: 75
    in reply to: 2012-2013 Data #19935

    Hi again, what would be a reason to include weekends if the data is the same either way?

    Trader2384
    Participant
    Post count: 75

    ok, what file references this config file or is it a registry thing? If it’s too complicated I’ll just wait for the update

    Trader2384
    Participant
    Post count: 75

    ok great. Any ideas for a temporary workaround?

    Trader2384
    Participant
    Post count: 75

    Good information, thanks. Before receiving this reply, I download EURUSD tick data starting 29-mar-2006 which appears to be intact but according to Tom’s post the data doesn’t start until 30-mar-2007 16:00. If that is true, then why are bars being drawn for dates before then?

    Also, does that starting date apply to all timeframes? That what it sounds like from Tom’s post.

    Trader2384
    Participant
    Post count: 75
    in reply to: 2012-2013 Data #19933

    same issue described above (Wed Mar 26, 2014 11:16 am reply) with weekends included

    what does checking “include weekends” do? I notice that even when this is checked, bars skip from Fri. to Sun. (i.e. weekends are not included).

    Trader2384
    Participant
    Post count: 75
    in reply to: 2012-2013 Data #19932

    date range: 20-feb-2012 through 19-feb-2013
    problematic bar: 28-jul-2012

    is it better to not filter weekends?
    does filter treat D1 differently than H4? Why would it open on 28-jul for D1 but 29-jul for H4?

    Thank you 🙂

    Trader2384
    Participant
    Post count: 75
    in reply to: 2012-2013 Data #19930

    btw, this is for EURUSD. Eagerly awaiting your response as these inconsistencies in data put the whole data set in question: even if tick data is being used if it is misaligned such that inaccurate test results are being produced, then what advantage does it have over broker’s 1-minute data that is less precise but correctly aligned?

    Trader2384
    Participant
    Post count: 75
    in reply to: 2012-2013 Data #19929

    yes, this doesn’t appear to be an ea issue. Opening bars on different TFs don’t match up (i.e. D1 & H4) for various date ranges including: 20-feb-2012 through 19-feb-2013. For example, within that range try 28-jul-2012: D1 opens at 00:00 while H4 opens at 29-jul at 20:00 and H1 and M15 open on 29-jul at 21:00. Data downloaded through latest build of Tickstory.

    Trader2384
    Participant
    Post count: 75

    it looks like the delay happens only when “use date” is selected. The farther date is from the beginning date of the data file, the longer it takes to load before running.

    Trader2384
    Participant
    Post count: 75

    to clarify: the test does not start immediately upon pressing the tester start button. From the moment I press the start button until the moment the test starts running on the chart in visual mode there is a delay of 15 seconds to a minute. During this time, the chart appears to be loading bars in the history. Meaning, if you press the end button during this loading period you will see new bars being added to the chart. Once it is finished, the tester template appears and the test begins. In jounal, it says “2014.03.18 12:39:37.527 TestGenerator: actual tick file “C:Users…MetaTrader – ExnesstesterhistoryEURUSDm15_0.fxt” found” during the loading period, and once the test begins it displays a message like “2014.03.18 12:40:49.137 time periods test inputs: MagicStart=6071;”. In the past I recall there was not a delay when running tests, but they would begin immediately upon pressing the start button.

    Trader2384
    Participant
    Post count: 75
    in reply to: D1/H4 mismatch #19863

    @tickstory wrote:

    Trader2384 – Could you please confirm the original issue you reported has now been resolved for you?

    Thanks!

    yes, I downloaded new files with the same date range/parameters and issue appears to be fixed.

    Trader2384
    Participant
    Post count: 75
    in reply to: D1/H4 mismatch #19862

    will test it over the next couple days and report back

    Trader2384
    Participant
    Post count: 75
    in reply to: D1/H4 mismatch #19860

    I’m not sure, sorry.

    Trader2384
    Participant
    Post count: 75
    in reply to: D1/H4 mismatch #19858

    I don’t know if you were replying to my last response but I didn’t understand what you meant by “H4 is not producing the same data as before
    and certainly doesn’t look anything like data from other ECN brokers.” Does that mean there is a problem with the dukascopy data – did it change since the beginning of this thread?

Viewing 15 posts - 16 through 30 (of 53 total)