You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* ``RfData`` objects are used to calculate single-station and single-event receiver
34
32
functions, whereas ``rf`` can handle multiple stations at once.
35
33
36
-
.. warning::
37
-
``RfPy`` was recently updated to fix a problem when running the scripts under Windows OS. The consequence is that version ``0.1.1`` will throw an error if the extension .py is specified when calling the scripts. The accompanying documentation also uses version ``0.2.1`` of ``StDb`` in the Tutorials section.
The main script packaged with ``RfPy`` uses FDSN web services through and ``ObsPy`` `Client` to load waveform data. For waveform data locally stored on your hard drive, the scripts can use a `Client` that reads a `SeisComP Data Structure <https://docs.obspy.org/packages/autogen/obspy.clients.filesystem.sds.html>`_ archive containing SAC or miniSEED waveform data. Check out the scripts ``rfpy_calc`` below and the argument ``--SDS-path`` and ``--dtype`` for more details.
90
+
91
+
Station Metadata
92
+
----------------
93
+
94
+
If you have data stored locally on your drive, it is likely you also
95
+
have a station `XML <https://www.fdsn.org/xml/station/>`_ file
96
+
containing the metadata. The corresponding ObsPy documentation is
You can now use a stationXML (`.xml`) file instead of the StDb `.pkl` format.
100
+
Alternatively, you can convert the stationXML file to an StDb `.pkl` file
101
+
by running the command ``gen_stdb station.xml`` (these options are only
102
+
available on StDb version 0.2.7. If you don't have a station `XML` file but you have
103
+
a dataless SEED file, you can convert it first to XML using `this tools <https://seiscode.iris.washington.edu/projects/stationxml-converter>`_.
104
+
105
+
.. note::
106
+
Please note that using the stationXML directly as input means you cannot
107
+
correct the orientation of H1 and H2 components using the azimuth correction term stored as ``azcorr`` in the StDb file, as this information is not stored in the stationXML file.
108
+
109
+
Waveform Data
110
+
-------------
111
+
112
+
The SDS folder containing the waveform data has the structure:
113
+
114
+
.. code-block:: python
115
+
116
+
archive
117
+
+ year
118
+
+ network code
119
+
+ station code
120
+
+ channel code +type
121
+
+ one file per day and location, e.g. NET.STA.LOC.CHAN.TYPE.YEAR.DOY
122
+
123
+
124
+
For example:
125
+
126
+
.. code-block:: python
127
+
128
+
SDS/
129
+
2014/
130
+
YH/
131
+
LOBS3/
132
+
HH1.D/
133
+
YH.LOBS3..CH1.D.2014.332
134
+
...
135
+
136
+
137
+
Note, the filename does not include the extension (`.MSEED` or `.SAC`), and the characters `.D` (for type Data) that appear in both the channel code and the filename. Note also the two dots (`..`). If there is a location code, it should appear between those dots (e.g., for a location code `10`, the corresponding filename should be `YH.LOBS3.10.HH1.D.2014.332`). There is no location code for the YH.LOBS3 data, and this field is simply absent from the filenames. Finally, the day-of-year (DOY) field must be zero-padded to be exactly 3 characters.
0 commit comments