Offline patch for sonde timeOffset#538
Merged
ShunLiu-NOAA merged 1 commit intoNOAA-EMC:developfrom Feb 18, 2026
Merged
Conversation
ShunLiu-NOAA
approved these changes
Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
In #496, it was shown that GSI applies special logic in
read_prepbufr.F90that overrides the twindow specified in the convinfo table for obs with balloon drift information. Essentially, GSI will attempt a fallback time (-3600s) if the original time falls outside the allowed window (5400s), and rejects the observation if the fallback still fails the new window check. This doesn't usually impact the 00/12z cycles since those are launch times. The impact from this change is usually noted in 01/13z cycles where the timeOffset can be -7500s (outside the -5400s time window) in which case, those obs gets snapped to -3600s.This PR adds this capability to change the timeOffset of the data via the
offline_ioda_patch.pyutility. Here is an example call to use this new function:There are hard coded kx values so it is technically safe to run on any ioda file and should only change types 120/220 timeOffsets, but it will add a new metaData variable called origtimeOffset.
Issue(s) addressed
Resolves/Results are documented in Issue #496
Checklist