[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 20001011: netcdf 3.4, f90, digital unix (cont.)
- Subject: Re: 20001011: netcdf 3.4, f90, digital unix (cont.)
- Date: Thu, 12 Oct 2000 14:58:57 -0600
>cc: address@hidden
>From: "Henry LeRoy Miller, Jr." <address@hidden>
>Organization: Institut fur Stratospherische Chemie (ICG-1)
>Keywords: 200010111001.e9BA1Z409434 netCDF 3.4 f90 DEC
Hi Henry,
> In regards to my earlier message about an early netcdf.f90 interface
> file and netcdf 3.4, I believe I've solved the problem.
>
> It appears that I now have a functioning interface on my Digital
> workstation. The crux of the problem was in the way that the
> netcdf.f90 interface file defined the dimension of an assumed size
> array, as displayed in the following example.
>
> Note the specification for dimension in this example. The use of
> colon (:) or asterisk (*) are the only differences in these examples.
>
> Works on AIX, but not on DEC:
> INTEGER FUNCTION NF_INQ_VARDIMID (NCID, VARID, dimids)
> integer, intent ( in) :: NCID
> integer, intent ( in) :: VARID
> integer, dimension(:), intent (out) :: dimids
> end function NF_INQ_VARDIMID
>
>
> Works on Linux and DEC:
> INTEGER FUNCTION NF_INQ_VARDIMID (NCID, VARID, dimids)
> integer, intent ( in) :: NCID
> integer, intent ( in) :: VARID
> integer, dimension(*), intent (out) :: dimids
> end function NF_INQ_VARDIMID
>
>
> Initially, I had a copy of the file from the AIX, with the first
> format. The file on the Linux machine had the second format. Both
> files were the same byte-size, but with a different character in
> these type dimension statements. Now that I've compiled the second
> file, my programs appear to get the correct dimids.
Thanks for the fix. We've included it in what will be available as the
next release.
--Russ
_____________________________________________________________________
Russ Rew UCAR Unidata Program
address@hidden http://www.unidata.ucar.edu