Question regarding the CLM 4.0 mapping toolset (mkmapdata.sh)

Hello,
I'm currently trying to implement variable resolution (var-res) grids within CESM 1.2.0 in both CAM and CLM on Yellowstone.  It has been done successfully in CAM, but my colleagues and I are currently working on CLM.  The main goal is to get 12.5 km var-res grids implemented into CLM 4.0 and CAM5 (Spectral Element).  So, currently we have created SCRIP and TEMPLATE files for the 12.5 km var-res grid and have begun to create the 13 mapping files in ~/mkmapdata/mkmapdata.sh   The problem is that once the script hits the mapping file "map_10x10min_IGBPmergeICESatGIS" it appears (according to my log file error below) that it doesn't find it in the repository on Yellowstone. ------------------------------------------------------------------------------Creating mapping file: map_10x10min_IGBPmergeICESatGIS_to_AR_30_x8_nomask_aave_da_c140109.ncFrom input grid:For output grid: AR_calif_30_x8.g_scrip.nc Either input or output grid or output mapping file is NOT set-------------------------------------------------------------------------------- I went into the repository on Yellowstone to take a look: /glade/p/cesmdata/cseg/inputdata/lnd/clm2/mappingdata/grids
and I found the file that should have been sourced within it: 
SCRIPgrid_10x10min_IGBPmergeICESatGIS_c110818.nc
So, I'm not sure why the job failed since the file is there. Does anyone have any ideas as to why it might have error'd out?  
I was able to comment out 10x10min_IGBPmergeICESatGIS within mkmapdata.sh (line 273) and proceed to generate the next two mapping files (3x3min_GLOBE-Gardner and 3x3min_GLOBE-Gardner-mergeGIS) and changed their date strings at the end of the file names to match the other files I generated previously.  Also, I've tried to see if I can moved forward on the next portion of the grid generation (mksurfdata_map), but it appears that you need to generate all 13 mapping files prior to moving to the next step.  So I'm stuck for the time being. I appreciate any insights you might have. Thanks in advance!
AR
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
This is due to the following bug in both cesm1.2.0 and cesm1.2.1http://bugs.cgd.ucar.edu/show_bug.cgi?id=1902
The bug report tells you about the change that needs to be made to get it to work. You just need to remove the need for mkmapdata.sh to try to map that particular resolution as it's un-needed for clm4_0.
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
This is due to the following bug in both cesm1.2.0 and cesm1.2.1http://bugs.cgd.ucar.edu/show_bug.cgi?id=1902
The bug report tells you about the change that needs to be made to get it to work. You just need to remove the need for mkmapdata.sh to try to map that particular resolution as it's un-needed for clm4_0.
 
Back
Top