-
Notifications
You must be signed in to change notification settings - Fork 163
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
Failures in GSI analysis due to inconsistent correlated error #2507
Comments
Removing the cris-fsr_n21 entry from the correlated_observations section of Another option is to leave the anavinfo file alone and move code around in
The For cris-fsr_n21,
GSI ctests were run using the modified |
To build g-w with the revised GSI source code, open a g-w PR to update the |
The |
The `gsi_enkf.fd` hash is updated to bring in revisions to GSI source code file `src/gsi/correlated_obsmod.F90`. The order in which set up checks are performed have been modified to allow `gsi.x` to successfully run retrospective GFS v17 cases with correlated error active. Resolves #2507
What is wrong?
Several users have experienced failures in the atmospheric analysis step:
This appears to be due to the inconsistency between the anavinfo file correlated error block and the satinfo. In the failed cases, the anavinfo file lists CrIS N21 while the historical satinfo files (set in config.anal) that were used did not. Many of the failed cases occurred for SDATEs in 2021.
See /scratch1/NCEPDEV/climate/Jessica.Meixner/cycling/turnonmarine/c48ci01/COMROOT/c48t01/logs/2021032418/failed.gdasanal.log.0
What should have happened?
The atmospheric analysis should have completed without failure.
What machines are impacted?
All or N/A
Steps to reproduce
Additional information
N/A
Do you have a proposed solution?
@ADCollard Do we need historical anavinfo files?
The text was updated successfully, but these errors were encountered: