Software Downloads – SOD

Releases

Version 1 Breaklog 2 Language(s) Release date Group(s)

3.2.9

via. Philip Crotwell, USC:

Fixed issue with restricted data.

JAVA

2019-06-26

LS-USC

3.2.8

via. Philip Crotwell, USC:

Fixed issue with instrument response download when channel is active.

JAVA

2016-11-30

LS-USC

3.2.7

via. Philip Crotwell, USC:

Numerous small bug fixes and stability improvements.

JAVA

2016-07-06

LS-USC

3.2.6

via. Philip Crotwell, USC:

Fixed an issue with SOD and instrument responses relating to the loc id change.

JAVA

2015-05-22

LS-USC

3.2.5

via. Philip Crotwell, USC:

Fixed an issue with SOD and the way loc ids are done in the FDSN web
services and use the USGS FDSN Event web service as the default instead
of IRIS for event locations. Also now check for catalogs and
contributors that cannot work with the server. Lastly, SOD now batches
requests to the seismogram server if possible, resulting in a
noticable speed improvement, 2x in some cases.

JAVA

2015-03-25

LS-USC

3.2.2

This release fixes an issue with responses from FDSN web services.

JAVA

2013-07-25

LS-USC

Summary

Standing Order for Data (SOD) is a program that automates tedious data selection, downloading, and routine processing tasks in seismology.

Description

SOD allows you to define your desired data based on earthquakes, recording stations, and the resulting combination of information. SOD then retrieves the data that matches the criteria and applies any number of processing steps using processors included in SOD and ones you’ve written yourself. All of this works for historical data, but as the name says, you can specify a “standing order” with SOD. If your criteria stretch off into the future, SOD will run until that day gathering seismograms for earthquakes as they occur.

Categories

Conversion Programs , Data Access , Data Extraction

External Developers

  • Philip Crotwell, Lithospheric Seismology (LS-USC)

Tags

SOD

1 – Click the version release to view details about each package release including screenshots, manuals/how–to's, and revision histories. If more than one version is listed it means that a specific set of functionality was added or removed and legacy versions that preserve behaviors are archived.

2 – A list of changes that are not backwards compatible. More than one version of a package will be listed if this field has an entry.

22:21:06 v.01697673