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

Problem with setting start_ymd and stop_ymd

Hi,
I am using standalone CAM 5.3. I was trying to run the model for 1st Dec 1978 to 31st Nov 2014. This is my build-namelist options.  ../cesm1_2_2/models/atm/cam/bld/build-namelist -test -runtype startup -config /center/w/basu/cam_5/cam_bld_obs/config_cache.xml -case obs_1 -namelist "&atm nhtfrq(1) = -6 mfilt(1) = 1460 stop_option = 'nyears' stop_n = 35 start_ymd = 19781201 stop_ymd = 20141215 ncdata = '/center/w/basu/cam_5/inputdata/atm/cam/inic/fv/cami-mam3_0000-01-01_0.9x1.25_L30_c100618.nc' bndtvs = '/center/w/basu/cam_5/inputdata/atm/cam/sst/sst_HadOIBl_bc_0.9x1.25_1850_2014_c150416.nc'/"I first tried with setting start_ymd and stop_ymd only but the model crashed.(shr_sys_abort) ERROR: (seq_timemgr_alarmInit) :ndays invalid opt_n
(shr_sys_abort) WARNING: calling shr_mpi_abort() and stopping
(shr_sys_abort) ERROR: (seq_timemgr_alarmInit) :ndays invalid opt_n
(shr_sys_abort) WARNING: calling shr_mpi_abort() and stopping
Rank 8 [Wed Nov 11 13:13:07 2015] [c1-0c0s1n2] application called MPI_Abort(MPI_COMM_WORLD, 1001) - process 8

So I set stop_option and stop_n as well.But now the model crashed again with a different error with ocn component. RTM will not be active
(seq_mct_drv) : Initialize ocn component OCN
(shr_file_setIO) file ocn_modelio.nml nonexistent
Rank 0 [Wed Nov 11 12:58:25 2015] [c0-0c0s1n0] application called MPI_Abort(MPI_COMM_WORLD, 1001) - process 0
(shr_sys_abort) ERROR: (shr_stream_findBounds) ERROR: LVD not found, all data is after yearLast
(shr_sys_abort) WARNING: calling shr_mpi_abort() and stopping
_pmiu_daemon(SIGCHLD): [NID 00002] [c0-0c0s1n0] [Wed Nov 11 12:58:25 2015] PE RANK 0 exit signal Aborted
[NID 00002] 2015-11-11 13:02:27 Apid 427879: initiated application termination
Application 427879 exit codes: 134
Application 427879 exit signals: Killed
Application 427879 resources: utime ~702s, stime ~5s, Rss ~507604, inblocks ~7752874, outblocks ~19233148


However with climatological boundary conditions the model is running. Thanks,Soumik
 

eaton

CSEG and Liaisons
When using CAM standalone scripts one must become more familiar with the
details of how build-namelist works.  The first thing to recognize is that
by default build-namelist tries to set up a run for present day
climatology.  To do a historical run like you are attempting requires
setting more namelist variables.  The build-namelist utility makes use of
the -use_case argument to do this.  This is also how build-namelist
supports the features of the CESM compsets.

The first problem you encountered is due to setting namelist variables
incorrectly.  The namelist documentation points out that the stop_ymd
variable should be used in conjunction with setting stop_option='date'.

The second problem is due to not setting the variables stream_year_first
and stream_year_last which are used to set up the namelists needed by the
DOCN and CICE codes when reading time varying input.  For this I'm afraid
the documentation is not very helpful.  The technique I'd recommend here is
to look at the namelists which are generated by giving build-namelist the
argument "-use_case 1850-2005_cam5".  You can then customize to suit your
own needs by adding namelist variables to the -namelist commandline
argument as these values will override any use case settings.  It is also
possible to do your customization in the file that defines the use case.
In this instance that file is
bld/namelist_files/use_cases/1850-2005_cam5.xml.

 
Top