topic Hi I am just trying to in Intel® Fortran Compiler

compilation error while building code

aketh_t_ — Mon, 18 May 2015 06:07:40 GMT

Hi,

I have been trying to compile a file with the following variable definitions. And I use the intel 15 set of compilers.

integer (int_kind), parameter :: max_blocks_clinic = 65

integer (int_kind) :: nblocks_x=8

integer (int_kind) :: nblocks_y=8

type tlt_info

real (r8), dimension(nx_block,ny_block,max_blocks_clinic) :: &
DIABATIC_DEPTH, & ! depth of the diabatic region at the
! surface, i.e. mean mixed or boundary layer
! depth
THICKNESS, & ! transition layer thickness
INTERIOR_DEPTH ! depth at which the interior, adiabatic
! region starts, i.e.
! = TLT%DIABATIC_DEPTH + TLT%THICKNESS
integer (int_kind), &
dimension(nx_block,ny_block,max_blocks_clinic) :: &
K_LEVEL, & ! k level at or below which the interior,
! adiabatic region starts
ZTW ! designates if the interior region
! starts below depth zt or zw.
! ( = 1 for zt, = 2 for zw )
end type tlt_info

However I got the following error.

loop.F90(55): error #6530: The array spec for this component must be of explicit shape and each bound must be an initialization expression. [DIABATIC_DEPTH]
DIABATIC_DEPTH, & ! depth of the diabatic region at the
-----------^
loop.F90(58): error #6530: The array spec for this component must be of explicit shape and each bound must be an initialization expression. [THICKNESS]
THICKNESS, & ! transition layer thickness
-----------^
loop.F90(59): error #6530: The array spec for this component must be of explicit shape and each bound must be an initialization expression. [INTERIOR_DEPTH]
INTERIOR_DEPTH ! depth at which the interior, adiabatic
-----------^
loop.F90(64): error #6530: The array spec for this component must be of explicit shape and each bound must be an initialization expression. [K_LEVEL]
K_LEVEL, & ! k level at or below which the interior,
-----------^
loop.F90(66): error #6530: The array spec for this component must be of explicit shape and each bound must be an initialization expression. [ZTW]
ZTW ! designates if the interior region

Any help on how this can be resolved???

Maybe not the best message

TimP — Mon, 18 May 2015 11:15:26 GMT

Maybe not the best message but how about making each of those integers parameter?

I tried it now.

aketh_t_ — Mon, 18 May 2015 13:47:08 GMT

I tried it now.

Still the error remains the same. Is it got to do with any flags coz , I have compiled a few files with this definition as a part of CESM.

If it is desired that the

mecej4 — Mon, 18 May 2015 13:53:22 GMT

If it is desired that the user defined type contain arrays whose sizes are determined at run-time, make those array components ALLOCATABLE (and perform allocation/deallocation after they are not needed, to save memory footprint), or consider using PDTs (parameterized derived types).

Quote:Aketh T. wrote: Is it

mecej4 — Mon, 18 May 2015 13:55:41 GMT

Aketh T. wrote:
Is it got to do with any flags

I don't think so. Please provide a (compilable) complete code example.

The code size is huge.

aketh_t_ — Mon, 18 May 2015 14:04:10 GMT

The code size is huge.

I can give a brief pointers about it and a link.

there are two files blocks.F90 (http://www.cesm.ucar.edu/models/cesm1.1/cesm/cesmBbrowser/html_code/pop/blocks.F90.html)

and

hmix_gm.F90 (http://www.cesm.ucar.edu/models/cesm1.0/cesm/cesmBbrowser/html_code/pop/hmix_gm.F90.html)

(try ctrl+F and look for type tlt_info)

These are just a few files that are a part of CESM. I have compiled the entire CESM and run these models, and they work.

The file blocks.F90 contains

mecej4 — Mon, 18 May 2015 14:51:26 GMT

The file blocks.F90 contains declarations for the named constants nx_block and ny_block. In order to use these constants in your declarations, you must have a USE BLOCKS statement in your code, or provide some other way to make these constants known (host association, USE of a module that uses BLOCKS.mod, etc.).

Hi I am just trying to

aketh_t_ — Wed, 20 May 2015 06:26:32 GMT

Hi I am just trying to simulate loop in hmix_gm rather than the entire hmix_gm.

in this stage all I want to do was copy paste a loop from hmix and definition of variables inside the loop from all the modules present.

I agree, I don't see anything

Martyn_C_Intel — Thu, 21 May 2015 00:30:38 GMT

I agree, I don't see anything to solve here. For example, assuming nblocks_x and nblocks_y to be a typo, and making the corrections discussed above, the following compiles:

module mymod
integer, parameter :: int_kind=selected_int_kind(8)
integer, parameter :: r8 =selected_real_kind(12)
integer (int_kind), parameter :: max_blocks_clinic = 65
integer (int_kind), parameter :: nx_block=8
integer (int_kind), parameter :: ny_block=8

type tlt_info
        real(r8), dimension(nx_block,ny_block,max_blocks_clinic) :: &
           DIABATIC_DEPTH, &
           THICKNESS,       &
           INTERIOR_DEPTH

        integer(int_kind), &
           dimension(nx_block,ny_block,max_blocks_clinic) :: &
           K_LEVEL, &
           ZTW
end type tlt_info

end module

Quote:aketh t. wrote:

mecej4 — Thu, 21 May 2015 14:50:30 GMT

aketh t. wrote:

These are just a few files that are a part of CESM. I have compiled the entire CESM and run these models, and they work. (#6)

Hi I am just trying to simulate loop in hmix_gm rather than the entire hmix_gm. In this stage all I want to do was copy paste a loop from hmix and definition of variables inside the loop from all the modules present. (#8)

Cutting and pasting fragments of code often produces new code that is not compilable. You have modified code from a widely used package -- a package which, presumably, is mostly error-free. The modified code in this instance is not accepted by the compiler, because of syntactic errors. The fact that similar modifications that you made earlier gave you working code does not guarantee that the present modification is error-free. Therefore, unless you show us your modifications, no progress can be made.