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

Compute dz in the halo for OBC segments #520

Merged
merged 4 commits into from
Mar 9, 2024

Conversation

kshedstrom
Copy link

  • It was blowing up with "forrtl: error (65): floating invalid" when accessing dz in the halo at the boundary, but just sometimes. My default layout is trouble while my testing layout of 48 cores is not.

Copy link

codecov bot commented Nov 15, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 37.17%. Comparing base (714d2da) to head (486486d).

Additional details and impacted files
@@            Coverage Diff            @@
##           dev/gfdl     #520   +/-   ##
=========================================
  Coverage     37.16%   37.17%           
=========================================
  Files           271      271           
  Lines         80655    80657    +2     
  Branches      15046    15047    +1     
=========================================
+ Hits          29979    29981    +2     
  Misses        45102    45102           
  Partials       5574     5574           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@kshedstrom
Copy link
Author

This now takes care of #518

@kshedstrom
Copy link
Author

My Huynh diffs were not at the boundaries, but were definitely not everywhere. It would be worthwhile for someone to figure out why they occur. They show up in hour three of tracer fields with a DT_THERM of an hour, at the bottom.
Screen Shot 2023-11-16 at 10 25 16 AM

Good point about the pass_var. I just report what I was seeing in the debugger.

@theresa-morrison
Copy link

I did some additional testing of this PR by comparing runs of the Northwest Atlantic regional model with this version of MOM6 vs. the dev-gfdl version of MOM6. I found that for both this branch and dev/gfdl MOM6 the answers did not change when the default number of halo points (4) was increased to a "very wide halo" (12 points).

Further work may be needed to determine the halo/stencil size of different OBC options, but for now I think this PR is tested and can be approved.

Copy link

@theresa-morrison theresa-morrison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great job Kate!

Copy link
Member

@Hallberg-NOAA Hallberg-NOAA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for this PR, Kate, and thank you Theresa for investigating it carefully and reviewing it.

 - It was blowing up with "forrtl: error (65): floating invalid"
 when accessing dz in the halo at the boundary, but just sometimes.
 My default layout is trouble while my testing layout of 48 cores
 is not.
 -even for PPM advection and OBCs.
src/core/MOM.F90 Outdated Show resolved Hide resolved
Removed allocated tests for the potentially statically allocated arrays CS%uhtr and CS%vhtr in a newly added line testing whether there are OBCs in use that would require a halo update on these arrays.  Even in dynamic memory mode, these arrays are always being allocated, so these tests served no purpose, but in static memory mode they led to compile time errors.  All answers are bitwise identical.
@kshedstrom
Copy link
Author

You may delete the comment.

@marshallward
Copy link
Member

The regression suite is finally back online!

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

@marshallward marshallward merged commit 88e12a5 into NOAA-GFDL:dev/gfdl Mar 9, 2024
12 checks passed
@kshedstrom kshedstrom deleted the halo_for_dz branch November 3, 2024 23:19
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