-
Notifications
You must be signed in to change notification settings - Fork 116
Zarr tutorial #323
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
Zarr tutorial #323
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Thanks @negin513 for your work on this! I took a pass through and made some minor edits ahead of the tutorial on Tuesday but I think this is ready to go! |
Thanks for the review @jhamman . LGTM! |
I'm currently resolving the build issues, will push some commits and merge shortly. |
🎊 PR Preview fe50cbf has been successfully built and deployed to https://xarray-contrib-xarray-tutorial-preview-pr-323.surge.sh 🕐 Build time: 0.009s 🤖 By surge-preview |
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.
Thank you both for this!
Hi @TomNicholas
Thanks for helping assign the tasks for the SciPy tutorial. This notebook is an introduction to Zarr, including some fundamentals of the format, key differences from NetCDF, and practical usage with cloud storage.
I ended up diverging from Ryan's notebook to incorporate more Zarr v3 concepts and cloud-scale considerations, especially around sharding.
For the large-scale data example, I recommend using CMIP6 hosted on Google Cloud, as it’s both substantial and publicly accessible via xarray and we already have the content ready.
I may not have much more bandwidth or time to continue working on this due to the other SciPy presentation preparations and tight timeline. Let me know if you'd like me to make any adjustments, or if it’s easier, I can give you collaborator access so you can push changes directly to the branch.
cc'd @jhamman since you are presenting this.
Resolves some tasks of Issue #321 .