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 use of DIN_LOC_ROOT_CLMFORC in CTSM, but document how to use softlinks when needed #3039

Open
ekluzek opened this issue Mar 28, 2025 · 1 comment
Labels
bfb bit-for-bit enhancement new capability or improved behavior of existing capability usability Improve or clarify user-facing options

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Mar 28, 2025

For usability we plan to remove the DIN_LOC_ROOT_CLMFORC variable in our submodules. And we should remove it from documentation as well. But, we should give instructions on how to use softlinks in order to have DATM forcing files to be in a different disk if that becomes a data management issue.

The submodule parent issue is here:

ESMCI/cime#3097

Definition of done:

  • Complete the list of removals from CDEPS, ccs_config, and CMEPS as defined above
  • Add a section to Users's Guide that talks about how to handle this if disk space becomes a problem
@ekluzek ekluzek added enhancement new capability or improved behavior of existing capability bfb bit-for-bit usability Improve or clarify user-facing options labels Mar 28, 2025
@ekluzek ekluzek added this to the ctsm6.0.0 (code freeze) milestone Mar 28, 2025
@ekluzek
Copy link
Collaborator Author

ekluzek commented Mar 28, 2025

It's currently only in LILAC

lilac/bld_templates/config_machines_template.xml:    <!-- DIN_LOC_ROOT_CLMFORC: override of DIN_LOC_ROOT specific to CLM
lilac/bld_templates/config_machines_template.xml:    <DIN_LOC_ROOT_CLMFORC>$$CIME_OUTPUT_ROOT/inputdata</DIN_LOC_ROOT_CLMFORC>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bfb bit-for-bit enhancement new capability or improved behavior of existing capability usability Improve or clarify user-facing options
Projects
None yet
Development

No branches or pull requests

1 participant