[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #KRB-849418]: netCDF versions



Hi Eve-Marie,

> I hope this email finds you well.
> I have an unusual project where I need to replicate on a linux cluster
> what is at NCEP on their IBM production machine. The versions they have
> in production is netCDF 3.5.0 which is 10 years old. (sight...) I
> actually can't get it to compile on my linux cluster.
> 
> I really need to make sure that the results will be the same in their
> scientific experiments and I was wondering if I should just try 3.5.1 or
> if using the latest (3.6.2) should give me the exact same answers. I am
> guessing most of the improvements are bug fixes and that it would be
> safe to use the latest but I need to make sure it would be indeed the
> same and that I wouldn't hit precisions issues for example.
> 
> Would you be able to shed some light on this or point me to some useful
> resources?

I recommend using the latest version available, netCDF-4.1.2, and if you only 
want
netCDF-3 capabilities, build it with the configure option --disable-netcdf-4.  
Also
if you have no need for the OPeNDAP remote access client now built into the 
library
even for netCDF-3 data, you can also use the configure option --disable-dap.  
That
will get you all the bug fixes in netCDF-3.6.3 as well as others for netCDF-3 
that
are only available in the netCDF-4 source distribution.  The new version has 
been
extensively tested, and even builds easily on cygwin platforms.  Get it from 
here:

  ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf.tar.gz

--Russ


Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: KRB-849418
Department: Support netCDF
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.