[CIG-SEISMO] parameter type error of display_topo_bathy_opendx.f90

Pieyre Le Loher Pieyre.Le_Loher at inria.fr
Wed Aug 25 09:06:51 PDT 2010


Dear Hu Yuanxin,

Yes, the error you mentioned concerning create_movie_shakemap_AVS_DX_GMT
may be due to the compiler. I remember I got a similar issue in the
beginning of the year.

Concerning display_topo_bathy_opendx.f90, it is a very old code in
/DATA/la_topography which we do not use any more. It is only for the model
of Southern California. You get these errors because the file constants.h
has been changed. I think we're going to delete this folder in SPECFEM
2.0.
If you want to visualize your mesh, you can create DX files in meshfem3D
or even in xgenerate_databases.

Best regards.

Pieyre Le Loher



> Dear Pieyre,
>
> I have read the code "display_topo_bathy_opendx.f90" in order to
> change topo_bathy_final.dat to DX file. But there were some error
> about parameter type. The error information is listed here:
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ifort -o display_topo_bathy_opendx display_topo_bathy_opendx.f90
> display_topo_bathy_opendx.f90(41): error #6404: This name does not
> have a type, and must have an explicit type.   [ORIG_LONG]
>     rlon = ORIG_LONG + (ix-1)*DEGREES_PER_CELL*SUBSAMP_FACTOR_OPENDX
> -----------^
> display_topo_bathy_opendx.f90(41): error #6404: This name does not
> have a type, and must have an explicit type.   [DEGREES_PER_CELL]
>     rlon = ORIG_LONG + (ix-1)*DEGREES_PER_CELL*SUBSAMP_FACTOR_OPENDX
> ------------------------------^
> display_topo_bathy_opendx.f90(41): error #6404: This name does not
> have a type, and must have an explicit type.   [SUBSAMP_FACTOR_OPENDX]
>     rlon = ORIG_LONG + (ix-1)*DEGREES_PER_CELL*SUBSAMP_FACTOR_OPENDX
> -----------------------------------------------^
> display_topo_bathy_opendx.f90(42): error #6404: This name does not
> have a type, and must have an explicit type.   [ORIG_LAT]
>     rlat = ORIG_LAT + (iy-1)*DEGREES_PER_CELL*SUBSAMP_FACTOR_OPENDX
> -----------^
> display_topo_bathy_opendx.f90(43): error #6404: This name does not
> have a type, and must have an explicit type.   [IZONE_UTM_LA]
>     call utm_geo(rlon,rlat,rx,ry,IZONE_UTM_LA,ILONGLAT2UTM)
> ---------------------------------^
> compilation aborted for display_topo_bathy_opendx.f90 (code 1)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> In my last email, I mentioned the error of executing
> create_movie_shakemap_AVS_DX_GMT. But I can run it normally on
> cluster. And on my PC, after simulation, it can run normally, too. I
> am confused by the problem. On cluster, the code was compiled by
> gfortran, but ifort on my PC. Can we attribute the problem to the
> difference of compiler, which resulted in different output files?
>
> Best regards,
>
> Hu Yuanxin
>




More information about the CIG-SEISMO mailing list