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

Add ability to name a different default config file for subset_data #1809

Closed
ekluzek opened this issue Jul 14, 2022 · 0 comments · Fixed by #1812
Closed

Add ability to name a different default config file for subset_data #1809

ekluzek opened this issue Jul 14, 2022 · 0 comments · Fixed by #1812
Assignees
Labels
enhancement new capability or improved behavior of existing capability

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Jul 14, 2022

I need the ability to name and use a different default config file for subset_data. This allows you to use subset data for example to use 1850 datasets, or a different resolution file.

I think eventually we plan to get the surface datasets from a fake_case that subset_data creates and that would supersede this usage. But, until we have that in place, this provides more flexibility that's easy to put into play.

This is required for #1674

@ekluzek ekluzek added the enhancement new capability or improved behavior of existing capability label Jul 14, 2022
@ekluzek ekluzek self-assigned this Jul 14, 2022
ekluzek added a commit to ekluzek/CTSM that referenced this issue Jul 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant