-
Notifications
You must be signed in to change notification settings - Fork 62
[rrfs-nco] change exec names to meet EE2 requirements #1303
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
base: rrfs-nco
Are you sure you want to change the base?
Conversation
|
These are executables I could not find in any of the scripts/, ush/, or job/ directories, but I may have missed them elsewhere. |
|
Thank you for this @JiliDong-NOAA. So I do not have to pull this branch and build everything, would it possible for you to list the contents of the executable directory that would be associated with this PR? |
Sure. The exec directory has: |
JamesPolly-NCO
left a comment
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.
The new executable names match up with sorc subdirectories as requested. Thank you for doing this @JiliDong-NOAA 👍
|
Are these executables used with the latest blending code? rrfs_util_fv3lam_pre_blending_tq.exe |
I tracked the hash history of rrfs_util. The current hash includes the updates from my PR #1189. Therefore, these executables contain the latest blending code. |
DESCRIPTION OF CHANGES:
The compiling is successful after the changes to app_build.sh but the full workflow has not been fully tested.
TESTS CONDUCTED:
Machines/Platforms:
Test cases:
ISSUE:
CONTRIBUTORS (optional):