A holistic microclimate model

You are here: Technical Model Webpage » ENVI-met Applications Homepage » DataStudio (BETA 2) for Python » Requirements

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
apps:datastudio:comparescenarioscriptdetails [2022/01/11 10:46] – freddiapps:datastudio:comparescenarioscriptdetails [2022/01/29 12:32] (current) – freddi
Line 8: Line 8:
  
 === General advice === === General advice ===
-  * Both scenarios should use the same meteorological conditions to keep the results compareable+  * Only change one input parameter at once (e.g. for scenario 2: only change the meteorological conditions and keep the model area the same or do it the other way around). Thus, the results are still compareable. 
   * The area of interest should exist in both scenarios.   * The area of interest should exist in both scenarios.
   * The script output should be shown together with screenshots of both model areas (scenario 1 and scenario 2)    * The script output should be shown together with screenshots of both model areas (scenario 1 and scenario 2) 
Line 79: Line 79:
 //(lines 32 - 33 in current script version)// //(lines 32 - 33 in current script version)//
  
-With index 0 we start at 23.06.2018 08:00h and with index 30 we end at 24.06.2018 14:00h. +With index 0 we start at 23.06.2018 08:00h and with index 92 we end at 27.06.2018 04:00h. 
  
 Anyway, if the simulation periods between both scenarios do not match, we need to define the indexes separately for each folder (scenario).  Anyway, if the simulation periods between both scenarios do not match, we need to define the indexes separately for each folder (scenario). 
Line 141: Line 141:
  
 {{:apps:datastudio:compscenoutput_polu.png}} {{:apps:datastudio:compscenoutput_polu.png}}
 +
 +==== Technical Note ====
 +Note that the execution-time of the script may be unexpected high, especially when you compare longer time periods or large areas. This is caused by limited implementation options caused by the Delphi-Python-interface. During execution, the GUI might not be reactive.