-
Notifications
You must be signed in to change notification settings - Fork 245
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
Various bugs/problems found running MOM6 on raijin in Aus #198
Comments
|
Concerning MEKE: is the issue that the loops at L439, L446, L452 do not need to be wide since the is a halo update at L457? If reducing those loop ranges to the computational domain works under valgrind then I think the model solutions will be unchanged (because of the halo update). |
OK, I'll give that a try. Thanks |
Just realized that LmixScale is used at L465 in a wider loop so that needs to be calculated wide as you suggested earlier... |
Something like this... % git diff -U0 src/parameterizations/lateral/MOM_MEKE.F90
diff --git a/src/parameterizations/lateral/MOM_MEKE.F90 b/src/parameterizations/lateral/MOM_MEKE.F90
index 562c22f..0ff7360 100644
--- a/src/parameterizations/lateral/MOM_MEKE.F90
+++ b/src/parameterizations/lateral/MOM_MEKE.F90
@@ -439 +439 @@ subroutine step_forward_MEKE(MEKE, h, SN_u, SN_v, visc, dt, G, CS)
- do j=js-1,je+1 ; do i=is-1,ie+1
+ do j=js,je ; do i=is,ie
@@ -446 +446 @@ subroutine step_forward_MEKE(MEKE, h, SN_u, SN_v, visc, dt, G, CS)
- do j=js-1,je+1 ; do i=is-1,ie+1
+ do j=js,je ; do i=is,ie
@@ -452 +452 @@ subroutine step_forward_MEKE(MEKE, h, SN_u, SN_v, visc, dt, G, CS)
- do j=js-1,je+1 ; do i=is-1,ie+1
+ do j=js,je ; do i=is,ie
@@ -636 +636 @@ subroutine MEKE_lengthScales(CS, MEKE, G, SN_u, SN_v, &
- do j=js,je ; do i=is,ie
+ do j=js-1,je+1 ; do i=is-1,ie+1 |
When running OM4_025 on raijin: forrtl: error (63): output conversion error, unit -5, file Internal Formatted Write The same thing in the ocean: forrtl: error (63): output conversion error, unit -5, file Internal Formatted Write |
forrtl: error (73): floating divide by zero |
- In NOAA-GFDL/MOM6#198, @nicjhan reported problems running OM4_025 with intel compiler in debug mode. This fixes the "output conversion error, unit -5, file Internal Formatted Write: error mentioned in that issue for MOM. - No answer changes.
- In #198, @nicjhan reported problems running OM4_025 with intel compiler in debug mode. This fixes the "output conversion error, unit -5, file Internal Formatted Write: error mentioned in that issue for MOM. - No answer changes.
* Setup OBC segments for COBALT/OBGC tracers - These are updates required to setup OBC segments for OBGC tracers. - Since COBALT package has more than 50 tracers using the MOM6 table mechanism for setting up OBC segments is not feasible. Rather, this update delegates such setup to mechanims used in ocean_BGS tracers leaving MOM6 mechanism for native tracers intact. - Fixed issues caught by MOM6 githubCI * Add capability to change obc segment update period - COBALT tracers do not need as frequent segment bc updates and can use a larger update period to speed up the model. This commit introduces a new parameter DT_OBC_SEG_UPDATE_OBGC that can be adjusted for obc segment update period. - This commit applies the change only to BGC tracers but can easily be changed to apply for all. * Insert missing US%T_to_sec - The unit conversion factor was missing causing a crash in a newer test. * Updates from Andrew Ross - Avoid low initial values in the tracer reservoirs * Per Andrew Ross review * corrected indentation per review * Avoid using module vars per review request - Reviewer asked to avoid using module variables with "save" attributes. - This commit hides the module variables inside the existing OBC type. * Coding style corrections per review * Modification per review: do_not_log if .not.associated(CS%OBC) Co-authored-by: Robert Hallberg <[email protected]>
This is a bit of a catch-all issue for problems that I've noticed while running MOM6 on raijin in Aus. Also I'm able to run valgrind on the compute nodes there, this may reveal some issues which I'll post here.
The text was updated successfully, but these errors were encountered: