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

Re: 19990817: NCSNC problem with netCDF v3.4

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: 19990817: NCSNC problem with netCDF v3.4
  • Date: Tue, 17 Aug 1999 10:42:33 -0600
Carlie,

>Date: Tue, 17 Aug 1999 12:16:36 -0400 (EDT)
>From: Carlie Coats <address@hidden>
>Organization: MCNC/NCSC Environmental Programs
>To: address@hidden (Steve Emmerson)
>Subject: Re: 19990813: NCSNC problem with netCDF v3.4
>Keywords: 199908101517.JAA21345

In the above message, you wrote:

> I see it now, now that I know where to look.
> I'm re-building now; should have it tested within a couple of hours.
> My guess is that it'll fix the problem.  (But still, why did the
> "NCSNC" not synch with disk?)

I don't know why both the NC_SHARE mode and explicit calls to NCSNC
are necessary in order to obtain synchronized behavior.  If it's any
consolation, I also expected that only NCSNC calls would suffice.
Unfortunately, the fellow who wrote the code and would know the reason
why both these features are necessary (Glenn Davis) died in a small
plane crash in May.

> Sorry to have been such a trouble over this... -- Carlie

Don't be.  You've discovered a possible incompatibility between
version 2 and version 3 of the netCDF package.  We'll have to think
about it here.

Incidentally, you might not be able to creaate the file with the NF_SHARE
mode-bit set using the netCDF version 2 API (though you can with the
version 3 API).  Please let me know if you have problems with this.

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