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 [2017/11/10 09:26] – external edit 127.0.0.1 | filereference:output:start [2018/03/07 16:33] – [Sumary on File Identifiers] enviadmin | ||
---|---|---|---|
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/ | + | * **Binary Files (EDX/ |
===== Name and storage logic ===== | ===== Name and storage logic ===== | ||
Line 16: | Line 16: | ||
==== 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 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, | ||
- | - **Atmosphere** [[filereference: | + | - **[[filereference: |
- **Buildings** | - **Buildings** | ||
- **Inflow** | - **Inflow** | ||
Line 38: | Line 38: | ||
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: | ||
Line 53: | Line 53: | ||
==== Sumary on File Identifiers ==== | ==== Sumary on File Identifiers ==== | ||
- | _AT_ : Atmospheric data file | + | <WRAP box left 80%> |
+ | <WRAP box left 40%> | ||
+ | ^ ID ^ Content ^ | ||
+ | | _AT_ | Atmospheric data | | ||
+ | | _BLDG_ | Building data (static or dynamic) | ||
+ | | _POLU_ | Pollutants | ||
+ | | _SO_ | Soil data | | ||
+ | | _SA_ | Solar Access (Main Model) | ||
+ | | _SAFAC_ | Solar Accerss (3D Facade data) | | ||
+ | | _FX_ | Surface data and surface fluxes | ||
+ | | _VEG_ | Vegetation data (Main Model) | ||
+ | </ | ||
+ | |||
+ | Other files are ASCII files. | ||
- | (to be cont.) |