1 / 8

NPVU and GRIB Update

NPVU and GRIB Update. Mary Mullusky and Mark Glaudemans. NPVU Modernization Background and Goal. Background : NPVU requires RFC QPF data in a very specific projection, format, and resolution (GriB encoded 10 km Lambert conformal conic) 

walt
Download Presentation

NPVU and GRIB Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NPVU and GRIB Update Mary Mullusky and Mark Glaudemans

  2. NPVU ModernizationBackground and Goal • Background: • NPVU requires RFC QPF data in a very specific projection, format, and resolution (GriB encoded 10 km Lambert conformal conic)  • RFCs use various grid generation and grid transformation tools to meet NPVU's requirement.  • For RFCs working with grids smaller than 10 km, the RFCs spatially average their grids to meet the 10km resolution requirement from NPVU and then NPVU reprocesses those same grids to a 4 km grids for verification. • Goal: Make this process simpler and considerably more efficient for both the RFCs and NPVU.

  3. NPVU ModernizationProject Timeline • Aug 2007 - RFC Verification Workshop Tish Soulliard presented the process for verifying QPF from various sources describing the upscaling and downscaling involved in the process. HSD given the action to "Investigate the feasibility of having all RFCs provide 2.5 km QPE and QPF to be verified by NPVU" • Oct 2007 - RFCs are trained on using GFE as a method to edit and collaborate on input grids • April 2008 - ABRFC identifies that there are no tools or mechanisms to convert GFE netCDF files to the grib encoded files that NPVU required (there are now – Mark will discuss next) • May – Jun 2008 - OCWWS/HSD polled all of the RFCs and learned that most planned to convert to GFE for QPF processing within the next two years. All RFCs wanted to process QPF at resolutions smaller than the 10km that NPVU currently receives. • Aug-Sep 2008 A small team of OCWWS/HSD, RFC and GSD staff write an informal needs and requirements document and present to OCWWS Performance Branch leadership • Oct - Nov 2008 OCWWS Performance Branch and HSD investigate possible solutions

  4. NPVU ModernizationProject Timeline • December 2008 OCWWS Performance Branch, HSD and GSD visit NERFC to receive a demo of GFE at RFCs and determine if it is feasible to setup GFE at  NPVU as the method to receive RFC QPF grids. The group decides to move forward to implementing GFE at NPVU • Jan -Feb 2009 OCWWS/HSD makes a proposal to the FY09 Workplan and priority process to secure funding for GFE hardware at NPVU and secure funding for GSD support • Jan - May 2009 OCWWS/Performance Branch Investigates setting up hardware at NCEP including coordinating with NCEP folks, creating specifications for new hardware, creating an AWIPS Request for Change and creating a Memorandum of Agreement between OCWWS and NCEP • June 2009 NCEP proposes using existing AWIPS hardware • June 2009 OCWWS/Performance Branch and NCEP installed GFE and configured for NPVUs verification domain

  5. NPVU ModernizationOngoing andRemaining Activities • Test Inter-Site Coordination (ISC) data flow (ongoing) • Test AWIPS process to get grib encoded files (e.g. NMAP files) into netCDF so these files can also be read into NPVU’s GFE • Start receiving RFC GFE grids through ISC and GRIB grids (e.g. NMAP) through AWIPS WAN into NPVU’s GFE verification domain • ISSUE: How can NPVU determine the official grid? • Proposal: ISC cutoff time of 18:30Z • Write GFE scripts to produce ascii verification pairs, create images and archive files • Write procedures to move ascii pairs, images and archive files from AWIPS to NPVU verification hardware • Modify Verification scripts to remove downscaling process • Run verification scripts with ascii pairs derived from GFE (do in parallel to existing process for a couple of months) Target: September 1 for parallel Operations

  6. RFC GRIB Encoding for NPVU

  7. Long-term GRIB Generation Plans • GRIBIT Application • For NPVU and CHPS • Transforms “xmrg” format to GRIB1 • Transforms MPE 1-hour QPE (and other process codes) • Legacy OHD application in AWIPS baseline • NC2GRIB Application • For NPVU and CHPS • Transforms non-CF-compliant netcdf format to GRIB1 • Transforms • MPE/DQC (QPE, QTE, freezing level) • GFE elements (QPF, QTF, ET, freezing level) • New OHD application (v3.1), not in AWIPS baseline yet

  8. CHPS GRIB Usage • GRIB1 is current choice for gridded output for CHPS • Use nc2grib for transforming GFE netCDF to GRIB1 • Updated MPE/DQC will produce GFE-style netCDF output…can then transform to GRIB1 • ABRFC and NWRFC using nc2grib • Demonstrated successful import by CHPS • Demonstrated successful import by NPVU • OHRFC also evaluating software

More Related