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 bugs in output files with rescaled heights #121

Merged
merged 2 commits into from
May 22, 2022

Conversation

Hallberg-NOAA
Copy link
Member

Fixed two minor bugs in the MOM6 output when run with Z_RESCALE_POWER not
equal to 0. All solutions are bitwise identical, but some of the diagnostic
output files have minor changes. With these corrections, several output files
are now unaltered by internal dimensional rescaling. The specific bug fixes
are:

  • Avoid using a rescaled depth as the vertical coordinate label in z-space
    output files. Only the coordinate label is impacted, but this bug fix avoids
    the chance of having silly values for this coordinate.

  • Rescale the depths back to mks units before taking their checksum for storage
    in the MOM_sum_output file. With this bug, the depth list file might be
    unnecessarily recreated with a new run with different scaling, but the file
    itself is fine.

  Fixed two minor bugs in the MOM6 output when run with Z_RESCALE_POWER not
equal to 0.  All solutions are bitwise identical, but some of the diagnostic
output files have minor changes.  With these corrections, several output files
are now unaltered by internal dimensional rescaling.  The specific bug fixes
are:

 - Avoid using a rescaled depth as the vertical coordinate label in z-space
   output files.  Only the coordinate label is impacted, but this bug fix avoids
   the chance of having silly values for this coordinate.

 - Rescale the depths back to mks units before taking their checksum for storage
   in the MOM_sum_output file.  With this bug, the depth list file might be
   unnecessarily recreated with a new run with different scaling, but the file
   itself is fine.
@codecov
Copy link

codecov bot commented May 3, 2022

Codecov Report

Merging #121 (7e71f92) into dev/gfdl (9292b58) will decrease coverage by 0.00%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##           dev/gfdl     #121      +/-   ##
============================================
- Coverage     33.52%   33.51%   -0.01%     
============================================
  Files           262      262              
  Lines         71175    71175              
  Branches      13284    13284              
============================================
- Hits          23861    23856       -5     
- Misses        42844    42847       +3     
- Partials       4470     4472       +2     
Impacted Files Coverage Δ
src/diagnostics/MOM_sum_output.F90 58.82% <0.00%> (ø)
src/framework/MOM_diag_remap.F90 79.54% <100.00%> (ø)
src/ALE/MOM_regridding.F90 23.00% <0.00%> (-0.54%) ⬇️

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 9292b58...7e71f92. Read the comment docs.

@Hallberg-NOAA Hallberg-NOAA added the bug Something isn't working label May 7, 2022
@marshallward
Copy link
Member

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

@marshallward marshallward merged commit 0b05686 into NOAA-GFDL:dev/gfdl May 22, 2022
@Hallberg-NOAA Hallberg-NOAA deleted the z_output_bugfix branch July 16, 2022 09:43
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