open TELEMAC-MASCARET The mathematically superior suite of solvers

Hallo!

Does anyone know about the folowing error?
I do not understand it and it never happened to me before.

"1. this process did not call "init" before exiting, but others in the job did.
This can cause a job to hang indefinitely while it waits for all processes to call "init".
By rule, if one process calls "init", then ALL processes must call "init" prior to termination.

2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to exiting or it will be considered an "abnormal termination"

This may have caused other processes in the application to be terminated by signals sent by mpiexec (as reported here)."

Thanks.

Best regards

Hi,

Could you post your conifguration file as well as the full listing of the error?
Are you on Linux/Windows ?
What version of telemac are you using ?

Thanks.

The error is the following:


ITERATION 0 TIME: 0.0000 S
PRERES: MAXIMUM COURANT NUMBER: 0.000000
THE LIQUID BOUNDARIES FILE CONTAINS
10 LINES WITH:
Q(2) Q(3)
DEBIMP : PROBLEM ON BOUNDARY NUMBER 2
GIVE A VELOCITY PROFILE
IN THE BOUNDARY CONDITIONS FILE
OR CHECK THE WATER DEPTHS

PLANTE: PROGRAM STOPPED AFTER AN ERROR
_____________
runcode::main:
/projekte/ematta/LWL_EL:
|runCode: Fail to run
|/usr/bin/mpiexec -wdir /projekte/ematta/LWL_EL/LWL_EL.cas_2014-11-24-14h38min24s -n 6 /projekte/ematta/LWL_EL/LWL_EL.cas_2014-11-24-14h38min24s/out_telemac2d
|~~~~~~~~~~~~~~~~~~
|STOP 2
|STOP 2
|STOP 2
|STOP 2
|STOP 2
|STOP 2
|

---

|mpiexec has exited due to process rank 1 with PID 24564 on
|node wahyd02 exiting improperly. There are two reasons this could occur:
|
|1. this process did not call "init" before exiting, but others in
|the job did. This can cause a job to hang indefinitely while it waits
|for all processes to call "init". By rule, if one process calls "init",
|then ALL processes must call "init" prior to termination.
|
|2. this process called "init", but exited without calling "finalize".
|By rule, all processes that call "init" MUST call "finalize" prior to
|exiting or it will be considered an "abnormal termination"
|
|This may have caused other processes in the application to be
|terminated by signals sent by mpiexec (as reported here).
|

---

I attach the cas file, geo file, liquid boundary and boundary files.
It says that there are problems at boundary 2 because I have implemented a little open boundary (5 nodes), which represent a channel that takes water from the computational domain.
To explain better, I have the following boundaries:
boundary 1: outflow, constant water elevation 300.3 m;
boundary 2: channel, imposed discharge of -28 m3/s;
boundary 3: inflow, imposed discharge 1000 m3/s

I think that the error comes because I have dry boundaries and telemac does not know how to compute the velocity for boundary 2 because there is no water. Do you have any suggestion to realize the channel in Telemac? I also attach a picture, so you can see the channel that I have to realize. It is about 100 m wide.

By the way, I use windows.

Thanks for any help.

Best regards

I forgot, I use Telemac version v6p3r2.

As you can see in the log the error comes from your boundaries:The rest is just gibberish from mpi because it dit not ended properly.

Hope it helps.

Sorry to bother, maybe was not clearly visible, after copying the error I wrote you something and attach some files, can you please read what I wrote?

Thanks a lot

My bad i missed the end of your post.

You need to set an non-zero depth to the boundary point.
Using the user subroutine debimp.

Hope it helps.

Hello,

Actually you are probably prescribing a discharge on a boundary that has no water depth. You can either change your initial conditions so that there is some water, or prescribe also the water depth for a few time steps. As a matter of fact, a discharge on dry bed would be a supercritical flow and in this case the depth must be given.

Your problem can also happen on a boundary with free depth that becomes supercritical, in this case the depth can decrease to 0, but generally this happens after some time in a computation, not at the first time step.

With best regards,

Jean-Michel Hervouet

Yes, thanks, I know that... the problem is that I have to compute this drought case and I think the only possibility is to change the mesh...
I tried altready to change the initial condition and impose the initial elevation much higher, but it does not work anyway.

Thanks.

Best regards

Hello,

Without changing the mesh, you can also change the bottom topography at the entrance so that there is always water at the entrance.

JMH