Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

The CESM‘component is selected to run

yuecheng

yuecheng
New Member
What version of the code are you using?
CESM2.2.0


Have you made any changes to files in the source tree?
NO


Describe every step you took leading up to the problem:
I hope that only the atmospheric and land modules are enabled, and other modules are not enabled. How do I do this


If this is a port to a new machine: Please attach any files you added or changed for the machine port (e.g., config_compilers.xml, config_machines.xml, and config_batch.xml) and tell us the compiler version you are using on this machine.
Please attach any log files showing error messages or other useful information.

No


Describe your problem or question: I hope that only the atmospheric and land modules are enabled, and other modules are not enabled. How do I do this
 

peverley

Courtney Peverley
Moderator
Staff member
Hi,

You'll want to construct a compset that uses the versions of CAM and CLM that you want plus the stub versions of the other components.

Here is the list of the component sets (compsets) for reference: CESM2.2.2 Component Sets Definitions

You'll want something like: XXXX_CAMYY_CLMZZ%SP_SICE_SOCN_SROF_SGLC_SWAV, where XXXX is the initialization time, YY is the CAM version (e.g. "60"), and ZZ is the CLM version (e.g. "50"). To create a case with the compset you create, you'll include "--compset XXXX_CAMYY_CLMZZ%SP_SICE_SOCN_SROF_SGLC_SWAV" in your ./create_newcase command.

Hope that helps.
Courtney
 
Vote Upvote 0 Downvote

yuecheng

yuecheng
New Member
Hi,

You'll want to construct a compset that uses the versions of CAM and CLM that you want plus the stub versions of the other components.

Here is the list of the component sets (compsets) for reference: CESM2.2.2 Component Sets Definitions

You'll want something like: XXXX_CAMYY_CLMZZ%SP_SICE_SOCN_SROF_SGLC_SWAV, where XXXX is the initialization time, YY is the CAM version (e.g. "60"), and ZZ is the CLM version (e.g. "50"). To create a case with the compset you create, you'll include "--compset XXXX_CAMYY_CLMZZ%SP_SICE_SOCN_SROF_SGLC_SWAV" in your ./create_newcase command.

Hope that helps.
Courtney
hi,
Thank you for your reply. Can I create a custom compset, and how should I do it?
 
Vote Upvote 0 Downvote

peverley

Courtney Peverley
Moderator
Staff member
Yes,

You'll want to add an XML entry to cime_config/config_compsets.xml. For example, if I wanted to add a pre-industrial compset called "COURTNEY" that uses CLM5, CAM6, and stubs for other components, I would add:

Code:
<compset>
  <alias>COURTNEY</alias>
  <lname>1850_CAM60_CLM50%SP_SICE_SOCN_SROF_SGLC_SWAV</lname>
</compset>

And then, I could use:

Code:
./create_newcase --compset COURTNEY ...

Courtney
 
Vote Upvote 0 Downvote

yuecheng

yuecheng
New Member
Yes,

You'll want to add an XML entry to cime_config/config_compsets.xml. For example, if I wanted to add a pre-industrial compset called "COURTNEY" that uses CLM5, CAM6, and stubs for other components, I would add:

Code:
<compset>
  <alias>COURTNEY</alias>
  <lname>1850_CAM60_CLM50%SP_SICE_SOCN_SROF_SGLC_SWAV</lname>
</compset>

And then, I could use:

Code:
./create_newcase --compset COURTNEY ...

Courtney
Thank you for your prompt response; it has been immensely helpful to me. I appreciate your assistance once again.
 
Vote Upvote 0 Downvote

peverley

Courtney Peverley
Moderator
Staff member
Hi,

My recommendation would be to once again create a custom compset that uses all of the same configurations as B1850, except the stub versions of CICE and ocean:

1850_CAM60_CLM50%BGC-CROP_SICE_SOCN_MOSART_CISM2%NOEVOLVE_WW3_BGC%BDRD

Of course, since this is a custom compset, it will not necessarily grab all of the desired defaults. So, for that, I would recommend building a normal B1850 case as well so you can set the defaults (via user_nl_*) to be the same (you can see all the namelist settings in the run/*_in files for each component).

Hope that answers your question!
Courtney
 
Vote Upvote 0 Downvote
Top