The Tomorrow.io TMS converter #1587
Conversation
|
@rhoneyager-tomorrow this should be able to be closed, as I've transferred this to an internal PR will this support the L1-TBR as well |
|
This PR targets V00-07 of the L1B-TB product (last week's release). The resampled 1B product (L1B-TBR) is not covered by this PR, as it's under a month old. Will likely address this separately in December. After every release we do reprocess older data to ensure a consistent product, and a few changes to the file structure were made in the past month based on feedback from older versions. Your TROPICS-based converter (#1588) isn't affected this time. The main difference between the L1B-TB and -TBR files is that in -TBR the brightness temperatures are resampled to the ch. 11 geolocation (boresight center). The channel geolocations are very close and typically agree to within 1-3 km. This means that either product is usable in JEDI. Here's an example subset of a Tomorrow-S2 scan pattern over the UK: 
Note that neither product resamples to a common field of view. I don't recall if the FOV differences are handled in the JEDI-CRTM interface, but it would be nice. |
|
Closing in favor of #1590. Would be nice if the CI supported this use case. https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/approving-workflow-runs-from-public-forks |
2 participants
Description
This PR adds the ability to convert data from the Tomorrow.io Microwave Sounder (TMS) L1B data product into IODA format. TMS is a 12-channel microwave sounder with heritage from the NASA TROPICS (Time-Resolved Observations of Precipitation structure and storm Intensity with a Constellation of Smallsats) instruments. The first two TMS satellites have launched, and many more are expected through 2025.
This code provides an example of how to use the IODA C++ API to write a converter.
While the code is designed for Tomorrow's instrument, it is also fully capable of converting the latest TROPICS L1B file format (V05-02).
Issue addressed
This lets @BenjaminRuston run some experiments with TMS data. USAF asked if I could pass along this converter to enable downstream use.
This may just resolve #1585, and it also offers an alternate path to fix #1574.
Dependencies
None
Downstream impact
JEDI can run with TMS!
Reviewing
I've got a set of diagnostic plots showing that the converter works as expected. Let me know where I should send this for review. The same goes for the L1B product documentation.
Ex. of using eva to plot a few granules for the W band channel:
The code has notes about recommended IODA updates. Perhaps @srherbener can take a look.
The ioda validation YAML will also need an update, as I have suggested several new MetaData variables. Thoughts on the naming scheme, or on any other part of this PR are quite welcome.