Changes between Version 74 and Version 75 of doc/app/iofiles/pids

Timestamp:

Nov 20, 2018 8:36:48 AM (6 years ago)

Author:

eckhard

Comment:

--

doc/app/iofiles/pids

@@ -11 +11 @@
 An example NCL-script to create a simple [[attachment:example_static|static input file]] can be found 
 [[attachment:example_driver_static.ncl|here]].
-To create a dynamic driver, PALM-4U provides the pre-processing tool [#inifor inifor], which extracts 1D/3D initialization data for the soil and atmosphere as well as boundary data for the PALM-4U domain from DWD-COSMO output. 
+To create a dynamic driver, PALM-4U provides the pre-processing tool [wiki:doc/app/iofiles/inifor INIFOR], which extracts 1D/3D initialization data for the soil and atmosphere as well as boundary data for the PALM-4U domain from DWD-COSMO output. 
 
 After reading the input files, PALM-4U performs consistency checks on the provided data.  
@@ -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 [../../inipar/#nesting_offline offline nesting]. 
+Utilizing the pre-processing tool [wiki:doc/app/iofiles/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. 
-For more information of how to create a dynamic input file, please see the '''inifor''' documention. 
+For more information of how to create a dynamic input file, please see the [wiki:doc/app/iofiles/inifor INIFOR documentation]. 
 For more detailed documentation of the input variables, please see [[attachment:PALM_input_data_standard_v1.9.pdf|Palm input data standard]].