Extension or composition of various existing plugins or program parts for the barrier-free transfer of meteorological data (representative of certain climatological heat events) into an urban climate model
Extension and composition of various existing plugins or program parts for the statistical processing of climate model data and barrier-free transfer of meteorological data (representative of certain climatological heat events) into an urban climate model
## Input:
## Input:
* predefined RCM data basis: NUKLEUS ensemble (9 member) → output is calculated for all 9 members
* predefined RCM data basis: NUKLEUS ensemble (9 member) → output is calculated for all 9 members
* predefined reference data, historical data, observational data: NUKLEUS ensemble (1961-1990, 2005-2014), DWD gridded station data → do we need this data also to calculate/define events?
* predefined RCM data basis - climate simulation and optionally observational data: NUKLEUS ensemble scenario runs (fixed reference 1961-1990, selectable GWL +2K, +3K), optionally: DWD gridded station data → do we need this data also to calculate/define events? → it depends on the method chosen
* choice of method: determined by whether bias-corrected data necessary/available (vertical air temperature profile)
* variant 0 (optimal) - bias-corrected data available: bias-corrected model data is used directly for picking out events and outputting data
* variant 1: bias is (proven) not significant: Procedure as variant 0
* variant 2 (most unfavorable): bias is unknown, is judged to be significant and no bias-corrected data: The raw model data are used to derive the climate change signal (e.g. 2K-World - reference period). The climate change signal is suitably imposed on measurement data. Challenge: Derivation of vertical profiles (only measurements at a height of 2 m are available for temperature).
* predefined frequency of output: 1h
* predefined frequency of output: 1h
* selectable in configuration:
* selectable in configuration:
* scenario resp. GWL: 2K, 3K
* scenario resp. GWL: 2K, 3K
* region, shape file, split by (see Climpact and PreprocNUK?): municipality (dropdown menu) or shapefile (file upload) → fieldmean
* region, shape file, split by (see Climpact and PreprocNUK?): municipality (dropdown menu) or shapefile (file upload) → fieldmean
* event: Astrid is still researching which are the most investigated events and time periods, e.g.
* event: Astrid is still researching how to define realistic time series of heat events using a statistical data analysis (which kind of statistics?, search of real time series of model ensemble matching the statisticsal analysis) of RCM model ensemble, e.g.
* repräsentitive summer day
* representative summer day (this corresponds to an average summer day, tasmax median per month), only consider tasmax>=25°C?
* heat period (different length, see option below)
* extreme summer day (tasmax percentile per month, TX90p), only consider tasmax>=30°C?
* Period with high thermal stress (is postponed for the time being, as many variables are included in the definition of a thermal index: tas (max), ground temperature, wind speed, air humidity, short/long-wave irradiation surface = radiation balance (tool available?))
* very extreme summer day (tasmax percentile per month, TX95p), only consider tasmax>=30°C?
* length of events: 1d - ~14d
* heat period (different length, heat wave typically at least 3d or 5d, longer period 14d relevant for indoor climate see option below)
* Period with high thermal stress (is postponed for the time being, as many variables are included in the definition of a thermal index like UTCI Universal Thermal Climate Index : tas, wind speed, air humidity, short/long-wave irradiation surface are used to calculate MRT mean radiation temperature (adaptable Fortran code available to calculate UTCI → Astrid)
* length of events: 1d - ~14d
* months of events (season is not differentiated enough): april, may, june, july, august, september
* months of events (season is not differentiated enough): april, may, june, july, august, september
◦ optional: impact model: PALM4U, Envimet (data format will be different for output)
◦ optional: impact model: PALM4U, Envimet (data format will be different for output)
## Output:
## Output:
* Data to download: 9 x timeseries (frequency: h, length: 1d - ~14d) of vertical temperature stratification (representative for selected event) which can be fed directly into an urban climate model
* Data to download: 9 x timeseries (frequency: 1h, length: 1d - ~14d) of vertical temperature stratification (representative for selected event) which can be fed directly into an urban climate model
* optional add ons:
* optional add ons:
* tiemseries of reference data and observational data for comparison of future 2K/3K future with the past
* timeseries of reference data and observational data for comparison of 2K/3K future with the past
* plot of all 9 timeseries (+ reference, observation) to visualize ensemble bandwidth (+ difference to past)
* plot of all 9 timeseries (+ reference, observation) to visualize ensemble bandwidth (+ difference to past)
* future wish list: timeseries of additional variables: wind speed and direction (optimal: vertical profile or at least at AGS height geostrophic wind), shortwave (direct, diffuse) radiation at surface, air humidity (optimal: vertical profile), boundary conditon at ground surface (only initialisation): soil temperature and humidity
## preliminary work plan: → will be put into gitlab at some point to manage tasks, issues etc.
## preliminary work plan: → will be put into gitlab at some point to manage tasks, issues etc.
1. create gitlab project
1. create gitlab project
2. research background and colllaboration, check existing tools/data:
2. research background and collaboration, check existing tools/data:
* remapping und topography correction: PreprocNUK (Christoph)
* remapping und topography correction: PreprocNUK (Christoph)
* climpact with default settings to NUKLEUS-ensemble (Martin)
* climpact with default settings to NUKLEUS-ensemble (Martin)
* calculation of heat events, meeting with Christoph, Marie, Christian, Miriam:
* calculation of heat events, meeting with Christoph, Marie, Christian, Miriam:
...
@@ -40,9 +47,9 @@ Extension or composition of various existing plugins or program parts for the ba
...
@@ -40,9 +47,9 @@ Extension or composition of various existing plugins or program parts for the ba
* length of the longest heatwave
* length of the longest heatwave
* mean temperature of all heatwaves
* mean temperature of all heatwaves
* peak daily value in the hottest heatwave
* peak daily value in the hottest heatwave
* data processing for spatial and temporal format for selected impact model, is there a converter COSMO to PALM4U? → Astrid researches
* data processing for spatial and temporal format for selected impact model, there are converter COSMO and WRF to PALM4U → COSMO: [INIFOR preprocessor in Fortran](https://gitlab.palm-model.org/releases/palm_model_system/-/tree/74033244757f83ffd6452b44884b92c6c6ae1a6e/packages/dynamic_driver/inifor)(u, v, w, T, Qv, P, TS and WS Soil initial condition), [WRF_interface](https://gitlab.palm-model.org/releases/palm_model_system/-/tree/74033244757f83ffd6452b44884b92c6c6ae1a6e/packages/dynamic_driver/wrf_interface), [WRF4PALM](https://github.com/dongqi-DQ/WRF4PALM) py code
4. coding: convert heat event definitions into code
4. coding: convert heat event definitions into code (scientific core of the plugin)
5. coding: read needed data from freva data pool (see climpact) and consider PreProcNUK for hight correction of input data!!!
5. coding: read needed data from freva data pool (see climpact; use of bias-corrected data) and consider PreProcNUK for hight correction of input data!!!
6. coding: convert RCM time series into impact model format
6. coding: convert (analysed/derived) RCM time series into impact model format