Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regarding convolution with the source time function #1668

Open
VarunD21029 opened this issue Jan 2, 2024 · 1 comment
Open

Regarding convolution with the source time function #1668

VarunD21029 opened this issue Jan 2, 2024 · 1 comment

Comments

@VarunD21029
Copy link

VarunD21029 commented Jan 2, 2024

I would like to know what the preferred way is to convolute the seismogram with the source time functions. The manual suggests using the Seismic Analysis Code (SAC) software for the task, but I am having difficulties reading the output file in SAC.
Thanks in advance for suggestions.

@danielpeter
Copy link
Contributor

I guess you meant "convolve", not "convolute" the seismograms - this might have different meanings :)

in general, the convolution step is part of your post-processing. thus, it depends on how you do your preferred post-processing. this could be with python scripts, perl scripts, bash scripts and/or together with SAC or obspy etc.

the SPECFEM3D package only provides a very simple convolution post-processing tool bin/xconvolve_source_timefunction when compiled. simple in the sense of only convolving "smooth triangle" functions (Gaussians with a decay such that they are similar to triangular functions).

regarding SAC, it should be able to read in the ASCII trace outputs using a command like

read alpha <tracefile>

for the rest of the procedure follow the SAC manual.

and other convolution possibilities can be found online using obspy or numpy for python scripts.

and hopefully other users following this discussion can provide you with more specific script examples on how to convolve your traces with arbitrary source time functions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants