-
Notifications
You must be signed in to change notification settings - Fork 224
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
Wrap rose #794
Wrap rose #794
Conversation
As discussed in GenericMappingTools#786 this is wrapping the GMT function **rose**.
Tests for wrapping rose.
/format |
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.
Hi @michaelgrund, this is looking excellent! I've had a quick skim and you're ticking off all the right boxes so far (well documented keyword arguments, top notch unit tests). Will try and give this a proper review once I have time (just busy right now finishing a thesis and preparing for a conference) so I'll ping the other devs @GenericMappingTools/python-maintainers to get some more eyes on this.
Oh, and this is optional, but you can also add a gallery example for rose
here in this PR or in a separate Pull Request 😉 I see you're making a few minor changes still, so keep up the good work! Feel free to let us know if you encounter any trouble with anything too.
Why isn't |
I thought providing a mixture would be a good choice @willschlitzer. However, I'm fine with adding a few more tests using |
/format |
We're trying our best to avoid using |
In case you are interested in including an alias for this option (not necessary before merging IMO), GenericMappingTools/gmt#5056 will add documentation to the GMT reST files for a |
Co-authored-by: Dongdong Tian <[email protected]>
I would do it after merging, potentially together with implementing the inquire option. |
@@ -0,0 +1,44 @@ | |||
""" |
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.
According to this comment: #876 (comment), the rose
example should be put into the "Histogram" category.
Edit: As the "Historagm" category is not created yet, it's OK to leave the example here now. We can create the category and move the example later.
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.
Ok fine, to keep track will open a new issue regarding that point.
The PR looks good. I just made some suggestions. The two comments about refactoring the tests can be addressed in a separate PR. |
Co-authored-by: Dongdong Tian <[email protected]>
Co-authored-by: Dongdong Tian <[email protected]>
Co-authored-by: Dongdong Tian <[email protected]>
No, thank you for your patience and doing all the side tasks like adding a new tutorial dataset! Feel free to Squash and Merge this PR in yourself @michaelgrund, be sure to change the commit message by summarizing what was done (and remove all those lines with "* Update base_plotting.py" or similar). You can also keep just a single instance of the "Co-authored-by ..." for every single person that helped. Let me know if it's unclear. |
Something wrong with the GitHub macOS hosts. I think they're unrelated. This PR is good to merge. |
I just merged the PR using my admin privileges. |
* Wrap rose * Add tests * Add a gallery example Co-authored-by: Will Schlitzer <[email protected]> Co-authored-by: Dongdong Tian <[email protected]> Co-authored-by: Wei Ji <[email protected]> Co-authored-by: Meghan Jones <[email protected]>
Description of proposed changes
As discussed in #786 this is wrapping the GMT function rose. Would be happy to receive any kind of feedback.
Reminders
make format
andmake check
to make sure the code follows the style guide.doc/api/index.rst
.Notes
/format
in the first line of a comment to lint the code automatically