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

Remove specific variable names for anomaly forcing and use a generic name #186

Open
ekluzek opened this issue Aug 26, 2022 · 7 comments · May be fixed by #292
Open

Remove specific variable names for anomaly forcing and use a generic name #186

ekluzek opened this issue Aug 26, 2022 · 7 comments · May be fixed by #292
Assignees
Labels
CESM Only enhancement New feature or request Responsibility: CTSM Responsibility to manage and accomplish this issue is the CTSM Software group

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Aug 26, 2022

There are specific names for each anomaly forcing variable, this should be redone to only have one generic name for all. The most common case is to use all variables and hence only one file is needed which is also easier to manage.

This relates to this CTSM issue.

http:://gitHub.com/ESCOMP/CTSM/issues/1730

@mvertens
Copy link
Collaborator

@ekluzek - are you going to take this on?

@ekluzek
Copy link
Collaborator Author

ekluzek commented Aug 26, 2022

Yes this is really simple
. And I'll do it with other work with anomaly forcing.

@mvertens
Copy link
Collaborator

Thanks. I've assigned you.

@ekluzek
Copy link
Collaborator Author

ekluzek commented Aug 26, 2022

@adrifoster will take this on. So I'll work with her if needed, and can also be a reviewer.

@adrifoster
Copy link
Contributor

Should I add something to the config_component.xml file? I noticed there isn't anything there right now for Anomaly.Forcings.

@ekluzek I know you said you had a plan for the different SSPs, so perhaps your plan was to add them there? It seems like we could do different stream entries for each SSP, and have the config_component file deal with that, but I'm not sure what your plans were!

@jedwards4b
Copy link
Contributor

@adrifoster What is the current status of this issue?

@ekluzek ekluzek added enhancement New feature or request CESM Only labels Jul 26, 2023
@ekluzek
Copy link
Collaborator Author

ekluzek commented Jul 26, 2023

@jedwards4b @adrifoster just talked about this. This is still something that we want her to do. But, it's not the highest priority right now. We are going to discuss the priority for this in CTSM tomorrow. We also realize that this is something that we need to take care of in the land group, so we will plan on that.

@ekluzek ekluzek added the Responsibility: CTSM Responsibility to manage and accomplish this issue is the CTSM Software group label Aug 3, 2023
@samsrabin samsrabin linked a pull request Sep 26, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CESM Only enhancement New feature or request Responsibility: CTSM Responsibility to manage and accomplish this issue is the CTSM Software group
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants