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

RTM_NAMELIST_OPTS: Undefined variable.

adrianne

New Member
Machine: yellowstone
Release: cesm1_1_2

/glade/p/cesmdata/cseg/runs/cesm1_1/b.e11.BRCP85EOZONEC5CN.f09_g16.001 ran from 2006 to 2100, but I need one more year, which required changing numerous input data sets in user_nl_cam. I tried setting CONTINUE_RUN = FALSE, then resubmitting, but got an error message that it was looking for the old oxid file, which it couldn't find in the new tracer_cnst_datapath. So I tried rebuilding. That didn't fix the problem. When I tried running "cesm_setup -clean; cesm_setup" I got the error message, "RTM_NAMELIST_OPTS: Undefined variable." which is no surprise, since it's not defined in env_run.xml.

Next, I took another ensemble member, b.e11.BRCP85EOZONEC5CN.f09_g16.002, reverted to the original oxid file, and the new namelist, and submitted the job without rebuilding or rerunning cesm_setup. That job works fine. I have compared the env_* and user_nl* files. The few differences are case numbers and fincl lists. cesm_setup is identical in both places.

I have two questions:
1) Why didn't it accept the change of oxid files?
2) How do I get the 001 run to reconfigure and rebuild?
 
Top