-
Notifications
You must be signed in to change notification settings - Fork 23
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
Flipped Syngine R-component seismogram by ForceSource? #82
Comments
Hi, you are probably right, here is a comparison between E and R component in a setting where I would expect them to be equal and with positive onset. So it seems E and N are probably correct as these are what we benchmarked previously and the issue is with R only. Thanks for reporting, would be happy to get an MR on this. Cheers,
|
The example is intuitive. Many thanks for this quick clarification! |
I faced the same problem. To check the consistency of the moment tensor response of instaseis and the single force Green's function of instaseis, I synthesized a moment tensor response from the single force Green's function numerically as follows.
For further reference. |
This is a duplicate of #77, I think. |
As you pointed out the two comments are almost the same. #77 compared the single force Green's function with those by difference code (Mineos). The above comment is a self-consistency check between instaseis' outputs. This is my first comment on GitHub issues, so please excuse any confusion in usage. |
Sorry, I was referring to the overall issue identified, not your specific comment. |
Hello,
Recently I attempted to benchmark Instaseis results with normal modes (MINOS) and SPECFEM3D. For the force source, I noticed that the R-components seem to be flipped for seismograms downloaded with Syngine. This phenomenon did not appear for a moment tensor source though. I put detailed descriptions below in the PDF file.
Just a minor issue, and I would like to check if there would be a bug related with the sign.
Issue.pdf
The text was updated successfully, but these errors were encountered: