Welcome, Guest
Username: Password: Remember me

TOPIC: WIND RESULTS HAVE +180 DEG COMPARING THE INPUT

WIND RESULTS HAVE +180 DEG COMPARING THE INPUT 1 year 5 months ago #41566

  • josiastud
  • josiastud's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 132
  • Thank you received: 2
HI everybody,
as you can see the wind result (left Bleukenue) have +180 deg comparing to the input (right Libreoffice).

direction_problem.png


this is my meteo_telemac.f

I don't know / see the problem with/in the file, but I may have modified it due to my previous lack of understanding of wind direction input in t3d,... but I am pretty sure I restored the file I had previously copied, ... but I don't know, maybe I didn't do things right ...

thx the help

Josias
Attachments:
The administrator has disabled public write access.

WIND RESULTS HAVE +180 DEG COMPARING THE INPUT 1 year 5 months ago #41567

  • c.coulet
  • c.coulet's Avatar
  • OFFLINE
  • Moderator
  • Posts: 3630
  • Thank you received: 1010
Hi
Except if you program some specific change in meteo file (I didn't look into your fortran), the convention for wind in data file is direction of wind coming. then in the result when you look the wind vector, the direction is the opposite...
As it seems your data is a wind intensity and cap, this means you should adapt the fortran to take in account the fact the data doesn't follow the convention...
Hope this helps
Christophe
The administrator has disabled public write access.
The following user(s) said Thank You: josiastud

WIND RESULTS HAVE +180 DEG COMPARING THE INPUT 1 year 5 months ago #41568

  • NZrigat
  • NZrigat's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 65
  • Thank you received: 15
Hi Josias,

Wind data usually follows meteorological convention (zero means "coming from north"), whilst you can run your TOMAWAC simulation in Nautical (zero means "going towards north") or Trigonometric convention (zero means "going towards east"), so what you really want is to have the same convention for your data, fortran and steering file. Given that your wind data is in meteorological and BlueKenue follows Nautical (oceanographic) convention -I believe-, the 180 degrees difference can be explained.

Normally if I'm writing a winds file (selafin), I write the data in nautical (add 180 degrees to original data) then run the simulation in nautical as well. I just can't remember if this was the case using ASCII files, might be worth checking if meteo.f adds the 180 degrees but I don't think so.

p.s.
Trigonometric = 270 - Meteo
Nautical = 180 + Meteo

Hope this helps,
Nayef
The administrator has disabled public write access.
The following user(s) said Thank You: josiastud
Moderators: pham

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