-
Notifications
You must be signed in to change notification settings - Fork 22
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
ModIvsModII diagnostic tool create-clim.sh script doesn't work when startyear>1000 #115
Comments
Do you have a case I can investigate? |
Also, please point me to the version of the script you used. |
I ran it with my two activation cases, stored on NIRD under /projects/NS9560K/users/ingvisau/: NFHISTnorpddmsbc_f19_f19_mg17_20231106140956 and NFHISTnorpddmsbc_f19_f19_mg17_20231106142112. |
It is this file: tools/diagnostics/ncl/ModIvsModII/create-clim.sh, I used branch: cam-Nor-dev |
Corrected script for preprocessing files for ncl aerosol plots Summary: Error in script for preprocessing history files used for creating aerosol plots Contributors: Øyvind Seland; Ingvild Sofie Sundby Aukan Reviewers: ingvisau; goldy Purpose of changes: Correcting the script so that it also works for model year > 1000 Github PR URL: #179 Changes made to build system: None Changes made to the namelist: None Changes to the defaults for the boundary datasets:None Substantial timing or memory changes: Nome Issues addressed by this PR: #115
Issue Type
Other (please describe below)
Issue Description
I tried to run ModivsModII on runs with startyear= 1985, and noticed that the filelist created by create-clim.sh only contained files with 1985. The script rewrites and updates the year-variable that goes into the creation of filelist entries (variable: aaYear) only if "FIRSTYEAR" is lower than 1000. For "FIRSTYEAR" > 1000, the variable 'aaYear', which is initially set to "FIRSTYEAR", stays unchanged. This can be easily fixed by updating the variable 'aaYear' with the while-loop counter-variable 'aYear' at the beginning of the loop.
Will this change answers?
No
Will you be implementing this yourself?
No
The text was updated successfully, but these errors were encountered: