-
Notifications
You must be signed in to change notification settings - Fork 168
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
Move GDASApp to CRTM 2.4 #1773
Move GDASApp to CRTM 2.4 #1773
Conversation
This hasn't been tested yet. I will do so and give the thumbs up once everything works as intended. |
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.
No issues with this.
A couple of requests.
Ok this is ready, it builds and GDASApp tests that use the workflow are working as intended. |
I will update the GDASApp hash once NOAA-EMC/GDASApp#550 is merged |
@CoryMartin-NOAA Would you please merge develop to feature/stable-nightly in GDASApp and update the commit hash to include recent updates from https://github.com/JCSDA-internal/fv3-jedi/pull/980. Thanks. |
@CoryMartin-NOAA I just checked the current commit hash |
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Automated global-workflow Testing Results:
|
Description
This PR moves the GDASApp to CRTM 2.4. It also removes the need for the global-workflow team to maintain CRTM coefficients in their fix space, instead we should be linking/copying them from wherever the CRTM coefficients are stored (like the way GSI does it). For now, that is an 'unofficial' location, but will eventually be the 'official' one.
Type of change
How Has This Been Tested?
Checklist