| 123 | | For an example input file, please see [[attachment:vm_driver|here]]. |
| | 123 | \\\\ |
| | 124 | |
| | 125 | === [=#example '''Creating input setup files'''] === |
| | 126 | |
| | 127 | An example setup file for virtual measurements can be found [[attachment:vm_driver|here]]. This file was created with the script [source:palm/trunk/SCRIPTS/palm_cvd palm_cvd] which comes with revision -r4400. To execute the script just run {{{palm_cvd .cvd.config_<your file suffix>}}}. [source:palm/trunk/SCRIPTS/palm_cvd palm_cvd] can be steered with a configuration file. In case 'real-world' campaigns shall be emulated, [source:palm/trunk/SCRIPTS/palm_cvd palm_cvd] reads the relevant coordinate information of the observational data, the sampled quantities as well as further metatdata, and merges these into a setup file, so that PALM can internally setup the corresponding sampling locations on the numeric grid. Therefore, [source:palm/trunk/SCRIPTS/palm_cvd palm_cvd] assumes that the 'real-world' data follows the (UC)2 data standard. With this approach, trajectory measurements (e.g. airborne- or other mobile measurements), stationary tower measurements, or vertical soundings can be emulated in PALM. \\ |
| | 128 | Further, independent of any campaign data, it is possible to prescribe additional sites with [source:palm/trunk/SCRIPTS/palm_cvd palm_cvd], where the respective UTM coordinates and the sampled quantities need to be specified in the config file. At the moment only stationary coordinates can be specified in the config file. However, it is planned to extend palm_cvd and its config file to be able to specify also trajectory measurements or more advanced sampling approaches such as Lidar scans. |
| | 129 | |
