NOTE: The netcdf-hdf mailing list is no longer active. The list archives are made available for historical reasons.
> ed@xxxxxxxxxxxxxxxx wrote:
>
> >>From our requirements on anonymous dimensions:
> >
> >* Dimensions do not always require a name.
> >
> >By this do we mearly mean that I can accept a dimension with a zero
> >length name, and that's it?
> >
> >Otherwise it acts exactly like a regular dimension?
> >
> >If so, this will be an easy one!
> >
> >John, was there something else you had in mind for this that I am missing?
> >Ed
> >
> >
> anonymous dimensions are local to the variable, as opposed to globally
> scoped dimensions which can be shared across variables. anonymous
> dimensions can be nameless, but it would be ok if they had a name if
> someone had an idea why that would be useful.
Hmm, why not just call them "private dimensions" then?
Quincey
>From owner-netcdf-hdf@xxxxxxxxxxxxxxxx 19 2003 Dec -0700 12:51:54
Message-ID: <wrxfzfg8u1x.fsf@xxxxxxxxxxxxxxxxxxxxxxx>
Date: 19 Dec 2003 12:51:54 -0700
From: Ed Hartnett <ed@xxxxxxxxxxxxxxxx>
In-Reply-To: <20031219132116.E29507@xxxxxxxxxxxxxxxxxxxxx>
To: netcdf-hdf@xxxxxxxxxxxxxxxx
Subject: Re: NCSA access to the netcdf4 prototype?
Received: (from majordo@localhost)
by unidata.ucar.edu (UCAR/Unidata) id hBJJptOY015488
for netcdf-hdf-out; Fri, 19 Dec 2003 12:51:55 -0700 (MST)
Received: from rodney.unidata.ucar.edu (rodney.unidata.ucar.edu
[128.117.140.88])
by unidata.ucar.edu (UCAR/Unidata) with ESMTP id hBJJpsp2015476
for <netcdf-hdf@unidata>; Fri, 19 Dec 2003 12:51:55 -0700 (MST)
Organization: UCAR/Unidata
Keywords: 200312191951.hBJJpsp2015476
References: <20031219132116.E29507@xxxxxxxxxxxxxxxxxxxxx>
Lines: 25
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-netcdf-hdf@xxxxxxxxxxxxxxxx
Precedence: bulk
"Robert E. McGrath" <mcgrath@xxxxxxxxxxxxx> writes:
> Russ & Ed,
>
> Several of us here at NCSA would like to look at the prototype. We
> don't know
> how to get to it.
>
> How do you guys want to handle this? Do you want to set up remote
> access to your
> CVS? Or what?
>
Howdy!
Russ and I just made some decisions about the way we're going to
distribute the software. Give me a couple of days to implement those
decisions, then you should just be able to get a tarball and
configure and install in the usual fashion.
We had intended to distribute the netcdf-3 and netcdf-4 libraries
seperately, but now we've realized that we better package them
together...
Ed
>From owner-netcdf-hdf@xxxxxxxxxxxxxxxx 24 2003 Dec -0700 05:18:33
Message-ID: <wrxn09ijtnq.fsf@xxxxxxxxxxxxxxxxxxxxxxx>
Date: 24 Dec 2003 05:18:33 -0700
From: Ed Hartnett <ed@xxxxxxxxxxxxxxxx>
To: netcdf-hdf@xxxxxxxxxxxxxxxx
Subject: some performance benchmarks for netcdf-4
Received: (from majordo@localhost)
by unidata.ucar.edu (UCAR/Unidata) id hBOCIYRh002550
for netcdf-hdf-out; Wed, 24 Dec 2003 05:18:34 -0700 (MST)
Received: from rodney.unidata.ucar.edu (rodney.unidata.ucar.edu
[128.117.140.88])
by unidata.ucar.edu (UCAR/Unidata) with ESMTP id hBOCIXp2002490
for <netcdf-hdf@unidata>; Wed, 24 Dec 2003 05:18:33 -0700 (MST)
Organization: UCAR/Unidata
Keywords: 200312241218.hBOCIXp2002490
Lines: 48
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-netcdf-hdf@xxxxxxxxxxxxxxxx
Precedence: bulk
Reply-To: netcdf-hdf@xxxxxxxxxxxxxxxx
Howdy all!
Russ suggested to me yesterday that I post these timing results. In
the tests below I write, and then read, 4 files. The first is in HDF5,
with no netCDF stuff at all. (Writing BE on a LE system, because
that's what netcdf does). The second file is pure netcdf-3, with no
netcdf-4 code involved. The third uses the netcdf-4 library to write a
file in netcdf classic format. Finally, the last file is created with
netcdf-4, with HDF5 as a storage layer. This is faster because it is
writing LE on a LE system (i.e. using HDF "native" format).
The CPU time is the combined total of time spent by the CPU on
user/library code, and the User time is wall clock time.
Russ would like to include some of these results in an AMS paper, but
I think we all need to give a thought to what we are measuring first.
About to write pure HDF5 file, one dataset, record by record: x 2000 y 300 z
500...
avg CPU time = 15.17 secs.
avg User Time = 43 secs.
About to write pure netcdf-3 file, record by record...
avg CPU time = 17.15 secs.
avg User Time = 45 secs.
About to write netcdf-3 file thru netcdf-4, record by record...
avg CPU time = 17.26 secs.
avg User Time = 45 secs.
About to write netcdf-4 (i.e. HDF5) file, record by record...
avg CPU time = 15.87 secs.
avg User Time = 36 secs.
About to read pure HDF5 file...
avg CPU time = 13.70 secs.
avg User Time = 34 secs.
About to read pure netcdf-3 file...
avg CPU time = 9.18 secs.
avg User Time = 29 secs.
About to read netcdf-3 file, created with netcdf-4...
avg CPU time = 11.64 secs.
avg User Time = 20 secs.
About to read netcdf-4 (i.e. HDF5) file...
avg CPU time = 12.49 secs.
avg User Time = 20 secs.
>From owner-netcdf-hdf@xxxxxxxxxxxxxxxx 24 2003 Dec -0700 05:26:54
Message-ID: <wrxekuujt9t.fsf@xxxxxxxxxxxxxxxxxxxxxxx>
Date: 24 Dec 2003 05:26:54 -0700
From: Ed Hartnett <ed@xxxxxxxxxxxxxxxx>
In-Reply-To: <wrxn09ijtnq.fsf@xxxxxxxxxxxxxxxxxxxxxxx>
To: netcdf-hdf@xxxxxxxxxxxxxxxx
Subject: Re: some performance benchmarks for netcdf-4
Received: (from majordo@localhost)
by unidata.ucar.edu (UCAR/Unidata) id hBOCQtFH011754
for netcdf-hdf-out; Wed, 24 Dec 2003 05:26:55 -0700 (MST)
Received: from rodney.unidata.ucar.edu (rodney.unidata.ucar.edu
[128.117.140.88])
by unidata.ucar.edu (UCAR/Unidata) with ESMTP id hBOCQsp2011748
for <netcdf-hdf@xxxxxxxxxxxxxxxx>; Wed, 24 Dec 2003 05:26:54 -0700 (MST)
Organization: UCAR/Unidata
Keywords: 200312241226.hBOCQsp2011748
References: <wrxn09ijtnq.fsf@xxxxxxxxxxxxxxxxxxxxxxx>
Lines: 6
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-netcdf-hdf@xxxxxxxxxxxxxxxx
Precedence: bulk
Reply-To: netcdf-hdf@xxxxxxxxxxxxxxxx
I forgot to mention that the times I posted are the average times of
each operation, averaged over 30 cycles of writing and reading the
files.
Ed
netcdf-hdf archives: