Load(): warning messages about ncdf and about socket connections. ncdf4 bug.
Load() uses cdo tools to regrid and ncrename to rename files at various points along its execution.
In some cases, for example when issuing the following script
Data <- Load(exp = c("m04o", "m04p"), obs = "ESA", var = "tos", sdates = paste0(1993:2009, '0501'), nleadtime = 4, leadtimemin = 1, leadtimemax = 4, storefreq = "monthly", sampleperiod = 1, nmember = 10, output = "lonlat", lonmin = -170, lonmax = -120, latmin = -5, latmax = 5, configfile="~obellprat/CFU/s2dverification/inst/config/IC3.conf")
the following warnings raise repeatedly (Execution doesn't stop, actually results are obtained properly):
Error in unserialize(node$con) : error reading from connection
Calls: <Anonymous> ... doTryCatch -> recvData -> recvData.SOCKnode -> unserialize
Execution halted
nco_err_exit(): ERROR NCO will now exit with system call exit(EXIT_FAILURE)
I think the first kind of errors are caused because of the second kind of errors.
Testing the cdo and ncrename commands manually
cdo remapcons,t106grid -selname,tos /cfu/data/esa/monthly_mean/tos/tos_200908.nc tmp.nc
ncrename -v lat,latitude -d lat,latitude -v lon,longitude -d lon,longitude -v .lev,ensemble -d .lev,ensemble -d .reftime,time tmp.nc
I get the following error output:
nco_err_exit(): ERROR Short NCO-generated message (usually name of function that triggered error): nco_enddef()
nco_err_exit(): ERROR Error code is -101. Translation into English with nc_strerror(-101) is "NetCDF: HDF error"
nco_err_exit(): ERROR NCO will now exit with system call exit(EXIT_FAILURE)
After checking in the Internet I've found it's likely an ncdf error, which is fixed in versions beyond 4.3.1 (see http://sourceforge.net/p/nco/bugs/44/)