-
Notifications
You must be signed in to change notification settings - Fork 29
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
Clarify frame of reference for SF and SS in MS_phasevels #23
Comments
That looks right to me. No particular reason that P-polarisation is output, just haven’t really needed it for anything up to now. Cheers, James On 4 Sep 2014, at 10:03, Andrew Walker [email protected] wrote:
|
Except what we actually return in SF and SS is the eigenvectors projected onto the plane normal to the propagation direction (we return S1P and S2P calculated from:
I think this is because this is the vector we need to plot in e.g. MS_sphere (so the vector is tangent to the sphere) but isn't what you would get from, for example, doing finite difference of wave propagation. Maybe what we should return is S1 and S2 (the sorted eigenvectors, which are, I think, what I've described above) and push the projection into MS_sphere and MS_plot? But we do need to do the projection calculation inside MS_phasevels in order to calculate pol (which is in the ray frame). It's just a question of what we need to return to the caller - maybe both S1 and S1P should be returned (this can be done in a backwards compatible way). |
We may want to know the polarisation direction for the qP wave. This can be added to the output in a fairly straight forward way. However, we still need to think about the reference frame - see issue #23.
For computing group velocities it would be useful for MS_phasevels to output the non-projected eigenvectors, and possibly also the slowness vectors (i.e. XI/V(i)). |
This was queried by a user, my answer was:
but some clarification in the documentation would be useful.
Also, why don't we output the qP polarisation direction?
The text was updated successfully, but these errors were encountered: