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

Enable private_sndStamp as the InfluxDB timestamp for the Summit EFD

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      After the latency tests at the Summit with M1M3 and M2 data, we switched on using the private_sndStamp as the InfluxDB timestamp.

      We notice, however, that some subsystems still have private_sndStamp in UTC instead of TAI.

      This change was tested with M2 data at the Summit and in particular, the "features" in the data introduced by the internal EFD latency are removed and Chronograf display is consistent with the timestamps produced by SAL.

        Attachments

          Issue Links

            Activity

            Hide
            afausti Angelo Fausti added a comment -

            The instances using private_sndStamp are the Tucson test stand and the Summit EFD for the moment. We plan on applying this change to all instances at some point.

            Show
            afausti Angelo Fausti added a comment - The instances using private_sndStamp are the Tucson test stand and the Summit EFD for the moment. We plan on applying this change to all instances at some point.

              People

              • Assignee:
                afausti Angelo Fausti
                Reporter:
                afausti Angelo Fausti
                Watchers:
                Angelo Fausti
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel