open TELEMAC-MASCARET The mathematically superior suite of solvers

Hi,
I am trying to build a river 2d model. I have an initial model to set the initial condition with 4 boundary conditions as follows:

1. inflow (~3700 m3/s) - Q (5 5 5)
2. inflow (~500 m3/s) - Q (5 5 5)
3. inflow (~3200 m3/s) - Q (5 5 5)
4. outflow (~6700 m3/s)- H (5 4 4)

Boundaries 1, 2 and 3 are given with a hydrograph and boundary 4 is set with a rating curve, this model works fine and gives me an initial condition Selafin.
The trouble comes when given some flooded areas that should not have water depth values I tried to impose an open and free boundary (h,q, v, u) (4 4 4 in the *.cli file) with a Thompson liquid boundary condition (option 2), and it gives me an error that has no hints and gives aborted job message.

In the cli file the order for the new boundaries is (4 4 4 – 5 5 5 – 5 5 5 – 5 5 5 - 5 4 4) as now I have 5 boundaries, I changed the LIQUID BOUNDARIES FILE and STAGE-DISCHARGE CURVES FILE accordingly as T Q(2) Q(3) Q(4) SL(5) and Z(5) Q(5) respectively, as well as the cas file, but now it does not work.

Could somebody give a hint on the possible error, I have not tried this type of boundary before and found something similar in the damm break in the example folder but so far I have not been able to make it work.

Gretting,
Chelo.


PD: the complete files are at
we.tl/t-3YeGmjG2h7

I am really sorry, I found out it was a really silly mistake that I overlooked, this post has been reported for it to be taken down as no longer needs to be answered.

PLEASE DO NOT RESPOND TO THIS QUESTION, AS IT IS ALREADY SOLVED.


Grettings,
Chelo.

Hello Chelo,

Perhaps you can tell what was the mistake so that other users do not reproduce it? It may also help them.

Chi-Tuan

Hello Chi-Tuan, I will be glad to do so.

First, my CLI file had an error of not adjacent nodes for the same boundary condition of (4 4 4) free (q,h,v,u) do to a badly replace close boundary (222) node that I did manually.

Second, as a result of this first error the position of the liquid boundary files was misplaced and the types of boundary conditions were not consistent with the CLI file, ex: Q(1) was misplaced as SL(1).Furthermore the OPTION FOR LIQUID BOUNDARIES and STAGE-DISCHARGE CURVES indexes where wrong and I assigned an strong setting (option 1) for a 444 boundary that did not had enough information to produce a valid flow.

Finally in order to easily visual the error source the DEBUGGER = 1 key name is very useful to give you a hint as of the reason and location of the error.

I attach my files in case anybody is just starting with modelling and would like to use this type of boundary condition.

Greetings,
Chelo.

Thanks Chelo for sharing your feedback,

Just a reminder, when the geometry and boundary conditions files are OK, you can use a script to visualise the mesh + boundaries (even open boundaries) + numbers and codes, e.g. with the TELEMAC-2D confluence example:
plot.py mesh2d --bnd -b geo_confluence.cli geo_confluence.slf
or
plot.py mesh2d --liq-bnd -b geo_confluence.cli geo_confluence.slf

Use plot.py -h or plot.py mesh2d -h to see the help and other options.

Hope this helps,

Chi-Tuan