Bug #894
wrong beach ball when rake=0
| Status: | Closed | Start date: | 2016-04-27 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Paul | % Done: | 100% | |
| Category: | - | |||
| Target version: | Candidate for next bugfix release | |||
| Affected version: | 5.x-svn | Platform: |
Description
The mechanism I am trying to plot is from GCMT (http://www.globalcmt.org/CMTsearch.html). Since the url link is too long, I just paste the screenshot.
Commands below can reproduce the bug. This command plots three beach balls with slightly different rake angles.
gmt psmeca -JX15c/7c -R116/127/23/26 -B1 -Sa2c -Fa0.2c/cc > meca.ps << EOF 118.68 24.39 15.0 351 81 -0.001 5.4 0 0 rake=-0.001 120.68 24.39 15.0 351 81 0 5.4 0 0 rake=0 122.68 24.39 15.0 351 81 0.001 5.4 0 0 rake=0.001 EOF
The output is:
When rake is exactly equal to 0, the beach ball is wrong. So, I think this may be a bug of psmeca.
PS: I am using GMT 5.2.1 under Linux x86_64.
Associated revisions
Fix issue #894 (A rake = 0 would reverse the polarities).
Added meca_13.sh in support of issue #894
History
#1
Updated by Joaquim about 1 year ago
- Status changed from New to Resolved
Ok, in r16346 I made the hacky fix of setting
if (rake == 0) rake = 0.00001;
Not ideal but should work and given this code was not written by us a perfect fix would risk to take real long time.
#2
Updated by Paul about 1 year ago
I have added new test script meca_13.sh to remind us. This now passes after JL's fix.
#3
Updated by Paul about 1 year ago
- Status changed from Resolved to Closed
- Assignee set to Paul
- % Done changed from 0 to 100
Closed as fixed - reopen if there are other problems related to this.
#4
Updated by Joaquim about 1 year ago
Paul, but it was you who said that some of our meca tests were failing after this fix. No more?
#5
Updated by Paul about 1 year ago
I have no more failures after reconciling the various troubles, so I am closing it for that reason.