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

GFSv16.3.9 - temporary satingest changes for NOAA-21 #1852

Merged
merged 9 commits into from
Sep 12, 2023

Conversation

KateFriedman-NOAA
Copy link
Member

Description

The PR merges the GFSv16.3.9 release branch into the dev/gfs.v16 branch upon implementation of this version into operations on Monday September 11th during the 12z cycle. This implemented version turned off NOAA-21 ingest temporarily ahead of the next upgrade to the GFS (see issue #1356). This upgrade also includes a fix for the tropcy build.

Resolves #1813

Type of change

Production update

Change characteristics

  • Is this a breaking change (a change in existing functionality)? NO
  • Does this change require a documentation update? YES (will happen in develop branch)

How has this been tested?

Tested in para by NCO ahead of implementation. Also tested by EMC before hand-off to NCO.

Checklist

  • Any dependent changes have been merged and published
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • New and existing tests pass with my changes
  • I have made corresponding changes to the documentation if necessary

KateFriedman-NOAA and others added 9 commits May 16, 2023 14:54
- update gfs version to v16.3.8
- update obsproc version to v1.2.0

Refs #1356
- Further edits to release notes to come.

Refs #1356
A temporary fix to allow the satingest changes to be implemented on August 29 without causing GSI to crash. Issue with the CRTM means that GSI will crash unless NOAA-21 radiances are switched off.

Obsproc version numbers should remain unchanged unless the obsproc changes are implemented before or at the same time as the satingest changes.
Update release notes to mention compilation error fix for gfs_bufr code. Resolves NCO bugzilla #1208.
For some reason the sorc/build_tropcy_NEMS.sh no longer works on WCOSS2 machines.   @RussTreadon-NOAA and @aerorahul found fixes that allow the build to complete.  This PR implements one of these fixes - removing the references to the NEMSIOGFS module, which is being loaded but does not have a version number attached.

Six executables result from this build as expected.   They should still be tested for functionality.

This references #1812.
- Rename the release notes to reflect updated version number
- Update version to v16.3.9 within release notes

Refs #1813
…6.3.9

Merge in updates from GFSv16.3.8 ARFC.

* origin/dev/gfs.v16:
  GFSv16.3.8 - add debug flag to resolve wave post runtimes (#1849)
Sync merge and update version for v16.3.9
@KateFriedman-NOAA KateFriedman-NOAA merged commit d9fe8a1 into dev/gfs.v16 Sep 12, 2023
1 check failed
@KateFriedman-NOAA KateFriedman-NOAA deleted the release/gfs.v16.3.9 branch September 12, 2023 16:05
WalterKolczynski-NOAA pushed a commit that referenced this pull request Sep 14, 2023
…1858)

GFS v16.3.9 was implemented 20230911 12Z.  The following changes were implemented into
operations:
- turns off ingest of NOAA-21 radiances into the GSI,
-  PlanetIQ GPSRO and NOAA-20 OMPS (Ozone Mapping and Profiler Suite) Ozone retrievals
will be actively assimilated,
-  OMPS observation errors will be adjusted.

g-w PR #1852 brought these changes into g-w branch [`dev/gfs.v16`](https://github.com/NOAA-EMC/global-workflow/tree/dev/gfs.v16).
This PR brings the same changes into g-w `develop`.

Fixes #1856
Fixes #1857

Related to, but not dependent on, GSI [#621](NOAA-EMC/GSI#621)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
production update Processing update in production
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants