Tidal modes twice bigger in the results, than in the forcing

Report or discuss software problems and other woes

Moderators: arango, robertson

Post Reply
Message
Author
User avatar
Eugen
Posts: 36
Joined: Wed Apr 06, 2016 4:36 pm
Location: University of Liege

Tidal modes twice bigger in the results, than in the forcing

#1 Unread post by Eugen »

Dear ROMS users,

For validation of tides at the domain of the North Sea, I decomposed SSH and U, V- velocity components from the results by using the pytides python tool.
Then I compared tidal amplitudes from the results at the points in the center of the domain with the amplitudes from the in-situ data, provided by the Flanders Institute (VLIZ), for three major modes (M2,S2 and N2).

And they happened to be twice bigger in ROMS, but the phases were OK.



The I compared the amplitudes spatially with the original TPXO Forcing file, and everywhere at the domain they are also twice bigger (!), except the place around the tidal node, because its location slightly differs from the original.



Then we reconstructed tidal ellipses out of u and v velocity components from ROMS results, and the major and minor axes and the inclination angle from the original forcing file, and compared them for the points at the center of the domain. And there is the same ratio of 2!




Why does it happen?

In the attachements, there are the header file and the .in file.
Attachments
north_sea_NESTING.in
(126.97 KiB) Downloaded 262 times
north_sea.h
(1.67 KiB) Downloaded 243 times
Evgeny Ivanov

PostDoc,
MAST, University of Liege, Belgium

Post Reply