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

(*)Fix a bug with BULKMIXEDLAYER & ML_MIX_FIRST>0 #329

Merged
merged 3 commits into from
Mar 3, 2023

Conversation

Hallberg-NOAA
Copy link
Member

Restored an else that was inadvertently deleted as a part of code clean up in MOM-ocean/MOM6 PR mom-ocean#1127 on June 5, 2020. This bug causes bulkmixedlayer to be called twice (with cumulative effects) when 0. < ML_MIX_FIRST < 1., and not to be called at all when ML_MIX_FIRST = 1. This bug only applies to cases where the bulk mixed layer is enabled by setting BULKMIXEDLAYER=True and USE_REGRIDDING=False (i.e., in layered mode configurations with active thermodynamics), however because the default value of ML_MIX_FIRST = 0, this bug does not appear to be used in any active test cases, and it went undetected when it was introduced. All answers in the MOM6-examples test suite are bitwise identical, but this could change answers in some cases.

  Restored an else that was inadvertently deleted as a part of code clean up in
MOM-ocean/MOM6 PR mom-ocean#1127 on June 5, 2020.  This bug causes bulkmixedlayer to be
called twice (with cumulative effects) when 0. < ML_MIX_FIRST < 1., and not to
be called at all when ML_MIX_FIRST = 1.  This bug only applies to cases where
the bulk mixed layer is enabled by setting BULKMIXEDLAYER=True and
USE_REGRIDDING=False (i.e., in layered mode configurations with active
thermodynamics), however because the default value of ML_MIX_FIRST = 0, this bug
does not appear to be used in any active test cases, and it went undetected when
it was introduced.  All answers in the MOM6-examples test suite are bitwise
identical, but this could change answers in some cases.
@Hallberg-NOAA Hallberg-NOAA added the bug Something isn't working label Feb 24, 2023
@codecov
Copy link

codecov bot commented Feb 24, 2023

Codecov Report

Merging #329 (e947e08) into dev/gfdl (7af22d6) will increase coverage by 0.00%.
The diff coverage is n/a.

❗ Current head e947e08 differs from pull request most recent head 49de830. Consider uploading reports for the commit 49de830 to get more accurate results

@@            Coverage Diff            @@
##           dev/gfdl     #329   +/-   ##
=========================================
  Coverage     37.15%   37.16%           
=========================================
  Files           265      265           
  Lines         74508    74508           
  Branches      13839    13839           
=========================================
+ Hits          27687    27689    +2     
+ Misses        41727    41725    -2     
  Partials       5094     5094           
Impacted Files Coverage Δ
...parameterizations/vertical/MOM_diabatic_driver.F90 46.31% <ø> (ø)
src/framework/MOM_document.F90 72.92% <0.00%> (+0.43%) ⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@marshallward
Copy link
Member

marshallward commented Mar 3, 2023

Gaea regression: https://gitlab.gfdl.noaa.gov/ogrp/MOM6/-/pipelines/18436 ✔️

@marshallward marshallward merged commit 348d7b7 into NOAA-GFDL:dev/gfdl Mar 3, 2023
@Hallberg-NOAA Hallberg-NOAA deleted the fix_ML_mix_first_bug branch May 10, 2024 22:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants