-
Notifications
You must be signed in to change notification settings - Fork 111
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
Improve error handling in the orog code #909
Labels
bug
Something isn't working
Comments
As a test, I commented out the copy of the gmted2010 data to the working directory in
This should result in an error. Running the regression tests showed the open of this file failed, the error handler was called, but processing continued. The 'oro' files contained zeroes for the terrain height.
|
GeorgeGayno-NOAA
pushed a commit
to GeorgeGayno-NOAA/UFS_UTILS
that referenced
this issue
Mar 12, 2024
Prepend 'FATAL ERROR' to the error message as required by NCO. Fixes ufs-community#909.
Rerunning the above test with the fix at 33a8df2 shows the program stops, as it should:
|
GeorgeGayno-NOAA
pushed a commit
to GeorgeGayno-NOAA/UFS_UTILS
that referenced
this issue
Mar 12, 2024
GeorgeGayno-NOAA
pushed a commit
to GeorgeGayno-NOAA/UFS_UTILS
that referenced
this issue
Mar 13, 2024
GeorgeGayno-NOAA
pushed a commit
to GeorgeGayno-NOAA/UFS_UTILS
that referenced
this issue
Mar 13, 2024
5 tasks
GeorgeGayno-NOAA
pushed a commit
to GeorgeGayno-NOAA/UFS_UTILS
that referenced
this issue
Mar 19, 2024
GeorgeGayno-NOAA
added a commit
to GeorgeGayno-NOAA/UFS_UTILS
that referenced
this issue
Mar 20, 2024
GeorgeGayno-NOAA
added a commit
to GeorgeGayno-NOAA/UFS_UTILS
that referenced
this issue
Mar 22, 2024
GeorgeGayno-NOAA
added a commit
that referenced
this issue
Mar 22, 2024
Update the netcdf_error routine to stop processing if an error occurs. Update error messages to comply with NCO requirements. Cleanup/fix the error handling for the read of the RAMP data. If read of RAMP data fails, stop program execution. Fixes #909.
BinLiu-NOAA
pushed a commit
to hafs-community/UFS_UTILS
that referenced
this issue
Jul 10, 2024
Update the netcdf_error routine to stop processing if an error occurs. Update error messages to comply with NCO requirements. Cleanup/fix the error handling for the read of the RAMP data. If read of RAMP data fails, stop program execution. Fixes ufs-community#909.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The orog code has a routine that checks for NetCDF i/o errors. However, it does not stop processing if an error is detected - it just prints the error to the log file.
I suspect that programmers have been calling this routine with the expectation that the program will stop if there is an error.
The text was updated successfully, but these errors were encountered: