open TELEMAC-MASCARET The mathematically superior suite of solvers

# _____ _______________________________
# ____/ TELEMAC Project Definitions /______________________________/
#
[Configurations]
configs: ubugfortrans ubugfmpich
# ubugfortransdbg ubugfmpich2 ubugfmpich2dbg
#
#
# _____ ___________________________________________________
# ____/ GENERAL /__________________________________________________/
[general]
root: /home/mishel/telemac/v7p1
version: v7p1
language: 2
modules: update system -dredgesim
option: parallel mpi
#
cmd_lib: ar cru <libname> <objs>
cmd_exe: /usr/bin/mpif90 -fconvert=big-endian -frecord-marker=4 -v -lm -o <exename> <objs> <libs>
#
mods_all: -I <config>
#
sfx_zip: .gztar
sfx_lib: .a
sfx_obj: .o
sfx_mod: .mod
sfx_exe:
#
val_root: <root>/examples
val_rank: all
# also possible val_rank: <3 >7 6
# _____ ____________________________________
# ____/ Ubuntu gfortran scalar /___________________________________/
[ubugfortrans]
#
brief: scalar mode, Fortran optimisation 3.
TELEMAC will work whether processor is 0 or 1
#
cmd_obj: gfortran -c -O3 -fconvert=big-endian -frecord-marker=4 <mods> <incs> <f95name>
cmd_exe: gfortran -fconvert=big-endian -frecord-marker=4 -v -o <exename> <objs> <libs>
# _____ ____________________________________
# ____/ Ubuntu gfortran scalar debug/___________________________________/
[ubugfortransdbg]
#
brief: scalar mode, Fortran debug mode.
TELEMAC will work whether processor is 0 or 1
#
cmd_obj: gfortran -c -g -fbounds-check -Wall -fbacktrace -finit-real=nan -fconvert=big-endian -frecord-marker=4 <mods> <incs> <f95name>
cmd_exe: gfortran -fconvert=big-endian -frecord-marker=4 -v -o <exename> <objs> <libs>
#
# _____ ____________________________________
# ____/ Ubuntu gfortran mpich2 /___________________________________/
[ubugfmpich]
#
brief: parallel mode, using mpiexec directly (of the MPICH2 package).
The only difference with the scalar versions (optimised) is the presence
of the key mpi_cmdexec and the -DHAVE_MPI compilation directive.
Of course, you also need the key par_cmdexec.
Finally, note that this configuration also works whether
processor is 0 or 1.
#
mpi_cmdexec: /usr/bin/mpiexec -wdir <wdir> -n <ncsize> <exename>
#
cmd_obj: gfortran -c -O3 -DHAVE_MPI -fconvert=big-endian -frecord-marker=4 <mods> <incs> <f95name>
#
incs_special: -I /usr/lib/mpich/include/
incs_parallel: -I /usr/lib/mpich/include/
incs_bief: -I /usr/lib/mpich/include/
libs_partel: ~/telemac/v7p1/optionals/metis-5.1.0/build/Linux-x86_64/libmetis/libmetis.a
libs_all: /usr/lib/mpich/lib/libmpich.so
#
# _____ ____________________________________
# ____/ Ubuntu gfortran mpich2 debug /___________________________________/
[ubugfmpich2dbg]
#
brief: parallel mode, using mpiexec directly (of the MPICH2 package).
The only difference with the scalar versions (debugged) is the presence
of the key mpi_cmdexec and the -DHAVE_MPI compilation directive.
Of course, you also need the key par_cmdexec.
Finally, note that this configuration also works whether
processor is 0 or 1.
#
mpi_cmdexec: /usr/bin/mpiexec -wdir <wdir> -n <ncsize> <exename>
#
cmd_obj: gfortran -c -g -fbounds-check -Wall -fbacktrace -finit-real=nan -DHAVE_MPI -DHAVE_MUMPS -fconvert=big-endian -frecord-marker=4 <mods> <incs> <f95name>
#
incs_special: -I /usr/lib/mpich2/include/ -I /home/telemac/mumps/MUMPS_5.0.0/include/
incs_parallel: -I /usr/lib/mpich2/include/ -I /home/telemac/mumps/MUMPS_5.0.0/include/
incs_bief: -I /usr/lib/mpich2/include/ -I /home/telemac/mumps/MUMPS_5.0.0/include/
libs_partel: /home/telemac/metis-5.0.2/libmetis.a
libs_all: /usr/lib/mpich2/lib/libmpich.so -L /home/telemac/mumps/MUMPS_5.0.0/lib -ldmumps -lmumps_common -lpord /home/telemac/mumps/SCALAPACK/libscalapack.a -L /home/telemac/mumps/BLAS-3.5.0 /home/telemac/mumps/BLAS-3.5.0/blas_LINUX.a /home/telemac/mumps/BLACS/LIB/blacs_MPI-LINUX-0.a /home/telemac/mumps/BLACS/LIB/blacsF77init_MPI-LINUX-0.a /home/telemac/mumps/BLACS/LIB/blacs_MPI-LINUX-0.a

Hello,

I used your install process and it worked fine, but I get some problems when I like to run the test model. I guess it has something to with MPI on Ubuntu.

Do you know how to solve this problem?

MPI_INITIALIZED F
[tvrl-OptiPlex-9020:3031] *** An error occurred in MPI_Comm_rank
[tvrl-OptiPlex-9020:3031] *** reported by process [1580466177,0]
[tvrl-OptiPlex-9020:3031] *** on communicator MPI_COMM_WORLD
[tvrl-OptiPlex-9020:3031] *** MPI_ERR_COMM: invalid communicator
[tvrl-OptiPlex-9020:3031] *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
[tvrl-OptiPlex-9020:3031] *** and potentially your MPI job)

---

Primary job terminated normally, but 1 process returned
a non-zero exit code.. Per user-direction, the job has been aborted.

---

---

mpiexec detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:

Process name: [[24116,1],0]
Exit code: 5

---

_____________
runcode::main:
:
|runCode: Fail to run
|/usr/bin/mpiexec -wdir /home/tvrl/telemac/v7p1/examples/telemac2d/bumpflu/t2d_bumpflu.cas_2018-01-26-14h33min02s -n 1 /home/tvrl/telemac/v7p1/examples/telemac2d/bumpflu/t2d_bumpflu.cas_2018-01-26-14h33min02s/out_t2d_bumpflu
|~~~~~~~~~~~~~~~~~~
|
|~~~~~~~~~~~~~~~~~~


Thanks in advance

Hi Stef,

I tried to follow the same steps but I got error messages.

I've attached a snapshot of the errors.

Thanks,
Mohammed

Hi Mohammed,


Could you add -cpp and try again?

Cheers
Huy

Hi Huy,

Thanks for your reply.

I tried it, but no change, same errors.

Cheers,
Mohammed

Hi
Did you make a clean full compilation?

Hi c.coulet,

No :). I did that now, I still got similar messages, but the compilation continued and completed.

I will try to run the examples to check if it's working properly.

Thanks for the help.

Cheers,
Mohammed

Hi,

I'm facing strange problem. After I've compiled telemac v7p3, I tested on single processor and parallel. It worked fine.

Then I run a 2D and 3D simulation for the coarse mesh of my model, it worked fine. But when I tried to run the same for my higher resolution mesh, I got this error message when I run it in parallel mode:

... partitioning base files (geo, conlim, sections, zones and weirs)
+> /home/ma211/telemac/v7p3/builds/ubugfmpich/bin/partel < PARTEL.PAR >> partel_T2DGEO.log
STOP 1
runPartition:
|runPARTEL: Could not split your file T2DGEO (runcode=1) with the error as follows:
|
|... The following command failed for the reason above (or below)
|/home/ma211/telemac/v7p3/builds/ubugfmpich/bin/partel < PARTEL.PAR >> partel_T2DGEO.log
|
| You may have forgotten to compile PARTEL with the appropriate compiler directive
| (add -DHAVE_MPI to your cmd_obj in your configuration file).


Although it works fine on single processor mode, and works fine on parallel mode for the coarser mesh.

Any ideas?

Thanks,
Mohammed

You should have a look into the partel_T2DGEO.log
The message about the partel compilation is a default message...
If it works on a coarser mesh, this means you probably have a problem with the finer mesh

You could also try to just run the partition step and see if it works or not.
It's also possible to run partel manually...

Regards

Hi Christophe,

Thanks for the reply.

The partel_T2DGEO.log shows this error:

ERROR IN BOUNDARIES J= 6092
WHILE NPTFR_P(I)= 5195
WHILE L= 5195

I run the finer mesh so many times on the single processor mode without any trouble, I activated check mesh while I'm running it in single mode, and there was no issue reported. It's only when I run the parallel mode.

I don't know if it matters, but when I constructed the fine mesh on Bluekenue, I used the option sub-mesh to integrate the finer mesh for a specific area within coarser mesh for the rest of the study area. So my finer mesh is actually has two resolutions.

What are the steps to run partel manually and how to run the partition step only?

Thanks,
Mohammed