open TELEMAC-MASCARET The mathematically superior suite of solvers

Hi,

I have recently been experiencing the following errors and unfortunately I don't know where they are coming from? I read from the error that it is about the SELAFIn geometry file, but I have been using it for almost a year and have had no problems with it so far... Can anyone help me and tell me what the problem is?
Thank you very much!

MASTER PROCESSOR NUMBER 0 OF THE GROUP OF 32
EXECUTABLE FILE: /work_beegfs/sungg1045/vier/okt.cas_2024-02-16-13h37min40s/A.EXE
LISTING OF TELEMAC2D

---

********************************************
* LECDON: *
* AFTER CALLING DAMOCLES *
* CHECKING OF DATA READ *
* IN THE STEERING FILE *
********************************************

EXITING LECDON. NAME OF THE STUDY:

OPENING FILES FOR TELEMAC2D
OPENING: T2DGEO-roughness.slf
OPENING: T2DCLI-roughness.cli
OPENING: T2DRES-Okt_eins_rough_output.slf
OPENING: T2DIMP-water.lqd
OPENING: T2ATMA-wind

*****************************
* MEMORY ORGANIZATION *
*****************************

READ_MESH_INFO: TITLE= newSelafin
NUMBER OF ELEMENTS: 22802
NUMBER OF POINTS: 11607

TYPE OF ELEMENT: TRIANGLE
TYPE OF BND ELEMENT: POINT

SINGLE PRECISION FORMAT (R4)

MXPTEL (BIEF) : MAXIMUM NUMBER OF ELEMENTS AROUND A POINT: 9
MAXIMUM NUMBER OF POINTS AROUND A POINT: 10
(GLOBAL MESH)
SEGBOR (BIEF) : NUMBER OF BOUNDARY SEGMENTS = 410
INCLUDING THOSE DUE TO DOMAIN DECOMPOSITION
USER_CORRXY (BIEF):NO MODIFICATION OF COORDINATES

MESH: MESH ALLOCATED

*************************************
* END OF MEMORY ORGANIZATION: *
*************************************

INITIALIZING TELEMAC2D FOR
INBIEF (BIEF): NOT A VECTOR MACHINE (ACCORDING TO YOUR DATA)
FONSTR : FRICTION COEFFICIENTS READ IN THE
GEOMETRY FILE
STRCHE (BIEF): NO MODIFICATION OF FRICTION

NUMBER OF LIQUID BOUNDARIES: 2


CORFON (TELEMAC2D): NO MODIFICATION OF BOTTOM
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.


Backtrace for this error:

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

(the full error is attached)

Hi
Not sure the error is coming from the geometry file ...
the message is not sufficient to localize the problem...
Few things to test, as usual in such situation

1. run in sequential mode to identify if it's linked to parrallel computation and domain decomposition or not
2. activate the debugger mode of the steering file (DEBUGGER = 1) to have an idea of the subroutine where the segfault arise
3. use the debug config to heve more information about the crash and identify precisely the segfault location

Hope this helps

Hi, thank you! For the second one the error massage lookes now like this (full one again attached), and it is the same with or without parallelism..


*****************************
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
* MEMORY ORGANIZATION *

*****************************Backtrace for this error:



Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
READ_MESH_INFO: TITLE= newSelafin

NUMBER OF ELEMENTS: 22802
Backtrace for this error: NUMBER OF POINTS: 11607


TYPE OF ELEMENT: TRIANGLE

TYPE OF BND ELEMENT: POINTProgram received signal SIGSEGV: Segmentation fault - invalid memory reference.


Backtrace for this error:

SINGLE PRECISION FORMAT (R4)

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

MXPTEL (BIEF) : MAXIMUM NUMBER OF ELEMENTS AROUND A POINT: 9

MAXIMUM NUMBER OF POINTS AROUND A POINT: 10Backtrace for this error:

(GLOBAL MESH)
SEGBOR (BIEF) : NUMBER OF BOUNDARY SEGMENTS = 410

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
INCLUDING THOSE DUE TO DOMAIN DECOMPOSITION

USER_CORRXY (BIEF):NO MODIFICATION OF COORDINATES
Backtrace for this error:


MESH: MESH ALLOCATED
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

*************************************

* END OF MEMORY ORGANIZATION: *Backtrace for this error:

*************************************

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

INITIALIZING TELEMAC2D FOR

CALLING LECLIM
Backtrace for this error: BACK FROM LECLIM

CALLING INBIEF
INBIEF (BIEF): NOT A VECTOR MACHINE (ACCORDING TO YOUR DATA)

Program received signal SIGSEGV: Segmentation fault - invalid memory reference. BACK FROM INBIEF


CALLING FONSTR
Backtrace for this error: FONSTR : FRICTION COEFFICIENTS READ IN THE

GEOMETRY FILE

STRCHE (BIEF): NO MODIFICATION OF FRICTIONProgram received signal SIGSEGV: Segmentation fault - invalid memory reference.



BACK FROM FONSTR
Backtrace for this error: CALLING FRICTION_CHOICE 0

IN FRICTION_CHOICE-INIT STEP

BACK FROM FRICTION_CHOICE 0Program received signal SIGSEGV: Segmentation fault - invalid memory reference.


Backtrace for this error:
CALLING WRITE_HEADER (TELEMAC-2D)

BACK FROM WRITE_HEADER (TELEMAC-2D)
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
CALLING WRITE_MESH (TELEMAC-2D)

BACK FROM WRITE_MESH (TELEMAC-2D)
Backtrace for this error:


NUMBER OF LIQUID BOUNDARIES: 2
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
CALLING CORNOR

BACK FROM CORNOR
Backtrace for this error: CALLING MASBAS2D


BACK FROM MASBAS2DProgram received signal SIGSEGV: Segmentation fault - invalid memory reference.

CALLING CORFON

Backtrace for this error:

CORFON (TELEMAC2D): NO MODIFICATION OF BOTTOM

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

BACK FROM CORFON

CALLING CONDINBacktrace for this error:

BACK FROM CONDIN
CALLING METEO

hi
according to this listing, I would say there is a problem in meteo...
That means you're using pressure or wind in your computation ...
check the related parameters and files...
Herd to say more with just the log...

Figured out the problem, there was a mistake with my wind file! Thank you so much!