Hello all,
Valuable answers from the experienced users Costas, Pierre-Louis and Tom.
Tracers and tidal flats is still an issue with TELEMAC-3D which may give bad results.
Anyway, you have changed some parameters since 1st sending:
- the FRICTION COEFFICIENT FOR THE BOTTOM for a Manning law was more realistic with a 0.04 value rather than 0.12 as Tom wrote,
- I would recommend to use OPTION FOR THE TREATMENT OF TIDAL FLATS = 1 rather than 2 (frozen values). I did not even know that it was possible to set this value with TREATMENT OF NEGATIVE DEPTHS = 2.
Before trying to optimise the options to decrease CPU time, I would suggest to investigate to avoid or decrease your issues.
Needing MAXIMUM NUMBER OF ITERATIONS FOR ADVECTION SCHEMES = 1500 and reaching this value seem to be the main issue. 1500 is quite big. Using a value greater than 200 is not so usual (only one test case in the examples database), and 200 is already quite big. It often means that you should decrease the time step...
Can you try to change the advection schemes for velocities + k-epsilon : with characteristics first, then try LIPS (SCHEME FOR ADVECTION OF... = 5 + SCHEME FOR ADVECTION OF... = 4) for velocities (and characteristics for k-epsilon).
Then try the same but with LIPS for tracers?
MAXIMUM NUMBER OF ITERATIONS FOR ADVECTION SCHEMES is used for schemes 13 and 14 only.
What about the boundary where you can see big velocities? Is it always wet or sometimes dry? What kind of boundary? Maritime? River? Shoreline?
Same question for your 2nd point: is it at the boundary or inside the computational domain?
Hope this helps,
Chi-Tuan
PS: The 3 keywords TREATMENT ON TIDAL FLATS FOR VELOCITIES/K-EPSILON/TRACERS should not be useful as only used with OPTION FOR THE TREATMENT OF TIDAL FLATS = 2 or ELEMENTS MASKED BY USER = YES, what is not recommended. You can delete these keywords from you steering file.