daniel
the problem is that inside you ms file, the channel cname is e.g. B Z,
while the response file is BHZ.
i do not think we can modify the RESP file to code B Z, lars could you
confirm ?
jens
On Thu, 24 Oct 2013, Daniel Portner wrote:
Jens,I have attached one such event that I have tried and response files for
two stations (each component). This problem persists with every event and
every station/component.
I appreciate the help.
-Daniel Portner
On Thu, Oct 24, 2013 at 2:23 AM, Jens Havskov <[email protected]>
wrote:
daniel
send the waveform file and the response file and i can check.
jens
On Wed, 23 Oct 2013, DANIEL E PORTNER wrote:
Jens Havskov <Jens.Havskov@...> writes:
daniel
two things can go wrong.
data does not have exactly the same
station, component or network code as
your data, a bit unlikely since you took
the files out with rdseed
the date of validity inside resp file
does not correspond to your data,
also a bit unlikely the wasy you got the
resp file
lars is the expert on resp file reading,
but he is away this week.
jens
On Tue, 8 Oct 2013, DANIEL E PORTNER
wrote:
Hi,
I saw a similar problem was
posted by Abhash Kumar last
year, but I was
still
not able to solve it given
the responses to his post.
I am trying to
use
instrument response files in
order to calculate body wave
magnitudes for
my
events. In order to get the
response files I used rdseed
as instructed
in the
most recent SEISAN manual.
This provided me with
response files of the
form:
RESP.XQ.NC01..BHE
for example.
I then copied these response
files to my CAL directory.
However, when I
open
the events in EEV and
attempt to use the ":"
command or the mb command,
I get
the error "No response
info". This happens for
every channel, despite
my
having response files for
each.
I have looked at the
response files and they are
valid for the necessary
time
windows. Similarly I have
tried to use PRESP and it
works for each
response
file. I have also looked
into the SEISAN.DEF file.
There does not seem
to be
any problem with it,
although I am not exactly
sure what specifical
problems
with the defaults I would be
looking for to solve this
problem.
Does anyone have another
idea of what might be my
problem as to why EEV
will
not recognize my response files?
Thanks for the help,
Daniel Portner
UNC-CH
_______________________________________________
seisan mailing list
seisan@...
http://mailman.uib.no/listinfo/seisan
Hi,
I have checked both the dates of validity and the stations,
components, and
network codes. These are most likely accurate, as you say,
because I used
rdseed on the same seed files to get the instrument response as
I did to get
the data.
I have also tried re-registering the events (after uploading the
response
files) but that did not allow the response files to be
recognized.
Do you have any other suggestions?
Thanks,
Daniel Portner
UNC-CH
_______________________________________________
seisan mailing list
[email protected]
http://mailman.uib.no/listinfo/seisan
_______________________________________________
seisan mailing list
[email protected]
http://mailman.uib.no/listinfo/seisan