open TELEMAC-MASCARET The mathematically superior suite of solvers

Hello,

I've been using the latest version of Blue Kenue to generate a Telemac2D mesh, making use of the new channel mesher and incorporating submeshes.

However, when I try to run the model (V5p9), I receive an error generated via the ELEBD subroutine:
"ERROR OF NUMBERING IN THE ELEMENT: ***** POSSIBLE REASON: THE BOUNDARY CONDITION FILE IS NOT RELEVANT TO THE GEOMETRY FILE".

Initially, I thought this might be a problem generating the boundary condition file through FUDAA but I have tried with other meshes and seems to work fine. On visual inspection of the mesh in Blue Kenue and FUDAA, there don't appear to be any obvious problems.

Does anyone have any ideas what the problem might be?

Thanks,

Enda

I'm not familiar with BlueKenue, but here some hints to verify if your boundary conditions file is relevant with your geometry file.

1- verify that boundary nodes number is equal to the number of lines in your BC file
2- If you are using different tools to generate your model, verify that you have the same numbering. This could be done easily by choosing randomly few nodes and see if they have the right coodinates, if they are really boundary nodes.
3- For Janet mesher, the numbering starts from 0, for Matisse, it begin from 1, for BlueKenue I don't know, try to verify!
4- If you are using fudaa, and if you can load your geometry file correctly, you can generate a BC file correctly, Janet do that also. So try to load your geometry file generated by blueKenue directly by fudaa, generate a BC file and use it in stead of the one generated by bluekenue.
Good luck
Riadh

Thanks Riadh.

The problem was that my mesh contained elements in channel areas (where I used .t3c meshes as submeshes) that overlapped on top of each other. Once I deleted the duplicate elements, it ran fine. Does anyone know if this could be a bug in the latest version of Blue Kenue?

On a related issue, does anyone have suggestions for the best method of changing/refining one area of a mesh in Blue Kenue, while keeping other areas identical to the original mesh (i.e. not just the same mesh size/density)?

Thanks in advance.

Enda

Hello,

OK, on my side I have increased the Fortran format for integers in ELEBD in next version, from I6 to I10, to avoid messages like:

"ERROR OF NUMBERING IN THE ELEMENT: *****
POSSIBLE REASON: THE BOUNDARY CONDITION FILE IS NOT RELEVANT TO THE GEOMETRY FILE".

With best regards,

Jean-Michel Hervouet

Thank you, Jean-Michel. Could you briefly explain how this change avoids the error message?

Hi
The Jean-Michel modification didn't avoid the error message. It just avoid the ***** in the message in order to gives you the number of the element that generates the error.
The ***** on a Fortran output indicated an oversize of the value in comparison to the output format.

Regards

Hi Enda,

Can you either post the t3m file here or send it to me at This email address is being protected from spambots. You need JavaScript enabled to view it. and I'll have a look at the "duplicate elements" problem.

Regarding your second question... In general the recommended approach is to separately create sub-meshes for areas where there may be special/different constraints and include these in a final mesh. The idea being that the whole meshing process is then fully parameterized and repeatable.

The next version of Blue Kenue does allow you to cut a hole in a mesh and then merge a submesh whose outline geometry is identical to the hole. This version is however still in development.
In addition, since this functionality breaks the philosophy of full parameterization/repeatability it should be used as a last resort.

Cheers... Martin

hello
I have a problem with overconstrained elements. I don´t know how fix it

Hello JHENNY,

Please create a new (separate) post and describe the issue that you have encountered and the steps that you have already tried in order to solve this issue. For example, have you read the Reference Manual? Searched for older telemac posts? included screen snapshots of what you have been able to do? etc. etc....

Kindly,
Alan