1 / 11

VERSUS at DWD - 2011

This article highlights the challenges faced during the implementation of VERSUS at DWD and the progress made so far. It discusses issues with database access, slow execution, disk space limitations, software problems, and the inability to control the loader. It also mentions examples of forecast data and the need for defining the operational suite. The article concludes with a question about the potential impact of introducing assimilation feedback files into VERSUS.

wax
Download Presentation

VERSUS at DWD - 2011

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. VERSUS at DWD - 2011 Ulrich Damrath & Ulrich Pflüger COSMO GM Rome, September 2011

  2. State of work with VERSUS @ DWD • Regular work with VERSUS • Submission of data for the common plots was done • Graphics and text files were produced for a lot of cases • Weather-type dependent verification in VERSUS was introduced • Work was done for some special cases • Work was not done in a quasi operational mode • Conditional verification and stress test • No quasi operational use of conditional verification • Stress test was not performed • WHY?

  3. Severe problems with VERSUS @ DWD - 1 • Access to mysql-database • Execution is sometimes very slow – probably because of the large size of the file ibdata1 in the mysql-directory (currently: 0.9 TByte). • Filotea gave some hints to overcome these problem, but the execution of the recommended data base requests need some time … • There was no disk space to introduce the stress-test data. • Access may be disturbed during an active loader phase. • Large time to wait for a response or • Interrupt of score calculation • php-problems • At browser sessions that are not direcly carried out at the versus server php dies after about one hour • At browser sessions that are directly carried out at the versus server this problem does not occur. • Software problems: • Decoding of bufr data did not work correctly for observations at 06 UTC (starting in March 2011) • Filotea gave the advice to install bufr_dc version 3.83. And it worked! • Some input data had to be recalculated. • More …

  4. Severe problems with VERSUS @ DWD - 2 • The running state of the loader cannot be controlled!!! • Loader cannot be stopped via the browser menu! • Processes appear to be stopped – but they are running! • Pressing the <Start>-button leads to a new loader process that has to be killed manually – if it can be catched • If the loader is really active with GRIBs the process is active for some seconds and can be killed. • If the loader is waiting for new files it generates a new process every second or so. This process is not easy to kill. • More …

  5. Severe problems with VERSUS @ DWD - 3 More …

  6. Severe problems with VERSUS @ DWD - 4 Nevertheless …

  7. Some typical examples: CEU T 2m forecasts July 1010

  8. Some typical examples: CDE T 2m forecasts July 1010

  9. Some typical examples: CEU TDEW 2m forecasts July 1010

  10. Some typical examples: CDE TDEW 2m forecasts July 1010 And lots of others …

  11. Current state • VERSUS is on the way to be operational at DWD • Operational suite has to be defined for • Standard verification • Conditional verification • Model intercomparison … • This can be done if the current problems are solved. • Open question: What will happen if the feedback files from assimilation will be introduced into VERSUS?

More Related