|
|
<!DOCTYPE html>
|
|
|
|
|
|
<html >
|
|
|
<head>
|
|
|
<meta charset="utf-8" />
|
|
|
<title>Overview — SeisComP Release documentation</title>
|
|
|
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
|
|
|
<link rel="stylesheet" href="../_static/seiscomp.css" type="text/css" />
|
|
|
<link rel="stylesheet" type="text/css" href="../_static/graphviz.css" />
|
|
|
<script type="text/javascript" src="../_static/seiscomp.js"></script>
|
|
|
<script type="text/javascript" id="documentation_options" data-url_root="../" src="../_static/documentation_options.js"></script>
|
|
|
<script src="../_static/jquery.js"></script>
|
|
|
<script src="../_static/underscore.js"></script>
|
|
|
<script src="../_static/doctools.js"></script>
|
|
|
<script src="../_static/language_data.js"></script>
|
|
|
<link rel="shortcut icon" href="../_static/favicon.ico"/>
|
|
|
<link rel="index" title="Index" href="../genindex.html" />
|
|
|
<link rel="search" title="Search" href="../search.html" />
|
|
|
<link rel="next" title="Historical Information" href="history.html" />
|
|
|
<link rel="prev" title="Introduction and Scope" href="introduction.html" />
|
|
|
</head>
|
|
|
<body>
|
|
|
<div class="header">
|
|
|
<div class="container">
|
|
|
<div class="brand">
|
|
|
<img class="logo" src="../_static/brands/seiscomp/text/white.svg"/>
|
|
|
<!-- span class="title">SeisComP Release</span -->
|
|
|
<span class="version">5.3.0</span>
|
|
|
</div>
|
|
|
</div>
|
|
|
</div>
|
|
|
<div class="nav">
|
|
|
<div class="container">
|
|
|
<div class="content"><a class="pull-right" id="sidebar-toggle">TOC</a>
|
|
|
|
|
|
<div class="related" role="navigation" aria-label="related navigation">
|
|
|
<ul>
|
|
|
<li class="right">
|
|
|
<a href="../genindex.html" title="General Index"
|
|
|
accesskey="I">
|
|
|
index
|
|
|
</a>
|
|
|
</li>
|
|
|
<li class="right">
|
|
|
<a href="history.html" title="Historical Information"
|
|
|
accesskey="N">
|
|
|
next
|
|
|
</a>
|
|
|
</li>
|
|
|
<li class="right">
|
|
|
<a href="introduction.html" title="Introduction and Scope"
|
|
|
accesskey="P">
|
|
|
previous
|
|
|
</a>
|
|
|
</li>
|
|
|
<li class="nav-item nav-item-0">
|
|
|
<a href="../index.html">Home</a>
|
|
|
</li>
|
|
|
</ul>
|
|
|
</div>
|
|
|
</div>
|
|
|
</div>
|
|
|
</div>
|
|
|
<div class="container">
|
|
|
<div class="fitted content" id="anchors-container">
|
|
|
<div class="body" role="main">
|
|
|
|
|
|
<div class="section" id="overview">
|
|
|
<span id="id1"></span><h1>Overview<a class="headerlink" href="#overview" title="Permalink to this headline">¶</a></h1>
|
|
|
<p>This overview section is intended to quickly introduce the reader into
|
|
|
key aspect of <cite>SeisComP</cite> and to provide the access points for further reading.</p>
|
|
|
<div class="section" id="modular-structure">
|
|
|
<h2>Modular structure<a class="headerlink" href="#modular-structure" title="Permalink to this headline">¶</a></h2>
|
|
|
<p>A <cite>SeisComP</cite> system is not a single piece of software but it involves automatic and
|
|
|
interactive modules working
|
|
|
separately to process data and to analyze seismicity.
|
|
|
Read the <a class="reference internal" href="concepts/modules.html#concepts-modules"><span class="std std-ref">concepts section on modules</span></a> for more conceptional details.</p>
|
|
|
<p>Each module has a particular task, such as:</p>
|
|
|
<ul class="simple">
|
|
|
<li><p>Acquisition of waveform data from one or more providers</p></li>
|
|
|
<li><p>Waveform archiving</p></li>
|
|
|
<li><p>Waveform processing to identify phase arrivals</p></li>
|
|
|
<li><p>Processing of phase picks to detect events and compute locations</p></li>
|
|
|
<li><p>Providing a user interface for manually reviewing events</p></li>
|
|
|
</ul>
|
|
|
<p>and many more. Key features are summarized in the <a class="reference internal" href="introduction.html#introduction"><span class="std std-ref">introduction</span></a>.</p>
|
|
|
<div class="figure align-center" id="id9">
|
|
|
<a class="reference internal image-reference" href="../_images/sc-interaction.png"><img alt="../_images/sc-interaction.png" src="../_images/sc-interaction.png" style="width: 16cm;" /></a>
|
|
|
<p class="caption"><span class="caption-text">Real-time data acquisition, archiving and automatic processing combined with manual analysis.</span><a class="headerlink" href="#id9" title="Permalink to this image">¶</a></p>
|
|
|
</div>
|
|
|
<div class="section" id="data-acquisition-modules">
|
|
|
<h3>Data acquisition modules<a class="headerlink" href="#data-acquisition-modules" title="Permalink to this headline">¶</a></h3>
|
|
|
<p>Data acquisition modules allow to provide and store waveform data in real-time.
|
|
|
They are described in the acquisition section of the modules documentation.</p>
|
|
|
</div>
|
|
|
<div class="section" id="automatic-processing-modules">
|
|
|
<h3>Automatic processing modules<a class="headerlink" href="#automatic-processing-modules" title="Permalink to this headline">¶</a></h3>
|
|
|
<p>Automatic processing modules allow real-time or offline processing of waveforms and event parameters.
|
|
|
They are described in the processing section of the modules documentation.</p>
|
|
|
</div>
|
|
|
<div class="section" id="interactive-modules">
|
|
|
<h3>Interactive modules<a class="headerlink" href="#interactive-modules" title="Permalink to this headline">¶</a></h3>
|
|
|
<p>Interactive <a class="reference internal" href="glossary.html#term-gui"><span class="xref std std-term">GUI</span></a> modules show waveforms and processing results and allow user interactions:</p>
|
|
|
<ul class="simple">
|
|
|
<li><p><a class="reference internal" href="../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a>: processing waveforms, locating events and determining magnitudes and focal mechnisms</p></li>
|
|
|
<li><dl class="simple">
|
|
|
<dt><a class="reference internal" href="../apps/scrttv.html#scrttv"><span class="std std-ref">scrttv</span></a>: view waveforms and phase picks, select events for processing in scolv, enable or disable stations</dt><dd><p>for automatic processing</p>
|
|
|
</dd>
|
|
|
</dl>
|
|
|
</li>
|
|
|
<li><p><a class="reference internal" href="../apps/scmv.html#scmv"><span class="std std-ref">scmv</span></a>: view station locations on a map with status information and waveforms, select events for processing in scolv</p></li>
|
|
|
<li><p><a class="reference internal" href="../apps/scesv.html#scesv"><span class="std std-ref">scesv</span></a>: view the latest events on a map and relevant event parameters</p></li>
|
|
|
<li><p><a class="reference internal" href="../apps/scheli.html#scheli"><span class="std std-ref">scheli</span></a>: view the seismogram of a station in a helicorder plot, save images automatically</p></li>
|
|
|
<li><dl class="simple">
|
|
|
<dt><a class="reference internal" href="../apps/scqcv.html#scqcv"><span class="std std-ref">scqcv</span></a>: view waveform quality control (QC) parameters, enable or disable stations</dt><dd><p>for automatic processing</p>
|
|
|
</dd>
|
|
|
</dl>
|
|
|
</li>
|
|
|
<li><p><a class="reference internal" href="../apps/scmm.html#scmm"><span class="std std-ref">scmm</span></a>: the messaging system monitor</p></li>
|
|
|
</ul>
|
|
|
<p>The GUI modules are described in the Interactive analysis section of this documentation.</p>
|
|
|
</div>
|
|
|
<div class="section" id="inventory-modules">
|
|
|
<h3>Inventory modules<a class="headerlink" href="#inventory-modules" title="Permalink to this headline">¶</a></h3>
|
|
|
<p>Inventory modules allow to manipulate inventories, e.g. to convert different formats
|
|
|
or to write information to the database.
|
|
|
They are described in the inventory section of the modules documentation.</p>
|
|
|
</div>
|
|
|
<div class="section" id="utility-modules">
|
|
|
<h3>Utility modules<a class="headerlink" href="#utility-modules" title="Permalink to this headline">¶</a></h3>
|
|
|
<p>Utility modules provide access to waveforms, the data base and much more.
|
|
|
They are described in the utilities section of the modules documentation.</p>
|
|
|
</div>
|
|
|
</div>
|
|
|
<div class="section" id="communication-and-database-access">
|
|
|
<h2>Communication and database access<a class="headerlink" href="#communication-and-database-access" title="Permalink to this headline">¶</a></h2>
|
|
|
<p>As modules run, they produce objects corresponding to geophysical concepts
|
|
|
such as <a class="reference internal" href="glossary.html#term-pick"><span class="xref std std-term">picks</span></a> and <a class="reference internal" href="glossary.html#term-origin"><span class="xref std std-term">origins</span></a>.
|
|
|
These objects are exchanged with, and stored for later use by, other modules.
|
|
|
Communication between these modules happens in two ways:</p>
|
|
|
<ol class="arabic simple">
|
|
|
<li><p>Via objects stored in, and retrieved from, a shared database.</p></li>
|
|
|
<li><p>Via messages exchanged between modules.</p></li>
|
|
|
</ol>
|
|
|
<p>Managing the communication between the modules in <cite>SeisComP</cite> is the job of the <a class="reference internal" href="concepts/messaging.html#concepts-messaging"><span class="std std-ref">messaging
|
|
|
system</span></a>.
|
|
|
The messaging system is controlled by <a class="reference internal" href="../apps/scmaster.html#scmaster"><span class="std std-ref">scmaster</span></a>. It acts as gatekeeper to the database,
|
|
|
and only the module <a class="reference internal" href="../apps/scmaster.html#scmaster"><span class="std std-ref">scmaster</span></a> is allowed
|
|
|
write access to the database.
|
|
|
Additional details are found under <a class="reference internal" href="concepts/messaging.html#concepts-messaging"><span class="std std-ref">Messaging system</span></a> in the <a class="reference internal" href="concepts.html#concepts"><span class="std std-ref">Concepts</span></a> chapter.</p>
|
|
|
<div class="figure align-center" id="id10">
|
|
|
<a class="reference internal image-reference" href="../_images/sc_system_standard.jpg"><img alt="../_images/sc_system_standard.jpg" src="../_images/sc_system_standard.jpg" style="width: 10cm;" /></a>
|
|
|
<p class="caption"><span class="caption-text">Modular organization of <cite>SeisComP</cite> with messaging system, RecordStream interface and database.</span><a class="headerlink" href="#id10" title="Permalink to this image">¶</a></p>
|
|
|
</div>
|
|
|
</div>
|
|
|
<div class="section" id="waveform-data">
|
|
|
<h2>Waveform data<a class="headerlink" href="#waveform-data" title="Permalink to this headline">¶</a></h2>
|
|
|
<p>Internally in <cite>SeisComP</cite>. most waveform data is currently handled as <a class="reference internal" href="glossary.html#term-miniseed"><span class="xref std std-term">miniSEED</span></a> data (Data Only
|
|
|
<a class="reference internal" href="glossary.html#term-seed"><span class="xref std std-term">SEED</span></a> records).
|
|
|
A time series of records is identified by its stream identifier,
|
|
|
following the SEED naming convention,</p>
|
|
|
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">NET</span><span class="o">.</span><span class="n">STA</span><span class="o">.</span><span class="n">LOC</span><span class="o">.</span><span class="n">CHA</span>
|
|
|
</pre></div>
|
|
|
</div>
|
|
|
<p>where:</p>
|
|
|
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">NET</span> <span class="o">-</span> <span class="n">two</span> <span class="ow">or</span> <span class="n">three</span> <span class="n">letter</span> <span class="n">alphanumeric</span> <span class="n">network</span> <span class="n">code</span>
|
|
|
<span class="n">STA</span> <span class="o">-</span> <span class="mi">1</span><span class="o">-</span><span class="mi">5</span> <span class="n">letter</span> <span class="n">alphanumeric</span> <span class="n">station</span> <span class="n">code</span>
|
|
|
<span class="n">LOC</span> <span class="o">-</span> <span class="mi">0</span> <span class="ow">or</span> <span class="mi">2</span><span class="o">-</span><span class="n">letter</span> <span class="n">alphanumeric</span> <span class="n">location</span> <span class="n">code</span>
|
|
|
<span class="n">CHA</span> <span class="o">-</span> <span class="mi">3</span><span class="o">-</span><span class="n">letter</span> <span class="n">channel</span> <span class="ow">or</span> <span class="n">stream</span> <span class="n">code</span>
|
|
|
</pre></div>
|
|
|
</div>
|
|
|
<p>Here <em>alphanumeric</em> means the digits 0 to 9, and uppercase letters A-Z.</p>
|
|
|
<p>For publicly-available seismic stations these are typically supplied
|
|
|
by external servers such as <a class="reference internal" href="../apps/seedlink.html#seedlink"><span class="std std-ref">seedlink</span></a> or <span id="id2"><em>CAPS</em> [<a class="reference internal" href="references.html#id82" title="CAPS. gempa module. URL: https://docs.gempa.de/caps/current/index.html.">3</a>]</span> servers.
|
|
|
For example, the <span id="id3"><em>GEOFON</em> [<a class="reference internal" href="references.html#id114" title="GEOFON. GFZ German Resarch Center for Geosciences. URL: https://geofon.gfz-potsdam.de/.">9</a>]</span> seismic network makes data available at port 18000
|
|
|
at geofon.gfz-potsdam.de which you may query and test using <a class="reference internal" href="../apps/slinktool.html#slinktool"><span class="std std-ref">slinktool</span></a>.</p>
|
|
|
<p>If you operate your own seismic network, you may collect data directly
|
|
|
from your station’s digitizer using one of the many plugins included with
|
|
|
the <a class="reference internal" href="../apps/seedlink.html#seedlink"><span class="std std-ref">seedlink</span></a> module.
|
|
|
You can configure <cite>SeisComP</cite> to obtain data for each station via <a class="reference internal" href="glossary.html#term-binding"><span class="xref std std-term">bindings</span></a>.
|
|
|
This configuration is described in the <a class="reference internal" href="tutorials/geofon_waveforms.html#tutorials-geofon-waveforms"><span class="std std-ref">tutorial on seedlink</span></a>.</p>
|
|
|
<p>Waveform data can be saved locally, using <cite>SeisComP</cite>’s <a class="reference internal" href="../apps/slarchive.html#slarchive"><span class="std std-ref">slarchive</span></a> module.
|
|
|
The waveform archive is organized in a structured way on your local file system,
|
|
|
with one file for each channel and day, known as the <a class="reference internal" href="glossary.html#term-sds"><span class="xref std std-term">SDS</span></a> archive.
|
|
|
Thanks to <cite>SeisComP</cite>’s <a class="reference internal" href="concepts/recordstream.html#concepts-recordstream"><span class="std std-ref">RecordStream</span></a> concept, its modules
|
|
|
can be reconfigured to use the local data from an archive, a server or from files, allowing <em>playbacks</em>.
|
|
|
This ability to replay old waveforms and re-analyze them, is very
|
|
|
important for exploring your system configuration, and developing
|
|
|
<cite>SeisComP</cite>.</p>
|
|
|
<p>Finally, being both a collector and a server of waveform data,
|
|
|
<a class="reference internal" href="../apps/seedlink.html#seedlink"><span class="std std-ref">seedlink</span></a> allows you to chain <cite>SeisComP</cite> installations together to
|
|
|
obtain waveform data from upstream sources and relay it to other data users.</p>
|
|
|
<div class="figure align-center" id="id11">
|
|
|
<a class="reference internal image-reference" href="../_images/sc-acquisition-server.png"><img alt="../_images/sc-acquisition-server.png" src="../_images/sc-acquisition-server.png" style="width: 10cm;" /></a>
|
|
|
<p class="caption"><span class="caption-text">Data flow from data centers and stations via plugins to seedlink and the waveform archive
|
|
|
both providing the data to local or remote <cite>SeisComP</cite> modules or other clients.</span><a class="headerlink" href="#id11" title="Permalink to this image">¶</a></p>
|
|
|
</div>
|
|
|
</div>
|
|
|
<div class="section" id="access-to-waveform-data">
|
|
|
<h2>Access to Waveform Data<a class="headerlink" href="#access-to-waveform-data" title="Permalink to this headline">¶</a></h2>
|
|
|
<p><cite>SeisComP</cite> modules can access waveform data from many difference sources,
|
|
|
such as a Seedlink server or an FDSN web service.</p>
|
|
|
<p>In <cite>SeisComP</cite> terminology, the data from these sources are <em>record streams</em>.
|
|
|
Access to the waveform data can be configured by setting an appropriate <a class="reference internal" href="glossary.html#term-recordstream"><span class="xref std std-term">RecordStream</span></a>.
|
|
|
Read the <a class="reference internal" href="concepts/recordstream.html#concepts-recordstream"><span class="std std-ref">concept description of the RecordStream</span></a>
|
|
|
and <a class="reference internal" href="../apps/global_recordstream.html#global-recordstream"><span class="std std-ref">technical documentation of the various implementations</span></a> for many more details.</p>
|
|
|
<div class="figure align-center" id="id12">
|
|
|
<a class="reference internal image-reference" href="../_images/recordstream.png"><img alt="../_images/recordstream.png" src="../_images/recordstream.png" style="width: 10cm;" /></a>
|
|
|
<p class="caption"><span class="caption-text">The RecordStream interface provides flexible access to waveform data.</span><a class="headerlink" href="#id12" title="Permalink to this image">¶</a></p>
|
|
|
</div>
|
|
|
<p>Taken together, this design gives <cite>SeisComP</cite> operators much flexibility.
|
|
|
Since messages can be exchanged between different computers, and
|
|
|
waveform data can be obtained from many sources, the different modules
|
|
|
do not all have to be on a single computer.
|
|
|
Multiple operators can connect to a single <cite>SeisComP</cite> installation from their own computers.</p>
|
|
|
</div>
|
|
|
<div class="section" id="station-metadata">
|
|
|
<h2>Station metadata<a class="headerlink" href="#station-metadata" title="Permalink to this headline">¶</a></h2>
|
|
|
<p>By <a class="reference internal" href="glossary.html#term-inventory"><span class="xref std std-term">inventory</span></a> we mean all information about seismic streams and stations
|
|
|
that is needed for processing the raw data obtained from sensors.
|
|
|
They are therefore also referred to as <em>station metadata</em>.
|
|
|
Read the <a class="reference internal" href="concepts/inventory.html#concepts-inventory"><span class="std std-ref">concepts section on inventory</span></a> for more details
|
|
|
on formats and configuration in <cite>SeisComP</cite>.</p>
|
|
|
<p>Inventories include</p>
|
|
|
<ul class="simple">
|
|
|
<li><p>Names and time periods of networks, stations, locations and streams (epochs)</p></li>
|
|
|
<li><p>Sample rates</p></li>
|
|
|
<li><p>Instrument responses (sensor and data logger)</p></li>
|
|
|
<li><p>Station and sensor coordinates</p></li>
|
|
|
</ul>
|
|
|
<p>and other essential information.
|
|
|
Today there are some common formats to store metadata:</p>
|
|
|
<ul class="simple">
|
|
|
<li><p>FDSN StationXML</p></li>
|
|
|
<li><p><cite>SeisComP</cite> inventory</p></li>
|
|
|
<li><p>Dataless SEED - the old <em>de facto</em> standard</p></li>
|
|
|
<li><p>ArcLink XML.</p></li>
|
|
|
</ul>
|
|
|
<p>Dataless SEED can be imported to, and exported from, <cite>SeisComP</cite> if needed.</p>
|
|
|
<p>You can get inventory information from various public sources including
|
|
|
<span id="id4"><em>EIDA</em> [<a class="reference internal" href="references.html#id94" title="EIDA. European Integrated Data Archive, Orfeus. URL: https://www.orfeus-eu.org/data/eida/.">4</a>]</span> or <span id="id5"><em>IRIS</em> [<a class="reference internal" href="references.html#id129" title="IRIS. Incorporated Research Institutions for Seismology. URL: https://www.iris.edu.">13</a>]</span> and many more. <span id="id6"><em>SMP</em> [<a class="reference internal" href="references.html#id254" title="SMP. Station Management Portal by gempa GmbH. URL: https://smp.gempa.de/.">21</a>]</span> allows you to
|
|
|
create and share meta data from your own
|
|
|
station network and to export an inventory in <a class="reference internal" href="glossary.html#term-scml"><span class="xref std std-term">SCML</span></a> format.</p>
|
|
|
<p>Inventories for all considered recording stations need to be imported
|
|
|
into <cite>SeisComP</cite>. and loaded into its database, before data can be processed.
|
|
|
There are various tools to do this.
|
|
|
The tools are described in the inventory section of this documentation.</p>
|
|
|
<div class="admonition note">
|
|
|
<p class="admonition-title">Note</p>
|
|
|
<p>In order to process data streams, the inventory must provide complete response information
|
|
|
for all the streams AND must match the <a class="reference internal" href="glossary.html#term-binding"><span class="xref std std-term">bindings</span></a> configuration.</p>
|
|
|
</div>
|
|
|
</div>
|
|
|
<div class="section" id="configuration">
|
|
|
<h2>Configuration<a class="headerlink" href="#configuration" title="Permalink to this headline">¶</a></h2>
|
|
|
<p>The basics of configuring a <cite>SeisComP</cite> system are described in the
|
|
|
<a class="reference internal" href="concepts/configuration.html#concepts-configuration"><span class="std std-ref">concepts section</span></a>. The <a class="reference internal" href="tutorials.html#tutorials"><span class="std std-ref">Tutorials</span></a> of this
|
|
|
documentation provide step-by-step recipes. The modules documentation explains
|
|
|
the modules functioning, their configuration and command-line parameters and
|
|
|
give additional examples and links to related topics.</p>
|
|
|
</div>
|
|
|
<div class="section" id="what-next">
|
|
|
<h2>What next?<a class="headerlink" href="#what-next" title="Permalink to this headline">¶</a></h2>
|
|
|
<p>The following <a class="reference internal" href="installation.html#installation"><span class="std std-ref">SeisComP Installation</span></a> section of this manual will help you install <cite>SeisComP</cite>.
|
|
|
You will then need to obtain some inventory and a source of waveform data.
|
|
|
Configure bindings, enable the processing modules, and restart <cite>SeisComP</cite>.
|
|
|
If all has gone well, you should see some stations as colorful triangles in
|
|
|
<a class="reference internal" href="../apps/scmv.html#scmv"><span class="std std-ref">scmv</span></a>,
|
|
|
and their traces in
|
|
|
<a class="reference internal" href="../apps/scrttv.html#scrttv"><span class="std std-ref">scrttv</span></a>.</p>
|
|
|
<p>Eventually, your new <cite>SeisComP</cite> system will pick and create origins,
|
|
|
should a locatable <a class="reference internal" href="glossary.html#term-event"><span class="xref std std-term">seismic event</span></a> take place while it
|
|
|
is running.</p>
|
|
|
</div>
|
|
|
<div class="section" id="where-to-go-for-more-help">
|
|
|
<h2>Where to Go for More Help<a class="headerlink" href="#where-to-go-for-more-help" title="Permalink to this headline">¶</a></h2>
|
|
|
<p>The <a class="reference internal" href="tutorials/help.html#tutorials-help"><span class="std std-ref">tutorial on help</span></a> provides comprehensive list of options
|
|
|
to get help on <cite>SeisComP</cite>.
|
|
|
Most <cite>SeisComP</cite> modules have built-in help messages and descriptive HTML
|
|
|
documentation. Read the <a class="reference internal" href="tutorials/help.html#tutorials-help"><span class="std std-ref">tutorial on help</span></a> for a neat
|
|
|
introduction.</p>
|
|
|
<p>There are other sources of information beyond this documentation. The
|
|
|
<span id="id7"><em>SeisComP forum</em> [<a class="reference internal" href="references.html#id242" title="SeisComP forum. GFZ. URL: https://forum.seiscomp.de/.">23</a>]</span> has many useful contributions from the community.
|
|
|
You are encouraged to register and post your own questions and comments there.</p>
|
|
|
<p>Professional support including installation, training courses, maintenance,
|
|
|
module development and modification is provided world-wide by
|
|
|
<a class="reference external" href="https://www.gempa.de/">gempa GmbH</a> <span id="id8">[<a class="reference internal" href="references.html#id113" title="gempa GmbH. The SeisComP development and maintenance company. URL: https://www.gempa.de/.">26</a>]</span>, a
|
|
|
software company out-sourced from GFZ and founded by the main <cite>SeisComP</cite>
|
|
|
developers.</p>
|
|
|
<p>Enjoy <cite>SeisComP</cite>!</p>
|
|
|
</div>
|
|
|
</div>
|
|
|
|
|
|
|
|
|
<div id="anchors-bottom"></div>
|
|
|
</div>
|
|
|
|
|
|
<div class="sidebar" role="navigation" aria-label="main navigation">
|
|
|
<div id="anchors-top"></div>
|
|
|
<div id="anchors" class="content">
|
|
|
<div id="searchbox" style="display: none" role="search">
|
|
|
<h3 id="searchlabel">Quick search</h3>
|
|
|
<div class="searchformwrapper">
|
|
|
<form class="search" action="../search.html" method="get">
|
|
|
<input type="text" name="q" aria-labelledby="searchlabel" />
|
|
|
<input type="submit" value="Go" />
|
|
|
</form>
|
|
|
</div>
|
|
|
</div>
|
|
|
<script>$('#searchbox').show(0);</script>
|
|
|
<h3><a href="../index.html">Table of Contents</a></h3>
|
|
|
<ul>
|
|
|
<li><a class="reference internal" href="#">Overview</a><ul>
|
|
|
<li><a class="reference internal" href="#modular-structure">Modular structure</a><ul>
|
|
|
<li><a class="reference internal" href="#data-acquisition-modules">Data acquisition modules</a></li>
|
|
|
<li><a class="reference internal" href="#automatic-processing-modules">Automatic processing modules</a></li>
|
|
|
<li><a class="reference internal" href="#interactive-modules">Interactive modules</a></li>
|
|
|
<li><a class="reference internal" href="#inventory-modules">Inventory modules</a></li>
|
|
|
<li><a class="reference internal" href="#utility-modules">Utility modules</a></li>
|
|
|
</ul>
|
|
|
</li>
|
|
|
<li><a class="reference internal" href="#communication-and-database-access">Communication and database access</a></li>
|
|
|
<li><a class="reference internal" href="#waveform-data">Waveform data</a></li>
|
|
|
<li><a class="reference internal" href="#access-to-waveform-data">Access to Waveform Data</a></li>
|
|
|
<li><a class="reference internal" href="#station-metadata">Station metadata</a></li>
|
|
|
<li><a class="reference internal" href="#configuration">Configuration</a></li>
|
|
|
<li><a class="reference internal" href="#what-next">What next?</a></li>
|
|
|
<li><a class="reference internal" href="#where-to-go-for-more-help">Where to Go for More Help</a></li>
|
|
|
</ul>
|
|
|
</li>
|
|
|
</ul>
|
|
|
|
|
|
<h4>Previous topic</h4>
|
|
|
<p class="topless"><a href="introduction.html"
|
|
|
title="previous chapter">Introduction and Scope</a></p>
|
|
|
<h4>Next topic</h4>
|
|
|
<p class="topless"><a href="history.html"
|
|
|
title="next chapter">Historical Information</a></p>
|
|
|
<div role="note" aria-label="source link">
|
|
|
<h3>This Page</h3>
|
|
|
<ul class="this-page-menu">
|
|
|
<li><a href="../_sources/base/overview.rst.txt"
|
|
|
rel="nofollow">Show Source</a></li>
|
|
|
</ul>
|
|
|
</div>
|
|
|
</div>
|
|
|
</div>
|
|
|
</div>
|
|
|
</div>
|
|
|
<div class="footer">
|
|
|
<div class="container">
|
|
|
<div class="horizontal layout content">
|
|
|
<a class="fade-in" href="https://www.gempa.de" target="_blank">
|
|
|
<img class="brand" src="../_static/brands/gempa.svg"/>
|
|
|
</a>
|
|
|
<div class="stretched align-center fitted content">
|
|
|
<div>
|
|
|
Version <b>5.3.0</b> Release
|
|
|
</div>
|
|
|
<div class="copyright">
|
|
|
Copyright © gempa GmbH, GFZ Potsdam.
|
|
|
</div>
|
|
|
</div>
|
|
|
<a class="fade-in" href="https://www.gfz-potsdam.de" target="_blank">
|
|
|
<img class="brand" src="../_static/brands/gfz.svg"/>
|
|
|
</a>
|
|
|
</div>
|
|
|
</div>
|
|
|
</div>
|
|
|
</body>
|
|
|
</html> |