-
Notifications
You must be signed in to change notification settings - Fork 150
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
global_4denvar ctest seg faults in debug mode #777
Comments
@wx20jjung found the following
|
That's for debugging purposes and should be removed. |
Orion debug test
Line 2788 of
Add print statements to Below are values for this profile as a function of vertical level`
As a test check the value of
Rebuild in debug mode and rerun
The traceback indicates that the divide by zero occurs in the crtm library. I recall mention of a divide by zero issue in previous versions of the crtm. Does this error still remain in crtm/2.4.0.1? Will pause here and let @azadeh-gh and @emilyhcliu investigate. |
Hera test Emily's parallel is a C384L127 / C192L127 using Thompson microphysics. When gmi is present this case seg faults in debug mode as documented in issue #778. Rerun with gmi data removed. The debug
Line 2773 of |
Hera test (continued)
Rebuild debug @azadeh-gh and @emilyhcliu : If the above change is acceptable, we can create a branch, make the change, and open a PR. The PR can also remove line 1209 of |
@RussTreadon-NOAA Thanks so much for fixing this for us. @azadeh-gh will run a single cycle test to double-check how much the safeguard added would change the results |
Work for this issue will be done in RussTreadon-NOAA:feature/thompson_reff |
As reported in PR #743, the debug mode
gsi.x
aborts in ctest global_4denvar with the errorLine 1881 of
crtm_interface..f90
isLine 2773 is
NCO builds and runs codes in debug mode as part of their pre-implementation testing. As such the debug mode
gsi.x
failure must be examined, understood, and resolved. This issue is opened to document this error and work toward resolution of the problem.Attention: @azadeh-gh , @emilyhcliu , @CatherineThomas-NOAA
The text was updated successfully, but these errors were encountered: