-
Notifications
You must be signed in to change notification settings - Fork 5
DOC: Provide dataset information in fetcher script help #48
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
DOC: Provide dataset information in fetcher script help #48
Conversation
ca030d6 to
7bdd7f0
Compare
7bdd7f0 to
28e166f
Compare
|
This was passing yesterday, and it is now failing with the same error as in #49 (comment) after today's push force. Definitely errors are not related to the patch sets. |
#50 fixes the issues. |
cbef0bb to
90c4750
Compare
90c4750 to
55a4b50
Compare
Provide dataset information in fetcher script description: add the dataset description and the zenodo links where the datasets dwell to the fetcher script description so that they are shown when the help is shown.
55a4b50 to
1d48465
Compare
1d48465 to
acbbe6b
Compare
Use the fetcher method callable provider in the dataset retrieval method. Improves code re-use.
Remove "Download" from the fetcher method descriptions for the sake of consistency across descriptions, and in order to describe the dataset itself rather than the method.
Refactor the dataset parameters tuples: - The dataset tuples do not provide an effective fetcher, but only the parameters needed to make the fetcher. Thus, the `fetcher_` prefix is removed. - Rename the method that provides the fetcher parameters accordingly. - The fetcher names are all built in the same way, and thus this is put into a method for the sake of best coding practices. Also, prefer naming the fetchers directly using the Dataset enum values.
acbbe6b to
41d5931
Compare
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, but you will still be able to re-open it. Thank you for your contributions. |
Resolves #44.