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

PCNST : Determination of number of constituents

A

andreasb

New Member
Hi,

In a new WACCM/CESM1.0.4 module I create additional constituents (cnst_add), which means that PCNST needs to be increased. At the moment I manually increase that in cam.buildexe.csh. Is that the appropriate way of doing it, or is there a way for CESM to automatically determine PCNST?

Thanks!
Andreas
 
S

santos

Member
Hi Andreas,

PCNST is determined by CAM's configure script, so there are a few different options:

- If using a personal sandbox or development branch with the code, you can edit CAM's configure script (models/atm/cam/bld/configure) to add your module's contribution to the total number of advected constituents ("$nadv"). This is the "appropriate" place to make the change when developing a new feature that needs to be integrated with CAM's build system.

- If you just want a particular case to run, and you know what value of PCNST you need ahead of time, you can pass the option "-nadv" to configure (via CAM_CONFIG_OPTS in env_configure.xml or env_build.xml). This is the "appropriate" place to make the change when you are doing a one-off test, or otherwise don't want to change the copy of CESM that you're using.

- If you need to see CAM's auto-generated value for PCNST before you add in your own tracers, you can keep doing what you're doing.
 
You must log in or register to reply here.
Top