Uh oh!
There was an error while loading. Please reload this page.
Add a tutorial for datetime data - #1193
Conversation
seisman
commented
Apr 7, 2021
@noorbuchi It's recommended to create a new branch and commit changes to it, rather than committing directly to your master branch. |
noorbuchi
commented
Apr 7, 2021
Thanks for mentioning that. We will definitely be using the git-flow in our fork to manage our work. I just had to push to the main branch in the fork to create a placeholder for our work |
noorbuchi
commented
Apr 12, 2021
@seisman I've been working a bit on the tutorial and I have a small question. When plotting points, should we link to the page that specifies the possible input for styling points? If so, where can I find this page? Thank you! |
I don't think we have a tutorial or a gallery example for different symbol styles yet. |
Uh oh!
There was an error while loading. Please reload this page.
noorbuchi
commented
Apr 12, 2021
Ok, I see. So should we try to explain the different shapes that the points could have? Similar to the |
seisman
commented
Apr 12, 2021
No, it should be in a separate gallery example. |
Co-authored-by: Dongdong Tian <seisman.info@gmail.com>
Hello @seisman@weiji14, I've been looking at the example you provided in #549 and I'm confused on what the frame argument is doing exactly. This is the example fig=pygmt.Figure() withpygmt.config(FORMAT_TIME_MAP="abbreviation"): fig.basemap( region=["2020-1-24T", "2020-1-27T", 0, 1], projection="X6c/1c", frame=["pa1K", "sa1K", "NWse"], ) fig.basemap(frame=["pa1K", "sa1K", "nwSE"])
fig.show()I understand the purpose of |
seisman
commented
Apr 12, 2021
It's not documented in PyGMT yet. You can find it in the GMT documentation (https://docs.generic-mapping-tools.org/dev/cookbook/options.html#axes-settings and https://docs.generic-mapping-tools.org/dev/cookbook/options.html#cartesian-time-axes). |
Co-authored-by: Dongdong Tian <seisman.info@gmail.com>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Yao Jiayuan <coreman.seism@gmail.com> Co-authored-by: Michael Grund <23025878+michaelgrund@users.noreply.github.com>
weiji14
left a comment
There was a problem hiding this comment.
This is looking really good. Thanks @noorbuchi for keeping on top of this! Agree with @seisman that we shouldn't leave this PR for too long, but I would recommend a couple more rounds of polish, and merging by the end of the working week (Friday).
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Wei Ji <23487320+weiji14@users.noreply.github.com>
Co-authored-by: Wei Ji <23487320+weiji14@users.noreply.github.com>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
This tutorial looks great to me 😄😄 😄 @noorbuchi, @munzekm, @cklima616 and @nathandloria Thanks a lot for your continuous contributions. Plotting datetime charts is very useful and I have learned a lot from this tutorial.
Co-authored-by: Dongdong Tian <seisman.info@gmail.com> Co-authored-by: Yao Jiayuan <coreman.seism@gmail.com>
Co-authored-by: Claire Klima <klimac@allegheny.edu> Co-authored-by: Dongdong Tian <seisman.info@gmail.com> Co-authored-by: Nathan Loria <lorian@allegheny.edu> Co-authored-by: Michael Grund <23025878+michaelgrund@users.noreply.github.com> Co-authored-by: Claire <46755872+cklima616@users.noreply.github.com> Co-authored-by: Yao Jiayuan <coreman.seism@gmail.com> Co-authored-by: Wei Ji <23487320+weiji14@users.noreply.github.com>
This tutorial will help users understand how to plot data in date and time ranges. It will discuss the different possible formats of the data and give examples of how the plots can be customized. Many community members mentioned the need for this tutorial so our team (@munzekm, @cklima616, @nathandloria and I) will working on it.
Preview at https://pygmt-git-fork-noorbuchi-master-gmt.vercel.app/tutorials/date_time_charts.html
Fixes#549
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