Open Wufaxing opened 10 months ago
Is there any errors in the S-wave time-to-depth conversion? Theoretically, Both Ps and Sp phases have the same procedure on this function.
yes, I use LQT to calculate SRFs, when I run rf2depth ccp.cfg, it only search files with comp of R
wyb@Wufatian:/mnt/c/Users/22247/Desktop/all_SRF/SRF_1.0$ rf2depth ccp.cfg
Traceback (most recent call last):
File "/home/wyb/.local/bin/rf2depth", line 8, in
Thanks for reporting this. I'm in holiday now, I'll debug this after back to work at January.
I'm developing S receiver function ccp stacking via seispy during this time and may know this one.
This is partially due to class RFStation and it's api. It needs a sample trace to init RFStation and collect neccessary information like stla, stlo .etc. Unfortunately, rf2depth didn't leave space for different comp. So by default, seispy is searching xxx_Rxxx.sac file rather than xxx_Lxxx.sac.
It's a little bit awkward time point, since I am working on ccp moduel right now to add S receiver function support and it requires weeks to write, run and go through a set of test.
Here's a couple of suggestions:
Hi all
In current version, I have written an API for read L component in RFStation
as below
RFStation('path/to/SRF', prime_comp='L')
But this function hasn't been embedded into rf2depth
. In the future, the 'rf2depth' will search components order by R, Q, L and Z.
ls the Time-to-depth conversion of SRF available now?