-
Notifications
You must be signed in to change notification settings - Fork 28
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
Change to use CRTM 2.4 #530
Conversation
Automated Global-Workflow GDASApp Testing Results:
|
Automated Global-Workflow GDASApp Testing Results:
|
@CoryMartin-NOAA Does this mean we have already decided to switch to CRTM 2.4 even though this change would break the current ctests? |
Hera test Install g-w
The
The The |
Try the following as a test
This failed because I forgot that Execute Do we have a script to remap the distributed directory structure to the flat directory? |
@emilyhcliu The develop branch of UFO requires 2.4 to build. We have a few options here, none are ideal in my opinion
Thoughts? As @RussTreadon-NOAA showed we need 2.4 coefficients for 2.4. I forget how the JEDI fix directory was created... GSI had a script to stage the CRTM coefficients, right? |
With the splitting of our single GSI repo into several functional GSI repos it looks like the script to stage crtm fix files got lost ... at least I can't find it yet. Perhaps the fix file script resides with the NCEPLIBS crtm install scripts. |
Set
I advise against using my |
I'm perhaps wondering if we should instead stick to 2.3 a bit longer with the UFO feature/gdasapp branch so that things can continue to run as intended? |
As the title says!