-
Notifications
You must be signed in to change notification settings - Fork 298
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
Some bounds assertions aren't done when threading is on #811
Comments
Yes, it looks like to me that I should be able to remove the OMP idef's and it should work correctly. So we'll have to try it and make sure it does. |
…eading is on (Issue ESCOMP#811)
Removing the |
…eading is on (Issue ESCOMP#811)
…removing the bounds....
…eading is on (Issue ESCOMP#811)
…removing the bounds....
Bounds assertion for C isotopes when threading is on Previously, the bounds of c13 and c14 in subroutines TruncateCStates and TruncateCandNStates were not checked when threading was on. This PR allows us to handle c13 and c14 arrays like everything else in CTSM including (bounds checking). This PR resolves issue #811
Fixed by @negin513 in ctsm1.0.dev084 |
Bounds assertion for C isotopes when threading is on Previously, the bounds of c13 and c14 in subroutines TruncateCStates and TruncateCandNStates were not checked when threading was on. This PR allows us to handle c13 and c14 arrays like everything else in CTSM including (bounds checking). This PR resolves issue ESCOMP#811
In these two blocks of code:
CTSM/src/biogeochem/CNPrecisionControlMod.F90
Lines 438 to 447 in 1720bc7
CTSM/src/biogeochem/CNPrecisionControlMod.F90
Lines 525 to 534 in 1720bc7
the bounds of subroutine arguments are not being checked if threading is on. It looks like this came in in
clm4_5_9_r184
. Presumably that was needed at some point, but I hope we can remove this now: if this is needed, I think that would suggest a threading bug.@ekluzek I'm assigning this to you since you made
clm4_5_9_r184
, but it probably isn't high priority. The fix should be simple (removing the#ifdefs
) as long as it doesn't cause problems.The text was updated successfully, but these errors were encountered: