A holistic microclimate model

You are here: Technical Model Webpage » ENVI-met Applications Homepage » ENVI-met Update History

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:updates [2026/09/23 16:10] – enviadminapps:updates [2026/09/23 16:20] (current) – enviadmin
Line 1: Line 1:
 ===== ENVI-met Update History ===== ===== ENVI-met Update History =====
 <WRAP left box 99%> <WRAP left box 99%>
- 
-<fs xx-large> Disclaimer about result differences between versions </fs> 
- 
-ENVI-met is subject to continuous substantial model development. Simulations run in a version may therefore differ from those run with earlier versions, as is normal for any major release of a physical model. Results from earlier versions remain valid as documented outputs of the model version used. For comparisons between scenarios, we recommend running all variants with the same version. 
  
 <fs xx-large>ENVI-met updates for version 6.0 //Lightning// (September 26)</fs> <fs xx-large>ENVI-met updates for version 6.0 //Lightning// (September 26)</fs>
Line 26: Line 22:
   * **Wind Comfort:** Multi-direction wind-field analysis with exceedance probabilities, graded against the NEN 8100, Lawson and Davenport standards. ** EXCLUSIVE TO BUSINESS LICENSE TIER**   * **Wind Comfort:** Multi-direction wind-field analysis with exceedance probabilities, graded against the NEN 8100, Lawson and Davenport standards. ** EXCLUSIVE TO BUSINESS LICENSE TIER**
   * **Surrounding-area presets:** Characterise the urban context upstream for each model domain border with ready-made urban-climate-zone and land-cover presets, from open water and countryside through to dense city cores.   * **Surrounding-area presets:** Characterise the urban context upstream for each model domain border with ready-made urban-climate-zone and land-cover presets, from open water and countryside through to dense city cores.
-  * **Absolute air temperature** is now the primary temperature in result files, listed ahead of potential temperature, and air pressure is referenced to the actual site elevation rather than a fixed standard value. Scripts that read result variables by position need to be updated (see note above).+  * **Absolute air temperature** is now the primary temperature in result files, listed ahead of potential temperature, and air pressure is referenced to the actual site elevation rather than a fixed standard value. Scripts that read result variables by position need to be updated.
   * **Building indoor climate & air-conditioning heat:** Set an indoor temperature per building and choose whether the heat its air conditioning removes is released into the surrounding air, letting you study the outdoor warming that cooling demand produces. Allow natural ventilation of buildings based on thermal indoor/outdoor thresholds and usage periods.    * **Building indoor climate & air-conditioning heat:** Set an indoor temperature per building and choose whether the heat its air conditioning removes is released into the surrounding air, letting you study the outdoor warming that cooling demand produces. Allow natural ventilation of buildings based on thermal indoor/outdoor thresholds and usage periods. 
   * **Spin-up of the model:** ENVI-met now runs a spin-up phase for soils, materials etc. that automatically derives their initial temperatures, replacing the previous manual soil temperature input.   * **Spin-up of the model:** ENVI-met now runs a spin-up phase for soils, materials etc. that automatically derives their initial temperatures, replacing the previous manual soil temperature input.
Line 105: Line 101:
  
  
 +<fs xx-large> Disclaimer about result differences between versions </fs>
 +
 +ENVI-met is subject to continuous substantial model development. Simulations run in a version may therefore differ from those run with earlier versions, as is normal for any major release of a physical model. Results from earlier versions remain valid as documented outputs of the model version used. For comparisons between scenarios, we recommend running all variants with the same version.
  
 <WRAP left box 99%> <WRAP left box 99%>