Differences

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

--- apps:forcingmanager [2020/04/14 15:17] – [Usage of Forcing File] enviadmin
+++ apps:forcingmanager [2021/03/19 10:08] – [Input Data] enviadmin
@@ Line 19: / Line 19: @@
 {{:apps:fo_csv_header.png?nolink|}}
-After indicating your CSV settings (separators and heading), deciding whether you would like to force either radiation or cloud coverage, and defining the measurement heights of your data, you can import your data to an ENVI-met Forcing File.
+After indicating your CSV settings (separators and heading), deciding whether you would like to force either radiation or cloud coverage, and defining the measurement heights of your data, you can import your data to an ENVI-met Forcing File. Regarding the columns for radiation / cloud coverage: Depending on the data you have, you can either enter the cloud cover for the different height levels (in octas) or the radiation (splitted into shortwave direct, diffuse and longwave radiation). Depending on what you choose, you have to tell the forcing manager how to interpret these columns, as cloud cover or as radiation data.
@@ Line 25: / Line 25: @@
 Using input data from local weather files can be a good way to realistically force your simulation boundary conditions. There are many types of weather files available and ENVI-met currently allows the import of *.EPW and *.TRY weather files. The Forcing Manager automatically reads the file format and converts it into a forcing file usable in the simulation process.
+**Choosing what to force**
+When preparing a simulation, you need to tell ENVI-met which of the data provided by the full forcing shall be used in the simulation. We only recommend forcing precipitation if you planning to simulate very long periods of time (several months). To learn about precipitation you can click here.
 ===== Usage of Forcing File =====