Composition
The application Seismic Catalog Recalculation is underneath composed of elements of three other applications - Localization, Spectral Analysis and Catalog Editor. The results of Localization and Spectral Analysis are used to generate parameters for an event, which is later updated or added to the input catalog with the use of the Catalog Editor application. For this reason, the inputs and outputs of the application are a composition of the three applications' inputs and outputs.
Input file specification
The application requires four types of files (one file per each type) - see Figure 1:
- Catalog - a seismic catalog of events in EPISODES Platform Matlab-based format.
- Miniseed Waveform (or any subtype) containing seismograms on which an event is recorded - either an event already contained in the catalog, for which we want to update the parameters, or a new event that should be added to the catalog.
- Network inventory, either in XML or datalessSEED format
- Velocity model in EPISODES Platform GDF format.
All of the files can be found within the platform's Episodes data (see AH Episodes quick start guide), uploaded to the workspace or obtained with one of Converters.
Figure 1. Application input files specification
Filling form values
The application form is composed of two parts - picking the P and/or S wave arrivals (marked with (1) in Figure 2) and setting the event details (marked with (2) and (3) in Figure 2).
The required picks are at least three points with P wave arrival and at least one pick for P and/or S wave. The picked points are used for the Localization application and the phases for the Spectral Analysis application (see the first section of this guide). For more information about the functionality related to picking wave arrivals see the Seismogram picking tool user guide.
The Event ID (marked with (2) in Figure 2) identifies the event in the catalog - if the ID already existed in the input catalog, the event details will be replaced in the resulting catalog, otherwise, an event will be added to the resulting catalog (see Catalog Editor user guide for more details on event ID specification). The event coordinates will be passed as parameter to the Localization application (see Localization user guide). Both values can be read from an existing catalog or other files containing event location and ID.
Figure 2. Application form with values filled
Produced output
Back to top
Related Documents