...
The SWIDB database was used in two ways: The results of the study were recorded in the Elaboration table. It was possible to have several Elaborations for one phenomenon, but generally, the final elaborations were collected in one Elaboration. This is how the study of Polish National NerworkNetwork was developed and exported to the International Seismic Center. The second way was to define the phenomenon in the Origin table, which collected studies and was unambiguously linked to the phenomenon by ID. The second method has become more common in induced seismology and is more consistent with SWIP5. The event information is kept in the Origins tables.
However, to enable reading of earlier databases, an additional module was developed that ignores the Origin tables and accepts the eartquakes earthquakes ID from the Elaboration tables. It should not be used for databases created in the second way. Additional module commands are marked in green.
...
- Loading elaboration for a seismogram with File
SWIDB Load elaboration for waveforms. Event ID is from the table Elaborations. - Loading elaborations for a given time period with the command File SWIDB Load all elaboration Load all elaborations. Event ID is from the table Elaborations.
- Loading a phenomenon dat for a given seismogram File SWIDB Load event for waveforms.
- Loading station (location) parameters from database File SWIDB Load event for waveforms.
- Listing all events (origin numbers) with the File SWIDB List Events. Origin numbers are printed in the report window, and at the end, the number of phenomena is printed (Fig. 21).
- Loading all events from the database with File SWIDB Load all events WARNING. This command can be lengthy with a large number of phenomena. Loading a phenomenon with a given Origin number using File SWIDB Load elaboration by numer Load elaboration by number.
Fig. 21 Report window
Children Display