Problems running CESM1.0

[meir02ster@gmail_com]

Hi, Brian.

Now the model failed at run step. Here is what I get:
[meir02@water test]$ ./test.generic_linux_pgi.run
./test.generic_linux_pgi.run: Set mpirun to /usr/local/mpi2/bin/mpirun
CCSM_COMPSET=F_2000_CAM5 (FC5)
COMP_ATM=cam
COMP_LND=clm
COMP_ICE=cice
COMP_GLC=sglc
COMP_OCN=docn
COMP_CPL=cpl
CCSM_LCOMPSET=F_2000_CAM5
CCSM_SCOMPSET=FC5
COMP_INTERFACE=MCT
BUILD_COMPLETE=TRUE
SMP_BUILD=a0l0i0o0g0c0
SMP_VALUE=a0l0i0o0g0c0
CICE_DECOMPTYPE=cartesian
CICE_AUTO_DECOMP=true
-------------------------------------------------------------------------
CCSM BUILDNML SCRIPT STARTING
- To prestage restarts, untar a restart.tar file into /home/meir02/cesm1_0/test/test/run
/home/meir02/cesm1_0/test/Buildconf/cpl.buildnml.csh: Set mpirun to /usr/local/mpi2/bin/mpirun
- Create modelio namelist input files
CCSM BUILDNML SCRIPT HAS FINISHED SUCCESSFULLY
-------------------------------------------------------------------------
CCSM PRESTAGE SCRIPT STARTING
- CCSM input data directory, DIN_LOC_ROOT_CSMDATA, is /home/meir02/ccsm4_0/inputdata
- Case input data directory, DIN_LOC_ROOT, is /home/meir02/ccsm4_0/inputdata
- Checking the existence of input datasets in DIN_LOC_ROOT
CCSM PRESTAGE SCRIPT HAS FINISHED SUCCESSFULLY
rm: No match.
Fri Sep 24 13:14:15 CDT 2010 -- CSM EXECUTION BEGINS HERE
Fri Sep 24 13:14:56 CDT 2010 -- CSM EXECUTION HAS FINISHED
Model did not complete - see /home/meir02/cesm1_0/test/test/run/cpl.log.100924-131349

Here is the cpl.log.100924-131349 file:

(seq_mct_drv) : Initialize each component: atm, lnd, ocn, and ice
(seq_mct_drv) : Initialize atm component
(seq_mct_drv) : Initialize lnd component

So the log file is not indicative at all. Hope to get some clues from you.

Thank you!
Rui

 

[meir02ster@gmail_com]

I am sorry I should not be too focused on the complaining file cpl.log*. I found the real errors in ccsm.log* files. It seems the problem is solved. Thanks!

Rui

 

[lixz@ieecas_cn]

It's OK. .........

 

[lixz@ieecas_cn]

I have the output files such as:
test3.cam2.h0.0001-01.nc test3.clm2.h0.0001-02.nc
test3.cam2.h0.0001-02.nc test3.clm2.h0.0001-03.nc
test3.cam2.h0.0001-03.nc test3.clm2.h0.0001-04.nc
test3.cam2.h0.0001-04.nc test3.clm2.h0.0001-05.nc
test3.cam2.h0.0001-05.nc test3.clm2.h0.0001-06.nc
test3.cam2.h0.0001-06.nc test3.clm2.h0.0001-07.nc
test3.cam2.h0.0001-07.nc test3.clm2.h0.0001-08.nc
When I want to open them by gradsc, gradsnc, gradsods or gradshdf, I got:
ga-> sdfopen test3.cam2.h0.0001-05.nc
Scanning self-describing file: test3.cam2.h0.0001-05.nc
test3.cam2.h0.0001-05.nc does not exist or is not a netCDF/HDF-SDS file.

Couldn't ingest SDF metadata.

 

[lixz@ieecas_cn]

After I deleted the variables slat and slon, it's OK. What's the intests by added them in output files from CESM1?

 

[eaton]

slon and slat are the coordinates of fields on the FV dycore's staggered grid. In the h0 files the U and V fields have been interpolated to cell centers. In the initial files the fields US and VS are the velocity components on the staggered grid which is used internally by the dycore. The slon and slat coordinate variables are needed for US and VS. These variables do not affect the status of the h0 files as netCDF files. Nor do they affect the compliance of the files to the CF metadata convention. The problem is in the application.