Skip to content
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

GSI code fix to handle the new in situ (ships) bufr subsets in nsstbufr observation data file #208

Closed
XuLi-NOAA opened this issue Sep 14, 2021 · 1 comment · Fixed by #209
Assignees

Comments

@XuLi-NOAA
Copy link
Contributor

XuLi-NOAA commented Sep 14, 2021

A ObsProc upgrade was implemented at 2021180600 GFS cycle. This introduced three new ships data, NC001013, NC001101 and NC001113, into sfcshp and therefore nsstbufr data file. The GSI code can handle the known (by GSI decoder) subsets correctly, but not for the unknown (new) subsets. The code, read_nsstbfr.f90, needs to be modified to handle the new subsets. Otherwise, as shown in GFS production, the NSST analysis can be degraded since some bad (not the true observation) data can be assimilated. The significant impact occurred over North Sea area (by UK), the foundation temperature becomes too cold by up to 6+ degree after about one week of the OpsProc upgrade implementation.

The modification of read_nsstbufr.f90 is straightforward, just add those three subsets.

The cycling run, starting from 2021083118, with the operational version of GFS, v16.1.2.1, at C768, is running. From the 12 cycles already done, it shows the too cold Tf analysis over North Sea is getting warmer, it may take about one week cycling run to become normal.

@MichaelLueken
Copy link
Contributor

These changes were merged to release/gfsda.v16.1.3 at 972d545. Closing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants