-
Notifications
You must be signed in to change notification settings - Fork 31
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
GDASApp EE2 compliance checklist for GFS v17 & v18 #1254
Comments
GDASApp PR #1221 resolved the FMS task. |
CRTMv3 should address task Use CRTM and CRTM-fix module instead of building and downloading fix files. |
GDASApp issue #1268 has been created to track the move from using a GDASapp built CRTM to using a pre-installed CRTM build via a module load. |
GDASApp issue #1269 has been created to track the addition of flags to optionally turn off the downloading of test data during the GDASApp build. |
I see in this PR: JCSDA-internal/ioda-converters#1548
I wonder if we can add this to our |
Thanks @CoryMartin-NOAA for spotting JCSDA-internal/ioda-converters#1548. Trying this in GDASApp is a good idea. Worse case is that it doesn't solve the copy -vs- link executable issue. Best case is that it does and we can check this item off the GDASApp EE2 compliance list. |
This issue is opened as a one-stop-shop to list GDASApp related EE2 compliance issues
$HOMEgfs/exec
- GDASApp issue #1302Separate issues and PRs will be opened to address the above tasks.
The text was updated successfully, but these errors were encountered: