-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MOM6 tidal momentum forcing #276
Comments
Yes, for the 025deg, the model can resolve tidal and internal wave dynamics. 1deg is too coarse to resolve internal tides explicitly, so it relies on parameterisations to represent the missing mixing associated with tides. |
I'm confused sorry. How are there tides in the 0.25deg config with |
My understanding is at this eddy-permitting resolution along with the topo, tides begin to appear natually without parameterisation. |
As discussed in today's OSIT catchup, we don't want explicit tides in any of our default global configs (although at 0.1° and higher some users may wish to switch it on). So we don't want tidal forcing. Instead, we need to parameterise the impact that the tide would have had. In OM2 we have vertical mixing and viscosity due to both barotropic and internal tides - see sec 3.2.6 in https://cosima.org.au/wp-content/uploads/2025/01/ACCESS-OM2-1-025-010deg-2025-01-24-7be8a1c.pdf |
see #176 (comment) |
Are we still missing the external input data for averaged tidal flow amplitudes ( |
I've obviously been away, but I don't think there's been any work on this since #176. |
ok, that will need to be fixed at some point |
Ta. I'll open an issue |
Closing as tidal forcing is now disabled in dev- branches :
|
Tidal momentum forcing (MOM6 parameter
TIDES
and associated parameters) has been disabled in our 0.25 deg configuration, but the changes were not carried across to our 1 deg configurations. Was this deliberate? @minghangli-uni, @aekiss?The text was updated successfully, but these errors were encountered: