DCC-DMC Synchronization File Format


About Synchronization Files

Synchronization files are ASCII descriptions of network/station/location/channel data holdings. The Synchronization file format was created to facilitate the verification and comparison of data holdings at DCC's and the DMC. For more information or if you have questions or comments about sync files e-mail us.


General Guidelines


The Header Line

The two fields in the header line are ordered and defined as follows:

DCC NameDate Modified

Where:

DCC NameE.g. DMC, ASL, IDA, or PIC (Passcal Instrument Center)
Date ModifiedThe latest date time span lines were modified, in SEED time format to the nearest day (YYYY,JJJ) with no spaces and zero padded to the left. This date should correspond to the latest date in the Date Line Modified Fields in the time span lines.

Example Header Line:

ASL|1998,274


The Time Span Lines

The sixteen fields in a time span line are ordered and defined as follows:

Network*

Station*

Location*

Channel*

Start Time*

End Time*

Max Clock Drift

Sample Rate

Number of Samples

Channel Flag
(C or T)

Station Volume

DCC Tape Number

DMC Volume Number

Comment

Date Line Mod DMC

Date Line Mod DCC

*Required Field (note that few fields are required)

Where:

NetworkThe approved SEED network code assigned by the DMC
StationThe approved Station Code, wildcards NOT permitted
LocationThe location ID. If not there, leave blank
ChannelThe SEED channel name, wildcards NOT permitted
Start TimeThe start date of data represented in this line, in SEED date format to the nearest second (YYYY,JJJ,HH:MM:SS), with no spaces and zero padded to the left.
End TimeThe end date represented in this line in SEED date format to the nearest second (YYYY,JJJ,HH:MM:SS), with no spaces and zero padded to the left.
Max Clock Drift Max clock drift in seconds per sample.
Sample RateNumber of samples per second.
Number of Samples Total number of samples in this time series. (Not stored at the DMC)
Channel FlagContinuous (C) or triggered (T)
Station VolumeAny Station Volume Identifier
DCC Tape NumberThe DCC assigned tape number
DMC Volume NumberThe DMC assigned tape number
CommentOne of the following comments:
DD - Data delayed (expected ship date)
DW - Data withheld (reason)
SD - Station down
TP - Tape problem (lost, blank)
OT - Other (specify)
NC - No comment
Date Line Modifed
by DMC
The date that the line was modified by the DMC in SEED date format to the nearest day (YYYY,JJJ), with no spaces and zero padded to the left.
Date Line Modifed
by DCC
The date that the line was modified by the DCC in SEED date format to the nearest day (YYYY,JJJ), with no spaces and zero padded to the left.

Examples of Time Span Lines:

IU|ANMO|01|BHE|1994,258,00:00:00|1994,265,00:00:00|.0005|20||CG|||||1998,275||
IU|ANMO|01|BHE|1994,265,00:00:00|1994,275,00:00:00|.0005|20||CG|||||1998,275||


Representing Continuous Time Spans

Preferably, continuous data for a given network/station/location/channel is written in one time span line. Continuous data -may- be represented in the synchronization file by a sequence of time span lines. The continuous data time span lines must be written such that a previous time span's end time and the next time span's start time:

1) Are equal (preferred)
2) Differ by less than some constant amount
3) Differ by less than 1/2*sample rate (Sample Rate field must be filled)

This ambiguous definition of what may constitute continuous data in a synchronization file is a result of trying to make the synchronization file format flexible and easy to write. Definitions of what consitute continuous data in a synchronization file which allow for the minimum number of fields being written to a synchronization file and which seem most likely to allow for a straight dump of start and end time values in a DCC's database are provided. Currently, the Max Clock Drift field is not being used as part of a continuous data definition. Though well suited for that, using it would require that the number of samples also be written to a synchronization file and few writers of synchronization files fill in that field.

Tools developed to operate on synchronization files should support the above definitions of continuous data as options.