Problem with regional CTSM5.3 simulation

[johanna_teresa]

Hello,

I am trying to run a regional simulation over Switzerland with ctsm5.3, which I had set up for a previous version of the model. The simulation keeps crashing after a few seconds, and the error logs point towards line 409 in CTSM/src/main/ncdio_pio.F90, which if I understand it correctly indicates a mismatch in dimension of some sort. In order to eliminate the possibility of a problem with my own previously generated (and now updated for version 5.3) surface data file I have re-created a test file over a similar region with:

./subset_data region --lat1 45.5 --lat2 48.5 --lon1 5.5 --lon2 10.5 --reg CH_in --create-surface --surf-year 2000 --create-mesh --create-domain --create-user-mods --inputdata-dir /capstor/scratch/cscs/jmalle/ctsm5_3/input --outdir /capstor/scratch/cscs/jmalle/ctsm5_3/input/regional_cases

and then used the generated surface datafile and mesh file.

Do you happen to know what the source for this error could be?

Logs and surfacedate/mesh files are attached, as are machine port related files. Steps I have taken during file creation are below.

Best,
Johanna

What version of the code are you using?
ctsm5.3.021

Describe every step you took leading up to the problem:
COMPILER=intel
COMPSET=I2000Clm50Sp
RES=CLM_USRDAT
./create_newcase --case ${CASEDIRPATH}${CASE} --compiler ${COMPILER} --compset ${COMPSET} --res ${RES} --mach eiger --driver nuopc --mpilib mpich --pecount 128 --run-unsupported
./xmlchange COMP_INTERFACE='nuopc'
./xmlchange ATM_DOMAIN_MESH='/capstor/scratch/cscs/jmalle/ctsm5_3/input/regional_cases/domain.lnd.fv0.9x1.25_gx1v7_CH_in_c250220_ESMF_UNSTRUCTURED_MESH.nc'
./xmlchange LND_DOMAIN_MESH='/capstor/scratch/cscs/jmalle/ctsm5_3/input/regional_cases/domain.lnd.fv0.9x1.25_gx1v7_CH_in_c250220_ESMF_UNSTRUCTURED_MESH.nc'
./xmlchange MASK_MESH='/capstor/scratch/cscs/jmalle/ctsm5_3/input/regional_cases/domain.lnd.fv0.9x1.25_gx1v7_CH_in_c250220_ESMF_UNSTRUCTURED_MESH.nc'
./xmlchange ATM_NX=4
./xmlchange LND_NX=4
./xmlchange ATM_NY=3
./xmlchange LND_NY=3

./case.setup
./preview_namelists
./case.build

./xmlchange ATM_NCPL=8
./xmlchange RUN_STARTDATE=$start_date
./xmlchange STOP_OPTION=$stop_opt
./xmlchange STOP_N=$stop_n
./xmlchange DATM_YR_ALIGN=$yr_start
./xmlchange DATM_YR_START=$yr_start
./xmlchange DATM_YR_END=$yr_end

./xmlchange JOB_WALLCLOCK_TIME=$time --subgroup case.run
./xmlchange JOB_QUEUE=$job_queue --force

./case.submit

 

[oleson]

I see this in your lnd log:

Reading initial conditions from file ./init_generated_files/finidat_interp_dest.nc
(GETFIL): attempting to find local file
finidat_interp_dest.nc
(GETFIL): using ./init_generated_files/finidat_interp_dest.nc
Reading restart dataset: ./init_generated_files/finidat_interp_dest.nc
check_dim_size ERROR: mismatch of input dimension 12
with expected value 221 for variable gridcell
Did you mean to set use_init_interp = .true. in user_nl_clm?
(Setting use_init_interp = .true. is needed when doing a
transient run using an initial conditions file from a non-transient run,
or a non-transient run using an initial conditions file from a transient run,
or when running a resolution or configuration that differs from the initial conditions.)

which indicates that your surface dataset has 12 (4x3?) gridcells, while the initial file that is being used (./init_generated_files/finidat_interp_dest.nc) has 221 gridcells.
That file is usually generated when use_init_interp is set to .true.
Did that file come from a previous simulation maybe? What is finidat set to in your lnd_in?