1 / 23

UW-CIMSS and ASPB 2010 Proving Ground Activities

This document outlines the baseline and option 2 products being developed for the GOES-R Proving Ground. It also provides information on the current testing and validation activities, as well as the plans for future collaborations and deliverables.

wsteward
Télécharger la présentation

UW-CIMSS and ASPB 2010 Proving Ground Activities

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. UW-CIMSS and ASPB 2010 Proving Ground Activities GOES-R Proving Ground Face-to-Face May 18-19, Boulder, CO Advanced Satellite Products Branch UW-Madison

  2. GOES-R PG Plan Decision Support Candidates • Baseline Products: • Volcanic Ash: detection & Height • Cloud and Moisture Imagery • Hurricane Intensity • Lightning Detection: Events, Groups & Flashes • Rainfall Rate / QPE • Total Precipitable Water • Fire/Hot Spot Characterization • Option 2 Products: • Aircraft Icing Threat • Convective Initiation • Enhanced “V” / Overshooting Top Detection • Low Cloud and Fog • SO2 Detection

  3. UW-CIMSS and ASPB GOES-R ProductsBaseline & Option 2

  4. UW-CIMSS and ASPB GOES-R ProductsBaseline & Option 2

  5. April 22, 2010 24-Hour Accumulated UWCI and OT Locations NLDN CG Lightning SPC Storm Reports

  6. GOES Proxy Overshooting Top (OT) and Decision Support Detection Provided to SPC HWT for GOES-R PG Spring 2010 6

  7. OT Validation 7

  8. UW/CIMSS is generating simulated ABI Bands 8-16 using NSSL-WRF once daily Currently in test mode, webpage is updated by 11am for 7 time steps. McIDAS areas for N-AWIPS display ABI Band 10 (7.34 µm) ABI Band 13 (10.35 µm) http://cimss.ssec.wisc.edu/goes_r/proving-ground/nssl_abi/nssl_abi_rt.html 8

  9. Estimated ABI Emitted-only bands

  10. Observed GOES-13 Imager

  11. UW-CIMSS and ASPB GOES-R ProductsR3 and Decision Aids

  12. PG Demonstration Activities • All products are being reformatted into GRIB2 -> AWIPS, AWIPS-II, McIDAS-V, GEMPAK, and other visualization software. • GINI formatting -- transition our current suite of imagery into AWIPS II.  We can format fields and products in GRIB2, but it is not an effective format for satellite imagery yet. • In field direct collaboration for SPC HWT and MKX (Sullivan) WFO.

  13. PG Demonstration Activities In-direct users at WFO in each region AWIPS Migration J. Gerth continues to serve as the CIMSS representative on the AWIPS II teleconference call for the GOES-R Proving Ground partners, as well as the AWIPS II Governance Tiger Team. Currently assessing operating system and hardware requirements to run AWIPS II outside of a NWS forecast office. Continue to receive and install new builds of the software, most recently TO11 DR9. WES ABI status – Pacific case, NSSL EWP WES training CI/OT/Imagery Training provided via fact sheets, VISITview, and lecture

  14. ABI WES case: Added a set of ABI simulated images from 21Z on Jun 26, 2008 14

  15. Partnerships • Norman SPC/NSSL HWT/AWC • Providing in field support for N-AWIPS/AWIPS CI, and Overshooting-top/Enhanced-V. Providing NSSL WRF ABI IR band simulations from 17 May – 18 June 2010 • Milwaukee WFO Haz Wx Testbed • In field UW-CIMSS researchers will be at office every Tues/Thur May – Aug, CI and Nearcasting demo • Collaborations with AK PG effort • M. Pavolonis to provide AVHRR Volash/SO2 and Low Cloud/Fog • Other WFOs that receive up to 38 products • Initial Hurricane Testbed collaboration

  16. GOES-R PG Long-range plans 17

  17. GOES-R Fog Detection Algorithm (night) 18

  18. AVHRR automated ash cloud warning system • The warning criteria is fully user configurable. • In addition to the text message, an automatically generated, pre-analyzed false color image along with product images are supplied to the user. Product Quick-look Text Warning

  19. AVHRR in AWIPS Example of other products: http://cimss.ssec.wisc.edu/goes/blog/wp-content/uploads/2009/08/090811_avhrr_ir_type_anim.gif 20

  20. Schedule • Participate and provide convective initiation and overshooting-top decision support products to Storm Prediction Center for evaluation and feedback (Spring 2010) • Participate in GOES-R Proving Ground review meeting (Spring 2010) • Provide on site GOES-R Proving Ground UW Convective Initiation and nearcasting training and collaboration with local Sullivan NWS office (Summer 2010) • Participate in Pac NWS Proving Ground meeting in Honolulu, Hawaii (Summer 2010) • Support GOES-R PG demonstration decision support product data infusion into AWIPS, N-AWIPS, and AWIPS Migration as needed (2010-2011) • Participate in GOES-R High Latitude Testbed activities including provide demonstration volcanic ash and low cloud/fog products via AWIPS (Fall 2010 – Spring 2011)

  21. Deliverables • Deliver and install two SDI-104 McIDAS ingest servers at Honolulu, Hawaii NWS office when direct readout antennae's are in place (Spring 2010) - Done • Provide experimental GOES-R AWG proxy product data streams to AWIPS for users in near real-time (Whole year) – On-going • Develop and distribute Pacific Ocean Weather Event Simulation case (Winter 2011) – In progress • Implement lightning proxy data code if obtained from GOES-R R3/AWG Lightning team (Winter 2011) • Generate near real-time regional WRF ARW synthetic ABI radiances (Spring 2011) – NSSL WRF ARW conversion to ABI IR bands • Annual report (Word and PPT) (Fall 2010)

  22. Problems/Issues/Discussion • PG still needs some flexibility to address user needs on a timely basis (e.g., customer responsiveness).   • should be able to supply requested products to users without having to wait for the next years plan.   • for example, MODIS SST and MKE, UWCI modifications, etc. • If it's not broke, don't fix it. For example, if MODIS data flows to each of the regions in a band-width effective method, why look to adding in data latency? • Fixed PG monthly meeting times for the year (eg,third Friday of each month at 18UTC). • Share ppt ahead of time; to reduce WebEx reliance. • AWG management interface with PG.   • will AWG run GOES (or MODIS) versions of ABI algorithms?   • Data format • GRB2 and BUFR may be what certain users expect, yet GOES-R formats are mostly netCDFv4

More Related