Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
filereference:output:start [2015/12/09 22:45] – [Level 3: Metatadata information in EDX file] enviadmin | filereference:output:start [2021/07/26 17:58] – enviadmin | ||
---|---|---|---|
Line 4: | Line 4: | ||
Each ENVI-met simulation creates a huge amount of data which is organized in different files and folders. | Each ENVI-met simulation creates a huge amount of data which is organized in different files and folders. | ||
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 | + | * **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. From Version 5 on, ENVI-met provides different options to analyse |
- | * **Binary Files (EDX/ | + | * **Binary Files (EDX/ |
+ | |||
+ | **In order to use advanced analysis functions like Time Series in LEONARDO, it is strongly recommended to store only one simulation run in the same folder and not to mix different model runs.** | ||
===== Name and storage logic ===== | ===== Name and storage logic ===== | ||
Line 16: | Line 18: | ||
==== Level 1: Storage by folder name ==== | ==== Level 1: Storage by folder name ==== | ||
- | [{{ : | + | {{ : |
- | The uppermost level of file organisation starts by sorting the output files into subfolders of the selected output folders. The figure above shows the folder structure of a typical ENVI-met output folder (some folders are only existing in the Advanced version of ENVI-met). All files in one folder are of the same structure and contain the same set of information, | + | The uppermost level of file organisation starts by sorting the output files into subfolders of the selected output folders. The figure above shows an example of the folder structure of a typical ENVI-met output folder (some folders are only existing in the Advanced version of ENVI-met, others may be added in the course of time). All files in one folder are of the same structure and contain the same set of information, |
- | - **Atmosphere** | + | - **[[filereference: |
- | - **Buildings** | + | - **[[filereference: |
- | - **Inflow** | + | - **[[filereference: |
- | - **Log** | + | - **Log** |
- | - **Pollutants** | + | - **[[filereference: |
- | - **Radiation** | + | - **[[filereference: |
- | - **Receptors** | + | - **[[filereference: |
- | - **Soils** \\ | + | - **[[filereference: |
- | - **SolarAccess** \\ | + | - **[[filereference: |
- | - **Surface** | + | - **[[filereference: |
+ | - **[[filereference: | ||
- | In addition, the BIOMet tool will create further folders, by default labled " | + | In addition, the BIOMet tool will create further folders, by default labled " |
Future versions or additional modules of ENVI-met will create further folders and file, but the general concept of storge will be the same. | Future versions or additional modules of ENVI-met will create further folders and file, but the general concept of storge will be the same. | ||
Line 37: | Line 40: | ||
Sorting the output files into folders provides a first system of order in the output data. However, once a file has been moved out of its folder or if several simulations come together, this system is not unique and not persistent. As a solution, the ENVI-met file name generation scheme allows a direct identification of the simulation files and their content. | Sorting the output files into folders provides a first system of order in the output data. However, once a file has been moved out of its folder or if several simulations come together, this system is not unique and not persistent. As a solution, the ENVI-met file name generation scheme allows a direct identification of the simulation files and their content. | ||
- | [{{ : | + | {{ : |
Each ENVI-met output filename consists of 3 parts: | Each ENVI-met output filename consists of 3 parts: | ||
- **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, | - **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, | ||
- **Type identifier**: | - **Type identifier**: | ||
- | - **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 ('' | + | - **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 ('' |
Line 52: | Line 55: | ||
==== Sumary on File Identifiers ==== | ==== Sumary on File Identifiers ==== | ||
- | _AT_ : Atmospheric data file | + | <WRAP box left 80%> |
+ | ^ ID ^ Content ^ Remark ^ | ||
+ | | _AT_ | Atmospheric data | ||
+ | | _BLDG_ | Building data | Both STATIC and DYNAMIC | ||
+ | | _POLU_ | Pollutants | ||
+ | | _SO_ | Soil data | | | ||
+ | | _SA_ | Solar Access | ||
+ | | _SAFAC_ | Solar Accerss | ||
+ | | _FX_ | Surface data and surface fluxes | ||
+ | | _VEG_ | Vegetation data | Main 3D Model, Observed plants are text files | | ||
+ | </ | ||
+ | |||
+ | <WRAP clear></ | ||
+ | |||
+ | Other files are ASCII files. | ||
- | (to be cont.) |