Transcript LEAD – WRF
LEAD – WRF How to package for the Community? Tom Baltzer Acronyms for LEAD Tools ADAS - ARPS Data Assimilation System (Center for Advanced Prediction of Storms at OU) ADaM - Algorithm Development and Mining (University of Alabama at Huntsville) IDV – Integrated Data Viewer (Unidata) OPeNDAP – Open-source Project for a Network Data Access Protocol (OPeNDAP.org) THREDDS – Thematic Real-time Environmental Distributed Data Services (Unidata) WRF – The Weather and Research Forecasting Model (ARW Core - NCAR) Also: WS-Eta – Workstation Eta Model Current Configuration - WRF being Steered by Chiz’s GEMPAK precipitation locator NCEP NAM (Eta) Forecast Precipitation Locator WRF Center Lat/Lon Regional Forecasts WS-Eta THREDDS Catalog OPeNDAP Access Unidata LEAD Test Bed Next Steps Millersville ADaM Precip Locator CAPS ADAS Assimilation NCEP NAM (Eta) Forecast Precipitation Locator THREDDS Catalog WRF Regional Forecasts WS-Eta OPeNDAP Access Unidata LEAD Test Bed Ultimately IDD Datasets • Radar • Surface & Upper air • Satellite • NCEP NAM NCEP NAM (Eta) Forecast ADaM Precipitation Locator ADAS WRF Center Lat/Lon Regional Forecasts WS-Eta THREDDS Catalog OPeNDAP Access Unidata LEAD Test Bed When/What to bring to Community? • Which of these capabilities is worthy of “packaging” for delivery to the Unidata Community? • What form is most desired? • Is it better to wait for Web Service model? Note: We’re not suggesting that we’d take over support for WRF, ADAS or ADaM Additional Info: CAPS ADAS Observations • 40km ETA/NAM for the background field. • Hourly SAO's (U.S., Canada, Mexico). • Oklahoma Mesonet. • West Texas Mesonet. • Ship/buoy/cman. • Raob, on raob hours. • Profiler data. • Level 2 radar data. • Level 3 (nids) radar data for missing level 2 radars (mostly military). • Visible and IR satellite data. • MDCRS data. Note that only reflectivity is used from the radars. Mesowest and Iowa mesonets will be added when I get a chance to fix some decoder problems.