-
Notifications
You must be signed in to change notification settings - Fork 1
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
CMIP data #17
Comments
If you are using NCDatasets (NetCDF_jll should support Zarr), one can also index a dataset via the NetCDF standard name (assuming that this attribute is defined). If there is only one longitude NetCDF variable, then
Maybe this helps... |
@Alexander-Barth I'm not sure how to use NCDatasets here. Do you have a MWE of using NCDatasets to grab a variable from a CMIP dataset in the cloud? |
Unfortunately, I don't have a MWE, just the general information here: Note however, NetCDF_jll does not jet have S3 supported activated. |
I don't have code nearby, but I had success in the past using Zarr and YAXArray : https://juliadatacubes.github.io/YAXArrays.jl/dev/examples/generated/UserGuide/openZarr/ |
Any recommended workflow for processing/analyzing CMIP data in Julia?
I thought I'd ask here for tips, which will undoubtedly be useful to me, and maybe help others too :)
cloud compute/download. I've been using Zarr.jl and AWS.jl (using code found in notebooks by @gaelforget, Ryan Abernathey, and others) with some success, but I thought I'd ask here if you'd recommend anything else? I usually go
dealing with inconsistencies between models (e.g., different coordinate names like
nav_lon
vslongitude
). The Python xmip package by Julius Busecke is specifically designed to address a lot of these issues. Is there anyone planning to port its functionality to Julia somewhere in this org? Or is it easy enough to use PyCall? Or do you do this all manually?xarray-like package. Which of the many packages do/would you use to manipulate gridded data from CMIP? For example, if I want to make some tracer budgets, I can deal with the different model grids (e.g., staggered or not) by hand (doing some tedious checks, interpolations/extrapolations, and so on), but surely there is a better way that leverages existing code?
Maybe this is all already answered somewhere and I just missed it, in which case sorry for the noise!
The text was updated successfully, but these errors were encountered: