<ol><li><a href="#ChangelogReleaseSeattle2013.200">Changelog Release Seattle 2013.200</a><ol><li><a href="#General">General</a><ol><li><a href="#Schema">Schema</a></li><li> <a href="#Documentation">Documentation</a></li></ol></li><li> <a href="#Newapps">New apps</a><ol><li><a href="#VSpackage">VS package</a></li></ol></li><li> <a href="#Changes">Changes</a><ol><li><a href="#Applications">Applications</a></li><li> <a href="#slarchive">slarchive</a></li><li> <a href="#scimex">scimex</a></li><li> <a href="#scconfig">scconfig</a></li><li> <a href="#scxmldump">scxmldump</a></li><li> <a href="#scinv">scinv</a></li><li> <a href="#dlsv2inv">dlsv2inv</a></li><li> <a href="#sc2pa">sc2pa</a></li><li> <a href="#scevent">scevent</a></li><li> <a href="#scautoloc">scautoloc</a></li><li> <a href="#spread">spread</a></li><li> <a href="#sdsarchiverecordstream">sdsarchive record stream</a></li><li> <a href="#seiscomp">seiscomp</a></li><li> <a href="#scwfparam">scwfparam</a></li><li> <a href="#scqcscqcvscrttvscmv">scqc, scqcv, scrttv, scmv</a></li><li> <a href="#GUIeventlist">GUI event list</a></li><li> <a href="#GUImaps">GUI maps</a></li><li> <a href="#AmplitudeProcessor">Amplitude Processor</a></li><li> <a href="#scolv">scolv</a></li></ol></li></ol></li></ol>

Changelog Release Seattle 2013.200




New apps

VS package












Autoloc tries to find out when the depth of a location is well enough constrained by the data. If that is the case, the depth is determined by the locator. If not, the configured default depth is used. You might want to control this behaviour. Therefore, a parameter autoloc.defaultDepthStickiness was introduced. It may range between 0 and 1. In principle, 0 means always free depth, no stickiness to the default depth. This is NOT yet available. Only the other extreme of 1 was implemented now, meaning "always stick to the default depth no matter what". This was needed by Akiko To as well as Saeed Soltani Moghaddam from Iran following the large event of April 16th. If this stickiness is left unchanged, nothing in the autoloc behaviour will change. The completely free depth is on the to-do list still, with low priority.

Actually besides using the absolute amplitude to determine if a pick should be considered an "XXL pick", there used to be an additional check of the SNR hardcoded into autoloc. The SNR had to be 8 at least, which makes perfectly sense for an unusually large earthquake, for which the XXL feature is intended to be used exclusively.

The new parameters to control the XXL feature are as follows (old parameter names are still supported by deprecated):

   # Arrivals with exceptionally large amplitudes may be flagged as XXL,
   # allowing faster, preliminary "heads-up" alerts. This is the minimum 
   # amplitude.
   autoloc.xxl.minAmplitude = ...

   # Minimum SNR for a pick to be flagged as XXL. NOTE that BOTH minAmplitude 
   # and minSNR need to be exceeded!
   autoloc.xxl.minSNR = ...

   # Minimum number of XXL phases. Currently the minimum possible value is 4.
   autoloc.xxl.minPhaseCount = ...

   # XXL picks from stations beyond maxDistanceXXL are ignored (for XXL alerts).
   autoloc.xxl.maxStationDistance = ...

   # Only up to this depth XXL preliminary origins may be created.
   autoloc.xxl.maxDepth = ...


sdsarchive record stream



scqc, scqcv, scrttv, scmv

GUI event list

GUI maps

Amplitude Processor