-
Notifications
You must be signed in to change notification settings - Fork 209
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
rename csm_share ? #3953
Comments
@fischer-ncar can you comment here? I think you have renamed it in your cime split work, right? |
Historically it was named that when it was created to refer to the original version of the Climate System Model (CSM). Meaning code shared between CESM model components. So yes if you think of CSM now meaning Climate System Model in a more generic sense -- you don't have to rename it. cime_share is probably a better name for now. But, it's always a question of how important is to change these directory names. |
The current directory names under src/share are fine. Its just the name of the resulting library that is really old. |
To partly answer my question: CIME CCS assumes there's a library called "csm_share" in Tools/Makefile and build.py. So I think we should coordinate if we want to rename it. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I agree that this should be changed and not closed. |
@ekluzek what's the label to keep it from being auto-closed? |
Low Priority - now set. |
Does the "csm" in "csm_share" stand for Climate System Model? That's pretty generic now. Or should we rename it to "cime_share". Is renaming something that has to be done in CCS or can we each rename it on our own after getting our own copies?
The text was updated successfully, but these errors were encountered: