Stretching compute

[Baimanight]

Hi,
when I use the MSNoise1.6_compute_stretching, I noticed that the error values seem to be quite large. After reviewing the 'stretch.py' file, I suspect that there may have been an oversight in converting the error into the appropriate unit. I made a modification that 'error = FWHM / 2 / nstr * str_range' for the error bars.
Additionally, I've observed some null error values and instances where the errors exceed 'nstr' in the final station_pairs.csv file. Could you please help me understand why this might be happening?
I appreciate your assistance and look forward to your helpful response.

[ThomasLecocq]

Hi, maybe @asyates or @LaureBrenot can help, I never used the stretching method extensively myself

[Baimanight]

Thanks for your response. Recently, based on your code, I am working with MATLAB to develop an improved stretching method for addressing clock error. And the final result looks good.

…

---Original--- From: "Thomas ***@***.***> Date: Mon, Jan 13, 2025 15:27 PM To: ***@***.***>; Cc: ***@***.******@***.***>; Subject: Re: [ROBelgium/MSNoise] Stretching compute (Discussion #390) Hi, maybe @asyates or @LaureBrenot can help, I never used the stretching method extensively myself — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[ThomasLecocq]

Hi,good thanks. Please report here back with that code & suggestions on how to improve the processing, so others can benefit !

[Baimanight]

Sure, I’m just finishing up some more debugging. I’ll be happy to share and reply here again soon!

…

---Original--- From: "Thomas ***@***.***> Date: Mon, Jan 13, 2025 19:16 PM To: ***@***.***>; Cc: ***@***.******@***.***>; Subject: Re: [ROBelgium/MSNoise] Stretching compute (Discussion #390) Hi,good thanks. Please report here back with that code & suggestions on how to improve the processing, so others can benefit ! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[asyates]

Hi,

Yes you're right, the error outputs were/are quite unusable in their current form (for the reason you describe, the lack of conversion into an appropriate unit). I've thus always used the max CC as an indicator of the uncertainty and ignored the error.

I was thinking to update the error output to simply reflect the theoretical error i.e. Weaver et al. (2011), which is based on the max CC, frequency bandwidth, and coda window choices (after a bit of testing, i was not so convinced that the width of the CC estimates is that useful either, because this also depends on frequency).

In this sense, would also be curious to see what you come up with before i go ahead with just introducing the theoretical error.