I am working with data from a Kinemetrics FBA-11 accelerometer network. I have used detrend(‘demean’) to remove drift but it seems that there are still artifacts from the instrument. I want to use instrument correction in obspy and I am wondering if there is a central database that provides the needed PAZ etc?
and it looks much better: I'm interested in displacement (FBA-11
accelerometers on 6th and 8th floor of a building). If I detrend the
stream and integrate twice (without correction) I get
If I now use instrument correction:
seedresp = {'filename':
'/home/hd/Dropbox/projects/current/RESP.XX.NS235..BNZ.FBA11.DC_50.2_5V.1G',#RESP
filename
'date': UTCDateTime("2007-08-09T07:57:49Z"),
'units': 'DIS' # Units to return response in ('DIS', 'VEL' or ACC)}
st_orig.simulate(paz_remove=None,seedresp=seedresp)
fl1 = 0
fl2 = 0.45
fl3 = 5.
fl4 = 500.
and use water_level=60.
What confuses is me is that calling Stream.simulate() with seedresp
set to units: 'VEL' and subsequently calling Stream.integrate() to get
the DIStance, gives something completely different than calling
Stream.simulate() with seedresp set to units: 'DIS'.
I can't say what is going wrong for you (with just pictures) but i can
say that it works in principle when using correct response information
and proper options and pre/post-processing:
#!/usr/bin/env python
from obspy import read
import matplotlib.pyplot as plt
I assume there is something wrong with your processing chain and the
response information you put together (e.g. digitizer?). You should end
up in m/s or m and your numbers are a bit high for that.
That was extremely helpful, thx! I now end up with (nearly) the same plot after correcting either directly for DIS or alternatively for ACC and then integrating twice (http://pastebin.com/esniGcGY). However, I’m still dubious about the actual numbers: the data is from a Kinemetrics FBA-11 acclerometer on the 6th floor of a building, hence they are way too high to make sense in meters?
Just a wild thought that you might have already dealt with, but did you include the sensitivity of the digitizer in your resp file (Volts/count)? I think the NRL response library assumes a digitizer with a unity sensitivity(1 Volt/count). You could always find the digitizer you are using in the NRL and include that piece into stage 2 of your resp file.
The only way to figure out digitizer settings without meta-data (such as a dataless SEED or stationXML file) is to contact the original deployer and ask, however, you are in luck. These data are also archived at the IRIS DMC so you can get the full meta-data there. Go to this link http://www.iris.edu/mda/FA, select any of the stations, then select “view RESP”…
Thanks Renate, that’s brilliant! I’m now using the RESP file from http://www.iris.edu/mda/FA but I’m getting a warning from Obspy:
WARNING: FIR normalized: sum[coef]=9.781111E-01; FA FABD 6N HNE
While the shape looks good, I’m dubious about the amplitude numbers…the maximum change of position during the event on the 6th floor would have only been 0.6mm? http://imgur.com/RFclca6
(The first row is uncorrected data, the 2nd instrument corrected for ACC with RESP and the third instrument corrected for DIS with RESP)
The (obs)python code I used is http://pastebin.com/QDPG7r0y