[installation] Change to nightly

This commit is contained in:
2025-10-30 12:04:59 +01:00
parent 2ff097f9d1
commit a31bc45cce
1441 changed files with 60368 additions and 56360 deletions

View File

@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Add a new station &#8212; SeisComP Release documentation</title>
<title>Add a new station &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
@ -12,21 +12,21 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
<link rel="search" title="Search" href="../../search.html" />
<link rel="next" title="Get real-time data from a remote Seedlink server (single station)" href="waveforms.html" />
<link rel="prev" title="Upgrading SeisComP" href="upgrading.html" />
<link rel="prev" title="Updating/Upgrading SeisComP" href="upgrading.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">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@ -49,7 +49,7 @@
</a>
</li>
<li class="right">
<a href="upgrading.html" title="Upgrading SeisComP"
<a href="upgrading.html" title="Updating/Upgrading SeisComP"
accesskey="P">
previous
</a>
@ -83,7 +83,7 @@ Depending on your needs, you will use parts of other tutorials to do this.</p>
<ul class="simple">
<li><p><a class="reference internal" href="waveforms.html#tutorials-waveforms"><span class="std std-ref">Get real-time data from a remote Seedlink server (single station)</span></a></p></li>
<li><p><a class="reference internal" href="processing.html#tutorials-processing"><span class="std std-ref">Configure real-time processing</span></a></p></li>
<li><p><a class="reference internal" href="archiving.html#tutorials-archiving"><span class="std std-ref">Set up local waveform archiving</span></a></p></li>
<li><p><a class="reference internal" href="archiving.html#tutorials-archiving"><span class="std std-ref">Maintain waveform archives</span></a></p></li>
</ul>
<p>Afterwards/Results/Outcomes:</p>
<ul class="simple">
@ -121,16 +121,16 @@ How to obtain this will vary.
You can fetch inventory from:</p>
<ul class="simple">
<li><p>Other SeisComP systems. Use <a class="reference internal" href="../../apps/scxmldump.html#scxmldump"><span class="std std-ref">scxmldump</span></a> to fetch inventories.</p></li>
<li><p>EIDA nodes <span id="id1">[<a class="reference internal" href="../references.html#id103" title="EIDA. European Integrated Data Archive, Orfeus. URL: https://www.orfeus-eu.org/data/eida/.">4</a>]</span>. Use web interfaces such as web browsers or <cite>wget</cite>
<li><p>EIDA nodes <span id="id1">[<a class="reference internal" href="../references.html#id128" title="EIDA. European Integrated Data Archive, Orfeus. URL: https://www.orfeus-eu.org/data/eida/.">4</a>]</span>. Use web interfaces such as web browsers or <cite>wget</cite>
to fetch an inventory.</p></li>
<li><p>Data centers providing <span id="id2"><em>FDSNWS</em> [<a class="reference internal" href="../references.html#id110" title="FDSNWS. International Federation of Digital Seismograph Networks. URL: http://www.fdsn.org/webservices/.">8</a>]</span>. Use web interfaces such as web browsers
<li><p>Data centers providing <span id="id2"><em>FDSNWS</em> [<a class="reference internal" href="../references.html#id135" title="FDSNWS. International Federation of Digital Seismograph Networks. URL: http://www.fdsn.org/webservices/.">8</a>]</span>. Use web interfaces such as web browsers
or <cite>wget</cite> to fetch an inventory.</p></li>
<li><p>Your own or shared user repositories on <span id="id3"><em>SMP</em> [<a class="reference internal" href="../references.html#id268" title="SMP. Station Management Portal by gempa GmbH. URL: https://smp.gempa.de/.">22</a>]</span>.</p></li>
<li><p>Your own or shared user repositories on <span id="id3"><em>SMP</em> [<a class="reference internal" href="../references.html#id301" title="SMP. Station Management Portal by gempa GmbH. URL: https://smp.gempa.de/.">24</a>]</span>.</p></li>
</ul>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>Create and share inventories</p>
<p>gempas <span id="id4"><em>SMP</em> [<a class="reference internal" href="../references.html#id268" title="SMP. Station Management Portal by gempa GmbH. URL: https://smp.gempa.de/.">22</a>]</span> is a tool for creating inventory from scratch and
<p>gempas <span id="id4"><em>SMP</em> [<a class="reference internal" href="../references.html#id301" title="SMP. Station Management Portal by gempa GmbH. URL: https://smp.gempa.de/.">24</a>]</span> is a tool for creating inventory from scratch and
community sharing. Create inventories for new or old networks and stations
from permanent or temporary deployments.
SMP provides inventories in <a class="reference internal" href="../glossary.html#term-SCML"><span class="xref std std-term">SCML</span></a> format in multiple versions
@ -214,7 +214,7 @@ Follow the <a class="reference internal" href="processing.html#tutorials-process
<section id="configuring-for-archiving">
<h2>Configuring for archiving<a class="headerlink" href="#configuring-for-archiving" title="Permalink to this heading"></a></h2>
<p>If you want to archive waveforms, consider how long they should be retained.
See <a class="reference internal" href="archiving.html#tutorials-archiving"><span class="std std-ref">Set up local waveform archiving</span></a> for how to do this.</p>
See <a class="reference internal" href="archiving.html#tutorials-archiving"><span class="std std-ref">Maintain waveform archives</span></a> for how to do this.</p>
</section>
</section>
@ -253,7 +253,7 @@ See <a class="reference internal" href="archiving.html#tutorials-archiving"><spa
<div>
<h4>Previous topic</h4>
<p class="topless"><a href="upgrading.html"
title="previous chapter">Upgrading SeisComP</a></p>
title="previous chapter">Updating/Upgrading SeisComP</a></p>
</div>
<div>
<h4>Next topic</h4>
@ -279,7 +279,7 @@ See <a class="reference internal" href="archiving.html#tutorials-archiving"><spa
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.

View File

@ -0,0 +1,639 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Amplitudes/Magnitudes: Regionalization, Aliases, Mw &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
<link rel="stylesheet" type="text/css" href="../../_static/seiscomp.css?v=c6da7ce6" />
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
<link rel="search" title="Search" href="../../search.html" />
<link rel="next" title="Play back archived waveforms" href="waveformplayback.html" />
<link rel="prev" title="Enable local FDSNWS server" href="servefdsnws.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 Development</span -->
<span class="version">7.0.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="waveformplayback.html" title="Play back archived waveforms"
accesskey="N">
next
</a>
</li>
<li class="right">
<a href="servefdsnws.html" title="Enable local FDSNWS server"
accesskey="P">
previous
</a>
</li>
<li class="nav-item nav-item-0">
<a href="../../index.html">Home</a>
</li>
<li class="nav-item nav-item-1">
<a href="../tutorials.html" accesskey="U">Tutorials</a>
</li>
</ul>
</div>
</div>
</div>
</div>
<div class="container">
<div class="fitted content" id="anchors-container">
<div class="body" role="main">
<section id="amplitudes-magnitudes-regionalization-aliases-mw">
<span id="tutorials-magnitude-region-aliases"></span><h1>Amplitudes/Magnitudes: Regionalization, Aliases, Mw<a class="headerlink" href="#amplitudes-magnitudes-regionalization-aliases-mw" title="Permalink to this heading"></a></h1>
<p>You will …</p>
<ul class="simple">
<li><p>Regionalize magnitudes.</p></li>
<li><p>Create new amplitude and magnitude types as aliases from other amplitudes and
magnitudes.</p></li>
<li><p>Map magnitudes to the moment magnitude, Mw.</p></li>
</ul>
<dl class="field-list simple">
<dt class="field-odd">Pre-requisites for this tutorial<span class="colon">:</span></dt>
<dd class="field-odd"><ul class="simple">
<li><p>Read the <a class="reference internal" href="../concepts/magnitudes.html#concepts-magnitudes"><span class="std std-ref">concepts section on magnitudes</span></a>.</p></li>
<li><p>Real-time data for the station must be available locally.
See <a class="reference internal" href="waveforms.html#tutorials-waveforms"><span class="std std-ref">Get real-time data from a remote Seedlink server (single station)</span></a> or <a class="reference internal" href="geofon_waveforms.html#tutorials-geofon-waveforms"><span class="std std-ref">Add real-time stations from GEOFON</span></a>.</p></li>
<li><p>Inventory must be loaded locally.</p></li>
</ul>
</dd>
<dt class="field-even">Afterwards/Results/Outcomes<span class="colon">:</span></dt>
<dd class="field-even"><ul class="simple">
<li><p>Regionalized amplitudes and magnitudes</p></li>
<li><p>New amplitude and magnitude types as aliases</p></li>
<li><p>Moment magnitudes</p></li>
</ul>
</dd>
<dt class="field-odd">Time range estimate<span class="colon">:</span></dt>
<dd class="field-odd"><ul class="simple">
<li><p>60 minutes</p></li>
</ul>
</dd>
</dl>
<hr class="docutils" />
<section id="regionalization">
<h2>Regionalization<a class="headerlink" href="#regionalization" title="Permalink to this heading"></a></h2>
<p>By regionalization, amplitudes and magnitudes can be computed depending on the
region of the source or source-receiver pairs.
Regions are defined by polygons in BNA or GeoJSON files which must be known to
<cite>SeisComP</cite>.</p>
<section id="amplitudes">
<span id="tutorials-amplitudes-region"></span><h3>Amplitudes<a class="headerlink" href="#amplitudes" title="Permalink to this heading"></a></h3>
<p>Measuring amplitudes only for sources or pairs of sources and stations in
specific regions is possible by regionalization. The region polygons are defined
by <a class="reference internal" href="#tutorials-magnitude-region"><span class="std std-ref">magnitude regionalization</span></a>. In
order to use the feature, regionalized amplitudes and magnitudes must have the
same type (name) and regionalization must be activated per amplitude type in
amplitude-type profiles of global bindings.</p>
</section>
<section id="magnitudes">
<span id="tutorials-magnitude-region"></span><h3>Magnitudes<a class="headerlink" href="#magnitudes" title="Permalink to this heading"></a></h3>
<p>With regionalization magnitudes can be computed with region-dependent parameters.
If magnitude regionalization is configured but a source or source-station pairs
are not considered, no magnitude of the corresponding type is computed.</p>
<section id="setup">
<h4>Setup<a class="headerlink" href="#setup" title="Permalink to this heading"></a></h4>
<p>The procedure to set up magnitude regionalization is:</p>
<ol class="arabic">
<li><p>Create one file which contains the polygons surrounding the regions within
which magnitude parameters shall apply. The polygon files are provided in
<a class="reference internal" href="../../apps/global_gui.html#sec-gui-layers-vector-format-bna"><span class="std std-ref">BNA</span></a> or
<a class="reference internal" href="../../apps/global_gui.html#sec-gui-layers-vector-format-geojson"><span class="std std-ref">GeoJSON format</span></a> and located as
set out in the <a class="reference internal" href="../../apps/global_gui.html#sec-gui-layers"><span class="std std-ref">documentation of map layers</span></a>. The file
can be created from any <cite>SeisComP</cite> GUI application providing maps, e.g.,
<a class="reference internal" href="../../apps/scmv.html#scmv"><span class="std std-ref">scmv</span></a>.</p></li>
<li><p>For the desired magnitude type create a magnitude-type profile in global
module configuration. The name of the profile matches the name of the
magnitude, e.g., <em>MLc</em> for the <a class="reference internal" href="../../apps/global_mlc.html#global-mlc"><span class="std std-ref">MLc magnitude</span></a>.</p></li>
<li><p>Configure the <code class="xref std std-confval docutils literal notranslate"><span class="pre">magnitudes.MLc.regionFile</span></code> parameter with the full
path and name of the polygon file created above.</p></li>
<li><p>Within the magnitude-type profile create one or more magnitude-region
profile(s) for defining the regionalized parameters applied to the region(s).
The name of a profile corresponds to the name of the polygon contained in the
polygon file to which the parameters shall apply. Use <em>world</em> for all regions
not covered by any polygon.</p></li>
<li><p>Configure the regionalized magnitude parameters of the magnitude-region
profile. Activate the <em>enable</em> parameter if you wish to apply this profile.</p></li>
<li><p>Restart the data processing:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>restart
</pre></div>
</div>
<p>or execute a GUI module.</p>
</li>
</ol>
<div class="admonition important">
<p class="admonition-title">Important</p>
<ul class="simple">
<li><p>Parameters which can be configured along with regionalization assume
defaults from global binding parameters but override global bindings
parameters when configured.</p></li>
<li><p>Once regionalization is active, magnitudes for events outside the
defined region(s) will not be computed. For considering such events add
another magnitude-region profile with the name “<em>world</em>”.
Magnitudes for events outside any other magnitude-region profile will then
be computed according to this profile.</p></li>
</ul>
</div>
</section>
<section id="setup-station-corrections">
<h4>Setup: station corrections<a class="headerlink" href="#setup-station-corrections" title="Permalink to this heading"></a></h4>
<p><a class="reference internal" href="../concepts/magnitudes.html#concepts-magnitudes-correction"><span class="std std-ref">Magnitude station corrections</span></a> can also
be applied in case of reBy regionalization, magnitudes can be computed with region-dependent properties.
Regions are defined by polygons in BNA or GeoJSON files which must be known to
<cite>SeisComP</cite>.gionalization. Simply add the names of the
magnitude-region profile along with the correction parameter to the original
parameter in global module configuration, <code class="file docutils literal notranslate"><span class="pre">global.cfg</span></code>, for the respective
magnitude type and station. Use comma separation for multiple regions and colon
for separating the region name from the value.</p>
<p>Example for correcting MLv computed at station GE.UGM:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">module.trunk.GE.UGM.magnitudes.MLv.offset</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">0.1, europe:0.2, asia:-0.1</span>
</pre></div>
</div>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>The configuration of parameters starting with <em>module.trunk.</em> is not
supported by <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>. All corresponding configurations must be done
by directly editing the configuration file, e.g.,
<code class="file docutils literal notranslate"><span class="pre">seiscomp/etc/global.cfg</span></code>.</p>
</div>
</section>
<section id="application">
<h4>Application<a class="headerlink" href="#application" title="Permalink to this heading"></a></h4>
<p>When configured, regionalization is automatically applied when computing
magnitudes in <a class="reference internal" href="../../apps/scmag.html#scmag"><span class="std std-ref">scmag</span></a> or <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a>.</p>
</section>
<section id="testing">
<span id="tutorials-mags-regionalize-testing"></span><h4>Testing<a class="headerlink" href="#testing" title="Permalink to this heading"></a></h4>
<ul>
<li><p>Regionalization:</p>
<ol class="arabic">
<li><p>Start <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a> with the option <code class="xref std std-option docutils literal notranslate"><span class="pre">--debug</span></code> and load an event of
interest</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>scolv<span class="w"> </span>--debug
</pre></div>
</div>
</li>
<li><p>Relocate the event for generating a new origin.</p></li>
<li><p>Compute magnitudes selecting the magnitude of interest.</p></li>
<li><p>Inspect the computed magnitudes in the
<a class="reference internal" href="../../apps/scolv.html#scolv-sec-magnitude-tab"><span class="std std-ref">Magnitude tab of scolv</span></a> or read the
debug output listing the considered magnitudes and stations along with
the regionalized parameters.</p></li>
</ol>
</li>
</ul>
</section>
</section>
</section>
<section id="amplitude-aliases">
<span id="tutorials-amplitude-aliases"></span><h2>Amplitude Aliases<a class="headerlink" href="#amplitude-aliases" title="Permalink to this heading"></a></h2>
<p>Amplitude aliases are new amplitude types based original ones. Such aliases
allow their specific configuration and computation. They can be created and
independent of magnitudes by <a class="reference internal" href="../../apps/scautopick.html#scautopick"><span class="std std-ref">scautopick</span></a> and <a class="reference internal" href="../../apps/scamp.html#scamp"><span class="std std-ref">scamp</span></a> and used for
<a class="reference internal" href="#tutorials-magnitude-aliases"><span class="std std-ref">magnitude aliases</span></a>.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>Amplitude aliases make use of the same parameter structure as the initial
amplitude but the parameters must be configured independently.</p>
</div>
<section id="id1">
<h3>Setup<a class="headerlink" href="#id1" title="Permalink to this heading"></a></h3>
<ol class="arabic">
<li><p>Global module configuration: Define the alias name in <a class="reference internal" href="../../apps/global.html#confval-amplitudes.aliases"><code class="xref std std-confval docutils literal notranslate"><span class="pre">amplitudes.aliases</span></code></a>.</p>
<p>Format and example:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">amplitudes.aliases</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">alias:original amplitude type</span>
<span class="na">amplitudes.aliases</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">MLc01:MLc</span>
</pre></div>
</div>
</li>
<li><p>Configure the amplitude bindings parameters. The parameters are identical to
those of the original amplitude type except that the name of the original
magnitude must be replaced by the name of the alias. You may thus first
configure the original amplitude and then replace the name.</p>
<p><strong>Example binding configuration</strong> for MLc01 derived from MLc:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">amplitudes.MLc01.preFilter</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">BW(3,0.5,12)</span>
<span class="na">amplitudes.MLc01.applyWoodAnderson</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">true</span>
<span class="na">...</span>
<span class="na">amplitudes.MLc01.enable</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">true</span>
<span class="na">amplitudes.MLc01.enableResponses</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">false</span>
<span class="na">amplitudes.MLc01.minSNR</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">1.5</span>
<span class="na">amplitudes.MLc01.signalBegin</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">-1</span>
<span class="na">amplitudes.MLc01.signalEnd</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">min(tt(S) + 10, 150)</span>
<span class="na">...</span>
<span class="na">amplitudes.MLc01.maxDepth</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">50</span>
</pre></div>
</div>
<p>Repeat the action for all applicable binding profiles.</p>
<p>Instead of adjusting the bindings profiles you may add the configuration to
global or any other module configuration by prepending
<em>module.trunk.[module]</em> where <em>[module]</em> is to be replaced by the name of the
module including <em>global</em>.</p>
<p><strong>Example global module configuration</strong> in <code class="file docutils literal notranslate"><span class="pre">global.cfg</span></code>:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">module.trunk.global.amplitudes.MLc01.preFilter</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">BW(3,0.5,12)</span>
<span class="na">module.trunk.global.amplitudes.MLc01.applyWoodAnderson</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">true</span>
<span class="na">...</span>
<span class="na">module.trunk.global.amplitudes.MLc01.enable</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">true</span>
<span class="na">module.trunk.global.amplitudes.MLc01.enableResponses</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">false</span>
<span class="na">module.trunk.global.amplitudes.MLc01.minSNR</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">1.5</span>
<span class="na">module.trunk.global.amplitudes.MLc01.signalBegin</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">-1</span>
<span class="na">module.trunk.global.amplitudes.MLc01.signalEnd</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">min(tt(S) + 10, 150)</span>
<span class="na">...</span>
<span class="na">module.trunk.global.amplitudes.MLc01.maxDepth</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">50</span>
</pre></div>
</div>
<p>Configuration of bindings profiles has the advantage that the parameters are
available on any client connected to the messaging including external
SeisComP systems. Writing to global module configuration may be more simple
than maintaining multiple bindings profiles but the configuration is not
available to clients in external computers/SeisComP systems.</p>
</li>
</ol>
</section>
<section id="id2">
<h3>Application<a class="headerlink" href="#id2" title="Permalink to this heading"></a></h3>
<ul class="simple">
<li><p>For automatic measurement by <a class="reference internal" href="../../apps/scautopick.html#scautopick"><span class="std std-ref">scautopick</span></a> or <a class="reference internal" href="../../apps/scamp.html#scamp"><span class="std std-ref">scamp</span></a> add the alias
name to the list of measured amplitudes in the corresponding module
configuration.</p></li>
<li><p>For using the measured amplitude value with magnitudes, create a
<a class="reference internal" href="#tutorials-magnitude-aliases"><span class="std std-ref">magnitude alias</span></a>.</p></li>
</ul>
</section>
<section id="id3">
<h3>Testing<a class="headerlink" href="#id3" title="Permalink to this heading"></a></h3>
<p>Compute amplitudes with <a class="reference internal" href="../../apps/scamp.html#scamp"><span class="std std-ref">scamp</span></a> or by magnitude aliases in <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a> and
read the debug log output as when testing
<a class="reference internal" href="#tutorials-mags-aliases-testing"><span class="std std-ref">magnitude aliases</span></a>.</p>
</section>
</section>
<section id="magnitude-aliases">
<span id="tutorials-magnitude-aliases"></span><h2>Magnitude Aliases<a class="headerlink" href="#magnitude-aliases" title="Permalink to this heading"></a></h2>
<p>Magnitude aliases are new magnitude types based original ones. Such aliases
allow their specific configuration and computation. They can be created from
magnitude and amplitude types native in <cite>SeisComP</cite> or from
<a class="reference internal" href="#tutorials-amplitude-aliases"><span class="std std-ref">amplitude aliases</span></a> which must be defined
first. Unless specified explicitly, the amplitude type
is the base amplitude of the original magnitude.
Other amplitude types or amplitude aliases must be defined first and given
explicitly.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>Magnitude aliases make use of the same parameter structure as the initial
magnitude but the parameters must be configured independently.</p>
</div>
<section id="id4">
<h3>Setup<a class="headerlink" href="#id4" title="Permalink to this heading"></a></h3>
<ol class="arabic">
<li><p>Create a magnitude alias in <code class="file docutils literal notranslate"><span class="pre">global.cfg</span></code> by configuring
<a class="reference internal" href="../../apps/global.html#confval-magnitudes.aliases"><code class="xref std std-confval docutils literal notranslate"><span class="pre">magnitudes.aliases</span></code></a>.</p>
<p>Format:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">magnitudes.aliases</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">alias:original magnitude type[:amplitude type]</span>
</pre></div>
</div>
<p>The amplitude type is optional and can be omitted when equal to the type of
the original magnitude.</p>
<p>Example for an alias magnitude, MLc1, derived from the MLc magnitude and
amplitude. Since initial amplitudes and magnitudes are identical, the
amplitude type can be dropped:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">magnitudes.aliases</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">MLc01:MLc:MLc</span>
<span class="na">magnitudes.aliases</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">MLc01:MLc</span>
</pre></div>
</div>
<p>Example for an alias magnitude, MLc1, derived from the MLc magnitude and
amplitude. Since initial amplitudes and magnitudes are different, the
amplitude type must be given and
<a class="reference internal" href="#tutorials-amplitude-aliases"><span class="std std-ref">configured independently</span></a></p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">magnitudes.aliases</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">MLc01:MLc:MLc01</span>
</pre></div>
</div>
</li>
<li><p>Configure the alias amplitude if any is used.</p></li>
<li><p>Configure the alias magnitude in <strong>either</strong> way:</p>
<ul>
<li><p><strong>Adjust binding profiles:</strong> Configure global bindings parameters by
directly adjusting binding profiles.</p>
<p>Parameters of original magnitudes which are supported by magnitude-type
profiles can be set for the magnitude alias in <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> by creating
a new magnitude-type profile having the name of the magnitude alias.</p>
<p>All other parameters must be written to the binding parameter files using
an external text editor:</p>
<ol class="arabic">
<li><p>Read the relevant parameter names of the original magnitude from global
binding, e.g., in <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> or the binding parameter file.
Parameter names must include the full hierarchy including all sections.
Example for parameter name of original magnitude:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">magnitudes.MLc.parametric.c1</span>
</pre></div>
</div>
</li>
<li><p>Edit all relevant binding parameter files, e.g.,
<code class="file docutils literal notranslate"><span class="pre">seiscomp/etc/key/global/profile_HHZ</span></code> in a text editor and set the
values for the alias magnitude. For default values, the parameters do not
need to be set.</p>
<p>Example of resulting parameter for alias magnitude MLc01:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">magnitudes.MLc01.parametric.c1</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">0.6</span>
</pre></div>
</div>
</li>
</ol>
</li>
<li><p><strong>Regionalization:</strong> Set up by <a class="reference internal" href="#tutorials-magnitude-region"><span class="std std-ref">regionalization</span></a>.</p>
<ul class="simple">
<li><p>Consider the tutorial above on
<a class="reference internal" href="#tutorials-magnitude-region"><span class="std std-ref">magnitude regionalization</span></a>.</p></li>
<li><p>For the name of new magnitude-type profiles now use the new alias name.</p></li>
</ul>
</li>
</ul>
<div class="admonition hint">
<p class="admonition-title">Hint</p>
<p>When initially configuring amplitude and magnitude aliases, <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>
does not know which original amplitude and magnitude types are considered and
the corresponding parameters may not be accessible.
The full list of parameters of the alias can, however, be derived from
original types:</p>
<ol class="arabic simple">
<li><p>Open scconfig and configure the original amplitude and magnitude
referenced by the alias.</p></li>
<li><p>Close scconfig.</p></li>
<li><p>Open the binding or module configuration file, e.g.,
<code class="file docutils literal notranslate"><span class="pre">seiscomp/etc/key/global/profile_HHZ</span></code> or <code class="file docutils literal notranslate"><span class="pre">global.cfg</span></code>.</p></li>
<li><p>Copy or rename the name of the referenced amplitude or magnitude in the
parameters to the name of the alias.</p></li>
<li><p>Open scconfig. The new parameters are now visible along with the
original one and can be adjusted. You may now remove all
irrelevant parameters of the original magnitude.</p></li>
</ol>
<p>This procedure applies to the adjustment of binding profiles and to
regionalization except that regionalization only supports magnitudes.</p>
</div>
<ul>
<li><p><strong>Write bindings parameters to global module configuration:</strong> Manually
adjust the module configuration file, e.g., <code class="file docutils literal notranslate"><span class="pre">global.cfg</span></code>. The
operation is not supported by <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>.</p>
<ol class="arabic">
<li><p>Read the relevant parameter names of the original magnitude from global
binding, e.g., in <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>. The names must include the full
hierarchy including all sections. Example:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">magnitudes.MLc01.parametric.c1</span>
</pre></div>
</div>
</li>
<li><p>Open the module configuration file, e.g.,
<code class="file docutils literal notranslate"><span class="pre">seiscomp/etc/global.cfg</span></code> in a text editor.</p></li>
<li><p>Prepend <em>module.trunk.global.</em> to the parameter name and add it along with
its value to the configuration file for all networks and stations.
Example:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">module.trunk.global.magnitudes.MLc01.parametric.c1</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">0.7</span>
</pre></div>
</div>
<p>For a given network or network and station replace <em>global</em> by the
<em>network</em> or the <em>network</em> and the <em>station</em> code. Example for network
CX and station PB01:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">module.trunk.CX.PB01.magnitudes.MLc01.parametric.c1</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">0.7</span>
<span class="na">module.trunk.CX.magnitudes.MLc01.parametric.c1</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">0.7</span>
</pre></div>
</div>
</li>
<li><p>Add the new magnitude name to the configuration of all relevant modules,
e.g., <a class="reference internal" href="../../apps/scamp.html#scamp"><span class="std std-ref">scamp</span></a>, <a class="reference internal" href="../../apps/scmag.html#scmag"><span class="std std-ref">scmag</span></a>, <a class="reference internal" href="../../apps/scevent.html#scevent"><span class="std std-ref">scevent</span></a>, <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a>.</p></li>
</ol>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>The parameters starting with <em>module.trunk.</em> are not available for
configuration in <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>.</p>
</div>
<div class="admonition warning">
<p class="admonition-title">Warning</p>
<p>Binding parameters configured in global module configuration should only
be considered exceptionally. These parameters will</p>
<ul class="simple">
<li><p>Override the corresponding parameters configured by regionalization
using the region <em>world</em>.</p></li>
<li><p>Not be written to the database and cannot be accessed by SeisComP
modules running on other computers.</p></li>
</ul>
</div>
</li>
</ul>
</li>
</ol>
</section>
<section id="id5">
<h3>Application<a class="headerlink" href="#id5" title="Permalink to this heading"></a></h3>
<ul class="simple">
<li><p>For automatic computation by <a class="reference internal" href="../../apps/scmag.html#scmag"><span class="std std-ref">scmag</span></a> add the alias name to the list of
measured magnitudes in the corresponding module configuration.</p></li>
<li><p>For interactive computation choose the magnitude alias name in <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a>
when computing magnitudes. The alias may be added to the default magnitudes in
the scolv module configuration.</p></li>
</ul>
</section>
<section id="tutorials-mags-aliases-testing">
<span id="id6"></span><h3>Testing<a class="headerlink" href="#tutorials-mags-aliases-testing" title="Permalink to this heading"></a></h3>
<ol class="arabic">
<li><p>Start <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a> with the option <code class="xref std std-option docutils literal notranslate"><span class="pre">--debug</span></code> and load an event of
interest</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>scolv<span class="w"> </span>--debug
</pre></div>
</div>
</li>
<li><p>Relocate the event for generating a new origin.</p></li>
<li><p>Compute magnitudes selecting the magnitude of interest including the new
alias.</p></li>
<li><p>Inspect the computed magnitudes in the
<a class="reference internal" href="../../apps/scolv.html#scolv-sec-magnitude-tab"><span class="std std-ref">Magnitude tab of scolv</span></a> or read the
debug output listing the considered magnitude names and aliases along with
the considered parameters and their values. Example where MLc1 is derived
from MLc with a modified maximum depth:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>...
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>GE.UGM:<span class="w"> </span>MLc1:<span class="w"> </span>effective<span class="w"> </span>correction<span class="w"> </span><span class="o">(</span>no<span class="w"> </span>locale<span class="o">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="m">1</span>.00:0.00
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>Parameters<span class="w"> </span><span class="k">for</span><span class="w"> </span>magnitude<span class="w"> </span>MLc1
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>+<span class="w"> </span>maximum<span class="w"> </span>depth:<span class="w"> </span><span class="m">50</span>.000<span class="w"> </span>km
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>+<span class="w"> </span>distance<span class="w"> </span>mode:<span class="w"> </span>hypocentral
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>+<span class="w"> </span>minimum<span class="w"> </span>distance:<span class="w"> </span>-1.000<span class="w"> </span>km
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>+<span class="w"> </span>maximum<span class="w"> </span>distance:<span class="w"> </span><span class="m">889</span>.561<span class="w"> </span>km
...
</pre></div>
</div>
</li>
</ol>
</section>
</section>
<section id="moment-magnitudes">
<span id="tutorials-mags-moment"></span><h2>Moment Magnitudes<a class="headerlink" href="#moment-magnitudes" title="Permalink to this heading"></a></h2>
<p>All magnitudes, Mx, can be mapped to a moment magnitude, Mw(Mx) by piecewise
linear interpolation.</p>
<div class="admonition warning">
<p class="admonition-title">Warning</p>
<p>Do not map <a class="reference internal" href="../glossary.html#term-magnitude-broadband-body-wave-mB"><span class="xref std std-term">mB</span></a>
or <a class="reference internal" href="../glossary.html#term-magnitude-broadband-P-wave-moment-Mwp"><span class="xref std std-term">Mwp</span></a> to Mw since
this is hardcoded already and done automatically by <a class="reference internal" href="../../apps/scmag.html#scmag"><span class="std std-ref">scmag</span></a>.</p>
</div>
<section id="id7">
<h3>Setup<a class="headerlink" href="#id7" title="Permalink to this heading"></a></h3>
<p>The configuration procedure is:</p>
<ol class="arabic">
<li><p>Set up a magnitude-type profile for the original magnitude type in global
module configuration. Use <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> for creating the profile.</p></li>
<li><p>Configure the parameter <em>MwMapping</em>, which will become available along with
the new profile, e.g., <code class="xref std std-confval docutils literal notranslate"><span class="pre">magnitudes.MLc.MwMapping</span></code>. Alternatively,
add the parameter to <code class="file docutils literal notranslate"><span class="pre">seiscomp/etc/global.cfg</span></code>. The parameter is
configured as a list of sample points of a piecewise linear function mapping
from the original magnitude, Mx, to Mw(Mx).
Example for Mw(MLc) based on MLc:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">magnitudes.MLc.MwMapping</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">MLc_0:Mw(MLc)_0,MLc_1:Mw(MLc)_1,...,MLc_N:Mw(MLc)_N</span>
</pre></div>
</div>
<p>Any magnitude value outside the configured range is ignored.</p>
</li>
</ol>
<p>The new moment magnitudes will be available along with the original magnitudes
and can be viewed in <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a> or <a class="reference internal" href="../../apps/scesv.html#scesv"><span class="std std-ref">scesv</span></a> and considered by <a class="reference internal" href="../../apps/scmag.html#scmag"><span class="std std-ref">scmag</span></a>
or <a class="reference internal" href="../../apps/scevent.html#scevent"><span class="std std-ref">scevent</span></a>.</p>
<p>In order to avoid that <a class="reference internal" href="../concepts/magnitudes.html#concepts-magnitudes-summary"><span class="std std-ref">summary magnitudes</span></a>
are computed from original magnitudes and mapped Mw together and biased to both,
the original magnitudes can be blocklisted in <a class="reference internal" href="../../apps/scmag.html#scmag"><span class="std std-ref">scmag</span></a>
(<a class="reference internal" href="../../apps/scmag.html#confval-summaryMagnitude.blacklist"><code class="xref std std-confval docutils literal notranslate"><span class="pre">summaryMagnitude.blacklist</span></code></a>).</p>
</section>
<section id="id8">
<h3>Application<a class="headerlink" href="#id8" title="Permalink to this heading"></a></h3>
<ul class="simple">
<li><p>Mapped Mw() magnitudes are automatically computed when configured.</p></li>
<li><p>For consideration in summary magnitudes configure and run <a class="reference internal" href="../../apps/scmag.html#scmag"><span class="std std-ref">scmag</span></a>.</p></li>
<li><p>For consideration in preferred magnitudes configure and run <a class="reference internal" href="../../apps/scevent.html#scevent"><span class="std std-ref">scevent</span></a> or
select in <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a>.</p></li>
<li><p>For interactive computation choose the original magnitude name in <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a>
when computing magnitudes.</p></li>
</ul>
</section>
</section>
</section>
<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" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
<input type="submit" value="Go" />
</form>
</div>
</div>
<script>document.getElementById('searchbox').style.display = "block"</script>
<div>
<h3><a href="../../index.html">Table of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Amplitudes/Magnitudes: Regionalization, Aliases, Mw</a><ul>
<li><a class="reference internal" href="#regionalization">Regionalization</a><ul>
<li><a class="reference internal" href="#amplitudes">Amplitudes</a></li>
<li><a class="reference internal" href="#magnitudes">Magnitudes</a><ul>
<li><a class="reference internal" href="#setup">Setup</a></li>
<li><a class="reference internal" href="#setup-station-corrections">Setup: station corrections</a></li>
<li><a class="reference internal" href="#application">Application</a></li>
<li><a class="reference internal" href="#testing">Testing</a></li>
</ul>
</li>
</ul>
</li>
<li><a class="reference internal" href="#amplitude-aliases">Amplitude Aliases</a><ul>
<li><a class="reference internal" href="#id1">Setup</a></li>
<li><a class="reference internal" href="#id2">Application</a></li>
<li><a class="reference internal" href="#id3">Testing</a></li>
</ul>
</li>
<li><a class="reference internal" href="#magnitude-aliases">Magnitude Aliases</a><ul>
<li><a class="reference internal" href="#id4">Setup</a></li>
<li><a class="reference internal" href="#id5">Application</a></li>
<li><a class="reference internal" href="#tutorials-mags-aliases-testing">Testing</a></li>
</ul>
</li>
<li><a class="reference internal" href="#moment-magnitudes">Moment Magnitudes</a><ul>
<li><a class="reference internal" href="#id7">Setup</a></li>
<li><a class="reference internal" href="#id8">Application</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
<div>
<h4>Previous topic</h4>
<p class="topless"><a href="servefdsnws.html"
title="previous chapter">Enable local FDSNWS server</a></p>
</div>
<div>
<h4>Next topic</h4>
<p class="topless"><a href="waveformplayback.html"
title="next chapter">Play back archived waveforms</a></p>
</div>
<div role="note" aria-label="source link">
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="../../_sources/base/tutorials/amplitudes-magnitudes.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>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; 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>

View File

@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Set up local waveform archiving &#8212; SeisComP Release documentation</title>
<title>Maintain waveform archives &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
@ -12,7 +12,7 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
@ -25,8 +25,8 @@
<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">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@ -69,12 +69,13 @@
<div class="fitted content" id="anchors-container">
<div class="body" role="main">
<section id="set-up-local-waveform-archiving">
<span id="tutorials-archiving"></span><h1>Set up local waveform archiving<a class="headerlink" href="#set-up-local-waveform-archiving" title="Permalink to this heading"></a></h1>
<section id="maintain-waveform-archives">
<span id="tutorials-archiving"></span><h1>Maintain waveform archives<a class="headerlink" href="#maintain-waveform-archives" title="Permalink to this heading"></a></h1>
<p>You will …</p>
<ul class="simple">
<li><p>Set up <a class="reference internal" href="../../apps/slarchive.html#slarchive"><span class="std std-ref">slarchive</span></a> with its necessary bindings</p></li>
<li><p>Set up <cite>purge_datafiles</cite> in crontab</p></li>
<li><p>Control the life-time of waveforms</p></li>
<li><p>Access waveforms</p></li>
</ul>
<p>Pre-requisites for this tutorial:</p>
<ul class="simple">
@ -88,11 +89,12 @@ somewhere else (see <a class="reference internal" href="waveforms.html#tutorials
<p>Afterwards/Results/Outcomes:</p>
<ul class="simple">
<li><p>Save real-time data in a local archive for later processing.</p></li>
<li><p>See <a class="reference internal" href="../glossary.html#term-miniSeed"><span class="xref std std-term">miniSEED</span></a> day files for GE stations in your local <a class="reference internal" href="../concepts/waveformarchives.html#concepts-waveformarchives"><span class="std std-ref">waveform archive</span></a>.</p></li>
<li><p>See <a class="reference internal" href="../glossary.html#term-miniSeed"><span class="xref std std-term">miniSEED</span></a> day files for GE stations in your local
<a class="reference internal" href="../concepts/waveformarchives.html#concepts-waveformarchives"><span class="std std-ref">waveform archive</span></a>.</p></li>
</ul>
<p>Time range estimate:</p>
<ul class="simple">
<li><p>5 minutes</p></li>
<li><p>20 minutes</p></li>
</ul>
<p>Related tutorial(s):</p>
<ul class="simple">
@ -100,19 +102,32 @@ somewhere else (see <a class="reference internal" href="waveforms.html#tutorials
<li><p>Tutorial on <a class="reference internal" href="waveformplayback.html#tutorials-waveformplayback"><span class="std std-ref">Play back archived waveforms</span></a></p></li>
</ul>
<hr class="docutils" />
<p><strong>Motivation</strong>:
Without activating archiving, your local Seedlink server
will only keep waveforms for a short time.
This makes it hard to review old events, for example.</p>
<p>In this example, well arrange for keeping waveforms for one week.
Before starting, youll need bindings for your stations;
see the tutorials <a class="reference internal" href="geofon_waveforms.html#tutorials-geofon-waveforms"><span class="std std-ref">Add real-time stations from GEOFON</span></a>
or <a class="reference internal" href="waveforms.html#tutorials-waveforms"><span class="std std-ref">Get real-time data from a remote Seedlink server (single station)</span></a>.</p>
<p>The <strong class="program">slarchive</strong> collects data and archives it
locally using a <a class="reference internal" href="../glossary.html#term-SDS"><span class="xref std std-term">SDS</span></a> file system structure of
nested subdirectories and systematically named files.</p>
<section id="motivation">
<h2>Motivation<a class="headerlink" href="#motivation" title="Permalink to this heading"></a></h2>
<p>Without activating waveform archiving, your local <a class="reference internal" href="../../apps/seedlink.html#seedlink"><span class="std std-ref">Seedlink server</span></a>
will only keep waveforms for a short period of time.
This makes it hard to review old events, for example.
<a class="reference internal" href="../../apps/slarchive.html#slarchive"><span class="std std-ref">slarchive</span></a> is therefore set up and used for archiving real-time waveforms
from a seedlink server.
In this example, well arrange for keeping waveforms for one week.</p>
<p>Before starting, youll need ensure to have access to readl-time data from a
<a class="reference internal" href="../../apps/seedlink.html#seedlink"><span class="std std-ref">seedlink</span></a> server. To make seedlink bindings for your stations see the
tutorials <a class="reference internal" href="geofon_waveforms.html#tutorials-geofon-waveforms"><span class="std std-ref">Add real-time stations from GEOFON</span></a> or <a class="reference internal" href="waveforms.html#tutorials-waveforms"><span class="std std-ref">Get real-time data from a remote Seedlink server (single station)</span></a>.</p>
</section>
<section id="background">
<h2>Background<a class="headerlink" href="#background" title="Permalink to this heading"></a></h2>
<p><a class="reference internal" href="../../apps/slarchive.html#slarchive"><span class="std std-ref">slarchive</span></a> collects data and archives it locally in the directory defined
by <a class="reference internal" href="../../apps/slarchive.html#confval-archive"><code class="xref std std-confval docutils literal notranslate"><span class="pre">archive</span></code></a> using a <a class="reference internal" href="../glossary.html#term-SDS"><span class="xref std std-term">SDS</span></a> file
system structure of nested subdirectories and systematically named files. For
working with the archived data, read the section on
<a class="reference internal" href="#tutorials-archiving-access"><span class="std std-ref">Access to Archived Data</span></a>.</p>
</section>
<section id="setup">
<h2>Setup<a class="headerlink" href="#setup" title="Permalink to this heading"></a></h2>
<p><a class="reference internal" href="../../apps/slarchive.html#slarchive"><span class="std std-ref">slarchive</span></a> requires a module configuration and bindings.
You may configure slarchive using <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> or by command-line actions.</p>
<section id="in-scconfig">
<h2>In scconfig<a class="headerlink" href="#in-scconfig" title="Permalink to this heading"></a></h2>
<h3>In scconfig<a class="headerlink" href="#in-scconfig" title="Permalink to this heading"></a></h3>
<ol class="arabic">
<li><p>Under the Modules tab, go to Acquisition, and select <strong class="program">slarchive</strong>.
Here you can see the default parameters used.
@ -156,93 +171,104 @@ from within a <a class="reference internal" href="../glossary.html#term-GUI"><sp
</ol>
</section>
<section id="command-line">
<h2>Command line<a class="headerlink" href="#command-line" title="Permalink to this heading"></a></h2>
<h3>Command line<a class="headerlink" href="#command-line" title="Permalink to this heading"></a></h3>
<p>You will need to edit each of your top-level key files to refer to
a new binding profile.
e.g.:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ cd ~/seiscomp/etc/key
$ vi station_GR_CLL
e.g.</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span><span class="nb">cd</span><span class="w"> </span>~/seiscomp/etc/key
$<span class="w"> </span>vi<span class="w"> </span>station_GR_CLL
</pre></div>
</div>
<p>Add the line <cite>slarchive:week</cite> to whatever lines are already there.
Afterwards it will look something like this:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="c1"># Binding references</span>
<span class="k">global</span><span class="p">:</span><span class="n">BH</span>
<span class="n">scautopick</span><span class="p">:</span><span class="n">default</span>
<span class="n">seedlink</span><span class="p">:</span><span class="n">geofon</span>
<span class="n">slarchive</span><span class="p">:</span><span class="n">week</span>
Afterwards it will look something like this</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="c1"># Binding references</span>
<span class="na">global</span><span class="o">:</span><span class="s">BH</span>
<span class="na">scautopick</span><span class="o">:</span><span class="s">default</span>
<span class="na">seedlink</span><span class="o">:</span><span class="s">geofon</span>
<span class="na">slarchive</span><span class="o">:</span><span class="s">week</span>
</pre></div>
</div>
<p>Repeat this for the top-level key file of each station
you wish this binding to apply to.
Now create the binding profile in the key directory.
This is a file with a name corresponding to the binding profile name; here: week</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ cd ~/seiscomp/etc/key
$ mkdir slarchive
$ vi slarchive/profile_week
# Number of days the data is kept in the archive. This requires purge_datafile
# to be run as cronjob.
keep = 7
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span><span class="nb">cd</span><span class="w"> </span>~/seiscomp/etc/key
$<span class="w"> </span>mkdir<span class="w"> </span>slarchive
$<span class="w"> </span>vi<span class="w"> </span>slarchive/profile_week
<span class="c1"># Number of days the data is kept in the archive. This requires purge_datafile</span>
<span class="c1"># to be run as cronjob.</span>
<span class="nv">keep</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="m">7</span>
$ seiscomp enable slarchive
$ seiscomp update-config slarchive
$ seiscomp restart slarchive
slarchive is not running
starting slarchive
$<span class="w"> </span>seiscomp<span class="w"> </span><span class="nb">enable</span><span class="w"> </span>slarchive
$<span class="w"> </span>seiscomp<span class="w"> </span>update-config<span class="w"> </span>slarchive
$<span class="w"> </span>seiscomp<span class="w"> </span>restart<span class="w"> </span>slarchive
slarchive<span class="w"> </span>is<span class="w"> </span>not<span class="w"> </span>running
starting<span class="w"> </span>slarchive
</pre></div>
</div>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>Left unattended, your disk will eventually fill up with archived data.
To prevent this you will need a script like <cite>purge_database</cite>,
which is provided with SeisComP.
This can be run once per day using the <cite>cron</cite> feature of your system.
The command:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ seiscomp print crontab
</section>
<section id="data-life-cycle">
<h3>Data life cycle<a class="headerlink" href="#data-life-cycle" title="Permalink to this heading"></a></h3>
<p>Left unattended, your disk will eventually fill up with archived data since
<a class="reference internal" href="../../apps/slarchive.html#slarchive"><span class="std std-ref">slarchive</span></a> itself does not delete any data.</p>
<section id="deleting-files">
<h4>Deleting files<a class="headerlink" href="#deleting-files" title="Permalink to this heading"></a></h4>
<p>To prevent your file system from filling up you may delete data using a script
like <cite>purge_database</cite>, provided with <cite>SeisComP</cite>. The script considers duration set
by the <em>keep</em> parameter in slarchive bindings for defining the number of days to
keep the data in your archive.
The script can be run once per day using the <cite>cron</cite> feature of your system.
The command</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>seiscomp<span class="w"> </span>print<span class="w"> </span>crontab
</pre></div>
</div>
<p>will print a number of lines to the terminal.
Type <cite>crontab -e</cite> and insert these lines into the crontab file for your
user (typically <cite>sysop</cite>).
<p>will print a number of lines with suggested actions to the terminal. Type
<cite>crontab -e</cite> and insert these lines into the crontab file for your user (typically <cite>sysop</cite>).
Exit your crontab editor.
Displaying your crontab should now show a line for <cite>purge_database</cite>.:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ crontab -l
20 3 * * * /home/sysop/seiscomp/var/lib/slarchive/purge_datafiles &gt;/dev/null 2&gt;&amp;1
[There may be other lines too.]
Displaying your crontab should now show a line for <cite>purge_database</cite>.</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>crontab<span class="w"> </span>-l
<span class="m">20</span><span class="w"> </span><span class="m">3</span><span class="w"> </span>*<span class="w"> </span>*<span class="w"> </span>*<span class="w"> </span>/home/sysop/seiscomp/var/lib/slarchive/purge_datafiles<span class="w"> </span>&gt;/dev/null<span class="w"> </span><span class="m">2</span>&gt;<span class="p">&amp;</span><span class="m">1</span>
<span class="o">[</span>There<span class="w"> </span>may<span class="w"> </span>be<span class="w"> </span>other<span class="w"> </span>lines<span class="w"> </span>too.<span class="o">]</span>
</pre></div>
</div>
<p>This shows you that the <cite>purge_datafiles</cite> script
will run every day at 3:20 a.m.</p>
</div>
<p>This shows you that the <cite>purge_datafiles</cite> script will run every day at 3:20 a.m.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>If you examine the <cite>purge_datafiles</cite> script, you will see that all it does
is look for files with a last modified time older than a certain number
is looking for files with a last modified time older than a certain number
of days ago.
The number of days to keep can be set station-by-station using the
ARCH_KEEP feature.
A convenient way to do this for many stations is with
multiple binding profiles, one for each length of time desired.</p>
multiple slarchive binding profiles, one for each length of time desired.</p>
</div>
</section>
<section id="checking-archiving-is-functioning">
<h2>Checking archiving is functioning<a class="headerlink" href="#checking-archiving-is-functioning" title="Permalink to this heading"></a></h2>
<section id="extending-disk-space">
<h4>Extending disk space<a class="headerlink" href="#extending-disk-space" title="Permalink to this heading"></a></h4>
<p>In case your file system fills up with data and you do not wish to delete
old ones, you may add an additional harddisk and configure <a class="reference internal" href="../../apps/slarchive.html#confval-archive"><code class="xref std std-confval docutils literal notranslate"><span class="pre">archive</span></code></a>
of <strong class="program">slarchive</strong> to store the new data there. Thereafter you may
configure the <em>combined</em> or the <em>sdsarchive</em> <a class="reference internal" href="../../apps/global_recordstream.html#global-recordstream"><span class="std std-ref">RecordStream</span></a> to read
the data from both sources.</p>
</section>
</section>
<section id="verification">
<h3>Verification<a class="headerlink" href="#verification" title="Permalink to this heading"></a></h3>
<ul>
<li><p>If <strong class="program">seedlink</strong> is configured correctly, a new stations streams
appears in output from <strong class="program">slinktool</strong>:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ slinktool -Q : | grep CLL
GR CLL HHZ D 2020/04/01 01:11:57.6649 - 2020/04/01 07:28:49.0299
GR CLL HHE D 2020/04/01 01:11:57.6649 - 2020/04/01 07:28:45.0299
GR CLL HHN D 2020/04/01 01:11:57.6649 - 2020/04/01 07:28:39.2299
<li><p>If <a class="reference internal" href="../../apps/seedlink.html#seedlink"><span class="std std-ref">seedlink</span></a> is configured correctly, a new stations streams
appear in output from <a class="reference internal" href="../../apps/slinktool.html#slinktool"><span class="std std-ref">slinktool</span></a></p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>slinktool<span class="w"> </span>-Q<span class="w"> </span>:<span class="w"> </span><span class="p">|</span><span class="w"> </span>grep<span class="w"> </span>CLL
GR<span class="w"> </span>CLL<span class="w"> </span>HHZ<span class="w"> </span>D<span class="w"> </span><span class="m">2020</span>/04/01<span class="w"> </span><span class="m">01</span>:11:57.6649<span class="w"> </span>-<span class="w"> </span><span class="m">2020</span>/04/01<span class="w"> </span><span class="m">07</span>:28:49.0299
GR<span class="w"> </span>CLL<span class="w"> </span>HHE<span class="w"> </span>D<span class="w"> </span><span class="m">2020</span>/04/01<span class="w"> </span><span class="m">01</span>:11:57.6649<span class="w"> </span>-<span class="w"> </span><span class="m">2020</span>/04/01<span class="w"> </span><span class="m">07</span>:28:45.0299
GR<span class="w"> </span>CLL<span class="w"> </span>HHN<span class="w"> </span>D<span class="w"> </span><span class="m">2020</span>/04/01<span class="w"> </span><span class="m">01</span>:11:57.6649<span class="w"> </span>-<span class="w"> </span><span class="m">2020</span>/04/01<span class="w"> </span><span class="m">07</span>:28:39.2299
</pre></div>
</div>
<p>This shows three streams being acquired from station CLL.
The second time shown is the time of the most recent data for each stream.</p>
</li>
<li><p>If <strong class="program">slarchive</strong> is configured correctly, waveform data for the
<li><p>If <a class="reference internal" href="../../apps/slarchive.html#slarchive"><span class="std std-ref">slarchive</span></a> is configured correctly, waveform data for the
station appears in <strong class="program">slarchive</strong>s SDS archive directory:</p>
<blockquote>
<div><div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>ls<span class="w"> </span>-l<span class="w"> </span>seiscomp/var/lib/archive/2020/GR/CLL
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>ls<span class="w"> </span>-l<span class="w"> </span>seiscomp/var/lib/archive/2020/GR/CLL
total<span class="w"> </span><span class="m">12</span>
drwxr-xr-x<span class="w"> </span><span class="m">2</span><span class="w"> </span>user<span class="w"> </span>user<span class="w"> </span><span class="m">4096</span><span class="w"> </span>Apr<span class="w"> </span><span class="m">1</span><span class="w"> </span><span class="m">06</span>:30<span class="w"> </span>HHE.D
drwxr-xr-x<span class="w"> </span><span class="m">2</span><span class="w"> </span>user<span class="w"> </span>user<span class="w"> </span><span class="m">4096</span><span class="w"> </span>Apr<span class="w"> </span><span class="m">1</span><span class="w"> </span><span class="m">06</span>:30<span class="w"> </span>HHN.D
@ -254,7 +280,39 @@ total<span class="w"> </span><span class="m">12728</span>
-rw-r--r--<span class="w"> </span><span class="m">1</span><span class="w"> </span>user<span class="w"> </span>user<span class="w"> </span><span class="m">7531008</span><span class="w"> </span>Apr<span class="w"> </span><span class="m">1</span><span class="w"> </span><span class="m">00</span>:03<span class="w"> </span>GR.CLL..BHZ.D.2020.091
</pre></div>
</div>
</div></blockquote>
<p>You may read these data files directly using <a class="reference internal" href="../../apps/scrttv.html#scrttv"><span class="std std-ref">scrttv</span></a>, e.g.:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>scrttv<span class="w"> </span>seiscomp/var/lib/archive/2020/GR/CLL/HHZ.D/*
</pre></div>
</div>
</li>
</ul>
</section>
</section>
<section id="access-to-archived-data">
<span id="tutorials-archiving-access"></span><h2>Access to Archived Data<a class="headerlink" href="#access-to-archived-data" title="Permalink to this heading"></a></h2>
<p>Archived waveforms can be read or provided in multiple ways depending on the
application.</p>
<ul>
<li><p>Offline reading with <a class="reference internal" href="../../apps/scrttv.html#scrttv"><span class="std std-ref">scrttv</span></a>: Read miniSEED files directly using
<a class="reference internal" href="../../apps/scrttv.html#scrttv"><span class="std std-ref">scrttv</span></a>, e.g.:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>scrttv<span class="w"> </span>seiscomp/var/lib/archive/2020/GR/CLL/HHZ.D/*
</pre></div>
</div>
</li>
<li><p>Automatically for data processing: <cite>SeisComP</cite> modules such as
<a class="reference internal" href="../../apps/scautopick.html#scautopick"><span class="std std-ref">scautopick</span></a> or <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a> can read data from SDS
archive with the <em>sdsarchive</em> <a class="reference internal" href="../../apps/global_recordstream.html#global-recordstream"><span class="std std-ref">RecordStream</span></a> when running on the
same computer.</p></li>
<li><p>External clients: You may provide the data to clients on other
computers using <a class="reference internal" href="../../apps/scwfas.html#scwfas"><span class="std std-ref">scwfas</span></a> or <a class="reference internal" href="../../apps/fdsnws.html#fdsnws"><span class="std std-ref">fdsnws</span></a> both providing data via
<span id="id1"><em>FDSNWS</em> [<a class="reference internal" href="../references.html#id135" title="FDSNWS. International Federation of Digital Seismograph Networks. URL: http://www.fdsn.org/webservices/.">8</a>]</span>.</p></li>
<li><p>Direct file access: For directly fetching <a class="reference internal" href="../glossary.html#term-miniSeed"><span class="xref std std-term">miniSEED</span></a> waveform data from
archive you may use <a class="reference internal" href="../../apps/scart.html#scart"><span class="std std-ref">scart</span></a> or Linux commands. You may combine scart
with other modules avoiding redundant file storage. Examples:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>scart<span class="w"> </span>-dEsv<span class="w"> </span>-t<span class="w"> </span><span class="m">2025</span>-02-01T01:00~2025-02-01T01:00<span class="w"> </span>/archive<span class="w"> </span><span class="p">|</span><span class="w"> </span>scrttv<span class="w"> </span>-
$<span class="w"> </span>scart<span class="w"> </span>-dEsv<span class="w"> </span>-t<span class="w"> </span><span class="m">2025</span>-02-01T01:00~2025-02-01T01:00<span class="w"> </span>/archive<span class="w"> </span><span class="p">|</span><span class="w"> </span>scautopick<span class="w"> </span>-I<span class="w"> </span>-<span class="w"> </span>-d<span class="w"> </span>localhost<span class="w"> </span>--ep<span class="w"> </span>--playback
</pre></div>
</div>
</li>
</ul>
</section>
@ -280,10 +338,21 @@ total<span class="w"> </span><span class="m">12728</span>
<div>
<h3><a href="../../index.html">Table of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Set up local waveform archiving</a><ul>
<li><a class="reference internal" href="#">Maintain waveform archives</a><ul>
<li><a class="reference internal" href="#motivation">Motivation</a></li>
<li><a class="reference internal" href="#background">Background</a></li>
<li><a class="reference internal" href="#setup">Setup</a><ul>
<li><a class="reference internal" href="#in-scconfig">In scconfig</a></li>
<li><a class="reference internal" href="#command-line">Command line</a></li>
<li><a class="reference internal" href="#checking-archiving-is-functioning">Checking archiving is functioning</a></li>
<li><a class="reference internal" href="#data-life-cycle">Data life cycle</a><ul>
<li><a class="reference internal" href="#deleting-files">Deleting files</a></li>
<li><a class="reference internal" href="#extending-disk-space">Extending disk space</a></li>
</ul>
</li>
<li><a class="reference internal" href="#verification">Verification</a></li>
</ul>
</li>
<li><a class="reference internal" href="#access-to-archived-data">Access to Archived Data</a></li>
</ul>
</li>
</ul>
@ -318,7 +387,7 @@ total<span class="w"> </span><span class="m">12728</span>
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.

View File

@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Add real-time stations from GEOFON &#8212; SeisComP Release documentation</title>
<title>Add real-time stations from GEOFON &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
@ -12,7 +12,7 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
@ -25,8 +25,8 @@
<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">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@ -92,7 +92,7 @@ as a source of data.</p></li>
</ul>
<p>Related tutorial(s):</p>
<ul class="simple">
<li><p>Tutorial on <a class="reference internal" href="archiving.html#tutorials-archiving"><span class="std std-ref">Set up local waveform archiving</span></a></p></li>
<li><p>Tutorial on <a class="reference internal" href="archiving.html#tutorials-archiving"><span class="std std-ref">Maintain waveform archives</span></a></p></li>
<li><p>Tutorial on <a class="reference internal" href="servefdsnws.html#tutorials-servefdsnws"><span class="std std-ref">Enable local FDSNWS server</span></a></p></li>
</ul>
<hr class="docutils" />
@ -114,10 +114,10 @@ This tutorial demonstrates how to use this data in your own SeisComP system.</p>
<section id="check-data-are-available">
<h2>Check data are available<a class="headerlink" href="#check-data-are-available" title="Permalink to this heading"></a></h2>
<p>First, well query the upstream Seedlink server, which runs on
host <cite>geofon.gfz-potsdam.de</cite> at port 18000.
host <em>geofon.gfz.de</em> at port <em>18000</em>.
We do this with SeisComPs <a class="reference internal" href="../../apps/slinktool.html#slinktool"><span class="std std-ref">slinktool</span></a> command, giving the <code class="docutils literal notranslate"><span class="pre">-L</span></code> option
to <a class="reference internal" href="../../apps/slinktool.html#slinktool"><span class="std std-ref">slinktool</span></a></p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>slinktool<span class="w"> </span>-L<span class="w"> </span>geofon.gfz-potsdam.de
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>slinktool<span class="w"> </span>-L<span class="w"> </span>geofon.gfz.de
6C<span class="w"> </span>GF01<span class="w"> </span>GF01
6C<span class="w"> </span>GF02<span class="w"> </span>GF02
6C<span class="w"> </span>GF03<span class="w"> </span>GF03
@ -133,7 +133,7 @@ of the stations for which data is available from this Seedlink server.
Well just be interested in a few stations, namely those corresponding
to broadband 20 sps vertical channels - with channel code BHZ, and with network
code GE</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>slinktool<span class="w"> </span>-Q<span class="w"> </span>geofon.gfz-potsdam.de<span class="w"> </span><span class="p">|</span><span class="w"> </span>grep<span class="w"> </span>^GE.*BHZ
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>slinktool<span class="w"> </span>-Q<span class="w"> </span>geofon.gfz.de<span class="w"> </span><span class="p">|</span><span class="w"> </span>grep<span class="w"> </span>^GE.*BHZ
GE<span class="w"> </span>ACRG<span class="w"> </span>BHZ<span class="w"> </span>D<span class="w"> </span><span class="m">2019</span>/11/28<span class="w"> </span><span class="m">06</span>:51:48.7500<span class="w"> </span>-<span class="w"> </span><span class="m">2019</span>/11/28<span class="w"> </span><span class="m">09</span>:18:32.1000
GE<span class="w"> </span>APE<span class="w"> </span>BHZ<span class="w"> </span>D<span class="w"> </span><span class="m">2019</span>/11/28<span class="w"> </span><span class="m">07</span>:40:52.0400<span class="w"> </span>-<span class="w"> </span><span class="m">2019</span>/11/28<span class="w"> </span><span class="m">12</span>:22:00.3950
GE<span class="w"> </span>ARPR<span class="w"> </span>BHZ<span class="w"> </span>D<span class="w"> </span><span class="m">2019</span>/11/27<span class="w"> </span><span class="m">23</span>:23:27.4400<span class="w"> </span>-<span class="w"> </span><span class="m">2019</span>/11/28<span class="w"> </span><span class="m">09</span>:41:22.1500
@ -162,14 +162,14 @@ then it will be a longer time ago.</p>
<li><p>Use WebDC3 <a class="footnote-reference brackets" href="#webdc" id="id1" role="doc-noteref"><span class="fn-bracket">[</span>1<span class="fn-bracket">]</span></a> or network pages <a class="footnote-reference brackets" href="#netpages" id="id2" role="doc-noteref"><span class="fn-bracket">[</span>2<span class="fn-bracket">]</span></a>
to obtain metadata for existing seismic networks.</p></li>
<li><p>Other sources of inventory, like a dataless SEED file, can also be used.</p></li>
<li><p>The Gempa Station Management Portal, <span id="id3"><em>SMP</em> [<a class="reference internal" href="../references.html#id268" title="SMP. Station Management Portal by gempa GmbH. URL: https://smp.gempa.de/.">22</a>]</span>,
<li><p>The Gempa Station Management Portal, <span id="id3"><em>SMP</em> [<a class="reference internal" href="../references.html#id301" title="SMP. Station Management Portal by gempa GmbH. URL: https://smp.gempa.de/.">24</a>]</span>,
is another important source of station metadata.
If you would like to create your own inventory you may use this online tool.
Before doing so, you will need to create an account on SMP.</p></li>
</ul>
<section id="option-1-using-fdsn-web-services">
<h3>Option 1: Using FDSN web services<a class="headerlink" href="#option-1-using-fdsn-web-services" title="Permalink to this heading"></a></h3>
<p>The FDSN web services <span id="id4">[<a class="reference internal" href="../references.html#id110" title="FDSNWS. International Federation of Digital Seismograph Networks. URL: http://www.fdsn.org/webservices/.">8</a>]</span> are the standard adopted by the FDSN and have been
<p>The FDSN web services <span id="id4">[<a class="reference internal" href="../references.html#id135" title="FDSNWS. International Federation of Digital Seismograph Networks. URL: http://www.fdsn.org/webservices/.">8</a>]</span> are the standard adopted by the FDSN and have been
deployed at almost every data centre.
One of them is called <em>fdsnws-station</em> and
is the service to contact to get all information related to stations, sensors,
@ -177,7 +177,7 @@ responses, etc.</p>
<p>To get data from the <em>fdsnws-station</em> web service you can use any web client (browser or command
line). For instance, the <em>wget</em> command. The file you will receive will be in
StationXML format.</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>wget<span class="w"> </span><span class="s2">&quot;http://geofon.gfz-potsdam.de/fdsnws/station/1/query?net=GE&amp;level=response&quot;</span><span class="w"> </span>-O<span class="w"> </span>ge.xml
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>wget<span class="w"> </span><span class="s2">&quot;http://geofon.gfz.de/fdsnws/station/1/query?net=GE&amp;level=response&quot;</span><span class="w"> </span>-O<span class="w"> </span>ge.xml
</pre></div>
</div>
</section>
@ -188,9 +188,9 @@ FDSN webservice servers, but also to explore available stations
and query event catalogs
from different data centres among other possibilities.</p>
<p>You can find detailed information about WebDC3 in the on-line documentation at
<span id="id5"><em>WebDC3</em> [<a class="reference internal" href="../references.html#id287" title="WebDC3. Documentation. URL: https://webdc3.readthedocs.io/.">26</a>]</span>.</p>
<span id="id5"><em>WebDC3</em> [<a class="reference internal" href="../references.html#id322" title="WebDC3. Documentation. URL: https://webdc3.readthedocs.io/.">29</a>]</span>.</p>
<ul>
<li><p>Go to <a class="reference external" href="http://eida.gfz-potsdam.de/webdc3">http://eida.gfz-potsdam.de/webdc3</a> with a browser.</p></li>
<li><p>Go to <a class="reference external" href="http://eida.gfz.de/webdc3">http://eida.gfz.de/webdc3</a> with a browser.</p></li>
<li><p>Click on “Explore stations” and move the slider to select only the current year
and only “Public permanent nets” on the Network type list.
Select the GE network, “All Stations”, BH channels, and click “Search”.</p></li>
@ -360,15 +360,14 @@ you can follow the same procedure for other networks/stations, provided you</p>
<aside class="footnote-list brackets">
<aside class="footnote brackets" id="webdc" role="doc-footnote">
<span class="label"><span class="fn-bracket">[</span><a role="doc-backlink" href="#id1">1</a><span class="fn-bracket">]</span></span>
<p>The WebDC3 service is available at <a class="reference external" href="http://eida.gfz-potsdam.de">http://eida.gfz-potsdam.de</a>.
See also
<p>The WebDC3 service is available at <a class="reference external" href="http://eida.gfz.de">http://eida.gfz.de</a>. See also
M. Bianchi, <em>et al.</em> (2015): WebDC3 Web Interface. GFZ Data Services.
doi:<a class="reference external" href="http://dx.doi.org/10.5880/GFZ.2.4/2016.001">10.5880/GFZ.2.4/2016.001</a></p>
</aside>
<aside class="footnote brackets" id="netpages" role="doc-footnote">
<span class="label"><span class="fn-bracket">[</span><a role="doc-backlink" href="#id2">2</a><span class="fn-bracket">]</span></span>
<p>For instance that of the GEOFON Program, at
<a class="reference external" href="https://geofon.gfz-potsdam.de/waveform/archive/network.php?ncode=GE">https://geofon.gfz-potsdam.de/waveform/archive/network.php?ncode=GE</a>.</p>
<a class="reference external" href="https://geofon.gfz.de/waveform/archive/network.php?ncode=GE">https://geofon.gfz.de/waveform/archive/network.php?ncode=GE</a>.</p>
</aside>
</aside>
</section>
@ -444,7 +443,7 @@ doi:<a class="reference external" href="http://dx.doi.org/10.5880/GFZ.2.4/2016.0
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.

View File

@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Help! Im stuck! Now what? &#8212; SeisComP Release documentation</title>
<title>Help! Im stuck! Now what? &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
@ -12,7 +12,7 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
@ -25,8 +25,8 @@
<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">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@ -174,10 +174,10 @@ To learn about them read the <a class="reference internal" href="#sec-tutorial-h
<figure class="align-center" id="id8">
<a class="reference internal image-reference" href="../../_images/help_forum.png"><img alt="../../_images/help_forum.png" src="../../_images/help_forum.png" style="width: 16cm;" /></a>
<figcaption>
<p><span class="caption-text">The <span id="id1"><em>SeisComP forum</em> [<a class="reference internal" href="../references.html#id256" title="SeisComP forum. GFZ. URL: https://forum.seiscomp.de/.">24</a>]</span>.</span><a class="headerlink" href="#id8" title="Permalink to this image"></a></p>
<p><span class="caption-text">The <span id="id1"><em>SeisComP forum</em> [<a class="reference internal" href="../references.html#id289" title="SeisComP forum. GFZ. URL: https://forum.seiscomp.de/.">26</a>]</span>.</span><a class="headerlink" href="#id8" title="Permalink to this image"></a></p>
</figcaption>
</figure>
<p>The <span id="id2"><em>SeisComP forum</em> [<a class="reference internal" href="../references.html#id256" title="SeisComP forum. GFZ. URL: https://forum.seiscomp.de/.">24</a>]</span> is the place to discuss <cite>SeisComP</cite>.
<p>The <span id="id2"><em>SeisComP forum</em> [<a class="reference internal" href="../references.html#id289" title="SeisComP forum. GFZ. URL: https://forum.seiscomp.de/.">26</a>]</span> is the place to discuss <cite>SeisComP</cite>.
Announcements about updates, training courses and more are posted
here by the developers, and users can post questions or discuss
new developments.
@ -309,14 +309,14 @@ OS:<span class="w"> </span>Ubuntu<span class="w"> </span><span class="m">18</spa
<section id="commercial-support">
<span id="sec-tutorial-help-commercial"></span><h3>Commercial support<a class="headerlink" href="#commercial-support" title="Permalink to this heading"></a></h3>
<p>Professional commercial support to SeisComP users is available from
<span id="id3"><em>gempa GmbH</em> [<a class="reference internal" href="../references.html#id122" title="gempa GmbH. The SeisComP development and maintenance company. URL: https://www.gempa.de/.">28</a>]</span>.</p>
<span id="id3"><em>gempa GmbH</em> [<a class="reference internal" href="../references.html#id147" title="gempa GmbH. The SeisComP development and maintenance company. URL: https://www.gempa.de.">31</a>]</span>.</p>
</section>
</section>
<section id="next-time-you-have-a-problem">
<h2>Next time you have a problem<a class="headerlink" href="#next-time-you-have-a-problem" title="Permalink to this heading"></a></h2>
<ul class="simple">
<li><p>Try some of the above techniques.</p></li>
<li><p>If you find a solution, dont forget to share it at the <span id="id4"><em>SeisComP forum</em> [<a class="reference internal" href="../references.html#id256" title="SeisComP forum. GFZ. URL: https://forum.seiscomp.de/.">24</a>]</span>.</p></li>
<li><p>If you find a solution, dont forget to share it at the <span id="id4"><em>SeisComP forum</em> [<a class="reference internal" href="../references.html#id289" title="SeisComP forum. GFZ. URL: https://forum.seiscomp.de/.">26</a>]</span>.</p></li>
</ul>
</section>
</section>
@ -389,7 +389,7 @@ OS:<span class="w"> </span>Ubuntu<span class="w"> </span><span class="m">18</spa
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.

View File

@ -1,406 +0,0 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Magnitudes: Regionalization, Aliases, Mw &#8212; 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/pygments.css?v=72bcf2f2" />
<link rel="stylesheet" type="text/css" href="../../_static/seiscomp.css?v=c6da7ce6" />
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
<link rel="search" title="Search" href="../../search.html" />
<link rel="next" title="Play back archived waveforms" href="waveformplayback.html" />
<link rel="prev" title="Enable local FDSNWS server" href="servefdsnws.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">6.9.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="waveformplayback.html" title="Play back archived waveforms"
accesskey="N">
next
</a>
</li>
<li class="right">
<a href="servefdsnws.html" title="Enable local FDSNWS server"
accesskey="P">
previous
</a>
</li>
<li class="nav-item nav-item-0">
<a href="../../index.html">Home</a>
</li>
<li class="nav-item nav-item-1">
<a href="../tutorials.html" accesskey="U">Tutorials</a>
</li>
</ul>
</div>
</div>
</div>
</div>
<div class="container">
<div class="fitted content" id="anchors-container">
<div class="body" role="main">
<section id="magnitudes-regionalization-aliases-mw">
<span id="tutorials-magnitude-region-aliases"></span><h1>Magnitudes: Regionalization, Aliases, Mw<a class="headerlink" href="#magnitudes-regionalization-aliases-mw" title="Permalink to this heading"></a></h1>
<p>You will …</p>
<ul class="simple">
<li><p>Regionalize magnitude</p></li>
<li><p>Create new magnitude types as aliases from other magnitudes and amplitudes.</p></li>
<li><p>Map magnitudes to the moment magnitude, Mw</p></li>
</ul>
<dl class="field-list simple">
<dt class="field-odd">Pre-requisites for this tutorial<span class="colon">:</span></dt>
<dd class="field-odd"><ul class="simple">
<li><p>Read the <a class="reference internal" href="../concepts/magnitudes.html#concepts-magnitudes"><span class="std std-ref">concepts section on magnitudes</span></a>.</p></li>
<li><p>Real-time data for the station must be available locally.
See <a class="reference internal" href="waveforms.html#tutorials-waveforms"><span class="std std-ref">Get real-time data from a remote Seedlink server (single station)</span></a> or <a class="reference internal" href="geofon_waveforms.html#tutorials-geofon-waveforms"><span class="std std-ref">Add real-time stations from GEOFON</span></a>.</p></li>
<li><p>Inventory must be loaded locally.</p></li>
</ul>
</dd>
<dt class="field-even">Afterwards/Results/Outcomes<span class="colon">:</span></dt>
<dd class="field-even"><ul class="simple">
<li><p>Regionalized magnitudes,</p></li>
<li><p>New magnitude types as aliases.</p></li>
<li><p>Moment magnitudes</p></li>
</ul>
</dd>
<dt class="field-odd">Time range estimate<span class="colon">:</span></dt>
<dd class="field-odd"><ul class="simple">
<li><p>30 minutes</p></li>
</ul>
</dd>
</dl>
<hr class="docutils" />
<section id="regionalize-magnitudes">
<span id="tutorials-magnitude-region"></span><h2>Regionalize Magnitudes<a class="headerlink" href="#regionalize-magnitudes" title="Permalink to this heading"></a></h2>
<p>By regionalization, magnitudes can be computed with region-dependent properties.
The procedure to set up magnitude regionalization is:</p>
<ol class="arabic">
<li><p>Create one file which contains the polygons surrounding the regions within
which magnitude parameters shall apply. The polygon files are provided in
<a class="reference internal" href="../../apps/global_gui.html#sec-gui-layers-vector-format-bna"><span class="std std-ref">BNA</span></a> or
<a class="reference internal" href="../../apps/global_gui.html#sec-gui-layers-vector-format-geojson"><span class="std std-ref">GeoJSON format</span></a> and located as
set out in the <a class="reference internal" href="../../apps/global_gui.html#sec-gui-layers"><span class="std std-ref">documentation of map layers</span></a>. The file
can be created from any <cite>SeisComP</cite> GUI application providing maps, e.g.,
<a class="reference internal" href="../../apps/scmv.html#scmv"><span class="std std-ref">scmv</span></a>.</p></li>
<li><p>For the desired magnitude type create a magnitude-type profile in global
module configuration. The name of the profile matches the name of the
magnitude, e.g., <em>MLc</em> for the <a class="reference internal" href="../../apps/global_mlc.html#global-mlc"><span class="std std-ref">MLc magnitude</span></a>.</p></li>
<li><p>Configure the <code class="xref std std-confval docutils literal notranslate"><span class="pre">magnitudes.MLc.regionFile</span></code> parameter with the full
path and name of the polygon file created above.</p></li>
<li><p>Within the magnitude-type profile create one or more magnitude-region
profile(s) for defining the regionalized parameters applied to the region(s).
The name of a profile corresponds to the name of the polygon contained in the
polygon file to which the parameters shall apply. Use <em>world</em> for all regions
not covered by any polygon.</p></li>
<li><p>Configure the regionalized magnitude parameters of the magnitude-region
profile. Activate the <em>enable</em> parameter if you wish to apply this profile.</p></li>
<li><p>Restart the data processing:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>restart
</pre></div>
</div>
<p>or execute a GUI module.</p>
</li>
</ol>
<div class="admonition important">
<p class="admonition-title">Important</p>
<ul class="simple">
<li><p>Parameters which can be configured along with regionalization assume
defaults from global binding parameters but override global bindings
parameters when configured.</p></li>
<li><p>Once regionalization is active, magnitudes for events outside the
defined region(s) will not be computed. For considering such events add
another magnitude-region profile with the name “<em>world</em>”.
Magnitudes for events outside any other magnitude-region profile will then
be computed according to this profile.</p></li>
</ul>
</div>
<section id="station-corrections">
<h3>Station corrections<a class="headerlink" href="#station-corrections" title="Permalink to this heading"></a></h3>
<p><a class="reference internal" href="../concepts/magnitudes.html#concepts-magnitudes-correction"><span class="std std-ref">Magnitude station corrections</span></a> can also
be applied in case of regionalization. Simply add the names of the
magnitude-region profile along with the correction parameter to the original
parameter in global module configuration, <code class="file docutils literal notranslate"><span class="pre">global.cfg</span></code>, for the respective
magnitude type and station. Use comma separation for multiple regions and colon
for separating the region name from the value.</p>
<p>Example for correcting MLv computed at station GE.UGM:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">module.trunk.GE.UGM.magnitudes.MLv.offset</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">0.1, europe:0.2, asia:-0.1</span>
</pre></div>
</div>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>The configuration of parameters starting with <em>module.trunk.</em> is not
supported by <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>. All corresponding configurations must be done
by directly editing the configuration file, e.g.,
<code class="file docutils literal notranslate"><span class="pre">seiscomp/etc/global.cfg</span></code>.</p>
</div>
</section>
</section>
<section id="magnitude-aliases">
<span id="tutorials-magnitude-aliases"></span><h2>Magnitude Aliases<a class="headerlink" href="#magnitude-aliases" title="Permalink to this heading"></a></h2>
<p>New magnitude types (aliases) can be created based on existing magnitude and
amplitude types but configured specifically.</p>
<p>The procedure to set up magnitude aliases is:</p>
<ol class="arabic">
<li><p>Create a magnitude alias in <code class="file docutils literal notranslate"><span class="pre">global.cfg</span></code> by configuring
<a class="reference internal" href="../../apps/global.html#confval-magnitudes.aliases"><code class="xref std std-confval docutils literal notranslate"><span class="pre">magnitudes.aliases</span></code></a>. Example:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">magnitudes.aliases</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">MLc1:MLc:MLc</span>
</pre></div>
</div>
</li>
<li><p>Configure the alias magnitudes in either way:</p>
<ul class="simple">
<li><p>Write bindings parameters to global module configuration or</p></li>
<li><p>Set up <a class="reference internal" href="#tutorials-magnitude-region"><span class="std std-ref">regionalization</span></a>:</p></li>
</ul>
<p><strong>Binding parameters in global module configuration:</strong></p>
<ol class="arabic">
<li><p>Read the relevant parameter names of the original magnitude from global
binding, e.g., in <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>. The names must include the full
hierarchy including all sections. Example:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">magnitudes.MLc01.parametric.c1</span>
</pre></div>
</div>
</li>
<li><p>Open the module configuration file, e.g.,
<code class="file docutils literal notranslate"><span class="pre">seiscomp/etc/global.cfg</span></code> in a text editor.</p></li>
<li><p>Prepend <em>module.trunk.global.</em> to the parameter name and add it along with
its value to the configuration file. Example:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">module.trunk.global.magnitudes.MLc01.parametric.c1</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">0.7</span>
</pre></div>
</div>
</li>
<li><p>Add the new magnitude name to the configuration of all relevant modules,
e.g., <a class="reference internal" href="../../apps/scamp.html#scamp"><span class="std std-ref">scamp</span></a>, <a class="reference internal" href="../../apps/scmag.html#scmag"><span class="std std-ref">scmag</span></a>, <a class="reference internal" href="../../apps/scevent.html#scevent"><span class="std std-ref">scevent</span></a>, <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a>.</p></li>
</ol>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>The parameters starting with <em>module.trunk.</em> are not available for
configuration in <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>.</p>
</div>
<div class="admonition warning">
<p class="admonition-title">Warning</p>
<p>Binding parameters configured in global module configuration should only
be considered exceptionally. These parameters will</p>
<ul class="simple">
<li><p>Override the corresponding parameters configured by regionalization
using the region <em>world</em>.</p></li>
<li><p>Not be written to the database and cannot be accessed by SeisComP
modules running on other computers.</p></li>
</ul>
</div>
<p><strong>Regionalization:</strong></p>
<ul>
<li><p>Consider the tutorial on
<a class="reference internal" href="#tutorials-magnitude-region"><span class="std std-ref">magnitude regionalization</span></a> above.</p></li>
<li><p>For the name of the new magnitude-type profile now use the alias name.</p>
<div class="admonition hint">
<p class="admonition-title">Hint</p>
<p>When adding the magnitude-region profile in
<a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>, scconfig does not know about the referenced original
magnitude. Therefore, not all possible configuration parameters may be
listed depending on the magnitude, e.g. for MLc. For getting the full
list, first create and configure a magnitude-region profile for the
referenced magnitude.</p>
<ol class="arabic simple">
<li><p>Close scconfig</p></li>
<li><p>Open the configuration file <code class="file docutils literal notranslate"><span class="pre">global.cfg</span></code></p></li>
<li><p>Rename the name of the referenced magnitude in the parameters to the
name of the alias.</p></li>
</ol>
</div>
</li>
</ul>
</li>
</ol>
</section>
<section id="moment-magnitudes">
<span id="tutorials-mags-moment"></span><h2>Moment Magnitudes<a class="headerlink" href="#moment-magnitudes" title="Permalink to this heading"></a></h2>
<p>All magnitudes, Mx, can be mapped to a moment magnitude, Mw(Mx).
The configuration procedure is:</p>
<ol class="arabic">
<li><p>Set up a magnitude-type profile for the original magnitude type in global
module configuration. Use <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> for creating the profile.</p></li>
<li><p>Configure the parameter <em>MwMapping</em>, which will become available along with
the new profile, e.g., <code class="xref std std-confval docutils literal notranslate"><span class="pre">magnitudes.MLc.MwMapping</span></code>. Alternatively,
add the parameter to <code class="file docutils literal notranslate"><span class="pre">seiscomp/etc/global.cfg</span></code>. The parameter is
configured as a list of sample points of a piecewise linear function mapping
from the original magnitude, Mx, to Mw(Mx).
Example for Mw(MLc) based on MLc:</p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">magnitudes.MLc.MwMapping</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">MLc_0:Mw(MLc)_0,MLc_1:Mw(MLc)_1,...,MLc_N:Mw(MLc)_N</span>
</pre></div>
</div>
<p>Any magnitude value outside the configured range is ignored.</p>
<div class="admonition warning">
<p class="admonition-title">Warning</p>
<p>Do not map the magnitudes <a class="reference internal" href="../glossary.html#term-magnitude-broadband-body-wave-mB"><span class="xref std std-term">mB</span></a>
and <a class="reference internal" href="../glossary.html#term-magnitude-broadband-P-wave-moment-Mwp"><span class="xref std std-term">Mwp</span></a> to Mw since
this is hardcoded already and done automatically by <a class="reference internal" href="../../apps/scmag.html#scmag"><span class="std std-ref">scmag</span></a>.</p>
</div>
</li>
</ol>
<p>The new moment magnitudes will be available along with the original magnitudes
and can be viewed in <span class="xref std std-ref">scolv`or :ref:`scesv</span> and considered by <a class="reference internal" href="../../apps/scmag.html#scmag"><span class="std std-ref">scmag</span></a>
or <a class="reference internal" href="../../apps/scevent.html#scevent"><span class="std std-ref">scevent</span></a>.</p>
<p>In order to avoid that <a class="reference internal" href="../concepts/magnitudes.html#concepts-magnitudes-summary"><span class="std std-ref">summary magnitudes</span></a>
are computed from original magnitudes and mapped Mw together and biased to both,
the original magnitudes can be blocklisted in <a class="reference internal" href="../../apps/scmag.html#scmag"><span class="std std-ref">scmag</span></a>
(<a class="reference internal" href="../../apps/scmag.html#confval-summaryMagnitude.blacklist"><code class="xref std std-confval docutils literal notranslate"><span class="pre">summaryMagnitude.blacklist</span></code></a>).</p>
</section>
<section id="final-tests">
<span id="tutorials-mags-regionalize-testing"></span><h2>Final Tests<a class="headerlink" href="#final-tests" title="Permalink to this heading"></a></h2>
<ul>
<li><p>Regionalization:</p>
<ol class="arabic">
<li><p>Start <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a> with the option <code class="xref std std-option docutils literal notranslate"><span class="pre">--debug</span></code> and load an event of
interest</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>scolv<span class="w"> </span>--debug
</pre></div>
</div>
</li>
<li><p>Relocate the event for generating a new origin.</p></li>
<li><p>Compute magnitudes selecting the magnitude of interest.</p></li>
<li><p>Inspect the computed magnitudes in the
<a class="reference internal" href="../../apps/scolv.html#scolv-sec-magnitude-tab"><span class="std std-ref">Magnitude tab of scolv</span></a> or read the
debug output listing the considered magnitudes and stations along with
the regionalized parameters.</p></li>
</ol>
</li>
<li><p>Magnitude aliases:</p>
<ol class="arabic">
<li><p>Start <a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a> with the option <code class="xref std std-option docutils literal notranslate"><span class="pre">--debug</span></code> and load an event of
interest</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>scolv<span class="w"> </span>--debug
</pre></div>
</div>
</li>
<li><p>Relocate the event for generating a new origin.</p></li>
<li><p>Compute magnitudes selecting the magnitude of interest including the new
alias.</p></li>
<li><p>Inspect the computed magnitudes in the
<a class="reference internal" href="../../apps/scolv.html#scolv-sec-magnitude-tab"><span class="std std-ref">Magnitude tab of scolv</span></a> or read the
debug output listing the considered magnitude names and aliases along with
the considered parameters and their values. Example where MLc1 is derived
from MLc with a modified maximum depth:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>...
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>GE.UGM:<span class="w"> </span>MLc1:<span class="w"> </span>effective<span class="w"> </span>correction<span class="w"> </span><span class="o">(</span>no<span class="w"> </span>locale<span class="o">)</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="m">1</span>.00:0.00
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>Parameters<span class="w"> </span><span class="k">for</span><span class="w"> </span>magnitude<span class="w"> </span>MLc1
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>+<span class="w"> </span>maximum<span class="w"> </span>depth:<span class="w"> </span><span class="m">50</span>.000<span class="w"> </span>km
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>+<span class="w"> </span>distance<span class="w"> </span>mode:<span class="w"> </span>hypocentral
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>+<span class="w"> </span>minimum<span class="w"> </span>distance:<span class="w"> </span>-1.000<span class="w"> </span>km
<span class="m">13</span>:30:46<span class="w"> </span><span class="o">[</span>debug<span class="o">]</span><span class="w"> </span>+<span class="w"> </span>maximum<span class="w"> </span>distance:<span class="w"> </span><span class="m">889</span>.561<span class="w"> </span>km
...
</pre></div>
</div>
</li>
</ol>
</li>
</ul>
</section>
</section>
<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" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
<input type="submit" value="Go" />
</form>
</div>
</div>
<script>document.getElementById('searchbox').style.display = "block"</script>
<div>
<h3><a href="../../index.html">Table of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Magnitudes: Regionalization, Aliases, Mw</a><ul>
<li><a class="reference internal" href="#regionalize-magnitudes">Regionalize Magnitudes</a><ul>
<li><a class="reference internal" href="#station-corrections">Station corrections</a></li>
</ul>
</li>
<li><a class="reference internal" href="#magnitude-aliases">Magnitude Aliases</a></li>
<li><a class="reference internal" href="#moment-magnitudes">Moment Magnitudes</a></li>
<li><a class="reference internal" href="#final-tests">Final Tests</a></li>
</ul>
</li>
</ul>
</div>
<div>
<h4>Previous topic</h4>
<p class="topless"><a href="servefdsnws.html"
title="previous chapter">Enable local FDSNWS server</a></p>
</div>
<div>
<h4>Next topic</h4>
<p class="topless"><a href="waveformplayback.html"
title="next chapter">Play back archived waveforms</a></p>
</div>
<div role="note" aria-label="source link">
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="../../_sources/base/tutorials/magnitude-regionalization.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>6.9.0</b> Release
</div>
<div class="copyright">
Copyright &copy; 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>

View File

@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Installation on Ubuntu &#8212; SeisComP Release documentation</title>
<title>Installation on Ubuntu &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
@ -12,12 +12,12 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
<link rel="search" title="Search" href="../../search.html" />
<link rel="next" title="Upgrading SeisComP" href="upgrading.html" />
<link rel="next" title="Updating/Upgrading SeisComP" href="upgrading.html" />
<link rel="prev" title="Tutorials" href="../tutorials.html" />
</head>
<body>
@ -25,8 +25,8 @@
<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">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@ -43,7 +43,7 @@
</a>
</li>
<li class="right">
<a href="upgrading.html" title="Upgrading SeisComP"
<a href="upgrading.html" title="Updating/Upgrading SeisComP"
accesskey="N">
next
</a>
@ -73,11 +73,14 @@
<span id="tutorials-postinstall"></span><h1>Installation on Ubuntu<a class="headerlink" href="#installation-on-ubuntu" title="Permalink to this heading"></a></h1>
<p>You will …</p>
<ul class="simple">
<li><p>Make a basic <cite>SeisComP</cite> installation</p></li>
<li><p>Make a basic <cite>SeisComP</cite> installation of SeisComP in version 4.0.0 on Ubuntu 20.04</p></li>
<li><p>Make an initial configuration</p></li>
<li><p>Perform function tests</p></li>
</ul>
<p>Pre-requisites for this tutorial:</p>
<ul class="simple">
<li><p>Internet access</p></li>
<li><p><a class="reference internal" href="../installation.html#installation"><span class="std std-ref">Documentation of installation</span></a></p></li>
</ul>
<p>Afterwards/Results/Outcomes:</p>
<ul class="simple">
@ -90,7 +93,7 @@
</ul>
<p>Related tutorial(s):</p>
<ul class="simple">
<li><p><a class="reference internal" href="upgrading.html#tutorials-upgrade"><span class="std std-ref">Upgrading SeisComP</span></a></p></li>
<li><p><a class="reference internal" href="upgrading.html#tutorials-upgrade"><span class="std std-ref">Updating/Upgrading SeisComP</span></a></p></li>
<li><p><a class="reference internal" href="addstation.html#tutorials-addstation"><span class="std std-ref">Add a new station</span></a></p></li>
<li><p><a class="reference internal" href="geofon_waveforms.html#tutorials-geofon-waveforms"><span class="std std-ref">Add real-time stations from GEOFON</span></a></p></li>
</ul>
@ -113,12 +116,18 @@ $<span class="w"> </span>sudo<span class="w"> </span>addgroup<span class="w"> </
$<span class="w"> </span>sudo<span class="w"> </span>usermod<span class="w"> </span>-a<span class="w"> </span>-G<span class="w"> </span>admin,adm,audio<span class="w"> </span>sysop
</pre></div>
</div>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>Adding a new user is not mandatory. You can install under an existing user
directory. Creating a new user is recommended as it allows an easy cleanup
of the system later simply by removing the new user if needed.</p>
</div>
</li>
<li><p>Check the size and the architecture. This is espcially required when installing
<a class="reference internal" href="#tutorials-postinstall-package"><span class="std std-ref">pre-compiled packages</span></a>:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ df -h
$ cat /etc/issue
$ uname -m
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>df<span class="w"> </span>-h
$<span class="w"> </span>cat<span class="w"> </span>/etc/issue
$<span class="w"> </span>uname<span class="w"> </span>-m
</pre></div>
</div>
<p>Compare the available disk space with the requirements given in
@ -130,32 +139,43 @@ if you see x86_64, you have 64-bit.</p>
</section>
<section id="install-from-source-code">
<span id="tutorials-postinstall-compile"></span><h2>Install from source code<a class="headerlink" href="#install-from-source-code" title="Permalink to this heading"></a></h2>
<p>To compile SeisComP from the source code follow the
<a class="reference internal" href="../build.html#build"><span class="std std-ref">instructions in the development section</span></a>. You may later download and add
maps as described below in the <a class="reference internal" href="#tutorials-postinstall-package"><span class="std std-ref">package section</span></a>.</p>
<p>To compile <cite>SeisComP</cite> from the source code follow the
<a class="reference internal" href="../build.html#build"><span class="std std-ref">instructions in the development section</span></a>. You may later download
and add maps as described below in the
<a class="reference internal" href="../installation.html#installation"><span class="std std-ref">Documentation of installation</span></a>.</p>
</section>
<section id="install-pre-compiled-release-packages">
<span id="tutorials-postinstall-package"></span><h2>Install pre-compiled release packages<a class="headerlink" href="#install-pre-compiled-release-packages" title="Permalink to this heading"></a></h2>
<p>You may download and installed pre-compile SeisComP binary package, maps and documentation.</p>
<p>You may install the <cite>SeisComP</cite> packages in either way:</p>
<ul class="simple">
<li><p><a class="reference internal" href="../installation.html#installation-gsm"><span class="std std-ref">gsm</span></a> (recommended) a package manager provided by
<span id="id1"><em>gempa GmbH</em> [<a class="reference internal" href="../references.html#id147" title="gempa GmbH. The SeisComP development and maintenance company. URL: https://www.gempa.de.">31</a>]</span>,</p></li>
<li><p><a class="reference internal" href="../installation.html#installation-manual"><span class="std std-ref">manually by extracting packages</span></a>.</p></li>
</ul>
<p>Here we refer to the manual extraction of packages. More details are given
in section <a class="reference internal" href="../installation.html#installation"><span class="std std-ref">SeisComP Installation</span></a>.</p>
<p>You may download and installed pre-compile <cite>SeisComP</cite> binary package, maps and
documentation.</p>
<ol class="arabic">
<li><p>Download the appropriate <cite>SeisComP</cite> binary package taking into
account your Linux distribution and the architecture.
Get the package from the download site of <cite>SeisComP</cite> <span id="id1">[<a class="reference internal" href="../references.html#id257" title="Helmholtz-Centre Potsdam - GFZ German Research Centre for Geosciences and gempa GmbH. The SeisComP seismological software package. GFZ Data Services. 2008. URL: https://www.seiscomp.de, doi:10.5880/GFZ.2.4.2020.003.">67</a>]</span> or from
<span id="id2"><em>Public download site of gempa</em> [<a class="reference internal" href="../references.html#id124" title="Public download site of gempa. URL: https://data.gempa.de/packages/Public/seiscomp/.">20</a>]</span>. Packages are available for Ubuntu and other Linux
Get the package from the download site of <cite>SeisComP</cite> <span id="id2">[<a class="reference internal" href="../references.html#id290" title="Helmholtz-Centre Potsdam - GFZ German Research Centre for Geosciences and gempa GmbH. The SeisComP seismological software package. GFZ Data Services. 2008. URL: https://www.seiscomp.de, doi:10.5880/GFZ.2.4.2020.003.">76</a>]</span> or from
<span id="id3"><em>Public download site of gempa</em> [<a class="reference internal" href="../references.html#id149" title="Public download site of gempa. URL: https://data.gempa.de/packages/Public/seiscomp/.">21</a>]</span>. Packages are available for Ubuntu and other Linux
flavors such as RHEL/CentOS and Debian.</p></li>
<li><p>When downloading the <cite>SeisComP</cite> binary packages you should also download</p>
<ul>
<li><p>maps for <cite>SeisComP</cite></p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>wget<span class="w"> </span><span class="s2">&quot;https://www.seiscomp.de/downloader/seiscomp-maps.tar.gz&quot;</span>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>wget<span class="w"> </span><span class="s2">&quot;https://www.seiscomp.de/downloader/seiscomp-maps.tar.gz&quot;</span>
</pre></div>
</div>
</li>
<li><p>the documentation package. Make sure, the documentation matches your
SeisComP version.</p>
<cite>SeisComP</cite> version.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>The <cite>SeisComP</cite> packages received from gempa GmbH contain the documentation
for the respective version and no separate download is required.</p>
<p>The <cite>SeisComP</cite> packages received from <span id="id4"><em>Public download site of gempa</em> [<a class="reference internal" href="../references.html#id149" title="Public download site of gempa. URL: https://data.gempa.de/packages/Public/seiscomp/.">21</a>]</span> contain the
documentation for the respective version and no separate download is
required.</p>
</div>
</li>
</ul>
@ -276,12 +296,12 @@ system the output from the command</p>
the <a class="reference internal" href="../../apps/seiscomp.html#seiscomp"><span class="std std-ref">seiscomp</span></a> command will be added to your shells path.</p>
<div class="admonition hint">
<p class="admonition-title">Hint</p>
<p>If, when you attempt to run a SeisComP command such as <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> or
<p>If, when you attempt to run a <cite>SeisComP</cite> command such as <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> or
<a class="reference internal" href="../../apps/scolv.html#scolv"><span class="std std-ref">scolv</span></a>, you receive an error message like</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>scconfig:<span class="w"> </span><span class="nb">command</span><span class="w"> </span>not<span class="w"> </span>found
</pre></div>
</div>
<p>then the most likely explanation is that you have not set your SeisComP
<p>then the most likely explanation is that you have not set your <cite>SeisComP</cite>
environment variables correctly.</p>
<p>Run the <cite>seiscomp</cite> command with the full path to
where you installed.
@ -300,7 +320,7 @@ fields, you can always accept the default values.</p>
Datacenter ID. These are used for Arclink and Seedlink, and in the information
describing data model objects such as origins and events.</p>
</li>
<li><p>The <cite>seiscomp</cite> command is a wrapper, which controls the SeisComP modules.
<li><p>The <cite>seiscomp</cite> command is a wrapper, which controls the <cite>SeisComP</cite> modules.
See <a class="reference internal" href="../management.html#system-management"><span class="std std-ref">System management</span></a>.
Run something by typing seiscomp followed by a command</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span><span class="w"> </span>$<span class="w"> </span>seiscomp<span class="w"> </span><span class="nb">help</span>
@ -317,12 +337,17 @@ Use<span class="w"> </span><span class="s1">&#39;help [command]&#39;</span><span
</pre></div>
</div>
</li>
<li><p>Start <a class="reference internal" href="../../apps/scmaster.html#scmaster"><span class="std std-ref">scmaster</span></a>.
<li><p>Start and test <a class="reference internal" href="../../apps/scmaster.html#scmaster"><span class="std std-ref">scmaster</span></a>.
As described in the <a class="reference internal" href="../overview.html#overview"><span class="std std-ref">Overview</span></a>, these are needed for
communication between the SeisComP database and the individual
SeisComP modules.</p>
communication between the <cite>SeisComP</cite> database and the individual
<cite>SeisComP</cite> modules.</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>seiscomp<span class="w"> </span>start<span class="w"> </span>scmaster
starting<span class="w"> </span>scmaster
$<span class="w"> </span>seiscomp<span class="w"> </span>status<span class="w"> </span>scmaster
</pre></div>
</div>
<p>In case errors are reported you should understand the full debug log:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>scmaster<span class="w"> </span>--debug
</pre></div>
</div>
</li>
@ -337,10 +362,10 @@ starting<span class="w"> </span>scmaster
</div>
<p>Learn more about <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> in this documentation.
You should see a screen/window like this.</p>
<figure class="align-center" id="id3">
<figure class="align-center" id="id5">
<a class="reference internal image-reference" href="../../_images/postinstall_scconfig.png"><img alt="../../_images/postinstall_scconfig.png" src="../../_images/postinstall_scconfig.png" style="width: 16cm;" /></a>
<figcaption>
<p><span class="caption-text">First view of <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> configurator.</span><a class="headerlink" href="#id3" title="Permalink to this image"></a></p>
<p><span class="caption-text">First view of <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> configurator.</span><a class="headerlink" href="#id5" title="Permalink to this image"></a></p>
</figcaption>
</figure>
</li>
@ -348,7 +373,7 @@ You should see a screen/window like this.</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>seiscomp<span class="w"> </span><span class="nb">exec</span><span class="w"> </span>scrttv
</pre></div>
</div>
<p>After seeing the SeisComP splash screen,
<p>After seeing the <cite>SeisComP</cite> splash screen,
youll likely get an error message “Could not read inventory (NULL)”.
After a new installation, thats okay.
Click that box away, and youll see a screen with
@ -356,10 +381,10 @@ Click that box away, and youll see a screen with
To see stations and data you will later need to
<a class="reference internal" href="addstation.html#tutorials-addstation"><span class="std std-ref">add inventory</span></a> and
<a class="reference internal" href="geofon_waveforms.html#tutorials-geofon-waveforms"><span class="std std-ref">waveforms</span></a> to your system.</p>
<figure class="align-center" id="id4">
<figure class="align-center" id="id6">
<a class="reference internal image-reference" href="../../_images/postinstall_scrttv.png"><img alt="../../_images/postinstall_scrttv.png" src="../../_images/postinstall_scrttv.png" style="width: 14.6cm;" /></a>
<figcaption>
<p><span class="caption-text">First view of the <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> configuration tool.</span><a class="headerlink" href="#id4" title="Permalink to this image"></a></p>
<p><span class="caption-text">First view of the <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a> configuration tool.</span><a class="headerlink" href="#id6" title="Permalink to this image"></a></p>
</figcaption>
</figure>
</li>
@ -406,7 +431,7 @@ To see stations and data you will later need to
<div>
<h4>Next topic</h4>
<p class="topless"><a href="upgrading.html"
title="next chapter">Upgrading SeisComP</a></p>
title="next chapter">Updating/Upgrading SeisComP</a></p>
</div>
<div role="note" aria-label="source link">
<h3>This Page</h3>
@ -427,7 +452,7 @@ To see stations and data you will later need to
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.

View File

@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Configure real-time processing &#8212; SeisComP Release documentation</title>
<title>Configure real-time processing &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
@ -12,21 +12,21 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
<link rel="search" title="Search" href="../../search.html" />
<link rel="next" title="Add real-time stations from GEOFON" href="geofon_waveforms.html" />
<link rel="prev" title="Set up local waveform archiving" href="archiving.html" />
<link rel="prev" title="Maintain waveform archives" href="archiving.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">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@ -49,7 +49,7 @@
</a>
</li>
<li class="right">
<a href="archiving.html" title="Set up local waveform archiving"
<a href="archiving.html" title="Maintain waveform archives"
accesskey="P">
previous
</a>
@ -224,7 +224,7 @@ from the upstream server.</p>
<div>
<h4>Previous topic</h4>
<p class="topless"><a href="archiving.html"
title="previous chapter">Set up local waveform archiving</a></p>
title="previous chapter">Maintain waveform archives</a></p>
</div>
<div>
<h4>Next topic</h4>
@ -250,7 +250,7 @@ from the upstream server.</p>
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.

View File

@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Enable local FDSNWS server &#8212; SeisComP Release documentation</title>
<title>Enable local FDSNWS server &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
@ -12,12 +12,12 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
<link rel="search" title="Search" href="../../search.html" />
<link rel="next" title="Magnitudes: Regionalization, Aliases, Mw" href="magnitude-regionalization.html" />
<link rel="next" title="Amplitudes/Magnitudes: Regionalization, Aliases, Mw" href="amplitudes-magnitudes.html" />
<link rel="prev" title="Add real-time stations from GEOFON" href="geofon_waveforms.html" />
</head>
<body>
@ -25,8 +25,8 @@
<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">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@ -43,7 +43,7 @@
</a>
</li>
<li class="right">
<a href="magnitude-regionalization.html" title="Magnitudes: Regionalization, Aliases, Mw"
<a href="amplitudes-magnitudes.html" title="Amplitudes/Magnitudes: Regionalization, Aliases, Mw"
accesskey="N">
next
</a>
@ -78,7 +78,7 @@ a configured station</p></li>
</ul>
<p>Pre-requisites for this tutorial:</p>
<ul class="simple">
<li><p>Tutorial on <a class="reference internal" href="archiving.html#tutorials-archiving"><span class="std std-ref">Set up local waveform archiving</span></a></p></li>
<li><p>Tutorial on <a class="reference internal" href="archiving.html#tutorials-archiving"><span class="std std-ref">Maintain waveform archives</span></a></p></li>
</ul>
<p>Afterwards/Results/Outcomes:</p>
<ul class="simple">
@ -183,12 +183,12 @@ results in the service returning a StationXML file.</p>
<section id="further-information">
<h2>Further Information<a class="headerlink" href="#further-information" title="Permalink to this heading"></a></h2>
<ul class="simple">
<li><p>The <a class="reference external" href="https://geofon.gfz-potsdam.de/waveform/builder.php">URL Builder at GEOFON</a>
<li><p>The <a class="reference external" href="https://geofon.gfz.de/waveform/builder.php">URL Builder at GEOFON</a>
lets you fill out a form to tailor your request.
The URL to use to make your request is displayed at the bottom of that page.</p></li>
<li><p>More example requests are at the
<a class="reference external" href="https://geofon.gfz-potsdam.de/waveform/webservices.php">FDSNWS description at GEOFON</a></p></li>
<li><p>The FDSN Web Services specification document <span id="id1">[<a class="reference internal" href="../references.html#id111" title="FDSN Web Service Specifications. International Federation of Digital Seismograph Networks. URL: http://www.fdsn.org/webservices/FDSN-WS-Specifications-1.2.pdf.">5</a>]</span> provides the
<a class="reference external" href="https://geofon.gfz.de/waveform/webservices.php">FDSNWS description at GEOFON</a></p></li>
<li><p>The FDSN Web Services specification document <span id="id1">[<a class="reference internal" href="../references.html#id136" title="FDSN Web Service Specifications. International Federation of Digital Seismograph Networks. URL: http://www.fdsn.org/webservices/FDSN-WS-Specifications-1.2.pdf.">5</a>]</span> provides the
technical documentation and examples.</p></li>
</ul>
</section>
@ -247,8 +247,8 @@ The above example is just for the first hour of 2020.</p>
</div>
<div>
<h4>Next topic</h4>
<p class="topless"><a href="magnitude-regionalization.html"
title="next chapter">Magnitudes: Regionalization, Aliases, Mw</a></p>
<p class="topless"><a href="amplitudes-magnitudes.html"
title="next chapter">Amplitudes/Magnitudes: Regionalization, Aliases, Mw</a></p>
</div>
<div role="note" aria-label="source link">
<h3>This Page</h3>
@ -269,7 +269,7 @@ The above example is just for the first hour of 2020.</p>
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.

View File

@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Create a new tutorial &#8212; SeisComP Release documentation</title>
<title>Create a new tutorial &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
@ -12,7 +12,7 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
@ -25,8 +25,8 @@
<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">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@ -94,7 +94,7 @@
<p>To use this template, youll need to:</p>
<ol class="arabic simple">
<li><p>Get the source code of the SeisComP documentation, e.g. from
<span id="id1"><em>SeisComP on GitHub</em> [<a class="reference internal" href="../references.html#id258" title="Seiscomp on github. URL: https://github.com/SeisComP.">1</a>]</span></p></li>
<span id="id1"><em>SeisComP on GitHub</em> [<a class="reference internal" href="../references.html#id291" title="Seiscomp on github. URL: https://github.com/SeisComP.">1</a>]</span></p></li>
<li><p>Copy this tutorial file (<code class="file docutils literal notranslate"><span class="pre">doc/base/tutorials/template.rst</span></code>) to the tutorials directory
with a new name, <code class="file docutils literal notranslate"><span class="pre">doc/base/tutorials/</span><em><span class="pre">nn</span></em><span class="pre">_</span><em><span class="pre">something</span></em><span class="pre">.rst</span></code>.</p></li>
<li><p>Change the reference at the top (first line); it must be
@ -197,7 +197,7 @@ $<span class="w"> </span>python3<span class="w"> </span>build-doc.py
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.

View File

@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Upgrading SeisComP &#8212; SeisComP Release documentation</title>
<title>Updating/Upgrading SeisComP &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
@ -12,7 +12,7 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
@ -25,8 +25,8 @@
<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">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@ -69,16 +69,18 @@
<div class="fitted content" id="anchors-container">
<div class="body" role="main">
<section id="upgrading-seiscomp">
<span id="tutorials-upgrade"></span><h1>Upgrading SeisComP<a class="headerlink" href="#upgrading-seiscomp" title="Permalink to this heading"></a></h1>
<section id="updating-upgrading-seiscomp">
<span id="tutorials-upgrade"></span><h1>Updating/Upgrading SeisComP<a class="headerlink" href="#updating-upgrading-seiscomp" title="Permalink to this heading"></a></h1>
<p>You will …</p>
<ul class="simple">
<li><p>Upgrade a SeisComP system</p></li>
<li><p>Update/Upgrade a SeisComP system</p></li>
<li><p>Migrate a SeisComP3 system to a newer SeisComP version</p></li>
</ul>
<p>Pre-requisites for this tutorial:</p>
<ul class="simple">
<li><p>Tutorial on <a class="reference internal" href="postinstall.html#tutorials-postinstall"><span class="std std-ref">installation</span></a> and SeisComP previously installed</p></li>
<li><p><a class="reference internal" href="../installation.html#installation"><span class="std std-ref">Documentation of installation</span></a></p></li>
<li><p>Tutorial on <a class="reference internal" href="postinstall.html#tutorials-postinstall"><span class="std std-ref">installation</span></a> and <cite>SeisComP</cite>
previously installed</p></li>
</ul>
<p>Afterwards/Results/Outcomes:</p>
<ul class="simple">
@ -91,72 +93,38 @@
<hr class="docutils" />
<section id="background">
<h2>Background<a class="headerlink" href="#background" title="Permalink to this heading"></a></h2>
<p>Installing a new SeisComP <a class="reference internal" href="#tutorials-upgrade-versions"><span class="std std-ref">release version</span></a>
is typically simple and the step described in <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Upgrade</span></a>
can be applied. <strong>More actions</strong> are required when</p>
<p>Updating/upgrading <cite>SeisComP</cite> to a higher
<a class="reference internal" href="../installation.html#installation-versions"><span class="std std-ref">release version</span></a> is typically simple and the
steps described in <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Update/Upgrade</span></a> can be applied.
<strong>More actions</strong> are required when</p>
<ul class="simple">
<li><p>Upgrading the major version of SeisComP as described in <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Upgrade</span></a>.</p></li>
<li><p>Upgrading the major version of SeisComP as described in <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Update/Upgrade</span></a>.</p></li>
<li><p>Upgrading <a class="reference internal" href="#tutorials-upgrade-v4"><span class="std std-ref">from SeisComP3 to SeisComP in version 4.0.0. or higher</span></a>.</p></li>
<li><p>Upgrading <a class="reference internal" href="#tutorials-upgrade-seedlink"><span class="std std-ref">from SeisComP3 Jakarta-2018.327 or older to Jakarta-2020.330 or
SeisComP in version 4 or higher</span></a>.</p></li>
</ul>
<section id="seiscomp-versions">
<span id="tutorials-upgrade-versions"></span><h3>SeisComP versions<a class="headerlink" href="#seiscomp-versions" title="Permalink to this heading"></a></h3>
<p>SeisComP has <a class="reference internal" href="../history.html#history"><span class="std std-ref">developed over time</span></a>. The versions can be distinguished
by the name of the release:</p>
<ul>
<li><p><strong>SeisComP since version 4.0.0</strong> uses release version numbers such as <em>5.2.1</em>
where</p>
<ul class="simple">
<li><p>5: major version with changes in API and database schema version, new features,
bug fixed, optimizations,</p></li>
<li><p>2: minor version with new features, bug fixed, optimizations,</p></li>
<li><p>1: patch number with bug fixes, optimizations.</p></li>
</ul>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>When increasing the major version number, an upgrade of
the database is required.</p>
</div>
</li>
<li><p><strong>SeisComP3</strong> uses release versions, names, numbers and patch numbers.</p>
<p>Full example: <em>SeisComP3-jakarta-2020.330.02</em></p>
<ul class="simple">
<li><p>3: release version</p></li>
<li><p>jakarta: release name</p></li>
<li><p>2020.330: release number</p></li>
<li><p>02: patch number</p></li>
</ul>
<p>Names are adjusted depending on changes in source code:</p>
<ul class="simple">
<li><p><strong>Release version:</strong> major changes in module groups, functionality, concepts, data model.
Example: SeisComp3 is SeisComP in version 3.0
in comparison to version 2.5 the GUIs were introduced.</p></li>
<li><p><strong>Release name:</strong> major changes in functionality, concepts, data model.
Example: with SeisComP3-Seattle the new user friendly configuration GUI <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>
was introduced.</p></li>
<li><p><strong>Release number:</strong> changes in data model version and/or major changes in applications and optimizations.
The numbers include the year and the day of the year of the software release.
Example: Jakarta-2018.327</p></li>
<li><p><strong>Patch number:</strong> optimizations of applications without changes in the data model version.</p></li>
</ul>
</li>
</ul>
<section id="upgrade-vs-update">
<h3>Upgrade vs. update<a class="headerlink" href="#upgrade-vs-update" title="Permalink to this heading"></a></h3>
<p>Here we understand that <em>upgrades</em> increase the major release version number
while <em>updates</em> only increase the minor version or the patch number, see section
<a class="reference internal" href="../installation.html#installation-versions"><span class="std std-ref">SeisComP Versions</span></a>.</p>
</section>
<section id="upgrade-seiscomp-on-multiple-machines">
<h3>Upgrade SeisComP on multiple machines<a class="headerlink" href="#upgrade-seiscomp-on-multiple-machines" title="Permalink to this heading"></a></h3>
<section id="upgrading-multiple-machines">
<h3>Upgrading multiple machines<a class="headerlink" href="#upgrading-multiple-machines" title="Permalink to this heading"></a></h3>
<p>Applications can only connect to a messaging system that runs with a database
in an equal or lower data base schema version. In distributed <cite>SeisComP</cite> systems
one machine host the messaging system and the database and all other machines
are connected to this messaging or are running independently, the <cite>SeisComP</cite>
installation on the machine operating the messaging is always updated last.</p>
in an equal or lower data base schema version. However, upgrading <cite>SeisComP</cite> to a
higher major release version typically increases the database scheme version.
Therefore, in distributed <cite>SeisComP</cite> systems where one machine hosts the messaging
system and the database and all other machines are connected to this messaging,
the <cite>SeisComP</cite> installation on the machine operating the messaging is always
upgraded last.</p>
<p><strong>Example:</strong> A distributed system includes a processing system with the
messaging system and database and a GUI work station connected to the processing
system:</p>
<ol class="arabic simple">
<li><p>Upgrade the GUI work station</p></li>
<li><p>Upgrade the processing system, take actions to
<a class="reference internal" href="#tutorials-upgrade-db"><span class="std std-ref">upgrade the database version</span></a>.</p></li>
<li><p><a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Upgrade</span></a> the GUI work station</p></li>
<li><p><a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Upgrade</span></a> the processing system, take actions
to <a class="reference internal" href="#tutorials-upgrade-db"><span class="std std-ref">upgrade the database version</span></a>.</p></li>
</ol>
<div class="admonition note">
<p class="admonition-title">Note</p>
@ -166,79 +134,39 @@ system:</p>
</div>
</div>
</section>
</section>
<section id="package-download">
<span id="tutorials-upgrade-download"></span><h2>Package Download<a class="headerlink" href="#package-download" title="Permalink to this heading"></a></h2>
<p>Get the SeisComP package in the latest version or older ones from gempa GmbH or
from the download website of <span id="id1">Helmholtz-Centre Potsdam - GFZ German Research Centre for Geosciences and gempa GmbH [<a class="reference internal" href="../references.html#id257" title="Helmholtz-Centre Potsdam - GFZ German Research Centre for Geosciences and gempa GmbH. The SeisComP seismological software package. GFZ Data Services. 2008. URL: https://www.seiscomp.de, doi:10.5880/GFZ.2.4.2020.003.">67</a>]</span>.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>gempa provides <span id="id2"><em>gsm - gempa software management tool</em> [<a class="reference internal" href="../references.html#id129" title="gsm - gempa software management tool. gempa solution. URL: https://data.gempa.de/packages/Public/gsm/.">29</a>]</span> for convenient and consistent download and
installation of SeisComP and other packages.</p>
</div>
<span id="tutorials-upgrade-download"></span><h3>Package download<a class="headerlink" href="#package-download" title="Permalink to this heading"></a></h3>
<p>Get and install the <cite>SeisComP</cite> package in the any available version from
<span id="id1"><em>gempa GmbH</em> [<a class="reference internal" href="../references.html#id147" title="gempa GmbH. The SeisComP development and maintenance company. URL: https://www.gempa.de.">31</a>]</span> or from the download website of <span id="id2">Helmholtz-Centre Potsdam - GFZ German Research Centre for Geosciences and gempa GmbH [<a class="reference internal" href="../references.html#id290" title="Helmholtz-Centre Potsdam - GFZ German Research Centre for Geosciences and gempa GmbH. The SeisComP seismological software package. GFZ Data Services. 2008. URL: https://www.seiscomp.de, doi:10.5880/GFZ.2.4.2020.003.">76</a>]</span> as described
in section <a class="reference internal" href="../installation.html#installation-packages"><span class="std std-ref">Installation of Packages</span></a>.</p>
</section>
<section id="documentation-of-changes">
<span id="tutorials-upgrade-changelog"></span><h2>Documentation of Changes<a class="headerlink" href="#documentation-of-changes" title="Permalink to this heading"></a></h2>
<p>The important novelties, optimizations and changes that are available after upgrading
are documented in the change log which can be read
<a class="reference external" href="https://www.seiscomp.de/doc/base/changelog.html">online</a>.
It is recommend to read the change log before taking further actions.</p>
<p>The details can also be found locally in the file</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span><span class="nv">$SEISCOMP_ROOT</span>/share/doc/seiscomp/CHANGELOG
</pre></div>
</div>
<p>which is integrated in the <a class="reference internal" href="../changelog.html#sc-changelog"><span class="std std-ref">documentation</span></a> or accessible
from the <em>Docs</em> panel in <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>.</p>
<span id="tutorials-upgrade-changelog"></span><h3>Documentation of changes<a class="headerlink" href="#documentation-of-changes" title="Permalink to this heading"></a></h3>
<p>The important novelties, optimizations and changes that are available after
upgrading are documented in the Changelog which is part of this documentation
and which can also be accessed through the <em>Docs</em> panel of <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>.
The installed locally installed file is
<code class="file docutils literal notranslate"><span class="pre">$SEISCOMP_ROOT/share/doc/seiscomp/CHANGELOG</span></code>
The Changelog can also be read
<a class="reference external" href="https://www.seiscomp.de/doc/base/changelog.html">online</a> but care should be
take that the version number matches your.´</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>New features are regularly advertised and described in detail on the
<a class="reference external" href="https://www.gempa.de/news/">News website of gempa GmbH</a> and on the
<span id="id3"><em>SeisComP forum</em> [<a class="reference internal" href="../references.html#id256" title="SeisComP forum. GFZ. URL: https://forum.seiscomp.de/.">24</a>]</span>.</p>
<p>New major release with the features are regularly advertised and described in
detail on the <a class="reference external" href="https://www.gempa.de/news/">News website of gempa GmbH</a> and
on the <span id="id3"><em>SeisComP forum</em> [<a class="reference internal" href="../references.html#id289" title="SeisComP forum. GFZ. URL: https://forum.seiscomp.de/.">26</a>]</span>.</p>
</div>
</section>
<section id="normal-upgrade">
<span id="tutorials-upgrade-normal"></span><h2>Normal Upgrade<a class="headerlink" href="#normal-upgrade" title="Permalink to this heading"></a></h2>
<p>The normal upgrade including upgrading the major version of SeisComP takes only
a few steps:</p>
<ol class="arabic">
<li><p><a class="reference internal" href="#tutorials-upgrade-download"><span class="std std-ref">Download</span></a> the SeisComP package.</p></li>
<li><p>Stop all SeisComP modules:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>stop
</pre></div>
</div>
</li>
<li><p>Install the new packages.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>Users of external, e.g., <cite>gempa</cite> modules must ensure that these external
modules match the SeisComP release version if they depend on SeisComP
libraries.</p>
</div>
</li>
<li><p>Test the database schema version and update bindings</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config
</pre></div>
</div>
<p><a class="reference internal" href="#tutorials-upgrade-db"><span class="std std-ref">Upgrade the database schema version</span></a> if
mismatches are reported.</p>
</li>
<li><p>After a successful upgrade, start all modules again and observe the status:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>start
seiscomp<span class="w"> </span>status<span class="w"> </span>started
</pre></div>
</div>
</li>
</ol>
</section>
<section id="upgrade-database-schema-version">
<span id="tutorials-upgrade-db"></span><h2>Upgrade database schema version<a class="headerlink" href="#upgrade-database-schema-version" title="Permalink to this heading"></a></h2>
<p>When installing a new SeisComP release with a higher major version number,
upgrading the database may be required. The database version will be tested and
the required actions will be shown when executing:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config
<span id="tutorials-upgrade-db"></span><h3>Upgrade database schema version<a class="headerlink" href="#upgrade-database-schema-version" title="Permalink to this heading"></a></h3>
<p>When upgrading <cite>SeisComP</cite> to a higher major version number as set out in section
<a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Update/Upgrade</span></a>, upgrading the database schema is typically
required, too. The database version will be tested and the required actions will
be reported when executing:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config**Special<span class="w"> </span><span class="k">case</span>:**
</pre></div>
</div>
<p>or when pressing the Update Configuration button in scconfig.
<p>or when pressing the Update Configuration button in <a class="reference internal" href="../../apps/scconfig.html#scconfig"><span class="std std-ref">scconfig</span></a>.
An upgrade from version SeisComP3 jakarta-2017.334 to SeisComP in version 5.1.0
will give, e.g.:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config
@ -253,13 +181,24 @@ INFO:<span class="w"> </span>checking<span class="w"> </span>DB<span class="w">
<span class="w"> </span>*<span class="w"> </span>migration<span class="w"> </span>to<span class="w"> </span>the<span class="w"> </span>current<span class="w"> </span>version<span class="w"> </span>is<span class="w"> </span>required.<span class="w"> </span>apply<span class="w"> </span>the<span class="w"> </span>following
<span class="w"> </span>scripts<span class="w"> </span><span class="k">in</span><span class="w"> </span>exactly<span class="w"> </span>the<span class="w"> </span>given<span class="w"> </span>order:
<span class="w"> </span>*<span class="w"> </span>mysql<span class="w"> </span>-u<span class="w"> </span>sysop<span class="w"> </span>-p<span class="w"> </span>-D<span class="w"> </span>seiscomp<span class="w"> </span>-h<span class="w"> </span>localhost<span class="w"> </span>&lt;<span class="w"> </span>/home/sysop/seiscomp/share/db/migrations/mysql/0_10_to_0_11.sql
<span class="w"> </span>*<span class="w"> </span>mysql<span class="w"> </span>-u<span class="w"> </span>sysop<span class="w"> </span>-p<span class="w"> </span>-D<span class="w"> </span>seiscomp<span class="w"> </span>-h<span class="w"> </span>localhost<span class="w"> </span>&lt;<span class="w"> </span>/home/sysop/seiscomp/share/db/migrations/mysql/0_11_to_0_12.sql
error:<span class="w"> </span>updating<span class="w"> </span>configuration<span class="w"> </span><span class="k">for</span><span class="w"> </span>scmaster<span class="w"> </span>failed
<span class="w"> </span>*<span class="w"> </span>mysql<span class="w"> </span>-u<span class="w"> </span>sysop<span class="w"> </span>-p<span class="w"> </span>-D<span class="w"> </span>seiscomp<span class="w"> </span>-h<span class="w"> </span>l
</pre></div>
</div>
<p>The shown migration scripts can be used directly as given and in the given order:</p>
<dl class="simple">
<dt><a href="#id4"><span class="problematic" id="id5">**</span></a>Special case:<a href="#id6"><span class="problematic" id="id7">**</span></a>ocalhost &lt; /home/sysop/seiscomp/share/db/migrations/mysql/0_11_to_0_12.sql</dt><dd><p>error: updating configuration for scmaster failed</p>
</dd>
</dl>
<p>The shown migration scripts can be used directly as given and in the given
order but you need to first stop all modules writing to or deleting objects from
the database such as <a class="reference internal" href="../../apps/scmaster.html#scmaster"><span class="std std-ref">scmaster</span></a>, <a class="reference internal" href="../../apps/scdb.html#scdb"><span class="std std-ref">scdb</span></a>, <a class="reference internal" href="../../apps/scardac.html#scardac"><span class="std std-ref">scardac</span></a> or
<a class="reference internal" href="../../apps/scdbstrip.html#scdbstrip"><span class="std std-ref">scdbstrip</span></a> running on the same or any connected machine, e.g.</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>stop<span class="w"> </span>scmaster
</pre></div>
</div>
<p><strong>Special case:</strong>
Thereafter, apply the migration according to your database:</p>
<ul>
<li><p>MySQL / MariaDB:</p>
<li><p>MySQL/MariaDB:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>mysql<span class="w"> </span>-u<span class="w"> </span>sysop<span class="w"> </span>-p<span class="w"> </span>-D<span class="w"> </span>seiscomp<span class="w"> </span>-h<span class="w"> </span>localhost<span class="w"> </span>&lt;<span class="w"> </span>/home/sysop/seiscomp/share/db/migrations/mysql/0_10_to_0_11.sql
mysql<span class="w"> </span>-u<span class="w"> </span>sysop<span class="w"> </span>-p<span class="w"> </span>-D<span class="w"> </span>seiscomp<span class="w"> </span>-h<span class="w"> </span>localhost<span class="w"> </span>&lt;<span class="w"> </span>/home/sysop/seiscomp/share/db/migrations/mysql/0_11_to_0_12.sql
</pre></div>
@ -273,31 +212,81 @@ psql<span class="w"> </span>-U<span class="w"> </span>sysop<span class="w"> </sp
</li>
</ul>
<p>Using the migration scripts provides a more user friendly way than copying the
lines of MySQL code from the changelog. In future versions we might add the option
lines of MySQL code from the changelog which was practise in past SeisComP3
versions. In future versions we might add the option
to automatically run the migrations.</p>
<div class="admonition warning">
<p class="admonition-title">Warning</p>
<p>Upgrading the database make take some time. Do no interrupt the process!
During this time, the <cite>SeisComP</cite> messaging system is unavailable causing a downtime of the system.</p>
During this time, the <cite>SeisComP</cite> messaging system is unavailable causing a
downtime of the system.</p>
</div>
<p>After applying the migration scripts the database should be at the correct version.
Test again with:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config
</pre></div>
</div>
<p>After successfully upgrading the database continue your previous upgrade procedure.</p>
<p>After successfully upgrading the database continue your previous upgrade
procedure.</p>
</section>
<section id="seiscomp3-to-version-4">
<span id="tutorials-upgrade-v4"></span><h2>SeisComP3 to version &gt;=4<a class="headerlink" href="#seiscomp3-to-version-4" title="Permalink to this heading"></a></h2>
<p>SeisComP in version 4 has some major differences to SeisComP3 which require adjustments.
The main differences are in the <a class="reference internal" href="#sec-tutorials-upgrading-path"><span class="std std-ref">directories of the SeisComP installation</span></a>
</section>
<section id="normal-update-upgrade">
<span id="tutorials-upgrade-normal"></span><h2>Normal Update/Upgrade<a class="headerlink" href="#normal-update-upgrade" title="Permalink to this heading"></a></h2>
<p>Normal updates/upgrades of the major version of <cite>SeisComP</cite> takes only a few steps:</p>
<ol class="arabic">
<li><p>If you are tracking your <cite>SeisComP</cite> installation using <strong class="program">git</strong>
(recommended), ensure all previous changes are committed and the installation
is clean.</p></li>
<li><p>Stop all SeisComP modules:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>stop
</pre></div>
</div>
</li>
<li><p>Download and install the <cite>SeisComP</cite> package as described in section
<a class="reference internal" href="../installation.html#installation-packages"><span class="std std-ref">Installation of Packages</span></a>.</p></li>
<li><p>Understand the Changelog of the installed <cite>SeisComP</cite> as described in section
<a class="reference internal" href="#tutorials-upgrade-changelog"><span class="std std-ref">Documentation of changes</span></a>.</p></li>
<li><p>Infrequently configuration parameters require changes which
are documented in the Changelog. You may also scan your configuration for
deprecated or obsolete configuration parameters or values using
<a class="reference external" href="https://data.gempa.de/packages/Public/tools/">gempa-checkSCconfig.py</a>
provided by <span id="id8"><em>gempa GmbH</em> [<a class="reference internal" href="../references.html#id147" title="gempa GmbH. The SeisComP development and maintenance company. URL: https://www.gempa.de.">31</a>]</span>. Apply changes accordingly.</p></li>
<li><p>The software dependencies may have changed after upgrading. Install them as
described in section <a class="reference internal" href="../installation.html#software-dependencies"><span class="std std-ref">Software Dependencies</span></a>.</p></li>
<li><p>Test the database schema version and update bindings</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>update-config
</pre></div>
</div>
<p><a class="reference internal" href="#tutorials-upgrade-db"><span class="std std-ref">Upgrade the database schema version</span></a> if
mismatches are reported. The mismatch reports will also give the upgrade
instructions. Repeat <em>seiscomp update-config</em> after upgrading the database
schema version.</p>
<p><strong>Background:</strong> When upgrading the major <cite>SeisComP</cite> version you
typically need to upgrade the database scheme version.</p>
</li>
<li><p>After a successful update/upgrade, start all modules again and observe the
status:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>seiscomp<span class="w"> </span>start
seiscomp<span class="w"> </span>status<span class="w"> </span>started
</pre></div>
</div>
</li>
<li><p>If you are tracking your <cite>SeisComP</cite> installation using <strong class="program">git</strong>
(recommended), commit all changes.</p></li>
</ol>
</section>
<section id="upgrading-from-seiscomp3">
<span id="tutorials-upgrade-v4"></span><h2>Upgrading from SeisComP3<a class="headerlink" href="#upgrading-from-seiscomp3" title="Permalink to this heading"></a></h2>
<p>SeisComP in version &gt;=4 has major differences to SeisComP3 which require
adjustments. The main differences are in the
<a class="reference internal" href="#sec-tutorials-upgrading-path"><span class="std std-ref">directories of the SeisComP installation</span></a>
and the <a class="reference internal" href="#sec-tutorials-upgrading-messaging"><span class="std std-ref">messaging system</span></a>.
The changes and the required actions are explained below. They must be considered
in addition to the steps set out in section <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Upgrade</span></a>.</p>
in addition to the steps set out in section <a class="reference internal" href="#tutorials-upgrade-normal"><span class="std std-ref">Normal Update/Upgrade</span></a>.</p>
<section id="files-and-directories">
<span id="sec-tutorials-upgrading-path"></span><h3>Files and directories<a class="headerlink" href="#files-and-directories" title="Permalink to this heading"></a></h3>
<p>With <strong>SeisComP3</strong> all the default installation typically required all modules and configurations
in the directories</p>
<p>With <strong>SeisComP3</strong> all the default installation typically required all modules
and configurations in the directories</p>
<ul class="simple">
<li><p>seiscomp3/ , typically $HOME/seiscomp3 or /opt/seiscomp3/</p></li>
<li><p>$HOME/.seiscomp3/</p></li>
@ -419,13 +408,13 @@ new groups in the configuration of queues</p>
</pre></div>
</div>
</li>
<li><p>Set groups per queue in <a class="reference internal" href="../../apps/scmaster.html#confval-queues.-name.groups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">queues.$name.groups</span></code></a>,
<li><p><strong>Special case:</strong> Set groups per queue in <a class="reference internal" href="../../apps/scmaster.html#confval-queues.-name.groups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">queues.$name.groups</span></code></a>,
ignoring groups in <a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a></p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">queues.production.groups</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">L1PICK, L1LOCATION, AMPLITUDE, PICK, LOCATION, MAGNITUDE, FOCMECH, EVENT, QC, PUBLICATION, GUI, INVENTORY, ROUTING, CONFIG, LOGGING, IMPORT_GROUP, SERVICE_REQUEST, SERVICE_PROVIDE</span>
</pre></div>
</div>
</li>
<li><p>Set groups in <a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a></p>
<li><p><strong>Special case:</strong> Set groups in <a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a></p>
<div class="highlight-properties notranslate"><div class="highlight"><pre><span></span><span class="na">defaultGroups</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">L1PICK, L1LOCATION, AMPLITUDE, PICK, LOCATION, MAGNITUDE, FOCMECH, EVENT, QC, PUBLICATION, GUI, INVENTORY, ROUTING, CONFIG, LOGGING, IMPORT_GROUP, SERVICE_REQUEST, SERVICE_PROVIDE</span>
</pre></div>
</div>
@ -434,9 +423,9 @@ ignoring groups in <a class="reference internal" href="../../apps/scmaster.html#
<div class="admonition warning">
<p class="admonition-title">Warning</p>
<p>When setting groups in the queues all groups configured in
<a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a> will be ignored unless <cite>${defaultGroups}</cite> is used.
Add all groups from <a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a> to the queues to keep the
default groups.</p>
<a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a> will be ignored unless <cite>${defaultGroups}</cite> is
used. Add all groups from <a class="reference internal" href="../../apps/scmaster.html#confval-defaultGroups"><code class="xref std std-confval docutils literal notranslate"><span class="pre">defaultGroups</span></code></a> to the queues to
keep the default groups.</p>
</div>
</li>
<li><p>Add the interface name, currently only <em>dbstore</em> is supported. Example for
@ -490,9 +479,8 @@ is <em>production</em>, e.g.</p>
</section>
<section id="seedlink">
<h3>Seedlink<a class="headerlink" href="#seedlink" title="Permalink to this heading"></a></h3>
<p>When upgrading from SeisComp3 Jakrata-2018.327 or older and using <a class="reference internal" href="../../apps/seedlink.html#seedlink"><span class="std std-ref">seedlink</span></a>,
consider the sections <a class="reference internal" href="#tutorials-upgrade-seedlink"><span class="std std-ref">SeedLink buffer</span></a> and
<a class="reference internal" href="#tutorials-proc-seedlink"><span class="std std-ref">SeedLink stream processor</span></a>.</p>
<p>When upgrading from SeisComp3 in version Jakrata-2018.327 or older and using
<a class="reference internal" href="../../apps/seedlink.html#seedlink"><span class="std std-ref">seedlink</span></a>, consider the section <a class="reference internal" href="#tutorials-upgrade-2018-327"><span class="std std-ref">Upgrading From SeisComP3 &lt;= Jakarta-2018.327</span></a>.</p>
</section>
<section id="automatic-module-check">
<h3>Automatic module check<a class="headerlink" href="#automatic-module-check" title="Permalink to this heading"></a></h3>
@ -509,8 +497,8 @@ modules automatically during computer startup, then the startup script must be
adjusted.</p>
</section>
</section>
<section id="upgrade-from-seiscomp3-jakarta-2018-327-or-before">
<h2>Upgrade From SeisComP3 Jakarta-2018.327 or Before<a class="headerlink" href="#upgrade-from-seiscomp3-jakarta-2018-327-or-before" title="Permalink to this heading"></a></h2>
<section id="upgrading-from-seiscomp3-jakarta-2018-327">
<span id="tutorials-upgrade-2018-327"></span><h2>Upgrading From SeisComP3 &lt;= Jakarta-2018.327<a class="headerlink" href="#upgrading-from-seiscomp3-jakarta-2018-327" title="Permalink to this heading"></a></h2>
<section id="seedlink-buffer">
<span id="tutorials-upgrade-seedlink"></span><h3>SeedLink buffer<a class="headerlink" href="#seedlink-buffer" title="Permalink to this heading"></a></h3>
<p>In SeisComP3 prior to Jakarta-2020.330 two stations with the same
@ -576,7 +564,7 @@ grep<span class="w"> </span>-A<span class="w"> </span><span class="m">2</span><s
<span class="w"> </span><span class="nv">net</span><span class="o">=</span><span class="s2">&quot;&quot;</span>
<span class="w"> </span><span class="k">while</span><span class="w"> </span><span class="nb">read</span><span class="w"> </span>a<span class="w"> </span>b<span class="w"> </span>c<span class="p">;</span><span class="w"> </span><span class="k">do</span>
<span class="w"> </span><span class="k">case</span><span class="w"> </span><span class="nv">$a</span><span class="w"> </span><span class="k">in</span>
<span class="w"> </span>--<span class="o">)</span><span class="w"> </span><span class="k">break</span><span class="p">;;</span>
<span class="w"> </span>--<span class="o">)</span><span class="w"> </span><span class="k">break</span><span class="p">;;</span>tutorials_upgrade_seedlink
<span class="w"> </span>name<span class="o">)</span><span class="w"> </span><span class="nb">eval</span><span class="w"> </span><span class="nv">sta</span><span class="o">=</span><span class="nv">$c</span><span class="p">;;</span>
<span class="w"> </span>network<span class="o">)</span><span class="w"> </span><span class="nb">eval</span><span class="w"> </span><span class="nv">net</span><span class="o">=</span><span class="nv">$c</span><span class="p">;;</span>
<span class="w"> </span><span class="k">esac</span>
@ -625,8 +613,8 @@ was used. This means when upgrading:</p>
data is generated (<a class="reference internal" href="../../apps/seedlink.html#confval-sources.chain.channels.unpack"><code class="xref std std-confval docutils literal notranslate"><span class="pre">sources.chain.channels.unpack</span></code></a>).</p>
</div>
</section>
<section id="id4">
<h4>Background<a class="headerlink" href="#id4" title="Permalink to this heading"></a></h4>
<section id="id9">
<h4>Background<a class="headerlink" href="#id9" title="Permalink to this heading"></a></h4>
<p>A stream processor is an object defined in XML, which is used to create MiniSEED
from raw data and optionally downsample the data. What is the difference between
attaching a stream processor to station and plugin instance?</p>
@ -681,17 +669,17 @@ LH* and VH* and the other one producing BN* and so on.</p>
<div>
<h3><a href="../../index.html">Table of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Upgrading SeisComP</a><ul>
<li><a class="reference internal" href="#">Updating/Upgrading SeisComP</a><ul>
<li><a class="reference internal" href="#background">Background</a><ul>
<li><a class="reference internal" href="#seiscomp-versions">SeisComP versions</a></li>
<li><a class="reference internal" href="#upgrade-seiscomp-on-multiple-machines">Upgrade SeisComP on multiple machines</a></li>
<li><a class="reference internal" href="#upgrade-vs-update">Upgrade vs. update</a></li>
<li><a class="reference internal" href="#upgrading-multiple-machines">Upgrading multiple machines</a></li>
<li><a class="reference internal" href="#package-download">Package download</a></li>
<li><a class="reference internal" href="#documentation-of-changes">Documentation of changes</a></li>
<li><a class="reference internal" href="#upgrade-database-schema-version">Upgrade database schema version</a></li>
</ul>
</li>
<li><a class="reference internal" href="#package-download">Package Download</a></li>
<li><a class="reference internal" href="#documentation-of-changes">Documentation of Changes</a></li>
<li><a class="reference internal" href="#normal-upgrade">Normal Upgrade</a></li>
<li><a class="reference internal" href="#upgrade-database-schema-version">Upgrade database schema version</a></li>
<li><a class="reference internal" href="#seiscomp3-to-version-4">SeisComP3 to version &gt;=4</a><ul>
<li><a class="reference internal" href="#normal-update-upgrade">Normal Update/Upgrade</a></li>
<li><a class="reference internal" href="#upgrading-from-seiscomp3">Upgrading from SeisComP3</a><ul>
<li><a class="reference internal" href="#files-and-directories">Files and directories</a></li>
<li><a class="reference internal" href="#software-dependencies">Software dependencies</a></li>
<li><a class="reference internal" href="#system-variables">System variables</a></li>
@ -703,11 +691,11 @@ LH* and VH* and the other one producing BN* and so on.</p>
<li><a class="reference internal" href="#system-daemon">System daemon</a></li>
</ul>
</li>
<li><a class="reference internal" href="#upgrade-from-seiscomp3-jakarta-2018-327-or-before">Upgrade From SeisComP3 Jakarta-2018.327 or Before</a><ul>
<li><a class="reference internal" href="#upgrading-from-seiscomp3-jakarta-2018-327">Upgrading From SeisComP3 &lt;= Jakarta-2018.327</a><ul>
<li><a class="reference internal" href="#seedlink-buffer">SeedLink buffer</a></li>
<li><a class="reference internal" href="#seedlink-stream-processor">SeedLink stream processor</a><ul>
<li><a class="reference internal" href="#chain-plugin">chain plugin</a></li>
<li><a class="reference internal" href="#id4">Background</a></li>
<li><a class="reference internal" href="#id9">Background</a></li>
</ul>
</li>
</ul>
@ -746,7 +734,7 @@ LH* and VH* and the other one producing BN* and so on.</p>
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.

View File

@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Play back archived waveforms &#8212; SeisComP Release documentation</title>
<title>Play back archived waveforms &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
@ -12,21 +12,21 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
<link rel="search" title="Search" href="../../search.html" />
<link rel="next" title="Help! Im stuck! Now what?" href="help.html" />
<link rel="prev" title="Magnitudes: Regionalization, Aliases, Mw" href="magnitude-regionalization.html" />
<link rel="prev" title="Amplitudes/Magnitudes: Regionalization, Aliases, Mw" href="amplitudes-magnitudes.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">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@ -49,7 +49,7 @@
</a>
</li>
<li class="right">
<a href="magnitude-regionalization.html" title="Magnitudes: Regionalization, Aliases, Mw"
<a href="amplitudes-magnitudes.html" title="Amplitudes/Magnitudes: Regionalization, Aliases, Mw"
accesskey="P">
previous
</a>
@ -136,14 +136,14 @@ data are initially sorted by station and must therefore be sorted by end time
using <a class="reference internal" href="../../apps/scmssort.html#scmssort"><span class="std std-ref">scmssort</span></a>. Use the resulting file <code class="file docutils literal notranslate"><span class="pre">[your</span> <span class="pre">miniSEED</span> <span class="pre">file]</span></code>
for your playback.</p>
<p>Example for one hour of data from the GE network from
<a class="reference external" href="https://geofon.gfz-potsdam.de/waveform/webservices/fdsnws.php">FDSNWS at GEOFON</a>:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>wget<span class="w"> </span>-O<span class="w"> </span>data.mseed<span class="w"> </span><span class="s2">&quot;http://geofon.gfz-potsdam.de/fdsnws/dataselect/1/query?net=GE&amp;cha=BH*&amp;starttime=2021-04-01T06:00:00Z&amp;endtime=2021-04-01T07:00:00Z&quot;</span>
<a class="reference external" href="https://geofon.gfz.de/waveform/webservices/fdsnws.php">FDSNWS at GEOFON</a>:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>wget<span class="w"> </span>-O<span class="w"> </span>data.mseed<span class="w"> </span><span class="s2">&quot;http://geofon.gfz.de/fdsnws/dataselect/1/query?net=GE&amp;cha=BH*&amp;starttime=2021-04-01T06:00:00Z&amp;endtime=2021-04-01T07:00:00Z&quot;</span>
scmssort<span class="w"> </span>-u<span class="w"> </span>-E<span class="w"> </span>data.mseed<span class="w"> </span>&gt;<span class="w"> </span><span class="o">[</span>your<span class="w"> </span>miniSEED<span class="w"> </span>file<span class="o">]</span>
</pre></div>
</div>
</li>
<li><p><strong>CAPS server:</strong> Extract the data from gempas CAPS server <span id="id1">[<a class="reference internal" href="../references.html#id91" title="CAPS. gempa module. URL: https://docs.gempa.de/caps/current/index.html.">3</a>]</span>
using <span id="id2"><em>capstool</em> [<a class="reference internal" href="../references.html#id94" title="capstool. gempa plugin. URL: https://docs.gempa.de/caps/current/apps/capstool.html.">27</a>]</span>:</p>
<li><p><strong>CAPS server:</strong> Extract the data from gempas CAPS server <span id="id1">[<a class="reference internal" href="../references.html#id116" title="CAPS. gempa module. URL: https://docs.gempa.de/caps/current/index.html.">3</a>]</span>
using <span id="id2"><em>capstool</em> [<a class="reference internal" href="../references.html#id119" title="capstool. gempa plugin. URL: https://docs.gempa.de/caps/current/apps/capstool.html.">30</a>]</span>:</p>
<div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>capstool<span class="w"> </span>-H<span class="w"> </span><span class="o">[</span>host<span class="o">]</span>:<span class="o">[</span>port<span class="o">]</span><span class="w"> </span><span class="o">[</span>request<span class="w"> </span>file<span class="o">]</span><span class="w"> </span>&gt;<span class="w"> </span>data.mseed
</pre></div>
</div>
@ -317,8 +317,8 @@ brackets, e.g. [your file]</p>
</div>
<div>
<h4>Previous topic</h4>
<p class="topless"><a href="magnitude-regionalization.html"
title="previous chapter">Magnitudes: Regionalization, Aliases, Mw</a></p>
<p class="topless"><a href="amplitudes-magnitudes.html"
title="previous chapter">Amplitudes/Magnitudes: Regionalization, Aliases, Mw</a></p>
</div>
<div>
<h4>Next topic</h4>
@ -344,7 +344,7 @@ brackets, e.g. [your file]</p>
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.

View File

@ -4,7 +4,7 @@
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Get real-time data from a remote Seedlink server (single station) &#8212; SeisComP Release documentation</title>
<title>Get real-time data from a remote Seedlink server (single station) &#8212; SeisComP Development 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/pygments.css?v=72bcf2f2" />
@ -12,12 +12,12 @@
<link rel="stylesheet" type="text/css" href="../../_static/graphviz.css?v=eafc0fe6" />
<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 data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=823bb831"></script>
<script data-url_root="../../" id="documentation_options" src="../../_static/documentation_options.js?v=744d344a"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=4825356b"></script>
<link rel="index" title="Index" href="../../genindex.html" />
<link rel="search" title="Search" href="../../search.html" />
<link rel="next" title="Set up local waveform archiving" href="archiving.html" />
<link rel="next" title="Maintain waveform archives" href="archiving.html" />
<link rel="prev" title="Add a new station" href="addstation.html" />
</head>
<body>
@ -25,8 +25,8 @@
<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">6.9.0</span>
<!-- span class="title">SeisComP Development</span -->
<span class="version">7.0.0</span>
</div>
</div>
</div>
@ -43,7 +43,7 @@
</a>
</li>
<li class="right">
<a href="archiving.html" title="Set up local waveform archiving"
<a href="archiving.html" title="Maintain waveform archives"
accesskey="N">
next
</a>
@ -88,7 +88,7 @@ which is already in inventory.</p>
</ul>
<p>Related tutorial(s):</p>
<ul class="simple">
<li><p><a class="reference internal" href="archiving.html#tutorials-archiving"><span class="std std-ref">Set up local waveform archiving</span></a></p></li>
<li><p><a class="reference internal" href="archiving.html#tutorials-archiving"><span class="std std-ref">Maintain waveform archives</span></a></p></li>
<li><p><a class="reference internal" href="servefdsnws.html#tutorials-servefdsnws"><span class="std std-ref">Enable local FDSNWS server</span></a></p></li>
<li><p><a class="reference internal" href="addstation.html#tutorials-addstation"><span class="std std-ref">Add a new station</span></a></p></li>
</ul>
@ -101,9 +101,9 @@ from GEOFON, IRIS, or some other public source.</p>
to confirm that it has current data.
We do this with SeisComPs <strong class="program">slinktool</strong> command,
giving it the -L option to list the available stations.
For this example, well use the server at host <cite>geofon.gfz-potsdam.de</cite>
For this example, well use the server at host <cite>geofon.gfz.de</cite>
on port 18000 (the default)</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ slinktool -L geofon.gfz-potsdam.de
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ slinktool -L geofon.gfz.de
AW VNA1 VNA1
AW VNA2 VNA2
[..]
@ -117,7 +117,7 @@ GR CLZ CLZ
<p>This can be a long list. It shows the network code and station code of each
of the stations for which data is available from this Seedlink server.
We can restrict the output to our station of interest using <cite>grep</cite>.</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ slinktool -Q geofon.gfz-potsdam.de | grep GR.CLL
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>$ slinktool -Q geofon.gfz.de | grep GR.CLL
GR CLL LHN D 2020/05/06 15:13:41.2249 - 2020/05/06 21:15:28.0299
GR CLL BHZ D 2020/05/06 15:13:41.2249 - 2020/05/06 21:22:13.1300
GR CLL BHN D 2020/05/06 15:13:41.2249 - 2020/05/06 21:22:15.4300
@ -157,8 +157,8 @@ The documentation for <strong class="program">seedlink</strong> gives details.</
<li><p>Double click on the profile.</p></li>
<li><p>Select the chain plugin for the souce from the drop-down menu</p></li>
<li><p>To add the plugin click on the green “plus” button on the left. Name it anything or even leave the name blank.</p></li>
<li><p>Open this and set the name of the server (<a class="reference internal" href="../../apps/slmon.html#confval-address"><code class="xref std std-confval docutils literal notranslate"><span class="pre">address</span></code></a>)
and its TCP port, <a class="reference internal" href="../../apps/slmon.html#confval-port"><code class="xref std std-confval docutils literal notranslate"><span class="pre">port</span></code></a>. Normally you leave the port at 18000 which is the default.</p></li>
<li><p>Open this and set the name of the server (<a class="reference internal" href="../../apps/slmon2.html#confval-address"><code class="xref std std-confval docutils literal notranslate"><span class="pre">address</span></code></a>)
and its TCP port, <a class="reference internal" href="../../apps/slmon2.html#confval-port"><code class="xref std std-confval docutils literal notranslate"><span class="pre">port</span></code></a>. Normally you leave the port at 18000 which is the default.</p></li>
<li><p>If you wish to limit the data requested to particular channels,
based on channel or location code,
set Seedlinks <a class="reference internal" href="../../apps/seedlink.html#confval-sources.chain.selectors"><code class="xref std std-confval docutils literal notranslate"><span class="pre">selectors</span></code></a> to “BH?.D” say
@ -260,7 +260,7 @@ you can follow the same procedure for other networks/stations, provided you</p>
<div>
<h4>Next topic</h4>
<p class="topless"><a href="archiving.html"
title="next chapter">Set up local waveform archiving</a></p>
title="next chapter">Maintain waveform archives</a></p>
</div>
<div role="note" aria-label="source link">
<h3>This Page</h3>
@ -281,7 +281,7 @@ you can follow the same procedure for other networks/stations, provided you</p>
</a>
<div class="stretched align-center fitted content">
<div>
Version <b>6.9.0</b> Release
Version <b>7.0.0</b> Development
</div>
<div class="copyright">
Copyright &copy; gempa GmbH, GFZ Potsdam.