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

Re: perl script fix.

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: perl script fix.
  • Date: Wed, 21 Jul 1999 11:29:45 -0600
Bill,

>Date: Wed, 21 Jul 1999 17:17:38 GMT
>From: "William C. Mattison" <address@hidden>
>Organization: NOAA/NWS
>To: address@hidden
>Subject: RE: Re: perl script fix.
>Keywords: 199907191509.JAA17058

In the above message, you wrote:

> Puzzling.  I put start[2] and count[2] back in, but with start[2]=0 and
> count[2]=1.  Start[1] was already 0.  It worked.  I have a C++ program
> (calling the version 3 netCDF for C), and in there, start[1], start[2],
> and count[2] are 0, and it works.

There are some slight differences in the way netCDF-2 and netCDF-3
are implemented---so I'm not too surprised at this.  I believe that
netCDF-2 didn't specify what would happen if a larger-than-necessary
shape specification was passed to the variable I/O routines---so the
result depends on how the implementation implements the API.  It's best
not to depend on such undocumented behavior.

--------
Steve Emmerson   <http://www.unidata.ucar.edu>