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

Re: (Fwd) Re: 19990928: NetCDF conversion problems on Crays

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: (Fwd) Re: 19990928: NetCDF conversion problems on Crays
  • Date: Tue, 28 Sep 1999 08:47:47 -0600
John,

>Date: Mon, 27 Sep 1999 10:30:06 -0400
>From: address@hidden (John Sheldon)
>Organization: GFDL
>To: address@hidden
>Subject: (Fwd) Re: 19990723: NetCDF conversion problems on Crays
>Keywords: 199907231930.NAA00955

In the above message, you wrote:

> Sorry to pester you over this, but I've got several users here who
> are quite anxious about not being able to control their internal-to-
> external conversion adequately....Basically, they want to be able to
> test the KIND (as in the FORTRAN "KIND") of a variable and call the
> appropriate output function. Then, they can turn on "-r8"-type compiler
> switches, yet retain the option to use REAL*4 variables, too.
> 
> Anything you can suggest?  Anything new in the pipeline?

There nothing new in the pipeline -- but there's nothing in the current
release that prevents what you want.  You can currently write Fortran-90
code that conditionally uses either doubleprecision or real netCDF I/O
routines -- it's just that the netCDF library has to have been compiled
with the "-dp" option and the netCDF library doesn't understand 128-bit
floating-point values.

I guess I don't understand what the problem is.

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