• If this is your first visit, you will have to register before you can post. To view messages, please scroll below and select the forum that you would like to visits. Questions? Be sure to check out the Forum FAQ.

Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

NT7 & Timestamp

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

    #16
    murfinp and DaManJ,

    I've only just started looking at sub-second data for a specific project. Out of curiosity, do you find millisecond time stamps more common or index time stamps? By index I mean within 1 second, trade data enters and is given an incrementing index number until that second ends.

    I can elaborate if needed but if you are talking ms timestamps you probably now what I'm on about.

    Thanks.

    Comment


      #17
      Originally posted by MXASJ View Post
      murfinp and DaManJ,

      I've only just started looking at sub-second data for a specific project. Out of curiosity, do you find millisecond time stamps more common or index time stamps? By index I mean within 1 second, trade data enters and is given an incrementing index number until that second ends.

      I can elaborate if needed but if you are talking ms timestamps you probably now what I'm on about.

      Thanks.
      Well NT is obviously using an index for their ticks within the 'second' period - otherwise NT wouldn't know what order they were in.
      btw, Rithmic is actually microsecond timestamp, not millisecond.
      Thats the second followed by 6 zeros
      [IMG]file:///C:/DOCUME%7E1/J/LOCALS%7E1/Temp/moz-screenshot-1.png[/IMG]
      Last edited by DaManJ; 09-27-2009, 09:44 AM.

      Comment


        #18
        To clarify: Of course ticks (and L2 data) are processed by NT in the sequence they come in. There is no need for an index whatsoever. Seconds/milli second or micro second resolution has nothing to do with maintaining the proper tick sequence (which NT does).
        DierkNinjaTrader Customer Service

        Comment


          #19
          Originally posted by NinjaTrader_Dierk View Post
          To clarify: Of course ticks (and L2 data) are processed by NT in the sequence they come in. There is no need for an index whatsoever. Seconds/milli second or micro second resolution has nothing to do with maintaining the proper tick sequence (which NT does).
          So why not just implement the change then

          Comment


            #20
            Please see my posts below. Thanks
            DierkNinjaTrader Customer Service

            Comment


              #21
              Originally posted by NinjaTrader_Dierk View Post
              There is no need for an index whatsoever.
              Then of course we can conclude that you save data in binary format (although that was obvious anyway).
              If the ticks were stored in a database table (not in binary) but with a row for each tick, then yes you would need an index because tables do not have a sense of order implicitly, like a binary file does.

              So I can presume the whole trouble for you, as I suggested below is the fact that you are storing in this binary format.

              I suppose then I can further presume that you are doing something like:
              12:01:01 tick tick tick tick tick 12:01:02 tick tick tick tick tick tick 12:01:03 etc.

              you could potentially change to:
              12:01:01.004453 tick 12:01:01.535235 tick etc. but then I suppose the size of your files and access db (where you store the binary as OLEObject) would increase significantly.
              I suppose also in NT7 you have not chosen to go with the better alternative of saving ticks into their own table, but instead are keeping this binary format.

              How hard would it be to change though? I mean, it would only be a few lower level objects to rewrite.
              It seem to me your current approach was probably trickier to implement than a db solution would have been

              Comment


                #22
                Here are the facts again:
                - tick sequence is maintained
                - timestamp granularity is down to 1 second
                - as of now we don't have any plans to change the granularity of the timestamps to milli or micro seconds

                Unfortunately there is no further information available on that subject. Thanks for your understanding.
                DierkNinjaTrader Customer Service

                Comment

                Latest Posts

                Collapse

                Topics Statistics Last Post
                Started by rontronimous, Today, 06:12 PM
                1 response
                3 views
                0 likes
                Last Post NinjaTrader_ShawnB  
                Started by Vinhasa, Today, 03:15 PM
                3 responses
                13 views
                0 likes
                Last Post NinjaTrader_Manfred  
                Started by 1001111, Today, 03:03 PM
                1 response
                9 views
                0 likes
                Last Post NinjaTrader_Tyler  
                Started by Seedbird, Today, 03:06 PM
                1 response
                13 views
                0 likes
                Last Post NinjaTrader_BrendanC  
                Started by mtamaku, Today, 02:46 PM
                1 response
                7 views
                0 likes
                Last Post NinjaTrader_Kate  
                Working...
                X