open TELEMAC-MASCARET The mathematically superior suite of solvers

Hello -

I have some old files from simulations that were done using TELEMAC-2D v5.1. I have not currently been using TELEMAC recently but I need to quickly modify the input hydrographs and run some of my old models again. I only had a license for 5.1 on an older machine; I can download and install the current version on newer machines (Windows 7, 64-bit) but there seems to be some incompatibility in file formats. At the moment I am in a bit of a hurry so I am looking for the quickest and easiest solution. Is there a simple way I can either have version 6 read my old input files, or else install version 5.1 on a newer machine just long enough to get it to take care of these few model runs? Thanks in advance for any suggestions.

Hello,

The selafin format has not changed for eons, and is still IEEE big_endian, so it is unlikely that you have a problem with formats, could you be more precise about this ?

Regards,

Jean-Michel Hervouet

Hi

As Jean-Michel said, old files should work well with latest telemac version.
The only incompatibility that could exist is in the user fortran file if you have one. In such case, you should create a new fortran file using the new source file and modifying it according your previous modification.

On the subject of installing the 5.1 version on a new machine, it's impossible because this version is not a free and open version.
Moreover, I'm not sure that you could find a setup for this old version (2001!).

Regards

Thanks for the reply. I thought before responding I should go back and try everything I could to see if I could get v6p1 installed and running. So we have done the following:

First, we thought we would try just installing the executables without trying to compile. So we followed the instructions on the Compiled Codes page first. We installed Strawberry Perl, then we downloaded and installed the Setup_TELEMAC_v6p1_windows_intel archive, extracted it, and installed it. We also installed Python 2.7 so we would have the option of going that route if necessary. We made the appropriate changes to the PATH statement and added the SYSTELCFG variable with the correct path to the config directory (for use with Perl), then we checked that the systel.ini file had the correct paths listed and the correct HOSTTYPE and PROJECT assignments. We weren't planning to use a fortran compiler but did download and install the g95 compiler and added its location to the PATH statement and changed FC_NAM to g95. We tried running telemac2d from the command line with one of the tutorial files. we then got a fatal error from runtel.pl, saying

Module <tm_info> inaccessible, compilation aborted at runtel.pl line 273.

Of course tm_info is in the same subdirectory as runtel.pl so it's not clear what triggered this problem.

Anyway, we eventually gave up on this option and tried the python option, but have had no luck there either. We changed the SYSTELCFG variable to the systel.cis-windows.cfg file with the correct path, then edited that file for the correct root directory, left the modules listed as "update" and "system", in the windows g95 scalar section we substituted g95 for ifort, in the compileTELEMAC.py file we substituted g95 for ifort, and then we executed the compileTELEMAC.py command. But as it was scanning various modules it got down as far as

... now scanning special_v6p1

and then

Building the who calls who tree for GREDELMET_AUTOP and dependents

came up and identified all the directories that are not related to g95, I suppose because they are connected to ifort. So I got a bunch of "no such file or directory" statements or "invalid argument" statements and then eventually exited from the compile.

Anyway, we next thought we would try simply running TELEMAC from the command line under python, so we executed the python runcode.py telemac2d -s cas-file command and we did this in a directory with a cas.txt file and all the associated files available. We tried this with several of the tutorial files and got the "inconsistent CAS file" statement. Then we ran it again and specified the -c wintels to make sure it was running the scalar option, and we got the following:

Not able to find your OBJECT command line: wintels\telemac2dv6p1.cmdo

... you have to compile this module at least:

+> telemac2d

At this point I suppose I could uninstall everything and start from scratch because obviously I am doing something wrong, but nothing I have tried has seemed to work. And I'm not much of a programmer but I had a very experienced programmer sitting with me this afternoon trying to help me troubleshoot and eventually he gave up as well.

Any recommendations would be welcome.

Hello,

Regarding the perl option : the tm_info problem is generally due to problems of installation of perl (e.g. two different perl competing or correct address of perl not given in the file systel.ini, which is the file in the directory where the variable SYSTELCFG points to), and of course the bin directory where tm_info is with all scripts perl must be in the PATH.

I hope this helps,

Jean-Michel Hervouet

Thanks Jean-Michel - I'll look again. It's possible that there were two competing versions of perl - someone may have installed an earlier version before I did. It can't be a problem with the PATH statement because the script that was looking for tm_info (runtel.pl)was actually in the same subdirectory (telemav6p1\bin)as tm_info, and that subdirectory was in the PATH statement and I rebooted the computer after modifying it. I will try uninstalling TELEMAC and perl and then just reinstall perl 2.7 and then TELEMAC again.

Is there a potential conflict when both perl and python are installed? I'm wondering why the other options didn't work.

thanks,

Andy

I meant to type telemac\v6p1\bin.

Here is an update on my progress trying to install version 6.1 on a 64-bit Windows machine. I am still having difficulties.

I uninstalled and then reinstalled TELEMAC. I checked to make sure I had only one version of perl installed (before reinstalling TELEMAC), and then modified path commands and SYSTEL.INI and the SYSTELCFG variable to make sure everything could be accessed properly. I verified that perl was running. I ran cfgmak.pl after updating SYSTEL.INI with the correct path information as specified in the directions under "important note." Then I opened a DOS window, went to a directory with the tutorial files for one of the examples, and typed

telemac2d cas.txt > cas.out

to save the text output.

The program didn't execute because it was looking for the systel.cfg file. It did have the correct path to find the config directory, where the systel.ini file (with all the correct edits included) was located, but that apparently is not what it was looking for. According to the instructions for installation using perl, the SYSTELCFG variable needs only the correct path to find the directory. The directions say only that the systel.ini file has to be in the config directory. I have attached my copy of the systel.ini file for reference.

Here is the message I got when I tried to run telemac from the command line:

c:\TELEMAC\temp\confluence>runcode.py telemac2d cas.txt


Loading Options and Configurations
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Not able to get to the configuration file: C:\TELEMAC\V6P1\config\systel.cfg

... in directory: C:\TELEMAC\V6P1\config
... use instead:
+> systel.cis-windows.cfg
+> systel.edf.cfg
+> systel.hrw.cfg

What should I do in order to get telemac to run from the command line?

thanks,

Andy

Here is the text of the systel.ini file:

[GENERAL]
#
#

---

Parametrage version+langue par defaut
# pour chaque code
# - LNGXXX (langue)
# - VERSXXX (version)
#---TELEMAC2D
LNGTEL=2
VERSTEL=v6p1
#---AESN
LNGAESN=2
VERSAESN=v6p1
#---RIG
LNGRIG=2
VERSRIG=v6p1
#---TELEMAC3D
LNGTEL3D=2
VERSTEL3D=v6p1
#---STBTEL
LNGSTB=2
VERSSTB=v6p1
#---POSTEL3D
LNGPOSTE=2
VERSPOSTE=v6p1
#---ARTEMIS
LNGARTE=2
VERSARTE=v6p1
#---SISYPHE
LNGSISY=2
VERSSISY=v6p1
#---TOMAWAC
LNGTOMA=2
VERSTOMA=v6p1
#---ESTEL2D
LNGESTEL2=2
VERSESTEL2=v6p1
#---ESTEL3D
LNGESTEL3=2
VERSESTEL3=v6p1
#---TELSIS
LNGTELS=2
VERSTELS=v6p1
#---SPARTACUS2D
LNGSPA=2
VERSSPA=v6p1
#
#

---

Repertoire d'installation et plate-forme
# (défini automatiquement lors de l'installation)
#
PROJECT=C:\TELEMAC\V6P1
HOSTTYPE=win64
#
#

---

Perl : chemins d'accès à l'interprete (bin)
# et aux modules (lib)
[PERL]
#PERLPATH=c:\strawberry\perl\bin
#PERLLIB=c:\strawberry\perl\lib
#
#-VERSION-5.9

---

Configs

---

#
# Compil : $FC $FC_OPT_OTHERS [$FC_OPT_COMPIL,$FC_OPT_DEBUG,$FC_OPT_PROFILE]
# Link : $LK $LK_OPT_OTHERS [$LK_OPT_DEBUG] [$LK_OPT_PROFILE] $LK_OPT_OUTNAME
#
#

---

#
#

---

WIN 32bits avec Intel Visual Fortran
#
[win32]
DIRLIB=win32
#
FC_NAM="g95 "
FC_OPT_OBJEXT="obj"
FC_OPT_COMPIL=" /compile_only /O2 /check=overflow /iface:nomixed_str_len_arg /warn:declaration /warn:argument_checking /warn:unused "
FC_OPT_COMPIL90=" /compile_only /nofixed /optimize:4 /check=overflow /iface:nomixed_str_len_arg /warn:declaration /warn:argument_checking /warn:unused "
FC_OPT_DEBUG=" /c /Od /traceback /debug:full /warn:declarations "
FC_OPT_PROFILE=" /c /warn:declarations "
FC_OPT_INCLUDE="/include:"
FC_OPT_OTHERS=" /nologo /convert:big_endian /extend-source:132 "
FC_OPT_OTHERS90=" /nologo /convert:big_endian "
#
LK_NAM="link"
LK_OPT_NORMAL=" "
# options supplementaires pour le format med
#LK_OPT_NORMAL=" /lf2c /lm /lz /lstdc++ "
LK_OPT_DEBUG=" /debug "
LK_OPT_PROFILE=" /debug /profile "
LK_OPT_OUTNAME=" /out:"
LK_OPT_OTHERS=" /MACHINE:IX86 /subsystem:console /incremental:no /stack:67108864 /nodefaultlib:libc.lib "
# bibliotheques supplementaires pour le format med
#LK_LIB_SPECIAL="<TELEMAC_HOME>\MED\libmed.a <TELEMAC_HOME>\MED\libhdf5.a "
#
LIB_NAM="link -lib"
LIB_OPT_LIBEXT="lib"
LIB_OPT_OUTNAME=" /out:"
LIB_OPT_OTHERS= " /nologo"
LIB_RANLIB=
#
METIS="libmetis32.lib"
#
RUN_DEBUG="xdb "
RUN_PROFILE=
#
#---- MPI2
#
FC_MPI="ifort "
LK_MPI="link /debug /MACHINE:IX86 /subsystem:console /incremental:no /stack:67108864 /nodefaultlib:libc.lib /out:<EXE> <OBJS> <LIBS> "
LIBS_MPI="""C:\Program Files (x86)\MPICH2\lib\fmpich2.lib"
DIRINC_MPI="""C:\Program Files (x86)\MPICH2\include"
# les 3" au début sont important pour contourner le traitement perl qui supprime systématiquement 2"
# solution bricolée en raison du problème posé par l'espace de "Program Files"
#
#- PC multiprocesseurs
#RUN_MPI="mpiexec -localonly <N> <EXE>"
#- réseau de PCs
RUN_MPI="mpiexec -file mpirun.txt"
#RUN_MPI="mpiexec -logon : -machinefile mpirun.txt -n <N> <EXE>"
#- PCs en réseau avec solution de connection simplifiee
#RUN_MPI="smpd -machinefile mpirun.txt"
#
#
#

---

#
# IF YOU WANT TO USE ARTEMIS// PLEASE UNCOMMENT INCDIRMUMPS AND LIBSMUMPSPAR
#
# 1 FILL BELOW THE LOCATION OF YOUR MUMPS INCLUDE DIRECTORY (INCDIRMUMPS =...)
#INCDIRMUMPS = /home/denis/MUMPS_4.9.0/include
#LIBMUMPSPAR="/home/telemac/mumpsmpi/mumpsmpi_<VERSARTE>/<HOSTTYPE>/mumpsmpi<VERSARTE>.a -L/home/denis/MUMPS_4.9.0/lib/ -ldmumps -lmumps_common -lpord -L/home/logiciels/intel/mkl/10.2.1.017/lib/em64t -lmkl_scalapack_lp64 -lmkl_blacs_ilp64 -lmkl_intel_lp64 -lmkl_sequential -lmkl_core -lguide -static-intel /home/logiciels/metis-4.0/lib/libmetis.a -L/home/denis/scotch_5.1_esmumps/lib -lesmumps -lscotch -lscotcherr -lm"
#LIBMUMPSSEQ="<TELEMAC_HOME>\mumpsvoid\mumpsvoid_<VERSARTE>\<HOSTTYPE>\mumpsvoid<VERSARTE>.lib"
#
#

---

#
# IF YOU DO NOT WANT USE ARTEMIS// MUMPS LIBRARY IS NOT NECESSARILY
#
# SO UNCOMMENT THE FOLLOWING STATEMENT AND WRITE THE LOCATION OF MUMPSVOID_<VERSARTE>.LIB LIBRARY
#
# SHOULD BE <PROJECT>\mumpsvoid\mumpsvoid_<VERSARTE>\<HOSTTYPE>\mumpsvoid<VERSARTE>.lib
#
LIBMUMPSPAR="<TELEMAC_HOME>\mumpsvoid\mumpsvoid_v6p1\<DIRLIB>\mumpsvoidv6p1.lib"
LIBMUMPSSEQ="<TELEMAC_HOME>\mumpsvoid\mumpsvoid_v6p1\<DIRLIB>\mumpsvoidv6p1.lib"
#
#
#

---

WIN 64bits avec Intel Visual Fortran
#
[win64]
DIRLIB=win64
#
FC_NAM="g95 "
FC_OPT_OBJEXT="obj"
FC_OPT_COMPIL=" /compile_only /O2 /check=overflow /iface:nomixed_str_len_arg /warn:declaration /warn:argument_checking /warn:unused "
FC_OPT_COMPIL90=" /compile_only /nofixed /optimize:4 /check=overflow /iface:nomixed_str_len_arg /warn:declaration /warn:argument_checking /warn:unused "
FC_OPT_DEBUG=" /c /Od /traceback /debug:full /warn:declarations "
FC_OPT_PROFILE=" /c /warn:declarations "
FC_OPT_INCLUDE="/include:"
FC_OPT_OTHERS=" /nologo /convert:big_endian /extend-source:132 "
FC_OPT_OTHERS90=" /nologo /convert:big_endian "
#
LK_NAM="link"
LK_OPT_NORMAL=" "
# options supplementaires pour le format med
#LK_OPT_NORMAL=" /lf2c /lm /lz /lstdc++ "
LK_OPT_DEBUG=" /debug "
LK_OPT_PROFILE=" /debug /profile "
LK_OPT_OUTNAME=" /out:"
LK_OPT_OTHERS=" /MACHINE:X64 /subsystem:console /incremental:no /stack:67108864 /nodefaultlib:libc.lib "
# bibliotheques supplementaires pour le format med
#LK_LIB_SPECIAL="<TELEMAC_HOME>\MED\libmed.a <TELEMAC_HOME>\MED\libhdf5.a "
#
LIB_NAM="link -lib"
LIB_OPT_LIBEXT="lib"
LIB_OPT_OUTNAME=" /out:"
LIB_OPT_OTHERS= " /nologo"
LIB_RANLIB=
#
METIS="metis64.lib"
#
RUN_DEBUG="xdb "
RUN_PROFILE=
#
#---- MPI2
#
FC_MPI="g95 "
LK_MPI="link /debug /MACHINE:X64 /subsystem:console /incremental:no /stack:67108864 /nodefaultlib:libc.lib /out:<EXE> <OBJS> <LIBS> "
LIBS_MPI="""C:\Program Files\MPICH2\lib\fmpich2.lib"
DIRINC_MPI="""C:\Program Files\MPICH2\include"
# les 3" au début sont important pour contourner le traitement perl qui supprime systématiquement 2"
# solution bricolée en raison du problème posé par l'espace de "Program Files"
#
#- PC multiprocesseurs
#RUN_MPI="mpiexec -localonly <N> <EXE>"
#- réseau de PCs
RUN_MPI="mpiexec -file mpirun.txt"
#RUN_MPI="mpiexec -logon : -machinefile mpirun.txt -n <N> <EXE>"
#- PCs en réseau avec solution de connection simplifiee
#RUN_MPI="smpd -machinefile mpirun.txt"
#
#
#

---

#
# IF YOU WANT TO USE ARTEMIS// PLEASE UNCOMMENT INCDIRMUMPS AND LIBSMUMPSPAR
#
# 1 FILL BELOW THE LOCATION OF YOUR MUMPS INCLUDE DIRECTORY (INCDIRMUMPS =...)
#INCDIRMUMPS = /home/denis/MUMPS_4.9.0/include
#LIBMUMPSPAR="/home/telemac/mumpsmpi/mumpsmpi_<VERSARTE>/<HOSTTYPE>/mumpsmpi<VERSARTE>.a -L/home/denis/MUMPS_4.9.0/lib/ -ldmumps -lmumps_common -lpord -L/home/logiciels/intel/mkl/10.2.1.017/lib/em64t -lmkl_scalapack_lp64 -lmkl_blacs_ilp64 -lmkl_intel_lp64 -lmkl_sequential -lmkl_core -lguide -static-intel /home/logiciels/metis-4.0/lib/libmetis.a -L/home/denis/scotch_5.1_esmumps/lib -lesmumps -lscotch -lscotcherr -lm"
#LIBMUMPSSEQ="<TELEMAC_HOME>\mumpsvoid\mumpsvoid_<VERSARTE>\<HOSTTYPE>\mumpsvoid<VERSARTE>.lib"
#
#

---

#
# IF YOU DO NOT WANT USE ARTEMIS// MUMPS LIBRARY IS NOT NECESSARILY
#
# SO UNCOMMENT THE FOLLOWING STATEMENT AND WRITE THE LOCATION OF MUMPSVOID_<VERSARTE>.LIB LIBRARY
#
# SHOULD BE <PROJECT>\mumpsvoid\mumpsvoid_<VERSARTE>\<HOSTTYPE>\mumpsvoid<VERSARTE>.lib
#
LIBMUMPSPAR="<TELEMAC_HOME>\mumpsvoid\mumpsvoid_v6p1\<DIRLIB>\mumpsvoidv6p1.lib"
LIBMUMPSSEQ="<TELEMAC_HOME>\mumpsvoid\mumpsvoid_v6p1\<DIRLIB>\mumpsvoidv6p1.lib"

I have resolved the problem. The command-line option was invoking the python script rather than the perl script. There were three or other problems that had to be resolved but I am now able to get TELEMAC to run both tutorial files and my own jobs.