Problem with netCDF library support
Added by Monique Gosseling over 8 years ago
Dear all,
I seem to have an issue with the library support in a Ubuntu 14.04 LTS machine. CDO has been installed to perform some analyses on netCDF files.
Whenever I want to perform a cdo command the machine gives back this message :
cdo sinfo: Open failed on >T2m_EC_1m_1971-80.nc<
Unsupported file type (library support not compiled in)
When I checked with cdo -V it returns this message :
Climate Data Operators version 1.6.2 (http://code.zmaw.de/projects/cdo)
Compiler: gcc -std=gnu99 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -pedantic -fPIC -pthread
version: gcc (Ubuntu/Linaro 4.8.2-4ubuntu1) 4.8.2
Compiled: by buildd on allspice (x86_64-unknown-linux-gnu) Nov 15 2013 17:10:54
Features: PTHREADS Z JASPER PROJ.4 MAGICS
Libraries: proj/4.7
Filetypes: srv ext ieg grb grb2 nc
CDI library version : 1.6.2 of Nov 15 2013 17:10:44
GRIB_API library version : 1.10.4
netCDF library version : 4.1.3 of Feb 24 2014 21:05:37 $
HDF5 library version : 1.8.11
SERVICE library version : 1.3.1 of Nov 15 2013 17:10:28
EXTRA library version : 1.3.1 of Nov 15 2013 17:10:20
IEG library version : 1.3.1 of Nov 15 2013 17:10:24
FILE library version : 1.8.2 of Nov 15 2013 17:10:20
So the netCDF is actually installed, however it does not work(not sure what the dollar sign means here!?)
I was thinking it is a path problem. Do any of you know what the problem is here and how this problem could be solved?
Kind regards,
Monique
Replies (2)
RE: Problem with netCDF library support - Added by Ralf Mueller over 8 years ago
Although the netcdf library is 4.1.3 the CDO binary was not build with nc4 support. You should update to a newer version of CDO.
Anaconda might be useful, because, you can install software below your $HOME dir. and for Linux64bit its already compiled - so no manual build needed.
hth
ralf
RE: Problem with netCDF library support - Added by Monique Gosseling over 8 years ago
Dear Ralf,
Thanks for your response. The problem is now solved with updating to a newer version of CDO.
Kind regards,
Monique