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

[netCDF #SXE-762095]: Corrections to netcdf 4.4.1 news page

Hi Dave,

Thanks for the copy edit; I appreciate the feedback.  It's always great to get 
a second opinion!

I'll forward this on with my agreement to our writer/resident editor and 
request he make the changes.

Thanks!

-Ward

> Netcdf support,
> 
> Please consider the following corrections and improvements to the news page
> for netcdf-4.4.1.  None of this is very important, but it may help clarify
> some things for less experienced users.
> 
> http://www.unidata.ucar.edu/blogs/news/entry/netcdf-4-4-1
> 
> > Note: netCDF 4.4.0 or earlier, combined with libhdf5 1.10.0
> > or greater, will generate netCDF files that cannot be read on
> > systems using earlier versions of libhdf5 (1.8.x), regardless
> > of the version of netCDF.
> 
> Change to: "Note: netCDF library 4.4.0 or earlier".
> 
> Change to "will generate netCDF-4 format files".
> 
> Change to "cannot be read by software using earlier versions".
> 
> [Table header:]
> > NetCDF Version    HDF5 Version    Minimum HDF5 version
> > required to read (no minimum version of netCDF for reading)
> 
> Change to "NetCDF Library Version    HDF5 Library Version    Minimum HDF5
> version required to read (no minimum version of netCDF library for reading)"
> 
> > Note: As documented, netCDF requires a minimum hdf5 version of 1.8.9
> 
> Change to "... netCDF-4 format support requires a minimum hdf5 library
> version of 1.8.9."
> 
> Below this note, add another one:  "Note:  NetCDF-3 format files are not
> affected by this issue.  NetCDF-3 files remain forward and backward
> compatible through all netCDF library versions 3.x through 4.x."
> 
> > Starting with release 4.4.1, netCDF-4 files will have superblock
> > version 0 instead of superblock version 2, as in previous netCDF
> > versions. This is due to a workaround required to avoid backwards
> > binary incompatibility when using libhdf5 1.10.x or greater.
> 
> Change to "workaround required to avoid backward read and write
> incompatibility".
> 
> > Superblock versions 0 and 2 appear to be forward- and
> > backward-compatible.
> 
> Change to "appear to be forward- and backward-compatible for both reading
> and writing."
> 
> Perhaps add "Superblock 1 files made by direct HDF5 applications are
> hypothetically also compatible, but this is not yet confirmed."  Certainly
> I have not yet tested a superblock 1 file.
> 
> > Other than a different superblock number the data should remain
> consistent.
> 
> Change to "Other than a different superblock number, all user data and
> metadata should remain consistent."
> 
> --Dave
> 
> 


Ticket Details
===================
Ticket ID: SXE-762095
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.