-
Notifications
You must be signed in to change notification settings - Fork 52
ufs/dev PR295 #604
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
ufs/dev PR295 #604
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving because you said there are fewer changes here but pointing them out just to double check, in FV3UFS NOAA-EMC/fv3atm #950 we have the following class of changes that aren't in this PR
get_tracer_index
->get_physics_tracer_index
integer, parameter :: physics_no_tracer = -99
Yes, I think that everything is good. FV3 and SCM now use different solutions for the get_tracer_index thing. The SCM has it defined in GFS_typedefs, but the FV3 uses the one from FMS (which the SCM doesn't use). |
The debug mode failure should be debugged at some point, but not here. It doesn't fail on any other platforms. |
Agreed, I was able to reproduce this error locally which will make it easier to debug. I'll track it down. |
Oh, good. I was not able to reproduce a failure locally. Which version of GNU were you able to reproduce with? I have 12.4 on my Mac. |
I'm using 12.2 on Derecho (by locally I meant off of Github lol). Using a debugger I found the specific place where the code is breaking due to NaNs, still working on why though. PR #607 has that branch. |
SOURCE: Dustin Swales NOAA-GSL
DESCRIPTION OF CHANGES:
SCM changes identical to FV3UFS NOAA-EMC/fv3atm #950.
ISSUE:
N/A
ASSOCIATED PRs: