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

20020425: netcdf under UNICOS: non-support of primitive types

Verena,

>Date: Thu, 25 Apr 2002 11:07:47 +0200
>From: Verena Cals <address@hidden>
>Organization: Forschungszentrum Jülich GmbH
>To: address@hidden
>Subject: netcdf / unicos
>Keywords: 200204250907.g3P97sa28336

The above message contained the following:

> Dear Steve,
> 
> I've changed all our programs for using netcdf 3.5.0 but now I've
> realized that it isn't yet possible to install the fortran 90 interface
> on the Cray (Unicos), but we need it. The installingfile describes for
> unicos the fortran 90 interface will be fixed in 3.5.1.
> On the unidata-webpage I found a beta-version from netcdf-3.5.1. Does
> the fortran 90 interface for unicos work in this beta-version? How long
> you will require to release netcdf 3.5.1?
> 
> best regards
> Verena
> -- 
> 
> Verena Cals
> 
> ICG I: Stratosphäre
> Forschungszentrum Jülich GmbH
> EMail: address@hidden

I assume that your problem deals with the lack of support for certain
primitive types in your Fortran-9x environment (e.g. your Fortran-9x
compiler doesn't support 1-byte and 2-byte integers).  If this
assumption is incorrect, then please let me know.

We hope and intend that version 3.5.1 will support computer systems
that are missing one or more primitive types even though it might be
necessary for the user to perform a manual step before building the
netCDF package on such a system.

We cannot say with certainty, however, when version 3.5.1 will be
released. You probably will need it before we release it. Therefore,
you should try to get version 3.5.0 working on your system rather than
waiting for the next version.  We will help you with this.

Please try the following:

    1.  Go into the f90/ subdirectory.

    2.  Examine the file "typeSizes.f90".  Note the kind type parameters
        for primitive types that do not exist on your Fortran-9x
        system.  For example, if your Fortran-9x system doesn't support
        1-byte and 2-byte integers, then make note of the parameters
        "OneByteInt" and "TwoByteInt".

    3.  Edit the file "netcdf_overloads.f90".  Remove all references
        to procedures associated with the kind type parameters of the
        previous step.  Continuing the example, you would remove the
        following:

            nf90_put_att_OneByteInt
            nf90_put_att_one_OneByteInt
            nf90_get_att_OneByteInt
            nf90_get_att_one_OneByteInt
            nf90_put_var_OneByteInt
            nf90_put_var_1D_OneByteInt
            nf90_put_var_2D_OneByteInt
                etc.
            nf90_put_att_TwoByteInt
            nf90_put_att_one_TwoByteInt
            nf90_get_att_TwoByteInt
            nf90_get_att_one_TwoByteInt
            nf90_put_var_TwoByteInt
            nf90_put_var_1D_TwoByteInt
            nf90_put_var_2D_TwoByteInt
                etc.

    4.  Build the netCDF package as you would normally, but with the
        above changes.

Good luck.  Please keep me informed of your progress.

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