Announcement

Collapse
No announcement yet.

1st bar of 120 min chart is equal to 1st bar of 60 min chart

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 1st bar of 120 min chart is equal to 1st bar of 60 min chart

    For the Euro Bund future contract GB U3-DT the first bar of
    each day for longer term intraday charts, f.e. 120min, 180min
    or 240min is created only from the first 60 minutes of trading
    and therefore is equal to the first bar of the 60 min chart.
    You can check this easily if you compare the closing prices
    in the different timeframes.
    The contract is traded from 8:00 to 19:00 local time, that is 6:00 - 17:00 GMT which converts to 23:00 - 10:00 Pacific Time.
    An appropriate time template that has to be used to display the
    contract. I have attached an example and marked the
    corresponding bars with an 'x'. The marked bars in the 120 TF are wrong. This seems to be a bug or is there any way to display correct longer term intraday charts of this contract?
    Attached Files

  • #2
    60 min chart of previous problem

    60 min chart for comparison
    Attached Files

    Comment


    • #3
      Thanks for the post. I am able to duplicate this, and will pass it along to our QA Team.
      Regards,
      Jay F.
      Product Manager
      _____________________________________
      Have a suggestion to improve our products?
      Click Support --> Request a Feature in eSignal 11

      Comment


      • #4
        Here's what I found out on the issue...

        The short answer is that the Tick Server (the machines that send intraday data) can not send a bar that spans midnight because data is stored in daily files and sent on a per/day basis.

        For example, the tick server reads the bars for 8/11/03 and sends them to the eSignal. Then, it reads the bars from the previous day and sends them. Essentially, this just can't be done with the current design.
        Regards,
        Jay F.
        Product Manager
        _____________________________________
        Have a suggestion to improve our products?
        Click Support --> Request a Feature in eSignal 11

        Comment


        • #5
          Thanks for the explanation. This seems to be a serious technical
          problem. Please consider however that the BUND future is a very
          popular product. It is one of the world's most heavily traded futures contracts and 120 or 180 min charts for a contract that is traded for 11 hours each day are not uncommon. Are there any plans to provide a solution for this issue in the near future?
          Last edited by dneier2003; 08-15-2003, 11:30 AM.

          Comment


          • #6
            Time templates and BarPeriods > 60minutes

            I have a similar problem.
            This has nothing to do with the midnight hour.

            I split a day into 5 (equal) periods.
            (or I try to any way)

            For EUREX which has an 11 hour trading period (09:00-20:00 CET)
            or (08:00-19:00 in UK) this means that I need bars of 132 minutes.

            However, the first bar IS ALWAYS WRONG.

            I have found that if the first bar is larger than 60minutes then eSignal/TimeTemplates just do not work correctly.

            In the above case the first bar starts at 09:12 UK time, rather than 08:00.

            This also occurs for LIFFE (08:00-17:00 UK) and the US.

            If you want a bar period greater than 1hr/60minutes something goes wrong, and data does not start being collected for the chart until some time later.

            any help to remedy would be appreciated, as i miss opening moves on my data.

            -macavity

            Comment


            • #7
              addition....

              I meant for the DAX future on EUREX.
              (08:00 - 19:00 UK Time at the moment)

              oh!
              I see midnight refers to midnight in the pacific (where the servers are?)

              -macavity

              Comment


              • #8
                ...more.....

                for an 11 hr trading day - 660 minutes

                132mins (5 periods) does not work.
                110mins (6 periods) does not work
                BUT
                66mins(10 periods) now works correctly (so it cant be simply the server clock)

                curious and curiouser

                -macavity

                Comment

                Working...
                X