|
|
|
## Waveform Data
|
|
|
|
|
|
|
|
REDPy reads and processes continuous timeseries of waveforms from any format that [ObsPy can read](https://docs.obspy.org/packages/autogen/obspy.core.stream.read.html), including but not strictly limited to seismic and acoustic data. Triggered data (i.e., small snippets of data around known events) may be used so long as they can be read, but with reduced utility. Users must specify in the [configuration file](#configuration-file) the source of the waveform data, which may be the path to files on a local disk, a local or remote waveserver (e.g. [Winston](https://volcanoes.usgs.gov/software/winston/index.shtml)), or [FDSN webservice](https://www.fdsn.org/datacenters/) (e.g., `IRIS`). The station, channel, network, and location codes for each channel of data to be incorporated must also be specified, and must match the metadata exactly—no wildcards are supported.
|
|
|
|
REDPy reads and processes continuous timeseries of waveforms from any format that [ObsPy can read](https://docs.obspy.org/packages/autogen/obspy.core.stream.read.html), including but not strictly limited to seismic and acoustic data. Triggered data (i.e., small snippets of data around known events) may be used so long as they can be read, but with reduced utility. Users must specify in the [configuration file](#configuration-file) the source of the waveform data, which may be the path to files on a local disk, a local or remote waveserver (e.g. [Winston](https://volcanoes.usgs.gov/software/winston/index.shtml)), or [FDSN webservice](https://www.fdsn.org/datacenters/) (e.g., IRIS). The station, channel, network, and location codes for each channel of data to be incorporated must also be specified, and must match the metadata exactly—no wildcards are supported.
|
|
|
|
|
|
|
|
## Configuration File
|
|
|
|
|
| ... | ... | @@ -16,9 +16,9 @@ Most of the default settings correspond to a possible run of the onset of the 20 |
|
|
|
The next most likely settings that may need changing are related to the outputs:
|
|
|
|
- Timeline: likely `minplot`, `recplot`, and `dybin` depending on the length of your run
|
|
|
|
- Family Plot: likely `printsta`
|
|
|
|
- If you wish to utilize the external catalog parameters with `checkcomcat=True`, you will likely need to change `stalats` and `stalons`.
|
|
|
|
- If you wish to utilize the external catalog parameters with `checkcomcat=True`, you will likely need to change `stalats` and `stalons`, and should evaluate the distance and magnitude thresholds appropriate for your dataset as well as whether you want to set `matchmax` to a value other than its default
|
|
|
|
|
|
|
|
Recommendations for further changes are included in the comments of `settings.cfg`.
|
|
|
|
Many other settings are configurable that are documented in the comments of `settings.cfg`, but some settings introduced in V1.0 that I like to use for my runs are: `merge_ratio=0.6`, `corr_nrecent=25`, `corr_nyoungest=25`, `corr_nlargest=50`, `use_nthcor=True`, and `corr_permit=0.1`.
|
|
|
|
|
|
|
|
## Optional Event Catalog
|
|
|
|
|
| ... | ... | |
| ... | ... | |