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

[胡元鑫]

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