Regarding the option TIDENAME

[aakashsane]

Hi,

I am a new user and I am confused about one option in the ocean.in file.
If I have to specify tidal forcing, should I specify it under
FRCNAME = ...... by switching off the options SSH_TIDES, UV_TIDES and RAMP_TIDES

OR switch on the options SSH_TIDES, UV_TIDES and RAMP_TIDES
and specify the tidal forcing file in the option ' TIDENAME '?

Best,
Aakash

[kate]

OR switch on the options SSH_TIDES, UV_TIDES and RAMP_TIDES
and specify the tidal forcing file in the option ' TIDENAME '?

Yes, this. Though I don't bother with RAMP_TIDES.

[wilkin]

There was a change made in July 2017 to remove tide forcing from the regular list of forcing files given in FRCNAME.

Here is the ticket:
https://www.myroms.org/projects/src/ticket/736

This was to facilitate using the same list of meteorological forcing files for every nest in nesting downscaling applications without repeating the whole list for each grid as was required previously. In such a situation only the parent grid needs tides, so logically the lists are not the same.

Note that the river source file was previously removed from the FRCNAME list for similar reasons.

[aakashsane]

Great, that clears things up.

Thanks!

-Aakash

[m.hadfield]

Though I don't bother with RAMP_TIDES.

An aside: If you have shallow water in your domain and wetting and drying is not enabled, RAMP_TIDES can be useful to avoid transients that drop the water level below the bathymetry, hence crashing the model.

[kate]

OK, interesting. It won't help with that storm surge two years into a run which caused things to blow up (and me to turn on WET_DRY).

[johnluick]

For some reason I was under the impression that RAMP_TIDES had been effectively hardwired in a few years back. From what you (Mark) are saying, I was wrong about that.

[m.hadfield]

See

https://www.myroms.org/svn/src/trunk/RO ... et_tides.F

and search for "ramp"

[johnluick]

Thanks, Mark! I see that ramp is still there.