Apply NIST SI unit convention to some gallery examples#1194
Conversation
I went through the gallery examples and found several things that could be improved: - Use conventions for SI units -
|
I find this warning when building the docs to be a bit annoying: Do you think the gallery example |
Of course, it's a good idea @meghanrjones. I think there will no conflicts appear with any other files. Renamed |
|
I think that |
maxrjones
left a comment
There was a problem hiding this comment.
Looks good! I just have one suggestion for the two list items in CONTRIBUTING.md. If you chose to keep your wording, please just add a period to the end of the sentence.
I learned from that link that I have broken some NIST rules in my papers 🤦
Co-authored-by: Meghan Jones <meghanj@hawaii.edu>
Unfortunately these rules and others are often broken in scientific publications 😄, sometimes based on the official styling guidelines of indiviudal journals. My favorite is putting the unit in squared brackets (e.g. distance [m]). |
|
Before merging, could you please change the PR title to something more descriptive like "Apply NIST SI unit convention and fix some gallery examples" (or something along those lines). Thanks! |
Co-authored-by: Dongdong Tian <seisman.info@gmail.com>
|
Looks great. Just one minor comment above. |
Co-authored-by: Yao Jiayuan <coreman.seism@gmail.com>
Done! Thanks @core-man. |
…gTools#1194) Co-authored-by: Meghan Jones <meghanj@hawaii.edu> Co-authored-by: Dongdong Tian <seisman.info@gmail.com> Co-authored-by: Yao Jiayuan <coreman.seism@gmail.com>
Description of proposed changes
I went through the gallery examples and found several things that could be improved:
vectors.pytovector_styles.pyto avoid warning on "Duplicate example file name(s)"In CONTRIBUTING.md
Reminders
make formatandmake checkto make sure the code follows the style guide.doc/api/index.rst.Slash Commands
You can write slash commands (
/command) in the first line of a comment to performspecific operations. Supported slash commands are:
/format: automatically format and lint the code/test-gmt-dev: run full tests on the latest GMT development version