-
Notifications
You must be signed in to change notification settings - Fork 0
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
Implement cams egg4 dataset (for co2) #26
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
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.
A demo notebook for downloading cams co2 data is available for reviewing this PR. (Note: ADS is very slow....the downloading query could take very long...be patient 😂 )
@geek-yang can you update the documentation as well? :) I just realize now I did not do that with the PrismDEM dataset haha. |
No problem! I will take care of it. |
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.
@geek-yang nice addition, thank you 👍
- I think we can improve it by adding a recipe that downloads cams data.
- Also, I still don't know which cams dataset can be downloaded using zampy. So, some clarifications should be added to the documentation. Because
model_level=60
andstep
are hardcoded, please see my comments. - How the test data is generated, perhaps it is better if we add a cell in the demo notebook that generates the test data.
Co-authored-by: SarahAlidoost <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
Thanks a lot for your review @SarahAlidoost.
An example recipe was added by Bart in the doc: To avoid duplication, I simply add
I add more to the documentation about these hardcoded parameters and the name of the target dataset (CAMS EGG4). Thanks for the suggestion!
After thinking about it, I feel that to add the generation of the test data to the demo notebook is not proper. The test data is designed specifically for unit tests. It could neither reflect what real data looks like nor let the user get a taste of all the dataset related methods shown in the notebook. While these demo notebooks are design as tutorials for users (and also developers) to get familiar with zampy API and to download real data and try the following steps (incl. ingest, load and convert). If we put them together the user might get a feeling that they could test all zampy methods with the test data and without downloading real data (which of course is not true). I think eventually we will move the test data generation script to |
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.
@geek-yang thank you for addressing my comments, changes look good 👍
Adding support for CAMS EGG4 dataset in zampy.