Running CESM2.1 with nudging at high resolution

[schu2@uwyo_edu]

Hello,I was trying to run CESM2.1 at f05_f05_mg17 resolution nudging toward MERRA2 but it stoppped when starting reading the files. Here is some info from cesm.log file:  Opened existing file /gpfs/fs1/p/cesm/chwg_dev/met_data/MERRA2/0.5x0.63/fv_0.47x0.63_nc3000_Co030_Fi 001_PF_nullRR_Nsw021_MERRA2_c180612.nc           1 Opened existing file /glade/p/cesmdata/cseg/inputdata/atm/cam/ozone_strataero/ozone_strataero_WACCM_ L70_zm5day_18500101-20150103_CMIP6ensAvg_c180923.nc           2 Opened existing file /glade/p/cesmdata/cseg/inputdata/atm/waccm/lb/LBC_1750-2015_CMIP6_GlobAnnAvg_c1 80926.nc           2 Opened existing file /gpfs/fs1/p/cesm/chwg_dev/met_data/MERRA2/0.5x0.63/2010/MERRA2_0.5x0.63_2010020 1.nc           2 WARNING: Rearr optional argument is a pio2 feature, ignored in pio1 pio_support::pio_die:: myrank=          -1 : ERROR: pionfread_mod.F90.in:         204 : NetCDF: Index exceeds dimension bound 
I didn`t understand why the value following the file is "1" or "2", and I think this caused the "Index exceeds dimension bound". Did anyone come to this kind of issue?Any help will be appreciated. 

 

[jedwards]

cesm2.1 is not supported at this resolution.  Index exceeds dimension bound indicates an incorrect access to the file and is not related to the number of currently open files (1 or 2)

 

[schu2@uwyo_edu]

Thank you Sir. I realized that cesm2.1 is not supported at this resolution so I interpolated the ncdata into 0.5 degree resolution and used "--run-unsupported" when I created the case.  The free-run works but the problem came out when i did nudging. Do you have any idea about this issue?