update to ccs_config_cesm1.0.7

[mvertens]

Update ccs_config to be consistent with the latest directory structure in ESCOMP. Used noresm2_5_alpha06 with updating ccs_config. Verified that the following built and ran successfully: ERS_Ln9.ne30pg3_ne30pg3_mtn14.NF1850.betzy_intel.cam-outfrq9s

[mvdebolskiy]

What cime tag are you using for this? Because my cases can't find any queue.

[mvertens]

@mvdebolskiy - please checkout out my branch https://github.com/mvertens/NorESM/tree/feature/noresm2_5_alpha04_v4 This has numerous branches on my forks that need PRs. But the ones that are needed for this PR are the new branches for cime and share.

[mvdebolskiy]

Ugh. This won't work with stand-alone clone of CTSM right now, since there we checkout what ESCOMP checks out except ccs_config.

[mvertens]

So maybe noresm should update the share and cime externals as well moving forwards? Its really hard to have our own separate forks and have CTSM do something different. That applies to stand-alone cam checkout as well. Thoughts?

[mvertens]

I meant CTSM should update not noresm should update.

[mvdebolskiy]

I can do that. But that will mean that CTSM updates will not get pulled fast if they are updating externals. (Which might affect Rosie if she checks out fates that has API changes that require specific version of cdeps/cmeps). I'll try to run your externals in the next couple of days.

[mvertens]

What version of cime and share is ctsm using now? Are they not up to date with the head of cesm?

[mvertens]

So I am confused. Why can't cesm have a different set of externals than CTSM? CTSM can point to an older ccs_config and not update cime and share. This is what happened in CESM/stand-alone-CTSM development. Maybe I'm missing something.

[mvdebolskiy]

What version of cime and share is ctsm using now? Are they not up to date with the head of cesm?

[cime]
local_path = cime
protocol = git
repo_url = https://github.com/ESMCI/cime
tag = cime6.0.217_httpsbranch03
required = True

[share]
tag = share1.0.18
protocol = git
repo_url = https://github.com/ESCOMP/CESM_share
local_path = share
required = True

[cmeps]
tag = cmeps0.14.50
protocol = git
repo_url = https://github.com/ESCOMP/CMEPS.git
local_path = components/cmeps
required = True

[cdeps]
tag = cdeps1.0.28
protocol = git
repo_url = https://github.com/ESCOMP/CDEPS.git
local_path = components/cdeps
externals =  Externals_CDEPS.cfg
required = True

[mvdebolskiy]

So I am confused. Why can't cesm have a different set of externals than CTSM? CTSM can point to an older ccs_config and not update cime and share. This is what happened in CESM/stand-alone-CTSM development. Maybe I'm missing something.

It totally can. We'll just have to point to different branches if this PR is merged before the Betzy update. Current CTSM/noresm tag is couple months old compared to ESCOMP because of git-fleximod. We can update to NorESM2.5 externals after we resolve git-fleximod question.

[mvertens]

@mvdebolskiy - this is ready for merging I believe. I'd like to get this in before we update the modules needed to run on login3.