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

(*)Add a halo update to fix VERTEX_SHEAR solutions #1221

Merged
merged 3 commits into from
Oct 15, 2020

Conversation

Hallberg-NOAA
Copy link
Collaborator

Added halo update for fluxes%p_surf_full when VERTEX_SHEAR=true. This field
is not used directly with the vertex shear code, but its halo regions are used
in the frazil code when the diabatic solver is using slightly wider halos to
work with the VERTEX_SHEAR option for shear mixing. Without this change, some
cases using VERTEX_SHEAR=True were not reproducing across PE layout, whereas now
they do. There is no flag to recover the old answers because the old answers
were ill-defined. All answers in the MOM6-examples test suite are bitwise
identical but there will be answer changes in some ice-ocean or coupled cases
with VERTEX_SHEAR=True; these cases should now reproduce across PE layouts.

This PR should help address MOM6 Issue #850.

  Added halo update for fluxes%p_surf_full when VERTEX_SHEAR=true.  This field
is not used directly with the vertex shear code, but its halo regions are used
in the frazil code when the diabatic solver is using slightly wider halos to
work with the VERTEX_SHEAR option for shear mixing.  Without this change, some
cases using VERTEX_SHEAR=True were not reproducing across PE layout, whereas now
they do.  There is no flag to recover the old answers because the old answers
were ill-defined.  All answers in the MOM6-examples test suite are bitwise
identical but there will be answer changes in some ice-ocean or coupled cases
with VERTEX_SHEAR=True; these cases should now reproduce across PE layouts.
@codecov-io
Copy link

codecov-io commented Oct 6, 2020

Codecov Report

Merging #1221 into dev/gfdl will increase coverage by 0.02%.
The diff coverage is 33.62%.

Impacted file tree graph

@@             Coverage Diff              @@
##           dev/gfdl    #1221      +/-   ##
============================================
+ Coverage     46.08%   46.10%   +0.02%     
============================================
  Files           214      224      +10     
  Lines         69399    70933    +1534     
============================================
+ Hits          31984    32706     +722     
- Misses        37415    38227     +812     
Impacted Files Coverage Δ
...g_src/external/GFDL_ocean_BGC/FMS_coupler_util.F90 0.00% <0.00%> (ø)
...fig_src/external/GFDL_ocean_BGC/generic_tracer.F90 0.00% <0.00%> (ø)
...c/external/GFDL_ocean_BGC/generic_tracer_utils.F90 0.00% <0.00%> (ø)
config_src/external/ODA_hooks/kdtree.f90 0.00% <0.00%> (ø)
config_src/external/ODA_hooks/ocean_da_core.F90 0.00% <0.00%> (ø)
config_src/external/ODA_hooks/ocean_da_types.F90 0.00% <0.00%> (ø)
config_src/external/ODA_hooks/write_ocean_obs.F90 0.00% <0.00%> (ø)
config_src/solo_driver/MESO_surface_forcing.F90 0.00% <0.00%> (ø)
config_src/solo_driver/user_surface_forcing.F90 0.00% <0.00%> (ø)
src/ALE/MOM_regridding.F90 31.47% <0.00%> (-0.17%) ⬇️
... and 217 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 48da975...921e7de. Read the comment docs.

@marshallward
Copy link
Collaborator

marshallward commented Oct 15, 2020

https://gitlab.gfdl.noaa.gov/ogrp/MOM6/-/pipelines/11388 🟡 ✔️

Note: parameters out of date due to pr/1217; This PR does not affect parameters so the parameters will be updated after this merge.

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 this pull request may close these issues.

4 participants