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

Plotting duplicated annotated line produces corrupt PS #3530

Open
joa-quim opened this issue Jun 24, 2020 · 6 comments
Open

Plotting duplicated annotated line produces corrupt PS #3530

joa-quim opened this issue Jun 24, 2020 · 6 comments
Labels
bug Something isn't working

Comments

@joa-quim
Copy link
Member

From forum post

data t.dat

> -L-100 -Sqd1.0i
-86.45235040920656 44.56074532391791
-87.15496366731526 44.63460538965384
-87.52203359612746 43.70375243465723
-87.57565650687522 42.81267315180862
-87.46872284091027 42.21696862267483
-87.29959207789203 41.98325754479477
-86.88164979096022 41.9742639278875
-86.56233691428744 42.29261909586023
-86.46591956240054 42.8760163962448
-86.67090781901327 43.41777121767043
-86.7207951116628 43.91664988596499
-86.45235040920656 44.56074532391791
> -L-100 -Sqd1.0i
-86.45235040920656 44.56074532391791
-87.15496366731526 44.63460538965384
-87.52203359612746 43.70375243465723
-87.57565650687522 42.81267315180862
-87.46872284091027 42.21696862267483
-87.29959207789203 41.98325754479477
-86.88164979096022 41.9742639278875
-86.56233691428744 42.29261909586023
-86.46591956240054 42.8760163962448
-86.67090781901327 43.41777121767043
-86.7207951116628 43.91664988596499
-86.45235040920656 44.56074532391791

command

gmt psxy t.dat -R-88.50/41.45/-84.56/46.23r -Jt-86.3855/1:2175000 -P -W0.50p,black -Sqd1.0i:+d+Lh > lixo.ps

Removing the duplicated segment makes it plot correctly.

@PaulWessel
Copy link
Member

Related to the segment header. Removing them and I get a plot with duplicated lines. There may be some restrictions on what changes to -Sq can be done via segment headers. WIll have to see in debug what actually happens to give me a SEGV.

@joa-quim
Copy link
Member Author

Dumb VS2019 no longer systematically crashes in those case, which was extremely useful for it would lead directly to the crashing point.

@PaulWessel
Copy link
Member

Scary that we must rely on Apple clang...

@joa-quim
Copy link
Member Author

Yep, have to resort to Julia to when want to make use of that facility.

@PaulWessel
Copy link
Member

Just thinking out aloud how -S in command line and segment header should work (I am not saying it works this way, but perhaps that is should):

  1. If no -S is given on the command line then any -S in a segment header is completely ignored (you are basically selecting line or polygon mode).
  2. If an unspecified symbol is given on the command line (-S) then the -S in a segment header is fully parsed.
  3. If a complete -S is given on the command line then any -S in a segment header should be ignored.

I am not sure about the third, but there should be a way to have either the command line (full syntax) or the segment header (-S) be in effect, no? We usually let command line options override defaults, and I guess in this context, settings in the segment header constitute defaults (?).

@stale
Copy link

stale bot commented Sep 26, 2020

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@stale stale bot added the stale This will not be worked on label Sep 26, 2020
@seisman seisman added bug Something isn't working and removed stale This will not be worked on labels Sep 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants