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

Question on the way of running.

Dear all:

what is the difference between running cam5 from 1) cesm/scripts/ using some compset (say FAMIPC5) and 2)the conventional way

.../bld/confiure ..... then make build-namelist.

I found the namelist generated in the conventional way is quite different from the former one.

Is it possible to use the namelist generated by the first way for cam binary in 2)?
 

eaton

CSEG and Liaisons
The benefit that running from the CESM scripts provides is that they set up commonly used runs (for example runs that are done for the CMIP5 project) and take care of the details of retrieving needed input datasets and archiving the output.

Running CAM from standalone scripts is typically better for development work and running non-standard configurations.

Taking the example of the FAMIPC5 compset, this compset includes a specification of the SST and sea ice datasets that should be used in AMIP simulations. This will produce a different namelist than a default CAM standalone run because by default CAM's build-namelist will set SST and sea ice files assuming present day climatology. However, if you know the AMIP datasets you want to use then you can easily add those customizations to a CAM standalone script.
 
Top