Open andersy005 opened 5 years ago
@andersy005, those particular files are binary files that the model reads and are in a version control system associated with CESM.
I think a higher priority would be to curate the grid files on which the esmlab
regridding workflow depends. These can be big, however, so not obvious how to proceed.
At this point, I don't believe grid_definitions.yml is really used by esmlab
at all. I had thought we might use this to store "known grids"...but we currently just check for the grid file.
the model reads and are in a version control system associated with CESM.
Are these publicly accessible (e.g: GitHub)??
To be clear, the POP grids are in a repo...the T62 grid is not.
They are in an Subversion repo: https://svn-ccsm-inputdata.cgd.ucar.edu/trunk/inputdata/ocn/pop
Maybe grid files could be handled in a manner similar to how cartopy
manages remote datasets, from Natural Earth, for instance.
https://github.com/SciTools/cartopy/blob/master/tools/feature_download.py https://github.com/SciTools/cartopy/blob/master/lib/cartopy/io/__init__.py
To be clear, the POP grids are in a repo...the T62 grid is not.
T62 grid is also in the svn repo (Along with some other shared grids): https://svn-ccsm-inputdata.cgd.ucar.edu/trunk/inputdata/share/scripgrids/
Not sure if grids in scrip format are helpful though.
It appears that all grid, topography, region mask files used in
regrid.py
are hosted in various locations on Glade. I was wondering if it would be feasible to have some kind of central registry for these? How big can these files get? Can we curate them in a public place (GitHub repo)?https://github.com/NCAR/esmlab/blob/538185f5f0dd75f243f39008da947a4a14d707c1/esmlab/grid_definitions.yml#L14-L16
https://github.com/NCAR/esmlab/blob/538185f5f0dd75f243f39008da947a4a14d707c1/esmlab/grid_definitions.yml#L149
Cc @matt-long