SAGE Facility MUSTANG metrics Web Service Documentation

timing_correction Time correction applied

Summary

This metric counts the times this clock quality flag is set from 0 (default) to 1 in the fixed section of the miniSEED header. This flag is set by the network operator when a timing correction stored in field 16 of the miniSEED fixed header has been applied to the data’s original time stamp. A value of 0 means that the stored timing correction has not yet been applied to the data.

Uses

If this flag is zero and field 16 is non-zero, a user requesting the data may choose to apply the stored timing correction.

Because this flag does not indicate whether or not a timing correction was calculated and stored, we do not anticipate this metric to be useful as an rrds service constraint.

Data Analyzed

Traces – one N.S.L.C (Network.Station.Location.Channel) per measurement
Window – 24 hours starting at 00:00:00 UTC
Data SourceIRIS miniSEED archive

SEED Channel Types – ?H?, ?L?, ?N?, ?G?, ?P?, VM? | High Gain, Low Gain, Accelerometer, Gravimeter, Geophone, Mass Channels

Algorithm

  • Request 24 hours of data for a single N.S.L.C.
  • Count and report the number times this binary flag is set to 1.

Metric Values Returned

value – number of times this flag is set to 1 that day
target – the trace analyzed, labeled as N.S.L.C.Q (Network.Station.Location.Channel.Quality)
start – beginning of the data day requested (00:00:00 UTC)
end – end of the data day requested (truncated as 23:59:59 UTC)
lddate – date/time the measurement was made and loaded into the MUSTANG database (UTC)

Contact

Updated