Enhance MET's regrid dictionary to add reinterpolation methods using point2grid #2658
Open
5 of 21 tasks
Labels
alert: NEED ACCOUNT KEY
Need to assign an account key to this issue
alert: NEED CYCLE ASSIGNMENT
Need to assign to a release development cycle
alert: NEED MORE DEFINITION
Not yet actionable, additional definition required
MET: Library Code
priority: high
High Priority
requestor: NOAA/EMC
NOAA Environmental Modeling Center
type: new feature
Make it do something new
Milestone
Describe the New Feature
ADDED CONTEXT: In conjunction with #2859, this issue seeks out a path to ingest tripolar projection datasets through MET. In particular, this issue deals with verifying tripolar projected datasets (such as RTOFS) on a polar stereographic projection (or any other supported projection) using interpolation methods. Currently MET is unable to process a tripolar projection that is not CF-compliant; CF-compliant netCDF files can utilize the point2grid tool to achieve interpolation.
On investigation, the CICE dataset (and other NOAA tripolar datasets) are not CF-compliant and will require additional methods added to point2grid for interpolation (which is being enhanced via #2857).
The work on this issue would expand the interpolation access from point2grid to the
regrid
dictionary available in grid-to-grid verification tools including Grid-Stat and MODE. This will require a call to the point2grid logic in theregrid
dictionary that can properly assess an input forecast file and determine if it is one of the supported tripolar formats. If it is, theregrid
dictionary will employ the proper logic to interpolate the tripolar grid into the desired projection.ORIGINAL ISSUE: We would like MET to be able to read in tripolar grids. The Real-Time Ocean Forecast System (RTOFS), for example, uses a tripolar grid. Tripolar grids are a 'composite of two grids connected along a specified "join" latitude' . In a tripolar grid, there is a bipolar grid on one side (north or south) of the "join latitude" and a single pole grid on the other side. For RTOFS, this join latitude is 47°N. North of 47°N is an Arctic bipolar grid and south of 47°N is a Mercator projection (see attached figure). Tripiolar grids are designed to mitigate the convergence of longitudes at the North Pole.
Note: WCOSS2 does not allow xESMF, so any functionality built can not use xESMF.
References:
Environmental Modeling Center: "About Global RTOFS". https://polar.ncep.noaa.gov/global/about/
Geophysical Fluid Dynamics Laboratory: "A Guide to Grid Coupling in FMS".
https://www.gfdl.noaa.gov/guide-to-grid-coupling-in-fms/
Murray, R. J., 1996: Explicit generation of orthogonal grids for ocean models. Journal of Computational
Physics, 126, 251-273. [link to PDF]
Acceptance Testing
Current RTOFS files can be downloaded from:
https://nomads.ncep.noaa.gov/pub/data/nccf/com/rtofs/prod/rtofs.YYYYMMDD/rtofs_glo_2ds_f000_ice.nc
(Please check this file is the correct one with Bob Grumbine, and I can edit as needed.)
If MET can read in and display a graphic of the contents of a tripolar grid, I think we'll be all set.
Time Estimate
Estimate the amount of work required here.
I can't give an estimate for how much work this is for DTC. My hope is that because this was once covered by two closed MET issues (using tools that we can't use on WCOSS2) that we might not be starting from scratch and this will take less time than thought.
Closed MET issues: #1231 and #1345
Sub-Issues
Consider breaking the new feature down into sub-issues.
Relevant Deadlines
EVSv2- with development to begin in early 2024.
Funding Source
Not defined.
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
New Feature Checklist
See the METplus Workflow for details.
Branch name:
feature_<Issue Number>_<Description>
Pull request:
feature <Issue Number> <Description>
Select: Reviewer(s) and Development issues
Select: Repository level development cycle Project for the next official release
Select: Milestone as the next official version
The text was updated successfully, but these errors were encountered: