[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 20000706: netcdf woes
- Subject: Re: 20000706: netcdf woes
- Date: Thu, 06 Jul 2000 15:58:29 -0600
Barbara,
> To: address@hidden
> From: Barbara Winter <address@hidden>
> Subject: netcdf woes
> Organization: UCAR/Unidata
> Keywords: 200007062035.e66KZHT26521
In the above message, you wrote:
> Hello,
>
> This e-mail began as a netcdf question to one of our local computer gurus,
> but he gave me your address and said to try that instead.
>
> My question is this:
>
> I've been using the updated 3.4 version of NetCDF to read and write
> files, and for my rather brainless purposes there's really not much
> difference between that and the older 2.4 version.
>
> However, when writing timepoints, the 2.4 command
>
> "call ncvpt(ncid, timeid, start(4), count(4), time, rcode)"
>
> does what it is supposed to, but the 3.4 commands
>
> "rcode = nf_put_var_double (ncid, timeid, time)"
> or "rcode = nf_put_vara_double (ncid, timeid, start(4), count(4), time)"
>
> don't, and no time points are written. Is there some other hoop to jump
> through to make these commands work? I'm declaring time as double
> precision in all cases.
There should be no difference between the "ncvpt" call and the
"nf_put_vara_double" call -- providing the netCDF file was opened
and closed correctly in each case. Are you correctly closing the netCDF
file? Do you check the return codes?
> I'm grateful for any hints, tricks, assurances it's not an IQ test, etc.!
>
> Barbara
>
>
> -----------------------------------------------------------------------------
> Barbara Winter
> Program in Atmospheric and Oceanic Sciences
> PO Box CN710, Sayre Hall
> Princeton University tel: (609) 258-1319
> Princeton, NJ 08544-0710 e-mail: address@hidden
> -----------------------------------------------------------------------------
>
>
> ------- End of Forwarded Message
Regards,
Steve Emmerson <http://www.unidata.ucar.edu>