Arun,
The message means that a procedure argument has an unexpected type
or rank. For example, a real when the argument must be an integer,
or an array when only a scalar is allowed. NF90_GET_VAR is a
generic procedure, which means that some of its arguments have
multiple choices. However, the type and rank are still limited to
what is supported by the Netcdf library.
CALL hdlerr( NF90_GET_VAR (il_file_id, il_lon_id, irreg_lon, &
ila_what(1:2), ila_dim(1:2)), __LINE__ )
You have five arguments to NF90_GET_VAR. Please check the
declaration of each argument against the specification:
http://www.unidata.ucar.edu/software/netcdf/docs/netcdf-f90/NF90_005fGET_005fVAR.html
Also, you have two procedure calls combined in one statement. It is
unlikely but possible that the problem is with the call to hdlerr,
not NF90_GET_VAR. To narrow down the error for debugging, break up
the line into two separate statements:
integer status
status = NF90_GET_VAR (il_file_id, ....
CALL hdlerr( status, __LINE__ )
--Dave
On 3/24/2011 2:28 AM, arun chaudhary wrote:
Hi Good Morning,
We are installting coupler Oasis3 at our site. We compiled and
installed oasis3 but there is one directory *oasis3/examples/tutorial. *
*which help in running the sample models. So during the compilation
of tutorial we are getting below error message:*
**
"read_grid_irreg.F90", line 61.16: 1513-062 (S) Generic procedure
reference can not be resolved due to incorrect actual argum
ent attributes.
"read_grid_irreg.F90", line 67.16: 1513-062 (S) Generic procedure
reference can not be resolved due to incorrect actual argum
ent attributes.
"read_grid_irreg.F90", line 76.16: 1513-062 (S) Generic procedure
reference can not be resolved due to incorrect actual argum
ent attributes.
"read_grid_irreg.F90", line 82.16: 1513-062 (S) Generic procedure
reference can not be resolved due to incorrect actual argum
ent attributes.
when we gone to "read_grid_irreg.F90 program then we found this is
calling a function NF90_GET_VAR:
+61 CALL hdlerr( NF90_GET_VAR (il_file_id, il_lon_id, irreg_lon, &
+62 ila_what(1:2), ila_dim(1:2)), __LINE__ )
+63 !
+64 WRITE(w_unit,*) 'We read globalgrid_lon'
+65 CALL flush(w_unit)
+66 !
+67 CALL hdlerr( NF90_GET_VAR (il_file_id, il_lat_id,
irreg_lat, &
+68 ila_what(1:2), ila_dim(1:2)), __LINE__ )
+69 !
+70 WRITE(w_unit,*) 'We read globalgrid_lat'
+71 CALL flush(w_unit)
+72 WRITE(w_unit,*) 'We read globalgrid_lat 2'
+73 WRITE(w_unit,*) 'ila_corners', ila_corners(:)
+74 CALL flush(w_unit)
+75 !
+76 CALL hdlerr( NF90_GET_VAR(il_file_id, il_clo_id, irreg_clo, &
+77 ila_what, ila_corners), __LINE__ )
+78 !
+79 WRITE(w_unit,*) 'We read globalgrid_clo'
+80 CALL flush(w_unit)
+81 !
+82 CALL hdlerr( NF90_GET_VAR (il_file_id, il_cla_id,
irreg_cla, &
+83 ila_what, ila_corners), __LINE__ )
We tried a lot , but not getting through , please help us to get
this problem resolved.
Regards
Arun Chaudhary
HCL Infosystems Ltd.
Camp at: NCMRWF Sec-62 Noida India.
