RTFDDA Engineering System Architecture Input Data Cycle Timing

4DWX System Architecture NOAAPort Internet Range Data Model Applications Cluster Data Applications System Auto- Nowcast System Web Displays JVIZ CQT MAT, WWT CIDD/MRRD

4DWX System Architecture DAS Data Applications Cluster NOAAPort Internet Range Data Web Displays JVIZ CQT MAT, WWTCIDD/MRRD Ingest: Data ingest Web Server System Monitor Web-based tools Server: Mysql RAID storage Display: Web Browser JVIZ Desktop Tools nport radar Spare No high-speed interconnect between nodes

4DWX System Architecture MAC Data Applications Cluster NOAAPort Internet Range Data Web Displays JVIZ CQT MAT, WWTCIDD/MRRD Admin node: Holds O/S & tools Interactive nodes (2): data ingest Pre processing Post processing Compute nodes (14): High speed interconnect (Myrinet or other) between nodes At least one kept as a spare “Good” nodes collected each RTFDDA cycle No external network connectivity

DAS Architecture NOAAPort Internet Range Data IngestServerDisplay RAID Storage Web ToolsDesktop Tools

RTFDDA Data Initial and Boundary Conditions –NAM –GFS –Sometimes other models – ECMWF, NNRP –From NCEP FTP servers –NOAAPort broadcasts a reduced set of these data which are not sufficient (vertical resolution and missing fields) for model initialization –00Z NAM/GFS is used as input to RTFDDA 05Z –12Z NAM/GFS is used as input to RTFDDA 17Z

RTFDDA Data Observations datasets –More observations are always being added –The data sources adapt as new data is added –Range data is always used and very important for local scale phenomena –Some obs are gathered at NCAR and distributed to the ranges –Some obs are gathered independently at each range –Only observations that measure direct model variables are currently used in the RTFDDA obs- nudging scheme (temp, wind, rh, etc)

Regional-scale model, based on PSU/NCAR MM5 (WRF) RTFDDA Cold start t Forecast FDDA New 48 h forecast every 3 hrs at 1 km res, using all new obs QuickSCAT TAMDAR LIDAR RADAR MESOWEST ACARS GOES

RTFDDA dataflow “in general” Ingest host ETA GFS WMO Satwinds NPN BLP ACARs RAWs MADIS Other NCEP Other Ranges NOAA NOAAPort FSL Model Cluster RTFDDA cycles Output Products Web server Web accessible Output Products UGUI gifs NAPS MEDOC FDDA sites Data host MDV server/files JVIZ Gridded Climatology Files

RTFDDA dataflow *ATEC range* Ingest Mysql  Files: SAMS Range Soundings Range PWIDS Files: Range Profilers Range Obs Web server Web accessible Output Products UGUI gifs NAPS MEDOC FDDA sites Data host MDV server/files JVIZ Gridded Climatology Files MAC RTFDDA cycles Output Products NCEPFSL-MADIS RAL WMO NOAAPort WMO

RTFDDA Cycles Current ATEC RTFDDA configurations run cycles every 3 hours, at 02Z, 05Z, 08Z, etc. This timing is based on data availability. 1, 2 or 6 hour cycle intervals are sometimes used –For rapid real-time updates (1 or 2 hour cycles) –For longer forecast output options (6 hour cycles) Precise cycle timing depends on –cluster compute-power –forecast length goals –data availability Output products generally use “the latest available” for the requested valid time –This assumes that the latest available is the most accurate

Anatomy of a Cycle Pre- process Obs FDDA Final Analysis MM5 running Process Add’l Obs Prelim + Forecast … MM5 running… 05:0007:0006:0008:00 Cycle Starts Longer or shorter for different cycle intervals

Cycle Output Valid Time Cycle Final Analysis Preliminary Analysis Forecast 05Z08Z11Z14Z17Z20Z