"Input soil moisture dataset is not vegetated as expected" error in soil moilsture stream

[kwzhang]

What version of the code are you using?
CESM2.1.3

Have you made any changes to files in the source tree?
sed -i "$ a use_soil_moisture_streams = .true." user_nl_clm
sed -i "$ a stream_fldfilename_soilm = '/data/home/zuozhy/zhangkw/CESM/OutputData/Ctl_B2000/H2OSOI_Climo.Ctl_B2000.clm2.daily.02020101-03001231.nc'" user_nl_clm
sed -i "$ a stream_fldfilename_ndep = '/data/home/zuozhy/zhangkw/CESM/importdata/fndep_clm_hist_b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.ensmean_1849-2015_monthly_0.9x1.25_c180926.nc'" user_nl_clm


Describe your problem or question:
I am using CESM2.1.3 to fix soil moisture variations by setting use_soil_moisture_streams = .true..
I am using the 2000_CAM60_CLM50%BGC-CROP_CICE_POP2%ECO%ABIO-DIC_MOSART_CISM2%NOEVOLVE_WW3_BGC%BDRD, abbreviated as B2000. First, I ran a 100-year simulation on top of the completed spin-up to obtain the climate state for daily H2OSOI. Second, I set use_soil_moisture_streams = .true. to fix H2OSOI to the climate state of daily H2OSOI. However, I still encountered the following error:

(GETFIL): attempting to find local file surfdata_1.9x2.5_hist_78pfts_CMIP6_simyr2000_c190304.nc
(GETFIL): using /data/share/CESM_inputdata/lnd/clm2/surfdata_map/release-clm5.0.18/surfdata_1.9x2.5_hist_78pfts_CMIP6_simyr2000_c190304.nc
Successfully read monthly vegetation data for
month 1

(shr_dmodel_readstrm) open : /data/home/zuozhy/zhangkw/CESM/OutputData/Ctl_B2000/H2OSOI_Climo.Ctl_B2000.clm2.daily.02020101-03001231.nc
(shr_dmodel_readstrm) file lb: /data/home/zuozhy/zhangkw/CESM/OutputData/Ctl_B2000/H2OSOI_Climo.Ctl_B2000.clm2.daily.02020101-03001231.nc 1
(shr_dmodel_readstrm) file ub: /data/home/zuozhy/zhangkw/CESM/OutputData/Ctl_B2000/H2OSOI_Climo.Ctl_B2000.clm2.daily.02020101-03001231.nc 2
Input soil moisture dataset is not vegetated as expected: gridcell= 1 active = T
ENDRUN:
ERROR: ('PrescribedSoilMoistureInterp') ERROR:: The input soil moisture stream is NOT vegetated for one of the land points


I believe both my experiments are based on B2000, and the vegetated cover for H2OSOI should be completely consistent. This error should not occur. I would like to know what might be causing this error?

Thank you!

 

[slevis]

@kwzhang I searched the Forums for "Input soil moisture dataset is not vegetated" and found that you encountered this error two years ago, as well:

Soil-moisture nudging experiments in CESM2

Hi, I am trying to nudge soil moisture to climotology in F2000climo in CESM2. I only found the Nudging Experiment example (U, V, T, Q) in CAM6.3 User guide. How can I perform a Soil-moisture nudging experiment? I think this experiment should be based on the CLM%, but I haven't found any...

bb.cgd.ucar.edu

An error when I set "use_soil_mositure_stream=.ture. "

Hi everyone, I would like to investigate the role of soil moisture in the influence of the Atlantic Multidecadal Variability (AMV) on the Eurasian climate. Therefore, I would like to design an experiment with prescribed postive-AMO SST pattern in Northern Atlantic and climatology of soil...

bb.cgd.ucar.edu

@oleson had offered an interesting suggestion in the second of these threads:
"set soilm_ignore_data_if_missing = .true. in your user_nl_clm. That would bypass the error but you'd want to check to see your soil moisture against the prescribed to see how different it is."
Keep in mind that bypassing the error could mask a real problem that may exist with your data.

However, you may prefer (and it may be better) to troubleshoot in order to understand why the error occurred:
- One thought that I posted in the first of the above threads, that you may wish to investigate by looking at the involved datasets and possibly also adding "write" statements in the code:
"the code is expecting vegetation or maybe at least bare soil in a grid cell and not finding it?"
- Another thought may be to repeat your steps with new very short simulations to see if you can get things to work the way that you expect. If this works, then you may have accidentally done something different in the case with the error, and you may need to revisit it.