JohnHalleyGotway
commented
2 years ago Recommend considering this feature request in the larger context of the libraries upon which MET already depends.
As of version 11.0.0, MET depends on:
- NetCDF4 and HDF5 (since NC4 depends on HDF5)
- HDF4 and hdfeos version 2
The lidar2nc tool requires the HDF4 library.
The modis_regrid tool requires the very old hdfeos version 2 library.
Adding support for this HDF-EOS5 data will like cause confusion/conflicts with the earlier HDF library versions used by these tools. Recommend that part of this work be to revisit these tools and consider:
- Reimplementing them with the newer HDF5 and HDF-EOS5 libraries.
- Removing them from MET if they are no longer needed and/or reimplementing them is too difficult or time consuming.
malloryprow
georgemccabe
jprestop
Describe the New Use Case
Create a new use case to verify Total Column Ozone against NASA's OMI dataset. The OMI data are in HDF-EOS5 (.he5) format. Use python embedding to ingest these gridded observations and run GridStat to verify against GFS and/or GEFS model output.
Use Case Name and Category
Provide use case name, following Contributor's Guide naming template, and list which category the use case will reside in. If a new category is needed for this use case, provide its name and brief justification
Input Data
Data on WCOSS2 are downloaded from NASA, so the data are the same. (On WCOSS2) /lfs/h1/ops/dev/dcom/YYYYMMDD/validation_data/aq/omi/omiaura${YYYY}m${mmdd}_v883-${YYYY}m${mmdd}t${HHMMSS}.he5 (From NASA) https://omisips1.omisips.eosdis.nasa.gov/outgoing/OMTO3e/OMI-Aura_L3-OMTO3e_${YYYY}m${mmdd}_v883-${YYYY}m${mmdd}t${HHMMSS}.he5
For example: https://omisips1.omisips.eosdis.nasa.gov/outgoing/OMTO3e/OMI-Aura_L3-OMTO3e_2023m0720_v883-2023m0725t160312.he5
A test of functionality could involve a small use case using the OMI dataset for Total Column Ozone. This parameter can be found in GFS and GEFS forecasts.
Note that the python embedding solution must work on WCOSS2. The python packages must either already be approved to run there or seek approval to add new one(s).
Acceptance Testing
Describe tests required for new functionality. As use case develops, provide a run time here
Time Estimate
Unsure. Issues should represent approximately 1 to 3 days of work.
Sub-Issues
Consider breaking the new feature down into sub-issues.
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
New Use Case Checklist
See the METplus Workflow for details.
feature_<Issue Number>_<Description>feature <Issue Number> <Description>