Initial bottom differs from the geometry file

Hello,

I created a mesh and ran a telemac 2D case (v8p3r0 on mac; files attached). It turned out that the initial bottom elevation in the result file (r2d.slf) differed from that of the geometry file (new_bridge_no_dam_2yr.slf). The elevation difference isn’t large, but I am confused because I thought they should be identical (see the picture).

I was wondering if anyone has experienced this before. What could have been the causes?

[name removed]

t2d.cas (2.54 KB)
new_bridge_no_dam_saddle.cli (86.5 KB)
new_bridge_no_dam_2yr.slf (988 KB)

Somehow the website did not let me upload the result file and the screenshot…

But the attachment should be able to generate a result file within minutes. Apologies for so many posts.

This usually happens when you use the key “BOTTOM SMOTHING”.

1 Like

I see! Thanks!

Do you know if BOTTOM SMOOTHING also applies during the simulation (like every time step)?

I don’t really know.

But I suspect it’s some sort of an AMR according to a conditional check every few timesteps.

Please correct me if I’m wrong, I can look it up further.

From what I’ve tried, if your model doesn’t require a very sophisticated mesh resolution, like channel slopes or sudden drop on the depth there is no need for the mesh refinement.

Even if it needed, it’s better to try to refine the mesh first using stbtel and see if the results are convenient or severe hydrodynamic conditions requires this key active.

In this case of activating the keyword sensitivity analysis is even more critical, as the degree of refinement could change the results entirely.

Good luck with your study

[name removed]

1 Like

Your answer is in the user manual. CONFRON is called once.

1 Like