open TELEMAC-MASCARET The mathematically superior suite of solvers

I ran the Mersey tutorial example for telemac2d in parallel processing mode which failed. Does anybody know why it failed and how to overcome this problem? I attach the log file for the failed run.

Dear hydroenvironmental

The log file is not attached. Could you post it again?
Did you test this example without any change (scalar mode)? If yes, is the result was OK?

Regards

Dear Tony (hydroenvironmental),

I found why the mersey telemac2d case does not work in parallel. We are working currently on a new release of the system, v6p0, which will be made available during the summer, in which we had already modified the way the subroutine streamline works. In short, I have now a new version of v5p9, including some of the coming parallelisation changes of v6p0. This latest version of v5p9 now works with the mersey in parallel.

I will shortly make this version available on this web-site.

Best regards,
Sébastien.

That's great :) as I was unsure how to debug this problem look forward to getting the upgraded source code and thanks very much for the very prompt reply to my query

Tony C

I have installed V5p9R5 as advised but on running the Mersey Example in parallel processing mode it still fails. I have attached the pdf of the error message


Any suggestions??

regards

Tony C

Having problem attaching error file so copied it to screen below

Tony C





MASTER PROCESSOR NUMBER 0 OF THE GROUP OF 4
EXECUTABLE FILE:
C:\TELEMAC\V5P9\training\telemac2d\tel2d_v5p9\test.gb\mersey\cas.txt31920_tmp\A
.EXE
BARRIER PASSED


LISTING OF TELEMAC-2D

---

TTTTT EEEEE L EEEEE M M AAAAA CCCCC
T E L E MM MM A A C
T EEE L EEE M M M AAAAA C
T E L E M M A A C
T EEEEE LLLLL EEEEE M M A A CCCCC

2D VERSION 5.9 FORTRAN 90
WITH SEVERAL TRACERS
Coupled with Sisyphe internally


END OF FILE FOR DAMOCLES



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


EXITING LECDON. NAME OF THE STUDY:
MERSEY ESTUARY

OPENING FILES FOR TELEMAC2D



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



READGEO1: TITLE= newmers

NUMBER OF ELEMENTS: 1149
NUMBER OF POINTS: 629
MXPTEL (BIEF) : MAXIMUM NUMBER OF ELEMENTS AROUND A POINT: 7
MAXIMUM NUMBER OF POINTS AROUND A POINT: 8
SEGBOR (BIEF) : NUMBER OF BOUNDARY SEGMENTS = 107
INCLUDING THOSE DUE TO DOMAIN DECOMPOSITION
CORRXY (BIEF):NO MODIFICATION OF COORDINATES

MESH: MESH ALLOCATED



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

INBIEF (BIEF): NOT A VECTOR MACHINE (ACCORDING TO YOUR DATA)
STRCHE (BIEF): NO MODIFICATION OF FRICTION


NUMBER OF LIQUID BOUNDARIES: 1

CORFON (TELEMAC2D): 1 BOTTOM SMOOTHINGS


================================================================================
ITERATION 0 TIME: 0.0000 S
STREAMLINE: USING PARALLEL VERSION OF CHARACTERISTICS
unable to read the cmd header on the pmi context, Error = -1
.
Error posting readv, An existing connection was forcibly closed by the remote host.(10054)
unable to read the cmd header on the pmi context, Error = -1
.
Error posting readv, An existing connection was forcibly closed by the remote host.(10054)
unable to read the cmd header on the pmi context, Error = -1
.
Error posting readv, An existing connection was forcibly closed by the remote host.(10054)
unable to read the cmd header on the pmi context, Error = -1
.
Error posting readv, An existing connection was forcibly closed by the remote host.(10054)

job aborted:
rank: node: exit code[: error message]
0: hydro-6388f10df: 1: Fatal error in MPI_Type_extent: Invalid datatype, error stack:
MPI_Type_extent(110): MPI_Type_extent(INVALID DATATYPE, extent=049DEBF0) failed
MPI_Type_extent(69).: Invalid datatype
1: hydro-6388f10df: 1: Fatal error in MPI_Type_extent: Invalid datatype, error stack:
MPI_Type_extent(110): MPI_Type_extent(INVALID DATATYPE, extent=049DEBF0) failed
MPI_Type_extent(69).: Invalid datatype
2: hydro-6388f10df: 1: Fatal error in MPI_Type_extent: Invalid datatype, error stack:
MPI_Type_extent(110): MPI_Type_extent(INVALID DATATYPE, extent=049DEBF0) failed
MPI_Type_extent(69).: Invalid datatype
3: hydro-6388f10df: 1: Fatal error in MPI_Type_extent: Invalid datatype, error stack:
MPI_Type_extent(110): MPI_Type_extent(INVALID DATATYPE, extent=049DEBF0) failed
MPI_Type_extent(69).: Invalid datatype
Duration of job : 0 seconds ( 0:0:0 ) (system=0.031 sec)

Tony,

Just to check - can you make sure you deleted the local executable (in the mersy directory) before re-runing telemac2d ...

telemac2d will then re-create a new executable for the mersey, given the new version of the system

Best regards,
Sébastien.