README.md

+# heat2urbanimpact
+
+## Work assignment
+
+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
+
+## Input: 
+* 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 frequency of output:  1h 
+* selectable in configuration: 
+    * scenario resp. GWL:  2K, 3K 
+    * 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.
+        * repräsentitive summer day
+        * heat period (different length, 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: tas (max), ground temperature, wind speed, air humidity, short/long-wave irradiation surface = radiation balance (tool available?))
+    * length of events: 1d - ~14d
+    * 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)
+
+## 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
+* optional add ons: 
+    * tiemseries of reference data and observational data for comparison of future 2K/3K future with the past
+    * plot of all 9 timeseries (+ reference, observation) to visualize ensemble bandwidth (+ difference to past)
+
+## preliminary work plan: → will be put into gitlab at some point to manage tasks, issues etc.
+1. create gitlab project 
+2. research background and colllaboration, check existing tools/data:
+    * remapping und topography correction: PreprocNUK (Christoph)
+    * climpact with default settings to NUKLEUS-ensemble (Martin)
+    * calculation of heat events, meeting with Christoph, Marie, Christian, Miriam:
+    * PSI plugin, MHWId plugin? (Christoph, Marie)
+    * program to spot extreme events (Miriams PhD study?)
+    * KIT and BTU calculated various climate indices, also for heat waves (Christian)
+        * https://climpact-sci.org/indices/#index-HWM,  /work/bb1203/ET-SCI
+        * number of individual heatwaves
+        * number of days that contribute to heatwaves
+        * length of the longest heatwave
+        * mean temperature of all heatwaves
+        * 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
+3. create plugin input mask → heat2urbanimpact_control.py
+4. coding: convert heat event definitions into code
+5. coding: read needed data from freva data pool (see climpact) and consider PreProcNUK for hight correction of input data!!!
+6. coding: convert RCM time series into impact model format
+7. … 

heat2urbanimpact_control.py

+#freva plugin development