You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For certain combinations of strike ($\phi$), dip ($\delta$), and rake ($\lambda$) angles, the moment tensor-based expression (mt convention) of the beach ball by meca module gives wrongly swapped compression & expression fill. The following figure is a typical example of this problem, showing the mechanism solution with the rake angle changing by 1 degree.
The aki convention does not cause this problem.
The moment tensor in the above example has an equal plunges between P-and T-axis, so this issue of GMT might be relevant. But note that the problem also occurs in the mt convention, not in the principal axis representation (-Sy option in GMT or principal_axis convention in PyGMT).
I also noticed that we cound avoid the problem by adding a very small value (such as 0.0001 degree) to the rake angle.
👋 Thanks for opening your first issue here! Please make sure you filled out the template with as much detail as possible. You might also want to take a look at our contributing guidelines and code of conduct.
@seisman, could you check if this is the same issue upstream as GenericMappingTools/gmt#8009? I'm not a seismologist, but would guess that this has to do with some numerical precision error in GMT's code for meca.
Description of the problem
For certain combinations of strike ($\phi$ ), dip ($\delta$ ), and rake ($\lambda$ ) angles, the moment tensor-based expression (
mt
convention) of the beach ball bymeca
module gives wrongly swapped compression & expression fill. The following figure is a typical example of this problem, showing the mechanism solution with the rake angle changing by 1 degree.The
aki
convention does not cause this problem.The moment tensor in the above example has an equal plunges between P-and T-axis, so this issue of GMT might be relevant. But note that the problem also occurs in the
mt
convention, not in the principal axis representation (-Sy
option in GMT orprincipal_axis
convention in PyGMT).I also noticed that we cound avoid the problem by adding a very small value (such as
0.0001
degree) to the rake angle.Minimal Complete Verifiable Example
Full error message
System information
The text was updated successfully, but these errors were encountered: