You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Plugins are dynamic libraries that are independent of the main SWIP5 program. They extend and define program functionalities. They can read and process waveforms, calculate the earthquake parameters, save and export work results, control other modules, and expand their functionality. Plugins may depend on one another, i.e. for the operation of one module another plugin is required, without which the module will not be included in the program (Fig. 1). For example, a magnitude counting module needs a plugin to simulate a Wood-Anderson seismometer.

The modules use SWIP5 resources and have access to the event elaboration in QuakeML, waveforms, and station parameters. They can broadcast information about performed actions to other modules and to windows of the program kernel. They modify the content of the elaboration window and all reports and messages from modules are printed in the report window.

This manual describes the modules for the basic interpretation of seismic phenomena, which are included in version 5.3.16 of the program. Due to the fact that the dynamics of module development are faster than changes in SWIP5 documentation, and the possibility of creating modules by other developers and users, the information contained in this documentation may be incomplete.

In the documentation, modules are divided by the functions they perform. For this reason, if a module performs functions of various kinds, it can be discussed in several chapters.

In addition to the basic SWIP5 program, there is a version for the console - SWIP5C. The purpose of SWIP5C is both online operation - automatic detection and localization, alerts, and periodic activities that do not require interaction with the operator, such as reports, summaries, website creation, etc. It works continuously in the background on computer servers or is invoked cyclically by the cron. The core SWIP5C (Console) does not have a GUI. It can use all modules but without their GUI functionality.


Fig. 1. Scheme of the SWIP5 modular structure.

.

Contents:

  • No labels