Add GSI fix files changes for v16.3

[emilyhcliu]

A GSI fix branch has been created to collect any changes for v16.3
The name of the branch is called: fix_v16.3
Please update GSI master in your fork and check out fix_v16.3 under fix directory

[MichaelLueken]

@emilyhcliu Are these modifications ready to be committed to the authoritative repository? Want to make sure before I move forward with these changes.

[ADCollard]

Changed use flag from -1 to 1 for Meteosat-9 AMVs (satid = 9) in global_convinfo.txt

[HaixiaLiu-NOAA]

Modified global_ozinfo.txt: adjusted obs errors and gross errors for the top 5 layer OMPSNP data. Add entry for ompslp_n21

[HaixiaLiu-NOAA]

@emilyhcliu how do you want to take care of the iuse change associated with Meteosat 8/9 switch on 6/1/2022? Should I create a new global_satinfo.txt file in the directory gfsv16_historical?

[emilyhcliu]

Set AVHRR MetOp-C AMV to 1 (244, 5, 1)
We begin to receive new format of B and C from March
The old format will continue until June
So, we will have both formats from March to June

The new format requires code changes and they are in develop already

AVHRR B and C will be in v16.3

There is no way to add the switch of AB to BC since NCO does not allow code change.

[emilyhcliu]

@emilyhcliu Are these modifications ready to be committed to the authoritative repository? Want to make sure before I move forward with these changes.

@MichaelLueken-NOAA Yes, these changes will go into the authoritative repository

[emilyhcliu]

@emilyhcliu how do you want to take care of the iuse change associated with Meteosat 8/9 switch on 6/1/2022? Should I create a new global_satinfo.txt file in the directory gfsv16_historical?

@HaixiaLiu-NOAA Will the switch of Meteosat8/9 definitely occur on 6/1/2022?

[ADCollard]

@emilyhcliu how do you want to take care of the iuse change associated with Meteosat 8/9 switch on 6/1/2022? Should I create a new global_satinfo.txt file in the directory gfsv16_historical?

@HaixiaLiu-NOAA Will the switch of Meteosat8/9 definitely occur on 6/1/2022?

@HaixiaLiu-NOAA @emilyhcliu There should be no need to worry about historical fix for Meteosat 8/9 AMVs as both are set to +1. The GSI will process whichever is in the dump file, so this is transparent to GSI once M9 is set to +1.

[emilyhcliu]

@emilyhcliu how do you want to take care of the iuse change associated with Meteosat 8/9 switch on 6/1/2022? Should I create a new global_satinfo.txt file in the directory gfsv16_historical?

@HaixiaLiu-NOAA Will the switch of Meteosat8/9 definitely occur on 6/1/2022?

@HaixiaLiu-NOAA @emilyhcliu There should be no need to worry about historical fix for Meteosat 8/9 AMVs as both are set to +1. The GSI will process whichever is in the dump file, so this is transparent to GSI once M9 is set to +1.

@ADCollard @HaixiaLiu-NOAA is thinking about the Meteosat8/9 switch for radiances.

[emilyhcliu]

@HaixiaLiu-NOAA @ADCollard
MeteoSat-9 is becoming operational satellite on June 1, 2022.
And, if the operational data stream (dump) will only contain data from operational satellite, then we can set the use flag to 1 for both MeteoSat-8 and MeteoSat-9 in the satinfo file. GSI will process whichever is in the dump file (just like Andrew pointed out).
This should also be the case for Himawari-8 and Himawari-9 CSR data.
Does this make sense to you?

@haixia, the seviri_m09 is not ready for radmon. Please open an PR to add that in.

[HaixiaLiu-NOAA]

@emilyhcliu @ADCollard I am not sure if CSR dumps generated in a similar way to the AMV dumps (i.e., only data from primary satellite are tanked and dumped). We need to ask Jeff and Iliana about this.

I will open a PR to add seviri_m09 into the radmon

[HaixiaLiu-NOAA]

The PR to add seviri_m09 into the RadMon has been opened. Please review it @emilyhcliu.

[emilyhcliu]

The PR to add seviri_m09 into the RadMon has been opened. Please review it @emilyhcliu.
@HaixiaLiu-NOAA thanks! Reviewed and approved!

[emilyhcliu]

@HaixiaLiu-NOAA @ADCollard MeteoSat-9 is becoming operational satellite on June 1, 2022. And, if the operational data stream (dump) will only contain data from operational satellite, then we can set the use flag to 1 for both MeteoSat-8 and MeteoSat-9 in the satinfo file. GSI will process whichever is in the dump file (just like Andrew pointed out). This should also be the case for Himawari-8 and Himawari-9 CSR data. Does this make sense to you?

@haixia, the seviri_m09 is not ready for radmon. Please open an PR to add that in.

@HaixiaLiu-NOAA @ADCollard Am I correct that we should set the use flag to 1 for both Himarari-8 and Himarari-9 in satinfo file? The same fot MeteoSat-8 and MeteoSat-9. Any thoughts?

[HaixiaLiu-NOAA]

@emilyhcliu I do not know if it is true that the CSR dumps will have similar situation as AMV for Meteosat 8/9 and Himawari8/9 (i.e. only data from primary satellite are in the operational tanks/dumps) I will send an email to Jeff/Iliana to check on that. Or could we wait till 6/1/2022 to check the operational CSR dumps to see if it is the case? When do you want to start the para for v16.3?

[emilyhcliu]

@HaixiaLiu-NOAA Ok, thanks for your explanation. Please go ahead and ask the question to Jeff/Iliana.
If we can not get a confirmed answer from them, we will just keep the use flag to -1 for Himawari-9 and MeteoSat-9 We can change it later.

[HaixiaLiu-NOAA]

@emilyhcliu we will need to keep iuse=-1 for Meteosat-9 and Himawari9 before the data in operational dump (6/1/2022 for Meteosat-09 and to be determined for Himawari-9) due to the bias correction spinup required to correctly use the CSR data from both instruments.

[MichaelLueken]

@emilyhcliu @ADCollard @HaixiaLiu-NOAA Are there any more changes to the fix files for GFS v16.3, or will I be able to update the fix files to use fix_v16.3 tomorrow after merging in @ADCollard PR #374?

[emilyhcliu]

@MichaelLueken-NOAA Changes for fix_v16.3 are all in place now. I will work with developers to make sure changes will be all in by the end of today. So, yes, please go ahead to update the fix after merging in Andrew's PR tomorrow.

[MichaelLueken]

The fix files changes in fix/fix_v16.3 have been merged to fix/rev2 and updated in the authoritative repository at eb220ca. Will keep this issue open until all potential fix file changes have been applied.

[emilyhcliu]

@MichaelLueken-NOAA Thanks. Yes, Keep this issue open for the v16.3 release branch.