Welcome, Guest
Username: Password: Remember me

TOPIC: 2D binary boundary forcing

2D binary boundary forcing 7 months 3 weeks ago #44494

  • Xinjie Zhang
  • Xinjie Zhang's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 50
  • Thank you received: 2
Hi coulet
I'm sorry I didn't understand you earlier. After I regenerated geo.slf, the problem of INITIAL MASS OF WATER IN THE DOMAIN: 0 did not occur, but now a new problem appeared, as shown in the attached figure.I tried to change the advection scheme but it didn't work.Wish you can give me some help.
Kind regards
Xinjie
Attachments:
The administrator has disabled public write access.

2D binary boundary forcing 7 months 3 weeks ago #44497

  • Xinjie Zhang
  • Xinjie Zhang's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 50
  • Thank you received: 2
Hi all
After adjusting the SCHEME FOR ADVECTION OF VELOCITIES=1 and setting the time step and simulation time to be shorter, it can be seen that the elevation at the boundary is increasing with the progress of simulation.
What measures can I take to correct it? In attachment 3 are my steering file geo file cli file and bin file. Looking forward to someone to give me some help or advice!
Kind regard!
Xinjie
Attachments:
The administrator has disabled public write access.

2D binary boundary forcing 7 months 2 weeks ago #44510

  • pham
  • pham's Avatar
  • OFFLINE
  • Administrator
  • Posts: 1559
  • Thank you received: 602
Hello Xinjie,

I strongly recommend you to carefully read the TELEMAC-3D user manual before posting on this forum.

As David say, the feature already exists in TELEMAC-3D, you only need to apply what is written in the manuals. please see the dedicated section for keyword BINARY BOUNDARY DATA FILE (including the cautions, but first the name of the keyword!).
If you use BINARY DATA FILE 2, as written in the TELEMAC-3D user manual, "the user has to handle their reading within the FORTRAN FILE" and you have not done anything...

TELEMAC can only do what you write in the steering file and Fortran file...

Anyway, please also read the recommendations written in the TELEMAC-3D user manual and TELEMAC-3D reference manual for every keyword you fill in your steering file, it may prevent you from bad uses and strange results, e.g. I noticed:
- COEFFICIENT FOR HORIZONTAL DIFFUSION OF VELOCITIES = 0.0001 whereas you use k-epsilon,
- you use a Strickler law to model bottom friction. With this law, friction coefficient is quite low! It is the default value if you use Nikuradse law (which is the recommended law in TELEMAC-3D, as told in the recommendations appendix).

Hope this helps,

Chi-Tuan
The administrator has disabled public write access.
The following user(s) said Thank You: Xinjie Zhang

2D binary boundary forcing 7 months 2 weeks ago #44515

  • Xinjie Zhang
  • Xinjie Zhang's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 50
  • Thank you received: 2
Hello Chi-Tuan,
First of all, thanks for your reply!
I am sorry that I did not use the keyword correctly before, but I found this mistake yesterday and changed it into BINARY BOUNDARY DATA FILE. However, after that, I did not get a good result in the simulation.The simulation results show that the seawater in the simulated area loses rapidly during the simulation process, and the water layer becomes very thin, as shown in the attached figure.
As for the use of keywords, I will also deeply learn their correct meaning and usage in the future.
However, what frustrates me at this stage is that the coupling of ocean current model and telemac has not been implemented (onverter.py hycom2srf →converter.py generate_bnd →BINARY BOUNDARY DATA FILE). I suspect there's something wrong with my methods but I can't find another way.
Finally, thank you again for your reply.
Best regard
Xinjie
Attachments:
The administrator has disabled public write access.

2D binary boundary forcing 7 months 1 week ago #44560

  • pham
  • pham's Avatar
  • OFFLINE
  • Administrator
  • Posts: 1559
  • Thank you received: 602
Hello Xinjie,

When you are not sure of the results you get, it is advised to proceed step by step:
- first, try simpler options that are known to work correctly, e.g. modelling tide (or using a LIQUID BOUNDARIES FILE, or using only keywords) PRESCRIBED... If it works, you can move to the following step; but if it does not, you can try to investigate first this issue. You could try the 3 options,
- then try BINARY BOUNDARY DATA FILE with dummy values that may be reproduced with keywords or LIQUID BOUNDARIES FILE,
- then you can wonder if your input file is correctly generated but I cannot assist if it is a Python script issue.

Hope this helps,

Chi-Tuan
The administrator has disabled public write access.
The following user(s) said Thank You: Xinjie Zhang

2D binary boundary forcing 7 months 1 week ago #44568

  • Xinjie Zhang
  • Xinjie Zhang's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 50
  • Thank you received: 2
Hi Chi-Tuan
Thank you very much for your advice, I will follow the advice and try again.
Kind regard
Xinjie
The administrator has disabled public write access.
Moderators: pham

The open TELEMAC-MASCARET template for Joomla!2.5, the HTML 4 version.