open TELEMAC-MASCARET The mathematically superior suite of solvers

Hi thanks for your answers.

I change what c.coulet say, to let as solid code 222. And it finally works ARTEMIS.

But if I let as a boundary condition "Closed Boundary (wall)" then the segment is not created. As a consequence, I can't define in fortran some parameters as reflexion, because there are no segments. That is why I tried to change the code in order to keep as a solid boundary (but now I see that the code was not appropiate). After that, the results seen in BlueKenue are not correct, everything stays in red.

Does somebody knows how to solve this? Which code should I put to define as a solid boundary? (The problem does not come from the geometry)

Thank you

Regards

Hello, this kind of error never occurred to me before. You say that this boundary file (222 instead of 400) does not work as expected?



Regards,
Costas

Hi, thanks for your answer.

Yes, in BlueKenue if I let a solid boundary as "Closed Boundary (wall)" in a segment, then appears a message that says that the segment will not be created. The messages says: WARNING: the boundary code of the ssegment is set to: Closed Boundary (wall),(222) This will effectively delete this segment. Continue? Yes/No.

After that, the segment is not created, it doesn't appear a "defining colour". And finally, if I want to define the paramenters in the fortran file I can't because the segment it has not been created.

That is why I tried to found another code that could substitute 222.

Although I don't know if my problem comes from here. After executing the files I sent you with ARTEMIS, I got as a result a red area, which is wrong. The exact message is: 60950 bad values found in object T01.

I guess that this problems are both related. If you could take a look I would really appreciate that.

Thanks

Regards

Hi again

I also notice that you let TETAP and ALFAP to 0 which is not logical as you model has different solid boundaries with a lot of orientation.

Hope this helps

Hi

Eugenia, you're mixing different things.
In the boundary file, all the boundary nodes are always described but in BK you just have to define the liquid boundaries.
In your case, as you have to recover the different boundaries to use the node numbering in the fortran file, so you prefer to give a name to the solid boundaries which could be done also in BK but you should take care to let the nodes with the right code which is 2 2 2 for solid boundaries...

Once your boundary file is ok, all other informations should be given in the fortran file or in the steering file.

Regards

Thank you very much.

I though I had to define ALL boundaries in BK, but I see I was wrong. Probably, I still get errors because some parameters had no sense, as you had said. I will keep solid boundaries as 222, and check my TETAP and ALFAP angles.

Thank you

Regards

Hi
Think to have a look in the examples (PORT_AUTO) in particular.
In the last version, there is an option for automatic calculation of angles...

Good luck

Regards