This repository was archived by the owner on May 10, 2023. It is now read-only.
Release 2018.327 patch15
·
129 commits
to build/jakarta/2018.327
since this release
Release 2018.327 patch15
-
fdsnws
- Reduce QuakeML exporter warnings: do not report a warning if the event does not reference
a preferred magnitude and reduce log level of event type mapping from warning to debug - Expose matchtimeseries WADL parameter only if data availability information is enabled
via config - Disable data availability information by default
- Add request logging for dataselect
- Reduce QuakeML exporter warnings: do not report a warning if the event does not reference
-
seedlink
- Fix duplicate mapping detection in scream_plugin_ring plugin. Whenever a duplicate stream
id was given then it was ignored regardless of the attached sysid. - Work around EarthData WNRO bug
- Fix duplicate mapping detection in scream_plugin_ring plugin. Whenever a duplicate stream
-
scolv
- Fix event type list preparation in combination with
olv.commonEventTypes.
- Fix event type list preparation in combination with
-
ql2sc
- Enable sending of keep-alive messages by default. This prevents connection resets by firewall
on long idle periods. - Fix bug that prevents forwarding updates if the routing must be resolved via the parent object
which hasn't updated. A workaround is to explicitly specify routing rules on all object levels. - Add event attribute synchronization per input host
- Enable sending of keep-alive messages by default. This prevents connection resets by firewall
-
python-apps
- Add simple script to dump public objects
-
Nuttli magnitude
- Fix phase priority parsing and fix crash
- Do not apply default uncertainties to Vmin/Vmax·
-
scdispatch
- Fix routing table lookup when dealing with merge operation
-
trunk
- Migration scripts for scwfparam db extension added thanks to Philipp Kaestli / ETHZ
- Fix LocSAT locator implementation to correctly send the initial hypocenter
parameters to libloc
-
scmag
- Avoid setting a network magnitude to NaN (not supported with any database)
and use 0 instead. In order to detect if a network magnitude is valid one could
use the station count (0 == invalid). But that is in general a hack for the
time being and the correct solution is to naje the Magnitude.value an
optional quantity.
- Avoid setting a network magnitude to NaN (not supported with any database)
-
GUI
- Improve spectrogram rendering speed
- Normalize spectrogram spectral amplitudes with respect to
sampling rate