Cannot run cesm1_2_2 using rcp8.5 surface data sets on Yellowstone

[judykeystsai@gmail_com]

Hi all,I tried to run cesm1_2_2 with BRCP85CN, T31 resolution on yellowstone (specifying -mach yellowstone) with the surface data set (i.e., surfdata_48x96_rcp8.5_simyr1850_c151030.nc) I generated using mksurfdata.pl tool in clm model. I got the errors about mismatch of UrbanIput in my lnd.log file (/glade/scratch/cytsai/TestRunT31_CESM122_v1/run/lnd.log.160111-161532):=========== UrbanInput
 /glade/scratch/cytsai/CESM_inputdata/lnd/clm2/surfdata/surfdata_48x96_rcp8.5_si
 myr1850_c151030.nc
 UrbanInput: parameter nlevurb=           15
 does not equal input dataset nlevurb=            5
 ENDRUN: called without a message string
===========And I also saw some weird message came out in the cesm.log file (/glade/scratch/cytsai/TestRunT31_CESM122_v1/run/cesm.log.160111-161532)===========   1: Opened existing file
   1: /glade/p/cesmdata/cseg/inputdata/atm/cam/topo/USGS-gtopo30_48x96_c050520.nc
   1:      131072
   1: NetCDF: Invalid dimension ID or name
   1: Divergence damper for spectral dycore NOT invoked
  15: Divergence damper for spectral dycore NOT invoked
  16: Divergence damper for spectral dycore NOT invoked....   1: Opened existing file
   1: /glade/scratch/cytsai/CESM_inputdata/lnd/clm2/surfdata/surfdata_48x96_rcp8.5_si
   1: myr1850_c151030.nc      458752
   1: NetCDF: Invalid dimension ID or name
   1: NetCDF: Invalid dimension ID or name
   1: NetCDF: Invalid dimension ID or name
   1: NetCDF: Invalid dimension ID or name
   1: NetCDF: Invalid dimension ID or name
   1: UrbanInput: parameter nlevurb=           15
   1: does not equal input dataset nlevurb=            5
===========I'm wondering are those error coming from the surface data set I generated?Thank you     

 

[erik]

The issue with CLM is very simple. You are using a surface dataset for clm4_5, with a run setup for clm4_0. Those two MUST be consistent.

 

[erik]

The issue with CLM is very simple. You are using a surface dataset for clm4_5, with a run setup for clm4_0. Those two MUST be consistent.

 

[erik]

The issue with CLM is very simple. You are using a surface dataset for clm4_5, with a run setup for clm4_0. Those two MUST be consistent.

 

[judykeystsai@gmail_com]

Hi Erik,
Thanks for your reply. I know that the surface data set I generated is from clm4_5. But I do not know how to spcify using clm4_5 when running cesm1_2_2.In fact, the ultimate goal is that I'd like to generate the surface data set using older version of cesm (cesm1_0_3) on yellowstone. However, I could not succeed so I was trying to play around creating the surface data set using the newer version of cesm...I posted my questions here: https://bb.cgd.ucar.edu/problems-generating-surfdata-using-mksurfdatapl-tool-cesm103-yellowstoneHope that either you or anyone in your group might know the solutions... Thank you  

 

[judykeystsai@gmail_com]

Hi Erik,
Thanks for your reply. I know that the surface data set I generated is from clm4_5. But I do not know how to spcify using clm4_5 when running cesm1_2_2.In fact, the ultimate goal is that I'd like to generate the surface data set using older version of cesm (cesm1_0_3) on yellowstone. However, I could not succeed so I was trying to play around creating the surface data set using the newer version of cesm...I posted my questions here: https://bb.cgd.ucar.edu/problems-generating-surfdata-using-mksurfdatapl-tool-cesm103-yellowstoneHope that either you or anyone in your group might know the solutions... Thank you  

 

[judykeystsai@gmail_com]

Hi Erik,
Thanks for your reply. I know that the surface data set I generated is from clm4_5. But I do not know how to spcify using clm4_5 when running cesm1_2_2.In fact, the ultimate goal is that I'd like to generate the surface data set using older version of cesm (cesm1_0_3) on yellowstone. However, I could not succeed so I was trying to play around creating the surface data set using the newer version of cesm...I posted my questions here: https://bb.cgd.ucar.edu/problems-generating-surfdata-using-mksurfdatapl-tool-cesm103-yellowstoneHope that either you or anyone in your group might know the solutions... Thank you