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.

Sign up for GitHub

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

Jump to bottom

Refactor surfrd for FATES #1785

Open
ekluzek opened this issue Jun 17, 2022 · 1 comment
Open

Refactor surfrd for FATES #1785

ekluzek opened this issue Jun 17, 2022 · 1 comment
Assignees
@ekluzek
Labels
code health improving internal code structure to make easier to maintain (sustainability) enhancement new capability or improved behavior of existing capability

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Jun 17, 2022

This starts with the following comment for ctsm5.1.dev099.

#1766 (review)

We'd like to do some refactoring in how the surface dataset is read in for FATES. We want to make it easier for it to start using crop datasets and also do some of the collapse functionality that is in CTSM.
@ekluzek ekluzek added enhancement new capability or improved behavior of existing capability code health improving internal code structure to make easier to maintain (sustainability) labels Jun 17, 2022
@ekluzek ekluzek self-assigned this Jun 17, 2022
@ekluzek
Copy link
Collaborator Author

ekluzek commented Jun 17, 2022

This relates to the following issues:

#1780
#1609
#1505
#1046

@glemieux glemieux removed the status in FATES issue board Oct 7, 2024
@glemieux glemieux moved this to ❕Todo in FATES issue board Oct 7, 2024
@slevis-lmwg slevis-lmwg mentioned this issue Oct 7, 2024
Open
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ekluzek ekluzek

Labels
code health improving internal code structure to make easier to maintain (sustainability) enhancement new capability or improved behavior of existing capability
Projects
CTSM-FATES priorities
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ekluzek