TS Format v1.3 --------- A G Jones: Ottawa: 30 April 1999 Time Series format for input to LIMS processing codes. Each time series file contains three sections. A comment block, an information block, and a data block. The file can either be in plain ASCII, or in formatted or unformatted BINARY. The channel order used is: Hx, Hy, Hz, Ex, Ey. This can be made more flexible if there is sufficient demand. -------------------------------------------------------------------------------- Modification history: v1.1: May 1997: Added COORD_SYS Added DECLIN Added INSTRUMENT Added SENSOR_i Added ENDTIME Added MIS_DATA Added UTM_ORIGIN Added UTM_ZONE Added UTM_NORTH Added UTM_EAST v1.2: Dec 1997: Added SEQ_REC Added Filter block v1.3: Apr 1999: Added ENDIAN Added BIN_FORM Added INFO_START & INFO_END -------------------------------------------------------------------------------- COMMENT BLOCK: ============== At the beginning of each data file, as many comment lines as required can be written. Each line must begin with the hash (#) mark. None of this information is required or read by the reading routine. Example:- # time series file from mp2ts # date: Mon May 12 10:15:57 1997 # # input file: sno101/sno101as.1mp # # site description: KM 222.5 # # Latitude :062:39:47 N # Longitude :116:12:32 W # # LiMS number : 52 # Magnetometer number : 52 # # Ex line length (m): 100.0000000 # Ey line length (m): 100.0000000 # # Azimuths relative to: MAGNETIC NORTH # Ex azimuth; -17 # Ey azimuth; 73 # Hx azimuth; -17 # Hy azimuth; 73 # If the file is BINARY/UNFORMATTED, then each line should be 80 characters long. -------------------------------------------------------------------------------- FILTER BLOCK: ============= The filter block should contain information about the filtering of the data by the instruments, and a routine to remove the effects of the filtering. Each line starts with a two-character '#F' so that it appears as a comment block to the time series reading programs. This information should be sufficiently complete that the time series file is "stand-alone". Example:- #F Filter block begin #F #F Filters applied to LiMS/LRMT data are: #F 1: Analogue anti-alias six-pole Bessel low-pass #F filters on each channel with -3 dB point at nominally 5 Hz. #F -calibrated values given below #F #F 2: Digital anti-alias multi-stage Chebyshev FIR filters #F with final stage at 2xsampling rate #F #F 1: Analogue single-pole Butterworth high-pass filters on the #F telluric channels only with -3 dB point at nominally 30,000 s #F -calibrated values given below #F #F Chan Calib Low-pass High-pass (s) #F 1 1.00 0.20 0.00 #F 2 1.00 0.20 0.00 #F 3 1.00 0.20 0.00 #F 4 1.00 0.20 30002.00 #F 5 1.00 0.20 30065.00 #F #F In the tsrestack code, these filter responses are #F removed using bessel7.f and high17.f #F #F Filter block end If the file is BINARY/UNFORMATTED, then each line should be 80 characters long. ------------------------------------------------------------------------------- INFORMATION BLOCK: ================== This block contains information about the site co-ordinates and site orientation, and other pertinent information. Each line must begin with a "greater-than" (>) sign, followed by a recognized keyword. After the keyword is either an equals (=) sign, or a colon (:), followed by a numeric value or alphabetic word. The block must begin with the keyword INFO_START, and must end with the keyword INFO_END The following keywords are currently supported:- INFO_START start of info block STATION the station name. 6-character alphanumberic INSTRUMENT the instrument used (integer) WINDOW the data window. 8-character alphanumeric (usually 6-station name plus two trailing identifiers) LATITUDE site latitude in degrees and decimals LONGITUDE site longitude in degrees and decimals ELEVATION site elevation in metres UTM_ORIGIN Longitude origin of UTM coordinates UTM_ZONE UTM zone UTM_NORTH UTM northing in m (referenced to the equator) UTM_EAST UTM easting in m (referenced to UTM_ORIGIN = 500000) COORD_SYS acquisition coordinate system. MAGNETIC NORTH for magnetic north TRUE NORTH for true north OTHER for other system DECLIN required only for COORD_SYS = MAGNETIC declination appropriate for the site and time FORM Data form. Either ASCII or BINARY FORMAT Data format. Either UNFORMATTED for FORM=BINARY or a format statement for FORM=ASCII e.g., FREE or (5g15.5) ENDIAN Endian of integers. Either "Big" or "Little" Required for FORM=BINARY. Big for SUNs & Motorola chips (big endian: lsb last) Little for DEC and DOS ordering of bits (little endian: lsb first) BIN_FORM Binary format. Either "DOS" or "IEEE" Required for FORM=BINARY. DOS for DEC and DOS ordering of bits IEEE for IEEE standard (SUNs & Motorola chips) SEQ_REC For FORM=BINARY then the SEQ_REC can be specified, which is the number of time sequences per record. It must be an integer, and the number of values per record will be SEQ_REC*NCHAN. The default for missing entry is SEQ_REC=1 For a binary file using Sun's FORTRAN compiler, there are 8 bytes of system information per record, so a 5-channel record of 20 bytes contains 29% (8/28) wasted space. This can be reduced by setting SEQ_REC to e.g. 12 (for 5 s digitizing rate then each record contains 1 min of data) for a waste reduced to 3% (8/240). NCHAN Number of data channels For each channel.... SENSOR_i code number for the i'th sensor (integer) AZIM_i the azimuth of the i'th data channel CHAN_i the channel name of the i'th data channel UNITS_i the units of the data of the i'th data channel GAIN_i the gain of the i'th data channel (usually 1.) BASELINE_i the baseline of the i'th data magnetic channel STARTTIME the data start time, in 12-char format yymmddhhmnss ENDTIME the data end time, not required T_UNITS units of DELTA_T. Either "Hz" or "s" DELTA_T digitizing rate MIS_DATA value for missing data INFO_END end of info block Example:- >INFO_START: >STATION :sno101 >INSTRUMENT: 52 >WINDOW :sno101as >LATITUDE : 62.6631 >LONGITUDE : -116.209 >ELEVATION : 0. >COORD_SYS :MAGNETIC NORTH >DECLIN : 27.3400 >FORM :BINARY >FORMAT :UNFORMATTED >SEQ_REC : 1 >NCHAN : 5 >CHAN_1 :HX >SENSOR_1 : 52 >AZIM_1 : -17 >UNITS_1 :nT >GAIN_1 :1.0 >CHAN_2 :HY >SENSOR_2 : 52 >AZIM_2 : 73 >UNITS_2 :nT >GAIN_2 :1.0 >CHAN_3 :HZ >SENSOR_3 : 52 >AZIM_3 : 0. >UNITS_3 :nT >GAIN_3 :1.0 >CHAN_4 :EX >SENSOR_4 : 52 >AZIM_4 : -17 >UNITS_4 :mV/km >GAIN_4 :1.0 >CHAN_5 :EY >SENSOR_5 : 52 >AZIM_5 : 73 >UNITS_5 :mV/km >GAIN_5 :1.0 >STARTTIME :960808211500 >ENDTIME :960818161000 >T_UNITS :s >DELTA_T : 5.00000 >MIS_DATA : 99999.9 >INFO_END : If the file is BINARY/UNFORMATTED, then each line should be 80 characters long. ------------------------------------------------------------------------------- DATA BLOCK: =========== The data follow, with one time instance per "line". Each line has NCHAN entries, in the channel order decribed in the information block. Example:- 1.98250 0.878400 3.64780 1.10889 2.02644 1.93980 0.976000 3.65390 1.15682 2.01610 1.90320 1.08580 3.66000 1.21346 1.99887 1.86050 1.21390 3.67220 1.28536 1.99887 1.81780 1.33590 3.68440 1.31586 2.00921 1.76290 1.40910 3.69050 1.25921 2.03678 1.70190 1.45180 3.70880 1.14157 2.08503 1.65920 1.49450 3.72100 1.11543 2.09881 1.64700 1.55550 3.72710 1.27664 2.05057 1.65920 1.64090 3.73930 1.44657 1.98164 1.68360 1.71410 3.74540 1.45964 1.95062 1.70190 1.75070 3.74540 1.38557 1.96785 1.70190 1.74460 3.73930 1.33546 2.00576 1.72020 1.72630 3.73930 1.30932 2.04023 1.72630 1.70190 3.73320 1.25486 2.07469 1.72630 1.69580 3.72710 1.21564 2.09192 1.74460 1.70800 3.72710 1.28536 2.06435 1.75680 1.74460 3.73320 1.40736 2.01266 1.76290 1.79340 3.74540 1.45746 1.99887 1.79340 1.82390 3.75150 1.42696 2.02299