-
Notifications
You must be signed in to change notification settings - Fork 313
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
Make polarcap surface datasets in ctsm5.3.0, remove VR 1850 datasets #2720
Comments
Is this critical for a 5.3 milestone of does it just need to come in by the CESM3 release? |
Always the right question to ask. In order to have a dataset for @adamrher to use in CTSM5.3 versions we might as well make it. It shouldn't be hard to add, unless we run into problems. So I suggest we do so unless it causes problems in making all the datasets. But, it's likely only needed by the release and not in 5.3. |
This isn't required for 5.3.0, but could be added on subsequent 5.3 tag (or else it needs to get into Could add PLUMBER2 and NEON surface data too. |
Confirming info listed here and in the grids speadsheet:
|
Yes, that's correct @slevis-lmwg. I noticed however that CONUS only has finidat entries for year 2013. Perhaps we can just replicate the POLARCAP finidat entries for CONUS? |
From meeting with @ekluzek |
Alongside #2716 we need to add creating 1979,1850,2000,1979-2026 surface datasets for the ne0.POLARCAP resolution. This means adding it to the ne0 and ne120 resolution list in the gen namelist multi script for mksurfdata_esmf.
As part of this we'll remove the 1850 VR datasets as they aren't planned to be needed by CAM as explained by @adamrher
Definition of done:
The text was updated successfully, but these errors were encountered: