CESM 2.0.0: ERROR No default value found for ncdata

[abhirami.m]

Hello,
I am trying to run the BHIST compset with the f02_g17 (~25 km) resolution as an unsupported case using --run-unsupported in CESM 2.0.0.
During the case setup/build, I receive the following error:

ERROR: No default value found for ncdata

I understand that this may be related to the atmospheric initial condition file. However, I can see the relevant input data available in the CESM inputdata repository.
Could someone please clarify why CESM is unable to find a default value for ncdata in this configuration? Do I need to explicitly specify the appropriate ncdata file in user_nl_cam, or is there another configuration required for the BHIST + f02_g17 unsupported case?
I also tried running an FHIST case with the ne120_g17 resolution, but I encountered the following error during the CLM build stage:

CLM build-namelist::CLMBuildNamelist::add_default():No default value found for flanduse_timeseries.
I can find the corresponding .log file in the input-data repository:

https://svn-ccsm-inputdata.cgd.ucar...120np4_hist_78pfts_simyr1850-2015_c170428.log

However, I cannot locate the actual flanduse_timeseries NetCDF file. Could someone please advise whether this input file is available elsewhere, or suggest the appropriate flanduse_timeseries file/settings for an FHIST case at this resolution?

Thank you.

 

[slevis]

In this thread I will help troubleshoot the landuse question.

These are the ne120np4_hist files that I see available in the repository:

landuse.timeseries_ne120np4_hist_16pfts_Irrig_CMIP6_simyr1850-2015_c170824.nc
landuse.timeseries_ne120np4_hist_16pfts_Irrig_CMIP6_simyr1850-2015_c190529.nc
landuse.timeseries_ne120np4_hist_16pfts_simyr1850-2015_c170428.log
landuse.timeseries_ne120np4_hist_78pfts_CMIP6_simyr1850-2015_c190715.nc
landuse.timeseries_ne120np4.pg3_hist_16pfts_Irrig_CMIP6_simyr1850-2015_c190529.nc
landuse.timeseries_ne120np4.pg3_hist_16pfts_Irrig_CMIP6_simyr1850-2015_c190816.nc
landuse.timeseries_ne120np4.pg3_hist_78pfts_CMIP6_simyr1850-2015_c190715.nc
landuse.timeseries_ne120np4.pg3_hist_78pfts_CMIP6_simyr1850-2015_c190816.nc

You can try one of the existing .nc files in your user_nl_clm.

 

[abhirami.m]

In this thread I will help troubleshoot the landuse question.

These are the ne120np4_hist files that I see available in the repository:

landuse.timeseries_ne120np4_hist_16pfts_Irrig_CMIP6_simyr1850-2015_c170824.nc
landuse.timeseries_ne120np4_hist_16pfts_Irrig_CMIP6_simyr1850-2015_c190529.nc
landuse.timeseries_ne120np4_hist_16pfts_simyr1850-2015_c170428.log
landuse.timeseries_ne120np4_hist_78pfts_CMIP6_simyr1850-2015_c190715.nc
landuse.timeseries_ne120np4.pg3_hist_16pfts_Irrig_CMIP6_simyr1850-2015_c190529.nc
landuse.timeseries_ne120np4.pg3_hist_16pfts_Irrig_CMIP6_simyr1850-2015_c190816.nc
landuse.timeseries_ne120np4.pg3_hist_78pfts_CMIP6_simyr1850-2015_c190715.nc
landuse.timeseries_ne120np4.pg3_hist_78pfts_CMIP6_simyr1850-2015_c190816.nc

You can try one of the existing .nc files in your user_nl_clm.

Thank you very much for looking into this and listing the available files.
Could you please share the source or direct link to the repository where these files are hosted?

 

[oleson]

I think that the most relevant file based on your log name would be landuse.timeseries_ne120np4_hist_78pfts_CMIP6_simyr1850-2015_c190715.nc. I don't see this in the inputdata repository.
But it seems to be showing up in the gdex repository: NSF NCAR GDEX Dataset d651077
Try using the filter to download it.

 

[abhirami.m]

I think that the most relevant file based on your log name would be landuse.timeseries_ne120np4_hist_78pfts_CMIP6_simyr1850-2015_c190715.nc. I don't see this in the inputdata repository.
But it seems to be showing up in the gdex repository: NSF NCAR GDEX Dataset d651077
Try using the filter to download it.

Thank you for the reply! it was very helpful, and I'm currently in the process of downloading the 78-pfts dataset as suggested. As it is a largedataset,
in the meantime, I tried running an FHIST compset on the ne120_g16 grid using the 16-pfts configuration, with landuse.timeseries_ne120np4_hist_16pfts_CMIP6_simyr1850-2015_c190715.nc as my landuse timeseries file. However, I ran into the following error :

Confirm that the year of your surface dataset
corresponds to the first year of your landuse_timeseries file
calling getglobalwrite with decomp_index= 87938 and clmlevel= gridcell
local gridcell index = 87938
global gridcell index = 82967
gridcell longitude = 69.7500000000000
gridcell latitude = 33.0162631088420
ENDRUN:
ERROR: ERROR in dynpftFileMod.F90 at line 162
(e.g., for a landuse_timeseries file starting at year 1850, which is typical,
you should be using an 1850 surface dataset),
and that your landuse_timeseries file is compatible with the surface dataset.

If you are confident that you are using the correct landuse_timeseries file
and the correct surface dataset, then you can bypass this check by setting:
check_dynpft_consistency = .false.
in user_nl_clm


It looks like the model is flagging a mismatch between my surface dataset and the 1850 start year of the landuse timeseries file,Can I get any advice on this error?
Thanks again for your help!

 

[abhirami.m]

Thank you for the reply! it was very helpful, and I'm currently in the process of downloading the 78-pfts dataset as suggested. As it is a largedataset,
in the meantime, I tried running an FHIST compset on the ne120_g16 grid using the 16-pfts configuration, with landuse.timeseries_ne120np4_hist_16pfts_CMIP6_simyr1850-2015_c190715.nc as my landuse timeseries file. However, I ran into the following error :

Confirm that the year of your surface dataset
corresponds to the first year of your landuse_timeseries file
calling getglobalwrite with decomp_index= 87938 and clmlevel= gridcell
local gridcell index = 87938
global gridcell index = 82967
gridcell longitude = 69.7500000000000
gridcell latitude = 33.0162631088420
ENDRUN:
ERROR: ERROR in dynpftFileMod.F90 at line 162
(e.g., for a landuse_timeseries file starting at year 1850, which is typical,
you should be using an 1850 surface dataset),
and that your landuse_timeseries file is compatible with the surface dataset.

If you are confident that you are using the correct landuse_timeseries file
and the correct surface dataset, then you can bypass this check by setting:
check_dynpft_consistency = .false.
in user_nl_clm


It looks like the model is flagging a mismatch between my surface dataset and the 1850 start year of the landuse timeseries file,Can I get any advice on this error?
Thanks again for your help!

Update: Turns out the 16-PFT configuration isn't viable for my case, I need to use the 78-PFT dataset after all. So I'll continue with the download and proceed with the 78-PFT setup as originally suggested.
Thanks again for the help! I'll follow up if I run into any issues once that's set up.