judykeystsai@gmail_com
New Member
Hi all,
I have some questions about surface data sets used for running CESM.I tried to generate my own surface data set in order to get CESM run with BRCP85CN, T31 and I noticed that there might be some problems of creating a "correct" surface data set by using the mksurfdata.pl (in cesm1_2_2). The model gave out errors of inconsistant urban level (nlevurb should be 15 insteand of 5).So I compared the dimensions of nlevurb in the surface data set I generated and the other surface data sets on yellowstone (i.e. the data set at /glade/p/cesmdata/cseg/inputdata/lnd/clm2/surfdata/surfdata_48x96_simyr1850_c110114.nc)I noticed that the one on yellowstone (surfdata_48x96_simyr1850_c110114.nc) has "nlevurb = 15"However, the surface data set I generated only has "nlevurb = 5" when using mksurfdata.pl tool.I think it might because the urban data file that the mksurfdata.pl tool used on yellowstone only has "nlevurb = 5"====ncudump -h /glade/p/cesm/cseg/inputdata/lnd/clm2/rawdata/mksrf_urban_0.05x0.05_simyr2000.c120621.nc netcdf mksrf_urban_0.05x0.05_simyr2000.c120621 {
dimensions:
lat = 3600 ;
lon = 7200 ;
numsolar = 2 ;
numrad = 2 ;
nlevurb = 5 ;
region = 33 ;
density_class = 3 ;====However, I notice that there's another urban file on yellowstone which has "nlevurb": ncdump -h /glade/p/cesm/cseg/inputdata/lnd/clm2/rawdata/mksrf_urban_0.05x0.05_simyr2000.c120418.nc
netcdf mksrf_urban_0.05x0.05_simyr2000.c120418 {
dimensions:
lat = 3600 ;
lon = 7200 ;
numsolar = 2 ;
numrad = 2 ;
nlevurb = 15 ;
region = 33 ;
density_class = 3 ;
And unfortunately the file "mksrf_urban_0.05x0.05_simyr2000.c120621.nc "was the one used in mksurfdata.pl tool...Does anyone know how to fix this? It seemed that the surface data set with "nlevurb = 15" is what the CESM required for surface data set Thank youJudy
I have some questions about surface data sets used for running CESM.I tried to generate my own surface data set in order to get CESM run with BRCP85CN, T31 and I noticed that there might be some problems of creating a "correct" surface data set by using the mksurfdata.pl (in cesm1_2_2). The model gave out errors of inconsistant urban level (nlevurb should be 15 insteand of 5).So I compared the dimensions of nlevurb in the surface data set I generated and the other surface data sets on yellowstone (i.e. the data set at /glade/p/cesmdata/cseg/inputdata/lnd/clm2/surfdata/surfdata_48x96_simyr1850_c110114.nc)I noticed that the one on yellowstone (surfdata_48x96_simyr1850_c110114.nc) has "nlevurb = 15"However, the surface data set I generated only has "nlevurb = 5" when using mksurfdata.pl tool.I think it might because the urban data file that the mksurfdata.pl tool used on yellowstone only has "nlevurb = 5"====ncudump -h /glade/p/cesm/cseg/inputdata/lnd/clm2/rawdata/mksrf_urban_0.05x0.05_simyr2000.c120621.nc netcdf mksrf_urban_0.05x0.05_simyr2000.c120621 {
dimensions:
lat = 3600 ;
lon = 7200 ;
numsolar = 2 ;
numrad = 2 ;
nlevurb = 5 ;
region = 33 ;
density_class = 3 ;====However, I notice that there's another urban file on yellowstone which has "nlevurb": ncdump -h /glade/p/cesm/cseg/inputdata/lnd/clm2/rawdata/mksrf_urban_0.05x0.05_simyr2000.c120418.nc
netcdf mksrf_urban_0.05x0.05_simyr2000.c120418 {
dimensions:
lat = 3600 ;
lon = 7200 ;
numsolar = 2 ;
numrad = 2 ;
nlevurb = 15 ;
region = 33 ;
density_class = 3 ;
And unfortunately the file "mksrf_urban_0.05x0.05_simyr2000.c120621.nc "was the one used in mksurfdata.pl tool...Does anyone know how to fix this? It seemed that the surface data set with "nlevurb = 15" is what the CESM required for surface data set Thank youJudy