open TELEMAC-MASCARET The mathematically superior suite of solvers

I compiled Telemac3D v8p2r0 on Ubuntu 20.04 using gfortran and openmpi (compilation config files are zipped in the attached file).

Acording to BlueKenue the 2D mesh seems OK. On previous Telemac version mesh was checked and OK.
Using the "Checking the mesh = no", the simulation runs without errors and gives reasonable results.

I changed compilation configuration files following some forum advices without success.
I also found some threads in the forum related to "checking the mesh" but none lead me to the solution.

All the files (I think) needed to reproduce the error are in the attached zip file.

The error appears in the end of the screen listing:

========================================================
POINT 41222 HAS ONLY 0 NEIGHBOURS
POINT 41223 HAS ONLY 0 NEIGHBOURS
POINT 41224 HAS ONLY 0 NEIGHBOURS
POINT 41225 HAS ONLY 0 NEIGHBOURS
8 OVERCONSTRAINED TRIANGLES
POSSIBLE BUT NOT RECOMMENDED
ISSUE DETECTED WHILE CHECING THE MESH

PLANTE: PROGRAM STOPPED AFTER AN ERROR
RETURNING EXIT CODE: 2
Traceback (most recent call last):
File "/home/luke/telemac_v8p2r0/v8p2r0/scripts/python3/telemac3d.py", line 7, in <module>
main('telemac3d')
File "/home/luke/telemac_v8p2r0/v8p2r0/scripts/python3/runcode.py", line 271, in main
run_study(cas_file, code_name, options)
File "/home/luke/telemac_v8p2r0/v8p2r0/scripts/python3/execution/run_cas.py", line 157, in run_study
run_local_cas(my_study, options)
File "/home/luke/telemac_v8p2r0/v8p2r0/scripts/python3/execution/run_cas.py", line 65, in run_local_cas
my_study.run(options)
File "/home/luke/telemac_v8p2r0/v8p2r0/scripts/python3/execution/study.py", line 612, in run
self.run_local()
File "/home/luke/telemac_v8p2r0/v8p2r0/scripts/python3/execution/study.py", line 440, in run_local
run_code(self.run_cmd, self.sortie_file)
File "/home/luke/telemac_v8p2r0/v8p2r0/scripts/python3/execution/run.py", line 182, in run_code
raise TelemacException('Fail to run\n'+exe)
utils.exceptions.TelemacException: Fail to run
/usr/bin/mpiexec -wdir /mnt/HDD/7.Runs/check_mesh/checkmesh.cas_2021-06-02-21h10min20s -n 1 /mnt/HDD/Work/7.Runs/check_mesh/checkmesh.cas_2021-06-02-21h10min20s/out_telemac3d

==============================================

Any advice is welcome. Thank you.

Hello,

Thanks for raising this bug. You are right, it worked in previous releases, but I think a change when calling CHECKMESH subroutine introduced this bug only in 3D for the 3D mesh (not the 2D mesh).

I think if you change the call of CHECKMESH in the INBIEF subroutine (at the end) with NPOIN2 rather than NPOIN, it will work (check only for the number of 2D points, not the 3D points). The error written is that you have 2 points at the same location, which is not allowed for the 2D mesh, but for the 3D mesh, it may happen (e.g. for tidal flats): it was written in the log that the smallest distance was 0 between node 1 and node 8246 which is the 3D mesh of plane 2, just above node 1 of plane 1.

The fix will be pushed for next release.

Anyway, it is just a check and the following of your computation is OK.
But it warned you that you have 2 overconstrained triangles (the 3 nodes belong to the boundaries) and I would recommend you to change your mesh a little bit to delete them (2 around coordinates (319 058 ; 8 977 420).

Chi-Tuan

Dear Chi-Tuan

Thank you for the kind attention and detailed explanation.
I did what you suggested (NPOIN--> NPOIN2) and it worked fine.
I also corrected the two overconstrained triangles.

Márcio