-
Notifications
You must be signed in to change notification settings - Fork 15
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
Support clm2 files #421
Support clm2 files #421
Conversation
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.
From visual inspection, this looks good. Thanks @chengzhuzhang!
@forsyth2 @chengzhuzhang , I ran into the same error when I was processing v1 land output |
Add a second fix to this PR is to support clm2 files in zppy's ncclimo call.
Issue reported by @BunnyVon
Notes from Charlie:
This issue occurs with output from EAM v1 and ELM v1, which use cam and clm2 , respectively, in the output filenames. For EAM v1, use -P cam (it seems like you tried this and it works fine). For ELM v1, use -P clm and ncclimo should automagically use clm2 in the filenames. The take-home message is that -P == --prc_typ actually specifies a "processing type" which is usually though not always the same as the associated string used in history file names. For --prc_typ=clm the string is clm2. In all other respects, -P elm and -P clm behave identically.