-
Notifications
You must be signed in to change notification settings - Fork 383
GMT figures are not fully isolated in one single session #5279
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
Comments
Sory, can you help me see the difference between 1 and 3? Looks the same to my old eye. |
The size of the annotations is slightly different. |
Can you confirm that this seems related to slightly different pens and font values? |
I have no idea. I tried to add -Vd to the two colorbar commands separately and check the debugging messages. Here are the main differences: The first figure shows:
but the second figure show:
|
Thanks, that gmt.frame message is the information I need: Looks like that file needs to get the same treatment as other files and be per-figure, per-subset, etc. It is using that file from the 2nd plot which is unrelated. I will start a separate fix. |
Otherwise information from one completed figure may leak into another, causing small differences. Tests pass, and no difference in the original post. Closes #5279.
Otherwise information from one completed figure may leak into another, causing small differences. Tests pass, and no difference in the original post. Closes #5279.
A bash script to reproduce the issue:
In this example, three figures are generated. The 1st and the 3rd figure uses the same code, so we expect makecpt1.pdf and makecpt2.pdf are the same, but actually, these two images are slightly different. However, if we remove the code for the 2nd figure, makecpt1.pdf and makecpt2.pdf are the same again.
I think it may mean that the "settings" for each "figure" are not fully isolated and it looks like a GMT bug.
Originally posted by @seisman in GenericMappingTools/pygmt#1289 (comment)
The text was updated successfully, but these errors were encountered: