-
Notifications
You must be signed in to change notification settings - Fork 229
Migrate the 'no_clip' parameter to the new alias system #4103
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
base: main
Are you sure you want to change the base?
Conversation
no_clip | ||
Do **not** clip contours or image at the frame boundaries [Default is ``False`` | ||
to fit inside ``region``]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am wondering to what "image" is refering here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It comes from the upstream documentation at https://docs.generic-mapping-tools.org/6.5/contour.html#n.
Here "image" is used because contour
can color the triangles using a CPT. See the example below:
gmt begin map
gmt makecpt -Cseis -T600/1000/100
gmt basemap -R0.5/6/0.5/6 -JX10c/10c -Baf
gmt plot @Table_5_11.txt -Sc0.2c
gmt contour @Table_5_11.txt -Wthin -C -I -N -t50
gmt end show

- J = projection | ||
- N = no_clip | ||
- V = verbose | ||
- c = panel | ||
- t = transparency |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- J = projection | |
- N = no_clip | |
- V = verbose | |
- c = panel | |
- t = transparency | |
- J = projection | |
- N = no_clip | |
- V = verbose | |
- c = panel | |
- t = transparency |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, not sure what GitHub is doing here, but actually I only removed one whitespace before the newly added bullet point for -N.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you want to remove one whitespace before -N
? I believe the current one is correct. See https://pygmt-dev--4103.org.readthedocs.build/en/4103/api/generated/pygmt.Figure.grdimage.html#pygmt.Figure.grdimage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same for me with the new GitHub UX. It's more likely a GitHub bug.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I experienced some unexpected behavior in the last days... Then we just leave this as is and in case one of the lists is not correctly aligned, we can still make a PR to fix this.
Some wrappers have the
no_clip
parameter, which can be either False or True. This PR migrates the parameter to the new alias system.no_clip
inFigure.plot
andFigure.plot3d
are not updated in this PR, because in these two methods,no_clip
can be False, True,"c"
or"r"
and we need to discuss the long-form arguments for "c"/"r". So leave it to a separate PR instead.