-
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
Remove climo_diurnal_input_files internal parameter #612
Conversation
46669a4
to
60bd208
Compare
0257e03
to
1a39add
Compare
Ran the following minimal cases (see #608):
These produce results both with and without explicitly setting @chengzhuzhang Is it better 1) to be explicit about the input files we're looking for (and thus require an extra parameter) or 2) to have zppy automatically determine the h number? (2) appears to work, but I'm concerned I just found a simple case where that happens to work. |
@forsyth2 thank you for working on this. To be explicit about the input files would be fine, I'm curious about the mechanism for zppy to automatically infer the h number? |
The second commit currently in this PR: b116dcf
could simply be replaced with
But my concern is that the directories I'm working with just happen to have only the correct |
@forsyth2 I looked it up |
1fba9aa
to
dcb9eb1
Compare
@chengzhuzhang I've updated the second commit (dcb9eb1) and it looks like everything still works if we remove the input file specification in all cases for diurnal cycle. It looks like it was originally introduced in aaaa61d#diff-ed02c5b26bf8ed8e97148b4f81cfdca9afc1706855f5a7aba9e0b7f3c47cee52. It seems the cleaner solution would have been to just use |
I've tested with:
|
Yes, I think it is a better solution. |
dcb9eb1
to
1624d00
Compare
Remove
climo_diurnal_input_files
internal parameter. Resolves #607