Spectrogram problems when obtaining data from IRIS for Ecuador Seismic Network
Closed this issue · 4 comments
I'm welcome to be excited about this 'sonify' project. But when it comes to seismic networks in the world, the problem is mainly with the EC
network ie EC.VCES..HHZ
and Its location is --
.
As you can see the screen should measure in color based on dB power, but it looks like the background is blue.
I'm getting a message like this:
WARNING (norm_resp): computed and reported sensitivities differ by more than 5 percent. Execution continuing.
Here's the initial response from the station.
URL: click here.
The code:
from sonify import sonify
from obspy import UTCDateTime
sonify(
network='EC',
station='VCES',
channel='HHZ',
starttime=UTCDateTime('2022-02-10T14:40:40.430304Z'),
endtime=UTCDateTime('2022-02-10T16:40:40.430304Z'),
location='--',
freqmin=1,
freqmax=23,
speed_up_factor=200,
fps=1, # Use fps=60 to ~recreate the JHEPC entry (slow to save!)
spec_win_dur=8,
db_lim=(-180, -130),
)
It's sensitivity is of 3.14195E8 @ 1.0 Hz (SEED Stage 0)
Hi @web-sys1, it looks like you're specifying the db_lim
manually. Try using db_lim=None
to allow sonify to choose suitable colormap limits automatically.
I took a look at the waveform processing and it looks like the response is being removed successfully.
@liamtoney
Thanks for telling me about it, but the question is still: why does the 1e-6
appear on the lower left side?
Now it works, but I still get a warning (norm_resp): computed and reported sensitivities differ by more than 5 percent. Execution continuing.
Should I worry?
@liamtoney Thanks for telling me about it, but the question is still: why does the
1e-6
appear on the lower left side?
That is the scaling value for the y-axis units. Meaning, the waveform ranges from about –0.000002 to +0.000002 µm/s.
Now it works, but I still get a `warning (norm_resp): computed and reported sensitivities differ by more than 5 percent. Execution continuing.`` Should I worry?
That's a sensor response issue that's out of our control — I believe it means that what ObsPy computes as the scalar sensitivity from the full response is different from what the network operator provides as the scalar sensitivity. You'd have to contact the network manager to find out what's up with that.
I'm gonna go ahead and close this issue. If you find something new, don't hesitate to make a new one!