Skip to content
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

Allow config['initial_conditions']=None option #44

Closed
oliverwm1 opened this issue Jan 10, 2020 · 2 comments
Closed

Allow config['initial_conditions']=None option #44

oliverwm1 opened this issue Jan 10, 2020 · 2 comments

Comments

@oliverwm1
Copy link

There are cases where a user might want to specify all initial conditions files via the patch_files option (e.g. if the initial conditions files need to be renamed or they are not all coming from the same directory). However if one leaves config['initial_conditions'] as default, the INPUT directory will be populated with irrelevant GFS initial conditions. The model won't use them if the namelist is set properly, but it's confusing.

@mcgibbon
Copy link
Collaborator

We discussed that you would use this change in a branch as a temporary measure. In the long run we want to do some more extensive changes, which we can discuss in #46.

@oliverwm1
Copy link
Author

I found a workaround so I'm going to close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants