Push notifications in your browser are not yet configured.
You are not logged in, you may not see all content and functionalities. If you have an account, please login .
I have no problems with ncdump on lffd1989010100c.nc, see the listing below.
I checked the file with
ncks -m
see below, which gives information about the format. It says “chunked? yes, compressed? yes” which means that the file is in netcdf4 with hdf/zip library applied. I guess this was performed in the gcmtoclm job in the post.tmpl (you should find anccopy -d 1
or similar command there). It seems to me that you have problems with netcdf4 on your computer systems.Please check whether the command “nccopy -k 1 lffd1989010100c.nc tmp.nc” works (this converts netcdf4 back to classical netCDF format). If it works check whether “ncdump -h tmp.nc” works. If so, replace lffd1989010100c.nc by tmp.nc and run the model again. Please provide the log file of that test. If it takes this hurdle and stops at the next boundary condition file you really have a problem with netCDF4.
// global attributes: :title = “E.Med 0.44 Starter Package subchain” ; :institution = “-” ; :source = “cclm.exe” ; :project_id = “-” ; :experiment_id = “me001” ; :realization = 1 ; :Conventions = “CF-1.0” ; :conventionsURL = “http://www.unidata.ucar.edu/packages/netcdf/conventions.html” ; :contact = “-” ; :references = “http://www.clm-community.eu/” ; :creation_date = “2013-11-06 11:07:58” ;
}