open TELEMAC-MASCARET The mathematically superior suite of solvers

Ok.

When I ask if your steering file is in agreement with your boundary conditions file, I want to say that if you have boundary with 544 code, you have in your steering file "PRESCRIBED ELEVATIONS" and if you have 566 code, you also have "PRESCRIBED VELOCITIES" with as values as boundaries.

Maybe you can start with a simple configuration, by prescribing only H for instance. You'll add the other variables after.

Are the initial values you have in your result file the same as in your binary boundary data file ?

What is the temporal frequency of your HYCOM data ? daily ? Does your simulation last enough time to consider 2 HYCOM time steps ?

You can also read this topic: www.opentelemac.org/index.php/kunena/21-...y-boundary-data-file

I think you can't share your configuration..

Laurent

Thank you again for your answer Laurent !

I didn't have writen PRESCRIBED VELOCITIES nor ELEVATIONS in my steering file because I thought they would overwrite the values from the boundary file (I read this in the user_manual) but I tried with it now and it doesn't change the results. And I had a look at Luz's topic and at her files and she didn't activate these keywords... What do you think I should do ?

I am sorry, I realised I cannot read the T3DBND file (I was talking about the wrong file previously) so I can't check its values...

The initial values of my result file are different from the HYCOM data I have. (As I can't open my boundary data file I can't directly compare the values). Maybe I should set the INITIAL CONDITIONS as "PARTICULAR" and work on the CONDIM subroutine...?

You are right, my HYCOM data has a daily frequency. I am now trying to run the simulation during more than 1 day to consider 2 HYCOM steps (I wasn't doing it untill now).

Actualy, I can share the files I am working on (I selected another area, smaller, so my calculations are simplified).

Thank you again so much for your time !
Ophélie

I just looked at your binary boundary file and for your 3 time steps, every variables are 0 (U,V,T,S), except the elevations that seem to be correct.

So I advise you to investigate this file or the way you created it. It's a serafin file with 4 points by elements (not triangles). You can read it with Python or Matlab subroutines for example. BlueKenue can't read it.

Laurent

Ah... Thank you very much for your answer then ! I will have a look at this file with a subroutine.

Thank you so much for your help.
Ophélie

Maybe your issue comes from the coordinates of your mesh that seem not to be in lat/lon as they are in the HYCOM data file. So the script convertToBND.py can't find your boundary points within the HYCOM grid.

Laurent

Thank you for your advice !

I have tried to put my GEO file in lat-lon coordinates and also my GEO file and HYCOM file in spherical coordinates but the results in Telemac don't change.

I have tried to check the binary boundary data file with different Python commands and with Linux commands but I don't understand the outputs, I don't know which value correspond to Elevation or Velocity for example... Do you have a subroutine that writes clearly which value is associated with which variable to share ?

I got the value thanks to the convertHYCOM.py script (the variables values look okay when I look at them with BlueKenue).
Then I use the convertToBND.py script. Is there a way to get a serafin file with 3 points by elements or is it okay that it has 4 points by elements even if my mesh is composed with triangles ?

Thank you again very much for your help.
Ophélie

It's normal that your T3DBND file is 4 points by element, as it only represents the conditions along the maritime boundaries of your mesh. It's a vertical section along the boundary, so the elements are not triangles, as for your mesh too on the vertical.

If the file resulting from convertHYCOM.py is ok, it should come from convertToBND.py. You can directly investigate the issue during the execution of this script, or after the creation of the T3DBND file with the python parserSELAFIN, or matlab toolbox from T. Benson for example.
The format of the T3DBND file is also selafin, with a classical header and description of the variables. Just the connectivity table has a 4th dimension.

I hope it helps,
Laurent

Hello again,

Thank you very much for your explanation Laurent !

Now, I get a boundary binary data file with values that seem to be correct (attached here for the UTM test). And its values are the same as the ones in the T3DBND file.

However, I still can’t see the HYCOM influence on my result file…
I have tried with only elevation prescribed (544) and with both elevation prescribed (566) but there is no difference.
I have also tried in the different coordinate systems (UTM, Lat-Lon and spherical) with the GEO file and BND file in the same coordinate system each time. All my BND files (UTM, lat-lon and spherical) have the same values.
I don’t know what I can do now to make it work…
Do you have any other ideas ?

Thank you for your time,
Ophélie

Hi Ophélie !

It seems to work in v7p3r0. Which version are you using ?

Laurent

Yes it is working for me too now ! at least for the Elevation... I had forgotten to add the keyword "PRESCRIBED ELEVATION". (I am using the same version).

I am still working on adding velocities...

Thank you so much for your help Laurent.

Ophélie