Skip to content
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

Double counting kv_slow in MOM_vert_friction.F90 #941

Closed
Hallberg-NOAA opened this issue Jul 2, 2019 · 2 comments · Fixed by NCAR/MOM6#114
Closed

Double counting kv_slow in MOM_vert_friction.F90 #941

Hallberg-NOAA opened this issue Jul 2, 2019 · 2 comments · Fixed by NCAR/MOM6#114

Comments

@Hallberg-NOAA
Copy link
Collaborator

Hallberg-NOAA commented Jul 2, 2019

I believe that the contribution of visc%Kv_slow is being double counted at open boundaries by the code starting at about line 1196 of MOM_vert_friction.F90, and that visc%Kv_shear is being double counted in its contribution to a_cpl when visc%Kv_slow is associated. Simply setting Kv_add in this block of code instead of incrementing it should correct the problem, but doing so could change answers.

I do not believe that this code is in use by anyone at GFDL, but someone at NCAR, like @gustavo-marques, should perhaps look into what this might be doing in solutions that do use visc%Kv_slow.

@gustavo-marques
Copy link
Collaborator

gustavo-marques commented Jul 2, 2019

@Hallberg-NOAA, thanks for reporting this. You are correct, visc%Kv_slow is double-counted at open boundaries.

We set ADD_KV_SLOW=False since a fatal error that avoids the double-counting is issued when this option is used in conjunction with use_KPP = True. ADD_KV_SLOW was meant to be a temporary workaround to allow diffusivities due to slowly varying processes to be passed to the solver. Later in the development process, visc%Kv_slow was added into visc/%Kv_shear so that KPP could match the interior/surface diffusivities.

I believe we should remove this entire block of code (and corresponding code related to ADD_KV_SLOW). If we decide to go this way, I can make these changes on dev/ncar, make sure answers do not change and then obsolete ADD_KV_SLOW. We would still want visc%Kv_slow for diagnostics purposes.

@gustavo-marques
Copy link
Collaborator

Closed via #972

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants