Changes between Version 72 and Version 73 of doc/app/iofiles/pids

Timestamp:

Aug 3, 2018 2:47:10 PM (7 years ago)

Author:

suehring

Comment:

--

doc/app/iofiles/pids

@@ -488 +488 @@
 
 The dynamic input file (see [../#PIDS_DYNAMIC PIDS_DYNAMIC]) comprises all data which might change depending on the day of year, such as initialization data, large-scale forcing tendencies or boundary data.  
-Utilizing the pre-processing tool [#inifor inifor], the respective data can be derived directly from the larger-scale [[http://www.cosmo-model.org/content/default.htm|COSMO model]] (except for active or passive chemical components which are not considered in the COSMO model). This way, the dynamic input file acts as a interface between a larger-scale model and PALM-4U, being a so-called [#nesting_offline offline nesting]. 
+Utilizing the pre-processing tool [#inifor inifor], the respective data can be derived directly from the larger-scale [[http://www.cosmo-model.org/content/default.htm|COSMO model]] (except for active or passive chemical components which are not considered in the COSMO model). This way, the dynamic input file acts as a interface between a larger-scale model and PALM-4U, being a so-called [../../inipar/#nesting_offline offline nesting]. 
 In case of a [../../nestpar nested] model run (online), only the parent domain considers the dynamic input_file for inititialization and offline-nesting, while embedded child models itself will be initialized and forced via its parent domains.    
 In order to activate input from the dynamic input file, setting of [../../inipar#initializing_actions initializing_actions] = 'inifor' is required.