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

Change most/all CLM51 compsets to CLM52 #1881

Closed
billsacks opened this issue Oct 25, 2022 · 1 comment
Closed

Change most/all CLM51 compsets to CLM52 #1881

billsacks opened this issue Oct 25, 2022 · 1 comment
Labels
closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix enhancement new capability or improved behavior of existing capability

Comments

@billsacks
Copy link
Member

In #1880 I will be creating a new CLM52 compset option. There probably won't be many differences between CLM51 and CLM52 (since my understanding is that we're going to use the new surface datasets even for CLM51), so I imagine we'll soon want to change most/all CLM51 compsets to CLM52, because presumably people will want to use the new behavior for #1878 as well as any other new behavior that comes in with CLM52.

In addition to changing this for I compsets, we should consider changing the standard F and B compsets to also use CLM52.

@billsacks billsacks added enhancement new capability or improved behavior of existing capability next this should get some attention in the next week or two. Normally each Thursday SE meeting. labels Oct 25, 2022
@billsacks
Copy link
Member Author

From today's discussion: we won't do a CLM52.

@billsacks billsacks added closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix and removed next this should get some attention in the next week or two. Normally each Thursday SE meeting. labels Oct 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix enhancement new capability or improved behavior of existing capability
Projects
None yet
Development

No branches or pull requests

1 participant