NetDC manual [ back ] [ forward ]

Response requests return detailed station and channel information to the user in the form of a specially formatted ASCII text file. When a data center is delegated to process ".RESP" requests, a file named "response.request" is created. The output for a response request is pulled from response files generated by the IRIS utility "rdseed" or similar utility.

An excerpt of ".RESP" text output is presented here for illustration:

   B050F03 	Station: 	SAO
   B050F16 	Network: 	BK
   B052F03 	Location: 	??
   B052F04 	Channel: 	BHE
   B052F22 	Start date:    	1996,143,21:30:00
   B052F23 	End date: 	1998,155,21:43:00
   #
   #		+------------------------------------+
   # 		| Response (Poles    and Zeros)      |
   # 		| BK SAO BHE 			     |
   # 		| 05/22/1996 to 06/04/1998   	     |
   # 		+------------------------------------+
   #
   B053F03 	Transfer function type: 	A [Laplace Transform (Rad/sec)]
   B053F04 	Stage sequence number: 		1
   B053F05 	Response in units lookup: 	M/S - Velocity in Meters Per Second
   B053F06 	Response out units lookup: 	V - Volts
   B053F07 	A0 normalization factor: 	986.834
   B053F08 	Normalization frequency: 	0.12
   B053F09 	Number of zeroes:    		2
   B053F14 	Number of poles:    		4
   # 		Complex zeroes:
   # 		i real imag real_error    imag_error
   B053F10-13 	0 0.000000E+00    0.000000E+00 0.000000E+00 0.000000E+00
   B053F10-13 	1 0.000000E+00    0.000000E+00 0.000000E+00 0.000000E+00
   # 		Complex poles:
   # 		i real imag real_error    imag_error
   B053F15-18 	0 -1.234120E-02    1.234150E-02 0.000000E+00 0.000000E+00
   B053F15-18 	1 -1.234120E-02    -1.234150E-02 0.000000E+00 0.000000E+00
   B053F15-18 	2 -1.958780E+01    2.456170E+01 0.000000E+00 0.000000E+00
   B053F15-18 	3 -1.958780E+01    -2.456170E+01 0.000000E+00 0.000000E+00
   #
   # 		+------------------------------------+
   # 		| Channel Sensitivity/Gain    	     |
   # 		| BK SAO BHE 			     |
   # 		| 05/22/1996 to 06/04/1998  	     |
   # 		+------------------------------------+
   #
   B058F03 	Stage sequence number: 		1
   B058F04 	Gain: 				2.255790E+03
   B058F05 	Frequency of gain: 		1.200000E-01 HZ
   B058F06 	Number of calibrations:    	0
   #
   # 		+------------------------------------+
   # 		| Response (Poles    and Zeros)      |
   # 		| BK SAO BHE 			     |
   # 		| 05/22/1996 to 06/04/1998   	     |
   # 		+------------------------------------+
   #
   B054F03 	Transfer function type: 	D
   B054F04 	Stage sequence number: 		2
   B054F05 	Response in units lookup: 	V - Volts
   B054F06 	Response out units lookup: 	COUNTS - Digital Counts
   B054F07 	Number of numerators:    	0
   B054F10 	Number of denominators:    	0
   #
   # 		+------------------------------------+
   # 		| Decimation 			     |
   # 		| BK SAO BHE 			     |
   # 		| 05/22/1996 to 06/04/1998 	     |
   # 		+------------------------------------+
   #
   B057F03 	Stage sequence number: 		2
   B057F04 	Input sample rate: 		5.120000E+03
   B057F05 	Decimation factor:   		1
   B057F06 	Decimation offset:    		0
   B057F07 	Estimated delay (seconds): 	6.152000E-03
   B057F08 	Correction applied (seconds): 	-6.250000E-03
   #
   # 		+------------------------------------+
   # 		| Channel Sensitivity/Gain   	     |
   # 		| BK SAO BHE 			     |
   # 		| 05/22/1996 to 06/04/1998  	     |
   # 		+------------------------------------+
   #
   B058F03 	Stage sequence number: 		2
   B058F04 	Gain: 				4.270340E+05
   B058F05 	Frequency of gain: 		1.200000E-01 HZ
   B058F06 	Number of calibrations:    	0

...(and so on)...

In terms of requesting ".RESP" data, the user must fill out all of the request fields, including the start and end time. The flexibility found in inventory requests does not carry over to the ".RESP" request type. By supplying the necessary information, you can expect to receive ".RESP" output that covers the specified stations and channels that have effective times within the start and end time request fields.

Because the output is ASCII text, many of the response shipments will be sent to the user through email. If the response output is especially large, the user will receive the data through FTP, accompanied by notification of the shipment through email.

introduction •• overall concept •• request format •• request reception and delegation
datagrams •• local request processing •• inventory requests •• response requests
waveform requests •• product shipment •• installation and setup •• writing interface code
troubleshooting •• future implementations •• conclusion •• appendix A - summary of NetDC datagrams

About IRIS | Members | Programs | USArray | Seismic Monitor | Earthquakes | SeismoArchives
Mailing Lists | Stations | Data | Software | Publications | News | Contact | Site Map | Search