130 likes | 292 Views
HD ( CP ) 2. O1 – Supersites Verbundtreffen Leipzig, 1.-2.10.2013. HD ( CP ) 2 – O1. Partners here today : TROPOS Patric Seifert, Holgers Baars, Andreas Macke FZJ Anne Hirsikko IGMK Kerstin Ebell , Ulrich Löhnert LIM Bernhard Pospichal
E N D
HD(CP)2 O1 – Supersites Verbundtreffen Leipzig, 1.-2.10.2013
HD(CP)2 –O1 Partners heretoday: TROPOS Patric Seifert, Holgers Baars, Andreas Macke FZJ Anne Hirsikko IGMK Kerstin Ebell, Ulrich Löhnert LIM Bernhard Pospichal DWDEileen Päschke, Jürgen Güldner, Uli Görsdorf, Volker Lehmann MPI Verena Grützun, Florian Rauser
HD(CP)2 –O1 RAO-Lindenberg Supersites to provide a continuous data flow of standardized and quality controlled atmospheric variables, together with their uncertainties. LACROS • advancing ARM & Cloudnet activities • deliver vertical (line of sight) profiles of temperature, wind, humidity, aerosol, clouds and precipitation • Unified remote sensing 1DVAR retrieval scheme to transform the observations into atmospheric variables • Data available in standardized and easily accessible database, which contains all relevant atmospheric variables including error covariances • Value Added Products (VAPs) containing algorithm evaluation, process studies or long-tem statistics
Milestones • Project Month 15: One year of Target Categorization and measurement data to data base (IGMK, FZJ, TROPOS) • Project Month 15: Implementation of 1DVAR retrieval scheme at JOYCE and Lindenberg Observatory (IGMK, FZJ, DWD) • Project Month 24: Provide one year of 1DVAR products to data base (IGMK, LIM, TROPOS) • Project Month 36: Publication of operational 1DVAR scheme application (DWD) HD(CP)2 –O1 Milestones
HD(CP)2 –O1 mostimportantpointsuntil end ofyear absolved absolved Data productstandard today & Dez.
HD(CP)2 –O1 Meeting goals • level1 data • finalize “core” data • prioritize further data (task forces) • time lines (uploading) • level2 & higher data: • prioritize by file name • create task forces • coupling to cloudnet • algorithm development • progress of different methods • “operational” installation
MWRnet - background • Currently there is lack of coordination of MWR operations poor quality results in unused potential of MWR data • The International Network of Microwave Radiometers (MWRnet) was started ~3 years ago • Motivation: increase the utilization of quality controlled ground-based MWR data • Goals: • Establish “best practices” for MWR observations and retrievals • Facilitate the access of well documented and QC MWR observations and retrievals (with errors!) • Provide a hub with near-real-time MWR data and retrievals for Observation System and Data Assimilation Experiments
MWRnet(http://cetemps.aquila.infn.it/mwrnet) About 61 members, more than 94 MWR worldwide
HD(CP)2 –O1 mwr_prostructure level1/2 dataproductsbased on mwr_prosoftwarepackagedevelopedwithinMWRnet level1 has been made HD(CP)2 compliant: sups_joy_mwrnn_l1_v00_tb_YYYYMMDDHHMMSS.nc sups_joy_mwrnn_l1_v00_tbbl_YYYYMMDDHHMMSS.nc
HD(CP)2 - O1 mwr_prodataflow • manual filter (“by eye”) • user-defined thresholds • housekeeping data • rain flag Need instrument-specific routine • Need large number of site-specific radiosondes (or model output) to run RT-model at MWR frequencies • Perform multi-linear regression and retrieve regression coefficients