Skip to content

Changes to add NOAA-21 and GOES-18 radiances in monitor mode #636

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.

Sign up for GitHub

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

Merged
RussTreadon-NOAA merged 4 commits into from
Oct 5, 2023
Merged

Changes to add NOAA-21 and GOES-18 radiances in monitor mode #636

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c360453
Changes to add NOAA-21 and GOES-18 radiances in monitor mode
ADCollard Oct 4, 2023
77188a3
Additional changes for CrIS N21
ADCollard Oct 4, 2023
66be004
Reinstate the exclamation point
ADCollard Oct 4, 2023
cf29fa1
Remove HIRS processing
ADCollard Oct 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion fix
Open in desktop
Submodule fix updated from 0a79d7 to f410c6
3 changes: 3 additions & 0 deletions scripts/exglobal_atmos_analysis.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -913,6 +913,7 @@ OBS_INPUT::
ahibufr ahi himawari8 ahi_himawari8 0.0 1 0
abibufr abi g16 abi_g16 0.0 1 0
abibufr abi g17 abi_g17 0.0 1 0
abibufr abi g18 abi_g18 0.0 1 0

@emilyhcliu emilyhcliu Oct 4, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will we assimilate ABI g18 clear-sky radiance?
Or, this is a place holder?

rapidscatbufr uv null uv 0.0 0 0
ompsnpbufr ompsnp npp ompsnp_npp 0.0 0 0
ompslpbufr ompslp npp ompslp_npp 0.0 0 0
Expand All @@ -926,6 +927,8 @@ OBS_INPUT::
sstviirs viirs-m j1 viirs-m_j1 0.0 4 0
ahibufr ahi himawari9 ahi_himawari9 0.0 1 0
sstviirs viirs-m j2 viirs-m_j2 0.0 4 0
atmsbufr21 atms n21 atms_n21 0.0 1 0
crisfsbufr21 cris-fsr n21 cris-fsr_n21 0.0 1 0

@emilyhcliu emilyhcliu Oct 4, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ATMS N21 will be assimilated and the CrIS N21 is a place holder, correct?

@emilyhcliu emilyhcliu Oct 4, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can not see the fix files from the github page. I believe that the use flag for ATMS N21 is set to 1, and the use flags for CrIS-fsr N21 and ABI-g18 are set to -1

I think we already made changes in abias and abias_pc for the three sensors in v16.3. implementation.

@RussTreadon-NOAA RussTreadon-NOAA Oct 4, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@emilyhcliu, I cloned ADCollard:release/gfsda.v16. A check of fix/global_satinfo.txt shows that the usage flags for atms_n21, cris-fsr_n21, and abi_g18 are -1 for all channels.

@ADCollard , the PR description indicates that we should see changes in fix/global_anavinfo.l127.txt. This file is identical between ADCollard:release/gfsda.v16 and NOAA-EMC:release/gfsda.v16.

Should we also see a difference between cris-fsr_n21 weights when comparing global_satinfo.txt from ADCollard:release/gfsda.v16 and NOAA-EMC:release/gfsda.v16?

@emilyhcliu emilyhcliu Oct 4, 2023 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @RussTreadon-NOAA
@ADCollard did mention that the purpose of this PR is to set CrIS N21, ATMS N21, and ABI G18 to monitoring mode in the description section of this PR.
So, the use flags for these three sensors should be -1 and they are set correctly in this PR.

@RussTreadon-NOAA RussTreadon-NOAA Oct 4, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, both current operations, gfs.v16.3.9, and this PR maintain all channels of atms_n21, cris-fsr_n21, and abi_g18 in monitor mode.

The only difference between ADCollard:release/gfsda.v16/fix and /lfs/h1/ops/prod/packages/gfs.v16.3.9/fix/fix_gsi is the addition of Rcov_crisn21 in ADCollard:release/gfsda.v16/fix

@ADCollard ADCollard Oct 4, 2023

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RussTreadon-NOAA @emilyhcliu Sorry, I was in a meeting. Yes, all three instruments need to be in monitor mode to facilitate bias correction spin-up.

@ADCollard ADCollard Oct 4, 2023

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ADCollard , the PR description indicates that we should see changes in fix/global_anavinfo.l127.txt. This file is identical between ADCollard:release/gfsda.v16 and NOAA-EMC:release/gfsda.v16.

Should we also see a difference between cris-fsr_n21 weights when comparing global_satinfo.txt from ADCollard:release/gfsda.v16 and NOAA-EMC:release/gfsda.v16?

@RussTreadon-NOAA If there are no changes for fix/global_anavinfo.l127.txt and fix/global_satinfo.txt, I must have made a mistake. Let me double-check. (My github/Gerrit skills need some work)

ompsnpbufr ompsnp n21 ompsnp_n21 0.0 0 0
ompstcbufr ompstc8 n21 ompstc8_n21 0.0 2 0
gomebufr gome metop-c gome_metop-c 0.0 2 0
Expand Down