-
Notifications
You must be signed in to change notification settings - Fork 162
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
Re-enable C48mx500_3DVarAOWCDA test #2438
Re-enable C48mx500_3DVarAOWCDA test #2438
Comments
Should fix [global-workflow/issues/2438](NOAA-EMC/global-workflow#2438 (comment))
This issue isn't resolved until the GDASapp hash has been updated in workflow |
I didn't mean to close it @WalterKolczynski-NOAA , sorry! We just merged a fix in the GDASApp. |
The GSI hash has been updated. We are now waiting on #2420 to update the GDAS app hash. Hopefully this will be done soon so we can get this test turned back on. |
The issue #2528 has been resolved enough to get past the first error. Now we have a new error that: |
Currently in COM for ice restarts I have:
whereas before we had:
I believe this is a change from #2510 @aerorahul should additional ice restart files needed for DA be copied to COM or should the DA jobs be looking for this data in another directory? |
It's a bug in the marine DA @JessicaMeixner-NOAA . We're inserting the analysis in the wrong restart when DO_IAU is switched on ... Oops. |
This PR turns the C48mx500_3DVarAOWCDA test back on. This required a few bugfixes in GDAS app which have now been merged. Resolves #2438 Resolves #2528 co-authors: @guillaumevernieres and @aerorahul who provided the bug fixes.
What new functionality do you need?
The C48mx500_3DVarAOWCDA had to be disabled as the ocean prep obs job was failing when some categories of obs were not present in dump. Once GDASApp has been updated, the submodule in workflow should be updated and the test turned back.
What are the requirements for the new functionality?
C48mx500_3DVarAOWCDA completes successfully.
Acceptance Criteria
Suggest a solution (optional)
No response
The text was updated successfully, but these errors were encountered: