Creating StationXML with a customized data logger

Hi,
I am following the ObsPy tutorial for creating a StationXML (https://docs.obspy.org/tutorial/code_snippets/stationxml_file_from_scratch.html) and was wondering if there’s away to bypass the datalogger response input? Deconvolving the instrument response without the data logger response is similar to deconvolving with the poles-zeros response, correct? We are using custom built data loggers and they are not in the NRL. What’s a good work around?

Trying to avoid this piece here:
datalogger_keys=['REF TEK', 'RT 130 & 130-SMA', '1', '200'])

Thanks very much!

Januka

Januka Attanayake

Research Fellow | Earthquake Seismology
Homepage: https://sites.google.com/site/janukaattanayake

School of Earth Sciences | McCoy Bldg. 200
University of Melbourne | Parkville 3010 VIC
Australia

Hi Januka

AFAIK the instrument response is an optional entry in the4 stationXML format, meaning that you can either skip or add whatever instruments you want. If you still want to make use of NRL for the sensor only, have a look at the method get_sensor_response() in obspy.clients.nrl.client.NRL ()

\p

När du har kontakt med oss på Uppsala universitet med e-post så innebär det att vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du läsa här: http://www.uu.se/om-uu/dataskydd-personuppgifter/ E-mailing Uppsala University means that we will process your personal data. For more information on how this is performed, please read here: http://www.uu.se/en/about-uu/data-protection-policy

Super! Thanks Peter.

I replaced nrl.get_response with nrl.get_sensor_response and can now avoid having to deal with the data logger response.

Thanks again!

Januka

Januka Attanayake

Research Fellow | Earthquake Seismology
Homepage: https://sites.google.com/site/janukaattanayake

School of Earth Sciences | McCoy Bldg. 200
University of Melbourne | Parkville 3010 VIC
Australia

Hi Januka

AFAIK the instrument response is an optional entry in the4 stationXML format, meaning that you can either skip or add whatever instruments you want. If you still want to make use of NRL for the sensor only, have a look at the method get_sensor_response() in obspy.clients.nrl.client.NRL (https://docs.obspy.org/packages/autogen/obspy.clients.nrl.client.NRL.html)

\p

In addition to the sensor response that you can get from the "Creating a StationXML file from Scratch" tutorial page, when using "nrl.get_sensor_response(sensor_keys=...)" instead of "nrl.get_response(...)", you can add custom resonse stages to the response object you get, in order to reflect your digitizer, see:

http://docs.obspy.org/packages/autogen/obspy.core.inventory.response.html?highlight=ResponseStage

When adding custom stages make sure that input/output unit chain is consistent and use "recalculate_overall_sensitivity" when done.

In any case, when you set up your own station metadata from scratch (in this case for the digitizer), you should definitly make a huddle test side-by-side with a well known instrument/digitizer combination that you can use to compare with.

best,
Tobias

Thanks Tobias. That sort of options will be most useful if worked out examples are given in the documentation like the GMT guys have.

Januka

Januka Attanayake

Research Fellow | Earthquake Seismology
Homepage: https://sites.google.com/site/janukaattanayake

School of Earth Sciences | McCoy Bldg. 200
University of Melbourne | Parkville 3010 VIC
Australia

In addition to the sensor response that you can get from the “Creating a
StationXML file from Scratch” tutorial page, when using
“nrl.get_sensor_response(sensor_keys=…)” instead of
“nrl.get_response(…)”, you can add custom resonse stages to the
response object you get, in order to reflect your digitizer, see:

http://docs.obspy.org/packages/autogen/obspy.core.inventory.response.html?highlight=ResponseStage

When adding custom stages make sure that input/output unit chain is
consistent and use “recalculate_overall_sensitivity” when done.

In any case, when you set up your own station metadata from scratch (in
this case for the digitizer), you should definitly make a huddle test
side-by-side with a well known instrument/digitizer combination that you
can use to compare with.

best,
Tobias

We gladly any contributions to tutorials/examples/code snippet pages in
our documentation via Pull Requests on GitHub.

cheers,
Tobias