Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-23748

Change private_sndStamp to TAI in MTM2 topics

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Invalid
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: ts_main_telescope
    • Labels:

      Description

      During my analysis to characterize the latency of the Summit EFD, I noticed that MTM2 topics have the private_sndStamp in UTC instead of TAI.

      At this moment we are running SAL version 4.0 at the Summit.

      This also relates to DM-23496, we want to use the private_sndStamp as the InfluxDB timestamp, so it would be nice to have all values in TAI.

      This issue was original entered by Angelo Fausti in TSS-3463

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CAP-83 CSCs Sending Timestamps in TAI

          • Major - Major loss of function.
          • To Do

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-24000 Enable private_sndStamp as the InfluxDB timestamp for the Summit EFD

          • Done

            Activity

            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment -

            Not an issue in M2 anymore because the M2 Python CSC based on ts_salobj is applied already.

            Show
            ttsai Te-Wei Tsai added a comment - Not an issue in M2 anymore because the M2 Python CSC based on ts_salobj is applied already.

              People

              Assignee:
              ttsai Te-Wei Tsai
              Reporter:
              aclements Andy Clements
              Reviewers:
              Angelo Fausti
              Watchers:
              Andy Clements, Angelo Fausti, Simon Krughoff, Te-Wei Tsai
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.