Current Use of Feedback Files Some Examples of Verification Products

1. Use of Feedback Files for Verification at DWDUlrich PflügerDeutscher Wetterdienst, Offenbachulrich.pflueger@dwd.de • Current Use of Feedback Files • Some Examples of Verification Products • Use of Feedback Files in VERSUS (Requirements) VERSUS 2 Priority Project Meeting Langen

2. Current Use of Feedback Files • in COSMO EU/DE Routine Verification and Experiment Verification • for each verification time (00, 06, 12, 18 UTC) one feedback file for all data (ASCII Format) • feedback file contains • Observation data • Report meta data (coordinates, height, obs. time, flags set by data assimilation (active, passive, rejected, qc info, etc.) • Observation deviations (COSMO DE): obs-an, obs-fc06, obs-fc12, obs- fc18 • Observation deviations (COSMO EU): obs-an, obs-fc06, ………..., obs- fc48 • building of feedback files • inital version created by data assimilation (obs, obs-an) • Model verification run calculates deviations of forecasts for the current verification time(obs-fc06, ……….., obs-fc48) • Update of feedback file with forecasts devations VERSUS 2 Priority Project Meeting Langen

3. Current Use of Feedback Files (continued) • feedback files are used for Upper Air Verification since more than 10 years now • COSMO EU/DE routinely verified/monitored against • radiosonde data (wind speed and direction, temp, rel.hum., geopotential) • aircraft data (wind speed and direction, temp, rel.hum.(3 aircrafts)) • windprofiler (wind speed and direction, temp. (some)Δ) • vad winds (wind speed and direction) • Arbitrary verification area (definition as a rectangle(λ,φ) or via station list) • Selection of observation data according data usage and qc information • Sorting in arbitrary vertical bins • in Routine Verification Δp = 25 hPa below 800 hPa and 50 hPa above • Calculation of forecast deviation statistics for selected forecast lead times for vertical bins or for standard pressure levels, plotting as vertical profile • daily or monthly mean profiles of Mean Error (BIAS), RMSE • Up to three runs can be compared in one plot • Time Series of daily or monthly mean profiles VERSUS 2 Priority Project Meeting Langen

4. Examples for Upper Air Verification Products:Monthly Mean Profiles for BIAS and RMSE (ML Aircraft) VERSUS 2 Priority Project Meeting Langen

5. Examples for Upper Air Verification Products:Monthly Mean Profiles for BIAS and RMSE (RS, Comparison) VERSUS 2 Priority Project Meeting Langen

6. Examples for Upper Air Verification Products:Monthly Mean Profiles for BIAS and RMSE (RS, Comparison) VERSUS 2 Priority Project Meeting Langen

7. Examples for Upper Air Verification ProductsTime Series of Daily Means of Temperature BIAS 00 h 48 h VERSUS 2 Priority Project Meeting Langen

8. Examples for Upper Air Verification ProductsTime Series of Monthly Means of Temperature BIAS 00 h 48 h VERSUS 2 Priority Project Meeting Langen

9. Use of Feedback Files in VERSUS Format and Content of Feedback Files: • Format of COSMO Feedback Files will be changed from ASCII to NETCDF • The format and content is documented in the „Feedback File Definition“ by A. Rhodin and C. Schraff • with the new NETCDF files there will be probably one file for conventional observation data (Synop, RS, aircraft, windprof, etc.) • and seperate files for mass data like radar, satellite etc. • data content will remain the same (obs, obs-fcxx, data usage and qc info) VERSUS 2 Priority Project Meeting Langen

10. Use of Feedback Files in VERSUS (continued) Requirements to a VERSUS front-end respectively VERSUS itself: • Usage of all kind of observations (Synop, RS, aircraft, windprof, vad, etc.) • Loading of feedback files from routine and experimental runs together (probably from a directory structure) • Internal data storage in VERSUS after the (VERSUS) step of assigning model data to obs data • Probably the internal VERSUS data base has to be extended in order to keep additional data like data usage information, qc information, etc. • Possibility to use qc information and data usage information for data stratification and conditional verification • e.g. selection of observations with certain level of quality • Arbitrary verification area (at least via a stationlist) • Possibility to calculate scores for any verification periods (day, sev. days, month, year) VERSUS 2 Priority Project Meeting Langen

11. Use of Feedback Files in VERSUS (continued) Requirements to a VERSUS front-end respectively VERSUS itself: • Time series of scores (daily, monthly), also for vertical profiles of scores • Operation of VERSUS via GUI and in Batch Mode • GUI • Selection of runs • Selection of period • Selection of verification area/stations ( posibility to use same set of observations in case of comparison between experiments) • Selection between bias corrected and original reported observation values • Selection of data stratification (conditions) and scores • etc. • batch mode (necessary for operational runs and experimental runs) • Selection of runs, period, etc. via a control file VERSUS 2 Priority Project Meeting Langen

12. Thank you for your attention VERSUS 2 Priority Project Meeting Langen

13. Examples for Upper Air Verification Products:Monthly Mean Profiles for BIAS and RMSE (Comparison) VERSUS 2 Priority Project Meeting Langen

14. Examples for Upper Air Verification Products:Monthly Mean Profiles for BIAS and RMSE (Comparison) VERSUS 2 Priority Project Meeting Langen

15. Examples for Upper Air Verification Products:Monthly Mean Profiles for BIAS and RMSE (Comparison) VERSUS 2 Priority Project Meeting Langen

16. Examples for Upper Air Verification Products:Monthly Mean Profiles for BIAS and RMSE (Comparison) VERSUS 2 Priority Project Meeting Langen

17. Examples for Upper Air Verification Products:Monthly Mean Profiles for BIAS and RMSE (Comparison) VERSUS 2 Priority Project Meeting Langen