Transition from Metop-A/B to Metop-B/C AMVs

[ilianagenkova]

Winds from Metop-A will end in September 2021.
Current operational winds from Metop-B will be replaced by winds from Metop-B and C extracted by a new algorithm (GOES-R-like nested tracking). The new winds will be stored in the new BUFR sequence (3-10-077) and computed on AWS Cloud.
Initial sample data has been tested for formating issues, reading routines are updated, see issue#67.

Some gaps in the data feed were resolved, and 005/080 winds were added to the sample files.
Evaluation experiment for Metop-B/C winds has started (v16x_june_metop)

[ilianagenkova]

Code changes related to Metop-B/C winds will be folded with other minor changes into one PR

[ilianagenkova]

The PR mentioned in the comment above was canceled.
Code changes needed to :

• accommodate the use of Metop-B/C winds
• accommodate the use of Mitigated GOES winds and write out AMVQ flag in diag files
• fix big for the LeoGeo winds (CLAT-->CLATH, etc)
• fix 'station_id'
• use correct VIIRS OE profile

are now combined in one working copy:
/scratch1/NCEPDEV/da/Iliana.Genkova/git/global-workflow/develop.20201222_v161.AMVQ_MetopBC_etc

[ilianagenkova]

Two more experiments are running:
v16x_june_bits: assimilating only Metop-B winds, and aiming to illustrate the impact of losing Metop-A instrument
v16x_june_off: data denial, not assimilating any Metop winds, to justify the use of new Metop-B/C winds (from new BUFR and algorithm)

[ilianagenkova]

While some experiments need to be repeated, the code changes are going in.
Added provisional code for reading Himawari-8 winds from the new BUFR format. That code is untested but approved to go into the master, due to the very short time window we will have between getting sample data, testing it and seeing this data in operations.

[MichaelLueken]

Hi @ilianagenkova. It looks like the changes associated with this issue were merged to the authoritative repository at affe4ed through PR #294. Is it safe to close this issue?