Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

CLM5 atmospheric forcings data

 I am trying to run CLM5 case. The case is created with  ./create_newcase --case ~/I1850Crop -res f19_g17 -compset I1850Clm50BgcCropCru The case is created successfully, since I get the message "This is a CESM scientifically supported compset at this resolution." I then run successfully "case.setup", but when i try to download the input data using  "./check_input_data --download" i get several error messages like Model datm missing file file1 = '/u/exact/brandino/cesm/inputdata/lmwg/atm_forcing.datm7.cruncep_qianFill.0.5d.v7.c160715/Solar6Hrly/clmforc.cruncep.V7.c2016.0.5d.Solr.1901-01.nc'
FAIL: SVN repo 'https://svn-ccsm-inputdata.cgd.ucar.edu/trunk/inputdata' does not have file 'https://svn-ccsm-inputdata.cgd.ucar.edu/trunk/inputdata/lmwg/atm_forcing.datm7.cruncep_qianFill.0.5d.v7.c160715/Solar6Hrly/clmforc.cruncep.V7.c2016.0.5d.Solr.1901-01.nc'
Reason:
svn: warning: W160013: URL 'https://svn-ccsm-inputdata.cgd.ucar.edu/trunk/inputdata/lmwg/atm_forcing.datm7.cruncep_qianFill.0.5d.v7.c160715/Solar6Hrly/clmforc.cruncep.V7.c2016.0.5d.Solr.1901-01.nc' non-existent in revision 30032
svn: E200009: Could not list all targets because some targets don't exist and this for more than 240 files Is this an issue with the SVN repo or I am doing something wrong? thanks, cheers, Matteo
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
Hi MatteoWhat machine are you running on?Note, that the CLM forcing data is saved on the inputdata repository under the "atm/datm7/" subdirectory (so https://svn-ccsm-inputdata.cgd.ucar.edu/trunk/inputdata/atm/datm7/atm_forcing.datm7.cruncep_qianFill.0.5d.v7.c160715). This works out of the box on machines where DIN_LOC_ROOT_CLMFORC=DIN_LOC_ROOT/atm/datm7, which is usually the case. On some machinessuch as the NCAR machine cheyenne, we've had to put the forcing data on a different disk because each of the forcing datasets is about 1TByte. Therewasn't enough space to fit them on the same disk as the rest of the inputdata. So we've had a different locaiton for each. The problem with this is thatthe check_input_data script doesn't handle this case. If you are on a mchine that you are setting up for yourself, it will be easier to setup if you configure it so that DIN_LOC_ROOT_CLMFORC=DIN_LOC_ROOT/atm/datm7. So I recommend doing that unless you can't. Even then -- because this forcing data is so large -- it WILL take a long time to download (likely mutlitple days). So you might wantto manage the download yourself using svn commands directly. Or as discussed in the older CLM User's Guideabout downloading the data, we recommend breaking it up into maybe 20 year segments. See this..http://www.cesm.ucar.edu/models/cesm1.2/clm/models/lnd/clm/doc/UsersGuide/x1230.html#datm_forc_data Hopefully, that helps...  
 
Top