evalieungh
New Member
Hi,
I am running single point simulations and run into CN balance check errors when trying to modify the soil depth. Compset 2000_DATM%GSWP3v1_CLM50%FATES_SICE_SOCN_MOSART_SGLC_SWAV_SESP (I2000Clm50Fates)
What version of the code are you using?
CTSM 5.3.034
(NorESMhub's CTSM fork, tag ctsm5.3.034_noresm_v6-1-g9da06e04c)
Older version that did not throw this error: ctsm5.1.dev108
Have you made any changes to files in the source tree?
Input data subset from defaults, GSWP3 forcing.
Surface data has also been modified, including setting zbedrock to 0.55m (more than the actual measurements!). I have also tested with an unaltered version of the surface data.
Other changes are probably not relevant as the model runs OK with them.
Describe every step you took leading up to the problem:
From the case folder's replay.sh:
./xmlchange --force CLM_USRDAT_DIR=/cluster/shared/noresm/inputdata/evaler/inputdata/skj_pt_gswp3
./xmlchange --force PTS_LON=6.41504
./xmlchange --force PTS_LAT=60.9335
#!/bin/bash
set -e
# Created 2025-07-03 11:17:25
CASEDIR="/cluster/work/users/evaler/noresm/FATES_INCLINE/cases/BA-GSWP3-bedrock"
/cluster/home/evaler/CTSM/cime/scripts/create_newcase --case "${CASEDIR}" --compset I2000Clm50Fates --driver nuopc --res CLM_USRDAT --machine betzy --run-unsupported --user-mods-dirs /cluster/shared/noresm/inputdata/evaler/inputdata/skj_pt_gswp3/user_mods --project nn9774k
cd "${CASEDIR}"
./case.setup
./xmlchange NTASKS=1
./xmlchange DATM_MODE=CLMGSWP3v1
./xmlchange STOP_N=5
./xmlchange STOP_OPTION=nyears
./xmlchange RUN_STARTDATE=1902-01-01,DATM_YR_START=1902,DATM_YR_END=1907
./xmlchange DATM_YR_ALIGN=1902
./xmlchange CLM_USRDAT_NAME=ALP4
./xmlchange CLM_USRDAT_DIR=/cluster/shared/noresm/inputdata/evaler/inputdata/skj_pt_gswp3
./xmlchange PTS_LON=6.41504
./xmlchange PTS_LAT=60.9335
./xmlchange JOB_WALLCLOCK_TIME=03:59:00
./xmlchange CLM_FORCE_COLDSTART=on
./case.build
./case.submit
user_nl_clm:
fsurdat = '$CLM_USRDAT_DIR/surfdata_ALP4_hist_2000_16pfts_c250701_modified.nc'
fates_paramfile='/cluster/home/evaler/CTSM/src/fates/parameter_files/fates_params_default.nc'
use_excess_ice = .false.
use_bedrock = .true.
If this is a port to a new machine: Please attach any files you added or changed for the machine port (e.g., config_compilers.xml, config_machines.xml, and config_batch.xml) and tell us the compiler version you are using on this machine.
Please attach any log files showing error messages or other useful information.
Machine: Betzy (Norway)
Run land log attached.
Describe your problem or question:
The model fails quickly on a CN balance check error. See attached land log file. This looks like known behaviour when using a FATES compset and setting use_bedrock = .true., see https://github.com/ESCOMP/CTSM/pull/1902. I have tried with both unchanged and modified surface data, but both end in the same error. If I set use_bedrock = .false. (as the default), the model seems to run just fine and produces and archives output. From use_bedrock = .true. error · Issue #732 · NGEET/fates it seems like the change to zbedrock is not used in practice unless use_bedrock is .true. This issue may also be relevant: use_bedrock = .true. error · Issue #732 · NGEET/fates
The problem is that my model experiment is for an alpine site with very shallow soil, and the soil depth is one of the most unreasonable model assumptions. I also have local measurements of actual soil depth that I want to use. So, using the bedrock option is important for my model experiment. I have some older simulation output with clm 5.1, where the surface data is modified with the same observational data and use_bedrock was .true. So has something broken that possibility in the newer versions? Has anyone found a way around this to make FATES run with restricted soil column and use_bedrock = .true.?
I am running single point simulations and run into CN balance check errors when trying to modify the soil depth. Compset 2000_DATM%GSWP3v1_CLM50%FATES_SICE_SOCN_MOSART_SGLC_SWAV_SESP (I2000Clm50Fates)
What version of the code are you using?
CTSM 5.3.034
(NorESMhub's CTSM fork, tag ctsm5.3.034_noresm_v6-1-g9da06e04c)
Older version that did not throw this error: ctsm5.1.dev108
Have you made any changes to files in the source tree?
Input data subset from defaults, GSWP3 forcing.
Surface data has also been modified, including setting zbedrock to 0.55m (more than the actual measurements!). I have also tested with an unaltered version of the surface data.
Other changes are probably not relevant as the model runs OK with them.
Describe every step you took leading up to the problem:
From the case folder's replay.sh:
./xmlchange --force CLM_USRDAT_DIR=/cluster/shared/noresm/inputdata/evaler/inputdata/skj_pt_gswp3
./xmlchange --force PTS_LON=6.41504
./xmlchange --force PTS_LAT=60.9335
#!/bin/bash
set -e
# Created 2025-07-03 11:17:25
CASEDIR="/cluster/work/users/evaler/noresm/FATES_INCLINE/cases/BA-GSWP3-bedrock"
/cluster/home/evaler/CTSM/cime/scripts/create_newcase --case "${CASEDIR}" --compset I2000Clm50Fates --driver nuopc --res CLM_USRDAT --machine betzy --run-unsupported --user-mods-dirs /cluster/shared/noresm/inputdata/evaler/inputdata/skj_pt_gswp3/user_mods --project nn9774k
cd "${CASEDIR}"
./case.setup
./xmlchange NTASKS=1
./xmlchange DATM_MODE=CLMGSWP3v1
./xmlchange STOP_N=5
./xmlchange STOP_OPTION=nyears
./xmlchange RUN_STARTDATE=1902-01-01,DATM_YR_START=1902,DATM_YR_END=1907
./xmlchange DATM_YR_ALIGN=1902
./xmlchange CLM_USRDAT_NAME=ALP4
./xmlchange CLM_USRDAT_DIR=/cluster/shared/noresm/inputdata/evaler/inputdata/skj_pt_gswp3
./xmlchange PTS_LON=6.41504
./xmlchange PTS_LAT=60.9335
./xmlchange JOB_WALLCLOCK_TIME=03:59:00
./xmlchange CLM_FORCE_COLDSTART=on
./case.build
./case.submit
user_nl_clm:
fsurdat = '$CLM_USRDAT_DIR/surfdata_ALP4_hist_2000_16pfts_c250701_modified.nc'
fates_paramfile='/cluster/home/evaler/CTSM/src/fates/parameter_files/fates_params_default.nc'
use_excess_ice = .false.
use_bedrock = .true.
If this is a port to a new machine: Please attach any files you added or changed for the machine port (e.g., config_compilers.xml, config_machines.xml, and config_batch.xml) and tell us the compiler version you are using on this machine.
Please attach any log files showing error messages or other useful information.
Machine: Betzy (Norway)
Run land log attached.
Describe your problem or question:
The model fails quickly on a CN balance check error. See attached land log file. This looks like known behaviour when using a FATES compset and setting use_bedrock = .true., see https://github.com/ESCOMP/CTSM/pull/1902. I have tried with both unchanged and modified surface data, but both end in the same error. If I set use_bedrock = .false. (as the default), the model seems to run just fine and produces and archives output. From use_bedrock = .true. error · Issue #732 · NGEET/fates it seems like the change to zbedrock is not used in practice unless use_bedrock is .true. This issue may also be relevant: use_bedrock = .true. error · Issue #732 · NGEET/fates
The problem is that my model experiment is for an alpine site with very shallow soil, and the soil depth is one of the most unreasonable model assumptions. I also have local measurements of actual soil depth that I want to use. So, using the bedrock option is important for my model experiment. I have some older simulation output with clm 5.1, where the surface data is modified with the same observational data and use_bedrock was .true. So has something broken that possibility in the newer versions? Has anyone found a way around this to make FATES run with restricted soil column and use_bedrock = .true.?