sod

Groups:

Authors:

Igor Morozov, 04/09

SOD (Standing Order for earthquake Data)

This tool implements the functionality of SOD (Standing Order for Data) software (http://www.seis.sc.edu/SOD/). Its basic purpose is to simplify generation of complex database requests for common earthquake data retrieval.

SOD queries the database for network, station, channel, event, and other earthquake-related information, and keeps track of the last retrieved event. Database queries can be repeated periodically, and the program can ramain running ubtil a specified date (see list STAND).

By default, database tables with names "$networks", "$stations", "$channels", and "$events" are used, and these names can be resolved by the dictionary used in the curresponding instance of DBASE. However, these table names can be changed by using list DBTABLE. The names of the fields in these tables should still correspond to the convention used in the dictionary.

Events and stations, etc. are selected by matching all of the criteria specified in several selection lists (ARRIVAL, BAND, DIST, AZIM, EVENT, NETWORK, or ORIGIN)

Different instances of selection lists are combined by using the 'OR' operation. Thus, if several ranges of distances (list DIST) or origins (list ORIGIN) are provided, events that fall into at least one of them are selected.

If TRACES list is present, the tool generates output anchor traces whenever a new event is received from the database. An anchor trace is output for each station currently found in the selected data subset. The event and station IDs from the database are put in the trace headers, and the time start and length of the trace is set according to the specified event. The name of the corresponding waveform table in the database is also put in the trace header. In very rare cases when several waveform tables may need to be checked, individual anchor traces are generated for each such table.

If data traces enter SOD, they can be used to control its operation. For example, if traces with different arrival names in their headers are generated by GENRATE, and SOD operates in WHEN=PROC mode, the complete SOD operation will be repeated for each input trace, extracting the corresponding arrivals.

Further in the processing flow, the traces can query the waveform tables in the database (by using HDRMATH -> list DBSQL) and get the data waveform downloaded inthe same flow.

Jobs containing this tool should normally be placed into processing flows submitted to remote servers by using WSERV. Following SOD, calls to POST tool would post the resulting data for downloading by the client.

wserv,post,sql,hdrmath,dataset,dbase

Module call format: