[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[netCDF #MEK-494808]: teaching netcdf4 about CDF-5 formatted files (the easy way)
- Subject: [netCDF #MEK-494808]: teaching netcdf4 about CDF-5 formatted files (the easy way)
- Date: Thu, 22 Mar 2012 16:01:01 -0600
Hi Rob,
> Been nearly a year since I sent out these patches. With NetCDF-4.2
> out, perhaps we can take another look.
Sorry, that slipped through the cracks when Ed left. Just to make sure we
remember, I've created a Jira ticket that you can monitor, if you want to
know what happens with it.
--Russ
> Just in case the history is not in this ticket, or forgotten, here are
> four patches against netcdf-4 trunk that will teach NetCDF-4 how to
> produce and consume CDF-5 formatted files
>
> CDF-5 as you know is the "big variable" support we did in
> Parallel-NetCDF and for years now we have had "add CDF-5 support to
> NetCDF" on our todo list. We keep running out of time -- and
> developers -- so this approach leveraging NetCDF-4's already existing
> support for parallel-netcdf seemed like an easy first step.
>
> - 0001-fixes-to-make-out-of-tree-vpath-builds-work.patch
> not critical. you can drop this. I just like to build out-of-tree
> (vpath) style. Some of the NetCDF-4 documentation rules are pretty
> insistent about making changes to $srcdir : this patch does not 100%
> get you a vpath build.
>
> - 0002-teach-netcdf4-about-CDF5-files.patch:
>
> this is for reading CDF-5 formatted files
>
> - 0003-teach-nc_inq_varid-how-to-use-pnetcdf-backend.patch
>
> many places in NetCDF-4 have switches for various backends (classic
> netcdf, netcdf4, hdf5, pnetcdf). nc_inq_varid did not have this
>
> - 0004-CDF-5-flags-for-netcdf4.patch
>
> teach NetCDF4 about the necessary flags to create CDF-5 formatted
> files.
>
> ==rob
>
>
> On Wed, Apr 27, 2011 at 12:37:02PM -0600, Unidata netCDF Support wrote:
> > > It's been about a month since I first submitted these patches. A few
> > > days after I submitted this ticket, you released NetCDF-4.1.2 so I
> > > imagine there were some festivities going on.
> > >
> > > I'm following the linux kernel patch submission process: if you don't
> > > hear anything in a few weeks, send again...
> > >
> > > Actually, its a good thing I get a second chance to submit: my first
> > > patchset was missing the important fifth patch that actually lets
> > > NetCDF4 create CDF-5 files.
> > >
> > > To re-summarize:
> > > - the first two patches are just little build fix changes for folks
> > > like me who try to build out-of-tree (vpath) style.
> > >
> > > - 0004-teach-nc_inq_varid-how-to-use-pnetcdf-backend.patch selects the
> > > pnetcdf driver in much the same way the rest of the netcdf4 api
> > > is able to
> > >
> > > - 0003-teach-netcdf4-about-CDF5-files.patch allows NetCDF4, configured
> > > with parallel-netcdf, to read CDF-5 formatted files generated by
> > > pnetcdf
> > >
> > > - 0005-CDF-5-flags-for-netcdf4.patch allows NetCDF-4 to generate CDF-5
> > > formatted files as long as NetCDF4 was configured with pnetcdf
> > > support.
> > >
> > > ==rob
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Rob Latham
> > > Mathematics and Computer Science Division
> > > Argonne National Lab, IL USA
> > >
> > >
> >
> > Howdy Rob!
> >
> > We are very interested in this and will be including the patch. But
> > probably not until the 4.2 release or later.
> >
> > I am going through some release planning now. When I get a better idea of
> > what will be released when, I will post on the website.
> >
> > On a related note, when's the next time you are coming to Boulder, if ever?
> > It would be great to meet up.
> >
> > Thanks,
> >
> > Ed
> >
> > Ticket Details
> > ===================
> > Ticket ID: MEK-494808
> > Department: Support netCDF
> > Priority: Critical
> > Status: Closed
> >
>
> --
> Rob Latham
> Mathematics and Computer Science Division
> Argonne National Lab, IL USA
>
>
Russ Rew UCAR Unidata Program
address@hidden http://www.unidata.ucar.edu
Ticket Details
===================
Ticket ID: MEK-494808
Department: Support netCDF
Priority: Critical
Status: Closed