open TELEMAC-MASCARET The mathematically superior suite of solvers

I have a serious problem with fortran files !
I use telemac2d on a windows 7 64 bits computer. Everythings seems to run correctly, but Ican't use fortran files !
Si I did some test with validation files and I discover the followings :
If I test a validation samples with fortan file , it runs with out problem, but if I open the fortan file, change nothing and save the file, when I launch Telemac,I obtain the following error message :
________________________________________________________
- FICHIER FORTRAN : t2d_tide-jmj.f

______________________________________________________________________________
*** COMPILATION ***

ifort /traceback /compile_only /O2 /QxHost /check=overflow /iface:nomixed_str_
len_arg /warn:declaration /warn:argument_checking /warn:unused /nologo /names:u
ppercase /convert:big_endian /extend-source:132 /include:C:\TELEMAC\v6p2r1\tel
emac2d\tel2d_v6p2\wintel64 /include:C:\TELEMAC\v6p2r1\sisyphe\sisyphe_v6p2\winte
l64 /include:C:\TELEMAC\v6p2r1\tomawac\toma_v6p2\wintel64 /include:C:\TELEMAC\v6
p2r1\bief\bief_v6p2\wintel64 /include:C:\TELEMAC\v6p2r1\special\special_v6p2\win
tel64 /include:C:\TELEMAC\v6p2r1\damocles\damo_v6p2\wintel64 /include:C:\TELEMAC
\v6p2r1\paravoid\paravoid_v6p2\wintel64 t2dfort.f
t2dfort.f(29): error #7002: Error in opening the compiled module file. Check IN
CLUDE paths. [BIEF]
USE BIEF

---

^
t2dfort.f(30): error #7002: Error in opening the compiled module file. Check IN
CLUDE paths. [DECLARATIONS_TELEMAC]
USE DECLARATIONS_TELEMAC

---

^
t2dfort.f(31): error #7002: Error in opening the compiled module file. Check IN
CLUDE paths. [BIEF_DEF]
USE DECLARATIONS_TELEMAC2D

---

^
t2dfort.f(59): error #6404: This name does not have a type, and must have an exp
licit type. [CTIDEV]
IF(CTIDEV.EQ.999999.D0) CTIDEV = SQRT(CTIDE)

---

^
t2dfort.f(59): error #6404: This name does not have a type, and must have an exp
licit type. [CTIDE]
IF(CTIDEV.EQ.999999.D0) CTIDEV = SQRT(CTIDE)

---

^
t2dfort.f(59): warning #7319: This argument's data type is incompatible with thi
s intrinsic procedure; procedure assumed EXTERNAL. [SQRT]
IF(CTIDEV.EQ.999999.D0) CTIDEV = SQRT(CTIDE)

---

^
t2dfort.f(59): error #6404: This name does not have a type, and must have an exp
licit type. [SQRT]
IF(CTIDEV.EQ.999999.D0) CTIDEV = SQRT(CTIDE)

---

^
t2dfort.f(119): error #6404: This name does not have a type, and must have an ex
plicit type. [TIDALDB]
IF(TIDALDB.EQ.1) THEN

---

^
t2dfort.f(121): error #6404: This name does not have a type, and must have an ex
plicit type. [T2D_FILES]
IF(T2D_FILES(T2DBDD)%NAME.EQ.' ') THEN

---

^
t2dfort.f(160): error #6404: This name does not have a type, and must have an ex
plicit type. [MESH]
CALL BORD_TIDAL_BC(MESH%NBOR%I,LIHBOR%I,LIUBOR%I,

---

^
t2dfort.f(160): error #6460: This is not a field name that is defined in the enc
ompassing structure. [NBOR]
CALL BORD_TIDAL_BC(MESH%NBOR%I,LIHBOR%I,LIUBOR%I,

---

^
t2dfort.f(160): error #6460: This is not a field name that is defined in the enc
ompassing structure.
CALL BORD_TIDAL_BC(MESH%NBOR%I,LIHBOR%I,LIUBOR%I,

---

^
t2dfort.f(160): error #6404: This name does not have a type, and must have an ex
plicit type. [LIHBOR]
CALL BORD_TIDAL_BC(MESH%NBOR%I,LIHBOR%I,LIUBOR%I,

---

^
t2dfort.f(160): error #6404: This name does not have a type, and must have an ex
plicit type. [LIUBOR]
CALL BORD_TIDAL_BC(MESH%NBOR%I,LIHBOR%I,LIUBOR%I,

---

^
t2dfort.f(161): error #6404: This name does not have a type, and must have an ex
plicit type. [NPTFR]
& NPTFR,KENT,KENTU,

---

^
t2dfort.f(161): error #6404: This name does not have a type, and must have an ex
plicit type. [KENT]
& NPTFR,KENT,KENTU,

---

^
t2dfort.f(161): error #6404: This name does not have a type, and must have an ex
plicit type. [KENTU]
& NPTFR,KENT,KENTU,

---

^
t2dfort.f(162): error #6404: This name does not have a type, and must have an ex
plicit type. [GEOSYST]
& MESH,GEOSYST,NUMZONE,LAMBD0,PHI0,

---

^
t2dfort.f(162): error #6404: This name does not have a type, and must have an ex
plicit type. [NUMZONE]
& MESH,GEOSYST,NUMZONE,LAMBD0,PHI0,

---

^
t2dfort.f(162): error #6404: This name does not have a type, and must have an ex
plicit type. [LAMBD0]
& MESH,GEOSYST,NUMZONE,LAMBD0,PHI0,

---

^
t2dfort.f(162): error #6404: This name does not have a type, and must have an ex
plicit type. [PHI0]
& MESH,GEOSYST,NUMZONE,LAMBD0,PHI0,

---

^
t2dfort.f(163): error #6404: This name does not have a type, and must have an ex
plicit type. [TIDALTYPE]
& TIDALTYPE,BOUNDARY_COLOUR,MAXFRO,

---

^
t2dfort.f(163): error #6404: This name does not have a type, and must have an ex
plicit type. [BOUNDARY_COLOUR]
& TIDALTYPE,BOUNDARY_COLOUR,MAXFRO,

---

^
t2dfort.f(163): error #6404: This name does not have a type, and must have an ex
plicit type. [MAXFRO]
& TIDALTYPE,BOUNDARY_COLOUR,MAXFRO,

---

^
t2dfort.f(179): error #6404: This name does not have a type, and must have an ex
plicit type. [ZF]
CALL BORD_TIDE(ZF%R,MESH%NBOR%I,LIHBOR%I,LIUBOR%I,

---

^
t2dfort.f(179): error #6460: This is not a field name that is defined in the enc
ompassing structure. [R]
CALL BORD_TIDE(ZF%R,MESH%NBOR%I,LIHBOR%I,LIUBOR%I,

---

^
t2dfort.f(180): error #6404: This name does not have a type, and must have an ex
plicit type. [NPOIN]
& NPOIN,NPTFR,AT,DT,NCOTE,NVITES,

---

^
t2dfort.f(180): error #6404: This name does not have a type, and must have an ex
plicit type. [AT]
& NPOIN,NPTFR,AT,DT,NCOTE,NVITES,

---

^
t2dfort.f(180): error #6404: This name does not have a type, and must have an ex
plicit type. [DT]
& NPOIN,NPTFR,AT,DT,NCOTE,NVITES,

---

^
t2dfort.f(180): error #6404: This name does not have a type, and must have an ex
plicit type. [NCOTE]
& NPOIN,NPTFR,AT,DT,NCOTE,NVITES,

---

^
t2dfort.f(180): error #6404: This name does not have a type, and must have an ex
plicit type. [NVITES]
& NPOIN,NPTFR,AT,DT,NCOTE,NVITES,

---

^
t2dfort.f(312): catastrophic error: Too many errors, exiting
compilation aborted for t2dfort.f (code 1)
ERREUR A LA COMPILATION

________________________________________________________
Execution terminee: telemac2d.bat
________________________________________________________
Compilation/linking/file errors detected.
Please see messages in: stdout above, stderr,
and/or file E:\Telemac\123_tide\Test4\t2d_tide-jmj_type.cas7772_error.log

No execution errors detected.

Working directory: E:\Telemac\123_tide\Test4\t2d_tide-jmj_type.cas7772_tmp
can be manually deleted with: E:\Telemac\123_tide\Test4\delete_t2d_tide-jmj_type
.cas7772.bat

Returning exit status 1

=========================================================
Telemac System 5.6 to 6.2 - Perl scripts version 6.2
=========================================================
I tried differents text editors as notepad++, worpad, ... and the editor of Intel parallel sutdio XE 2011 and obtained the same error !
Thanks in advance for all suggestions

Hello Philippe,

That sounds strange, even the first executable line USE BIEF does not work, it is certainly linked to the file format (so it is even more strange that it occurs with several editors). I suspect the carriage returns at the end of lines. What if you copy, then change nothing and save, and do a diff between the original and the saved file ? It could be that commands like dos2unix (not sure of the name) will change something. You could post a file so that I can see what is inside (I see the weird carriage returns on my HP unix).

Regards,

Jean-Michel

Hello Jean Michel,

Nice to read you !

In fact after other tests, it seems that the problem is different.

Yesterday, tests were carried out in a directory already used one month ago and where the .exe file existed. I think that the compilation was not done but Telemac used the existing .exe file. In this directory, if I save again the file fortran, the compilation does not occur.
Yesterday, I also compared the two fortran files with an hexadecimal editor and found no difference between the two files.

This morning I tested again after removing the .exe file and the compilation did not performed, nor with the original .f or with the new one.

In conclusion, it seems that the compilation does not run correctly on my machine, so it was properly one month ago.

Do you have some suggestions ?

Best regards

Hello Philippe,

Then you could try to run directly the compiler on the Fortran file, like e.g.:

f90 princi.f

and see if the compiler starts (it will fail because of missing modules and libraries but at least you wil se if it works). If it starts then it is a problem with the configuration files, if it does not start it is a problem with the compiler.

Have a nice end of week-end,

JMH

Hello Jean Michel,
The compiler started !
After a telephone call with Pierre L. this morning, we found that "TELEMAC/v6p2r1/Bief" was not present ! in fact it was slipping in "TELEMAC/v6p2r1/Artemis"

Problem solve !

Thank you very much to you and Pierre for your help !

Philippe