Changes between Version 6 and Version 7 of doc/app/iofiles/pids/vm

Timestamp:

Oct 21, 2020 12:25:55 PM (5 years ago)

Author:

suehring

Comment:

--

doc/app/iofiles/pids/vm

@@ -125 +125 @@
 === [=#example '''Creating input setup files'''] ===
 
+palm_cvd has two options. First, the custom-mode, where you can manually setup a variable number of measurements points (in UTM coordinates) and specify the respective output variables yourself. However, so far only point- or tower measurements are possible, complex trajectories cannot be described this way.
+In the second mode, palm_cvd already reads existing NetCDF files from observation campaigns and extract the required information. However, this requires that the input NetCDF files are already formatted according to the [UC]2 data standard.
+
 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. \\
-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.  
-
+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 (custom-mode). 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.  
+
+{{{palm_cvd}}} reads a config file (a default config file is available in /trunk/SCRIPTS/.cvd.config.default). The measurement input file requires a number of global attributes which you can specify accordingly. If you cannot give any reasonable information here, just leave it empty. 
+
+{{{
+[global]
+
+author = name, mail-adress
+contact_person = 
+acronym = 
+comment = 
+data_content = 
+dependencies = 
+keywords = 
+source = 
+campaign = iop 1
+location = B
+site = Ernst Reuter Platz
+institution = Leibniz Universität Hannover, Institute of Meterology and Climatology # for (UC)2 conform in/output please follow guidelines in table A3
+palm_version = 6.0
+references =
+}}}
+
+In case there exist already NetCDF files with the required metadata, you need to specify the path to the data in the input-section: 
+{{{
+[input]
+
+data_path = < path to your observational input data >
+}}}
+If you do not have such files, just leave it empty.
+
+The output path and name of your setup file need to be specified here:
+{{{
+[output]
+
+output_path     = < your output path >
+output_filename = vm_driver
+}}} 
+
+In case you want to specify measurement locations manually, you need to adjust the following section in .cvd.config.xxx:
+{{{
+[custom_positions]
+
+# Give the number of custom sampling coordinates
+number_positions = 4
+
+# Give site coordinates: E_UTM (m), N_UTM (m), z (m).
+# Please give z in meters above ground.
+#
+#             [ E_UTM,    N_UTM,      z (agl) ]
+
+coordinates1: [ 387670.0, 5819090.0,  4.0     ]
+coordinates2: [ 387676.0, 5819139.0,  1.0     ]
+coordinates3: [ 387630.0, 5819065.0,  41.0    ]
+coordinates4: [ 387270.0, 5819191.0,  8.5     ]
+
+# Give the variables that shall be sampled. Note, there is a 
+# number of default variables that will be always sampled, which is:
+# u, v, w, theta and hus (mixing ratio).
+# On top of these, you can individually prescribe further variables
+# for each site. In order to prescribe further variables, please
+# follow the naming convention defined in the [UC]2 data standard.
+
+vars_to_be_measured1: [ "u", "v", "w", "theta", "rlus", "rsus" ]
+vars_to_be_measured2: [ "rnds", "wdir" ]
+vars_to_be_measured3: [ "us" ]
+vars_to_be_measured4: [ "utheta", "vtheta", "wtheta", "wspeed" ]
+}}}
+
+A list of variables that are currently supported and their naming convention can be found [../../../virtual_measurement_parameters here].