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

Get lobata in ccs_config and working with NUOPC #1794

Closed
ekluzek opened this issue Jun 30, 2022 · 0 comments · Fixed by #1515
Closed

Get lobata in ccs_config and working with NUOPC #1794

ekluzek opened this issue Jun 30, 2022 · 0 comments · Fixed by #1515
Assignees
Labels
enhancement new capability or improved behavior of existing capability

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Jun 30, 2022

To support FATES users we need to get lobata as a supported cime machine in ccs_config and working with NUOPC. See the FATES issue for more details on this...

NGEET/fates#881

@ekluzek ekluzek added the enhancement new capability or improved behavior of existing capability label Jun 30, 2022
@ekluzek ekluzek moved this from Needs Prioritization to Todo ~ weeks in CESM: infrastructure / cross-component SE priorities Jun 30, 2022
@ekluzek ekluzek moved this from Todo ~ weeks to In Progress in CESM: infrastructure / cross-component SE priorities Jul 12, 2022
fischer-ncar added a commit to ESMCI/ccs_config_cesm that referenced this issue Jul 15, 2022

This PR adds the necessary configuration files and entries to include the FATES development workstation, lobata as a supported machine. It also removes the now retired lawrencium-lr2 entry.

Addresses NGEET/fates#881 and ESCOMP/CTSM#1794
Repository owner moved this from In Progress to Done in CESM: infrastructure / cross-component SE priorities Jul 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability
Projects
Status: Done (or no longer holding things up)
Development

Successfully merging a pull request may close this issue.

2 participants