A holistic microclimate model

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
filereference:output:start [2018/03/07 16:37]
enviadmin
filereference:output:start [2019/05/31 13:16] (current)
enviadmin [Overview]
Line 5: Line 5:
 In general, there are two different types of output files regardless their content: In general, there are two different types of output files regardless their content:
   * **Simple Text Files**: Files which contain data in pure ASCII text format. Usually, the content of the file are described in the first row of the file. These file can be read and visiualized with any software that can read text files (which should be about every piece of software that can visiualize data).   * **Simple Text Files**: Files which contain data in pure ASCII text format. Usually, the content of the file are described in the first row of the file. These file can be read and visiualized with any software that can read text files (which should be about every piece of software that can visiualize data).
-  * **Binary Files (EDX/​EDT)**:​ The main ENVI-met output files are stored in a binary format and require special software to be read. The [[leonardo:​start|LEONARDO]] software included in the ENVI-met system offers a comfortable and visual access to all data and give various options for 2D and 3D visualisation. In addition, with the help of the reference for the [[filereference:​edx_edi|EDX/​EDT file format]], own reader routines can easily be developed.+  * **Binary Files (EDX/​EDT)**:​ The main ENVI-met output files are stored in a binary format and require special software to be read. The [[leonardo:​start|LEONARDO]] software included in the ENVI-met system offers a comfortable and visual access to all data and give various options for 2D and 3D visualisation. In addition, with the help of the reference for the [[filereference:​edx_edi|EDX/​EDT file format]], own reader routines can easily be developed.  Moreover, ENVI-met provides the option to convert EDX/EDT data to the [[wp>​NetCDF|NetCDF format]] ​ via the **NetCDF application** found in the Headquarter
  
 ===== Name and storage logic ===== ===== Name and storage logic =====
Line 43: Line 43:
   - **Simulation Base Name**: This is the given working name for the simulation. You define this name in the .SIMX simulation configuration file. It should be not too log (as more data are added) and unique. In the example above, ​ ''​urbanLayout''​ has been selected ​ as basename.   - **Simulation Base Name**: This is the given working name for the simulation. You define this name in the .SIMX simulation configuration file. It should be not too log (as more data are added) and unique. In the example above, ​ ''​urbanLayout''​ has been selected ​ as basename.
   - **Type identifier**: ​ The type identifier describes the content of the file following the categories listed above. For example ''​_AT_''​ defines that this file holds atmospheric data. The different content ids are listed in the description of the output files categories and at the end of this page.    - **Type identifier**: ​ The type identifier describes the content of the file following the categories listed above. For example ''​_AT_''​ defines that this file holds atmospheric data. The different content ids are listed in the description of the output files categories and at the end of this page. 
-  - **Time of data**: The last part of the filename represents the model time the data were taken. In the example above, the file represents the stae of the atmosphere (''​_AT_''​) at 13:00 model time. If the data in the file are not time sensitive, this part of the filename is empty.+  - **Time of data**: The last part of the filename represents the model time the data were taken. In the example above, the file represents the state of the atmosphere (''​_AT_''​) at 13:00 model time. If the data in the file are not time sensitive, this part of the filename is empty. ​From Version 4.4.3 (Summer 19) onwards, the order of the time step has been changed to Year-Month-Date (YYYY-MM-DD + Time)
  
  
Line 62: Line 62:
 | _SAFAC_ | Solar Accerss ​  | Facade and Single Wall data  | | _SAFAC_ | Solar Accerss ​  | Facade and Single Wall data  |
 | _FX_ | Surface data and surface fluxes ​ |  | | _FX_ | Surface data and surface fluxes ​ |  |
-| _VEG_ | Vegetation data (Main Model) ​ ​| ​Individual ​plants are text files |+| _VEG_ | Vegetation data  | Main 3D Model, Observed ​plants are text files |
 </​WRAP>​ </​WRAP>​