| 10 | | In order to setup the measurement locations, a measurement setup file is required. This file contains all information about the measurement coordinates, the measured variables, the type of the measurement (timeseries-, profile-, or trajectory measurements), as well as further attributes such as site names, etc.. For a description of required attributes and variables, as well as an example input file, please see [../iofiles/pids#virtual_measurement_input here]. |
| 11 | | Since revision -r4400 PALM comes with a pre-processor script [source:palm/trunk/SCRIPTS/palm_cvd palm_cvd], which is a python3 script and setup the input file according to your prescribed observation locations. |
| 12 | | Please note, all sampled variables are defined at the grid center, i.e. velocity components and fluxes are interpolated online. The following list gives an overview about the quantities that can be sampled (naming convention follows the (UC)2 standard): |
| | 10 | In order to setup the measurement locations, a setup file is required. This file contains all information about the measurement coordinates, the measured variables, the type of the measurement (timeseries-, profile-, or trajectory measurements), as well as further attributes such as site names, etc.. For a description of required attributes and variables, as well as an example input file, please see [../iofiles/pids/vm here]. |
| | 11 | Since revision -r4400 PALM comes with a pre-processor script [source:palm/trunk/SCRIPTS/palm_cvd palm_cvd], which is a python3 script to setup the input file according to your prescribed observation locations. |
| | 12 | |
| | 13 | {{{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. \\ |
| | 14 | 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. |
| | 15 | |
| | 16 | Please note, all sampled variables are defined at the grid center, i.e. velocity components and fluxes are interpolated online. The following list gives an overview about the quantities that can be sampled (naming convention follows the [UC]2 standard): |
