smgui is a module to analyse seimsic traces in terms of common strong ground motion parameters to fulfill the requirements of engineering seismology


SMGUI (Strong Motion Graphical User Interface)


smgui is a module to analyse seimsic traces in terms of common strong ground motion parameters to fulfill the requirements of engineering seismology. The userfriendly GUI allows for example the calculation of

  • Root-mean-square (RMS) of acceleration, velocity and displacement
  • Arias (Ia) and characteristic (Ic) intensities
  • Cumulative Absolute Velocity (CAV) and Specific Energy Density (SED)
  • Effective design acceleration (EDA)
  • predominant (Tp) and mean (Tm) periods
  • Fourier and Power spectra
  • Response spectra

It also allows to filter the frequency content of the given signal and filtering prior to time-integration of the signal (to obtain velocity and displacement time-histories).

smgui is able to read waveform data from any data service supported from SeisComP3 as SeedLink, ArcLink, file, sdsarchive etc.

Finally, and due to its full integration within SeisComP3, smgui complements the functionality of SeisComP3 regarding strong motion analysis. Waveforms and results can be exported in ASCII format.


The smgui can be started by

./seiscomp exec smgui -H -I arclink://


Data selection

The Figure below shows the starting page of smgui. On the left side is the loaded inventory showing all available networks. These networks can be browsed down to the channel level (for example BHZ).


Screenshot of initial view

Once a channel is selected, the waveforms are loaded. The right side of smgui shows the spectrogram in the upper part and the corresponding waveforms in the lower part.

By a left click on the time scale, the time window can be panned. Using the right mouse button and holding it, a zooming in time is possible. To zoom in, left click on the start time, hold the mouse button, move to the right and release the button when the end time is reached. A green horizontal bar should appear in case the selection was successful. To zoom out, to the same, but move the mouse to the left side. A red bar should appear in case the time window selection was successful.

To select the processing time window, left click in the waveforms to select the start time, hold the button and move the mouse to the end time. Then release the mouse button. The select time window should be marked. It can be either reselected or the black triangles on the time scale can be moved to change start and ent time. The figure below shows an example of a data selection.


Screenshot of data selection

Data processing

After the channel and time window is selected, the user can calculate the strong motion parameter through a click on the process button. The figure below shows the processing results page. .. _fig-results:


Screenshot of processing results

The processing results as well as the waveform data can be exported in a flat ASCII file.



smgui inherits global options.


Type: boolean

Switch to offline mode Default is false.


-h, --help

show help message.

-V, --version

show version information

--config-file arg

Use alternative configuration file. When this option is used the loading of all stages is disabled. Only the given configuration file is parsed and used. To use another name for the configuration create a symbolic link of the application or copy it, eg scautopick -> scautopick2.

--plugins arg

Load given plugins.

-D, --daemon

Run as daemon. This means the application will fork itself and doesn't need to be started with &.

--verbosity arg

Verbosity level [0..4]. 0:quiet, 1:error, 2:warning, 3:info, 4:debug

-v, --v

Increase verbosity level (may be repeated, eg. -vv)

-q, --quiet

Quiet mode: no logging output

--print-component arg

For each log entry print the component right after the log level. By default the component output is enabled for file output but disabled for console output.

--component arg

Limits the logging to a certain component. This option can be given more than once.

-s, --syslog

Use syslog logging back end. The output usually goes to /var/lib/messages.

-l, --lockfile arg

Path to lock file.

--console arg

Send log output to stdout.


Debug mode: --verbosity=4 --console=1


Trace mode: --verbosity=4 --console=1 --print-component=1 --print-context=1

--log-file arg

Use alternative log file.