| 3 | | PALM provides a standardized way via the NetCDF data format to input e.g. global attributes, topography data or surface properties, vegetation properties, etc., as well as initialization data and boundary conditions for the prognostic variables. |
| | 3 | == PALM Input Data Standard (PIDS) == |
| | 4 | PALM provides a standardized way to input e.g. global attributes, topography data or surface properties, vegetation properties, etc., as well as initialization data and boundary conditions for the prognostic variables via the NetCDF data format. In the following, these files are referred to as so-called '''drivers'''. |
| 5 | | Input variables are distinguished between [#./static static], [#./dynamic dynamic], [#./rad radiation], [#./chem chemistry], [#./aerosol aerosol] and [#./vm virtual measurements] input variables, while for each a separate input file exists. |
| 6 | | The static input file, indicated by the filename suffix _STATIC, contains all static information, such as topography, geographical latitude and longitude, surface and vegetation information. |
| 7 | | The dynamic input file, indicated by the filename suffix _DYNAMIC, contains dynamic information on the initial state of the atmosphere or time-dependent boundary conditions. |
| 8 | | The radiation input file, indicated by suffix _RAD, contains static and dynamic information on radiation properties such as trace gas profiles or sky-view factors. |
| 9 | | The chemistry input file, indicated by suffix _CHEM, contains static and dynamic information on chemical species and emissions. |
| 10 | | The aerosol input file, indicated by suffix _SALSA (from the aerosol module name "SALSA"),contains aerosol emission information. |
| 11 | | |
| 12 | | == How to create drivers == |
| 13 | | You can use [source:palm/trunk/SCRIPTS/create_basic_static_driver.py this python script] as a starting point for creating your own static driver. Also, the [source:palm/trunk/SCRIPTS/palm_csd palm_csd] tool can be used for this purpose (not documented yet). To create a dynamic driver, PALM 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 domain from DWD-COSMO output and the tool [wiki:doc/app/iofiles/wrf_interface WRF interface], which extracts meteorological and chemical initialization and boundary data from WRF and CAMx outputs. |
| 14 | | After reading the input files, PALM performs consistency checks on the provided data. |
| 15 | | To create a setup file for virtual measurements, you can use the [source:palm/trunk/SCRIPTS/palm_cvd palm_cvd] script. |
| 16 | | |
| 17 | | == Details of input files == |
| 18 | | All applied input variables are listed and explained in the following pages and additional remarks on restrictions and initialization are given. |
| | 6 | All available input variables are listed and explained in the following pages and additional remarks on restrictions and initialization are given. |
| 22 | | Follow the links below to go to the respective description: |
| 23 | | * [./static static driver] \\ |
| 24 | | * [./dynamic dynamic driver] \\ |
| 25 | | * [./rad radiation driver] \\ |
| 26 | | * [./chem chemistry driver] \\ |
| 27 | | * [./aerosol aerosol driver] \\ |
| 28 | | * [./vm virtual measurements file] \\ |
| | 10 | Input data is distinguished between [#./static static], [#./dynamic dynamic], [#./rad radiation], [#./chem chemistry], [#./aerosol aerosol], and [#./vm virtual measurements] input variables. For each category a separate PIDS driver file can be used: |
| | 11 | |
| | 12 | * The static input file ({{{PIDS_STATIC}}}), contains all static information, such as topography, geographical latitude and longitude, surface and vegetation information. For details, see [./static static driver] \\ |
| | 13 | * The dynamic input file ({{{PIDS_DYNAMIC}}}) , contains dynamic information on the initial state of the atmosphere or time-dependent boundary conditions. For details, see [./dynamic dynamic driver] \\ |
| | 14 | * The radiation input file ({{{PIDS_RAD}}}, contains static and dynamic information on radiation properties such as trace gas profiles or sky-view factors (attenttion: implementation is under way). For details, see [./rad radiation driver] \\ |
| | 15 | * The chemistry input file ({{{PIDS_CHEM}}}) contains static and dynamic information on chemical species and emissions. For details, see [./chem chemistry driver] \\ |
| | 16 | * The aerosol input file ({{{PIDS_SALSA}}}, after the aerosol module name "SALSA"),contains aerosol emission information. For details, see [./aerosol aerosol driver] \\ |
| | 17 | * The virtual measurement input file ({{{PIDS_VM}}}, comprises metadata to perform on-the-fly virtual measurements. For details, see [./vm virtual measurements file] \\ |
| | 18 | * PIDS_UVEM (description coming soon) |
| | 19 | * PIDS_WTM (description coming soon) |
| | 20 | |
| | 21 | There are additional drivers if the RRTMG radiation model is used: |
| | 22 | * Longwave radiation driver (rrtmg_lw.nc) |
| | 23 | * Shortwave radiation driver (rrtmg_sw.nc) |
| | 24 | RRTMG is shipped along with standard drivers that contain standard atmospheric properties of pressure, temperature, humidity, greenhouse and trace gases up to the top of the atmosphere which can be copied to the {{{INPUT}}} folder if no other data is available. |
| | 35 | |
| | 36 | == Preparation of the static driver == |
| | 37 | PALM comes with two tools that can help to create the static driver: |
| | 38 | |
| | 39 | 1. You can use the python script [source:palm/trunk/SCRIPTS/create_basic_static_driver.py create_static_driver] as a starting point for creating your own static driver. The script contains an example how to populate the driver with generic topography. |
| | 40 | |
| | 41 | 2. The tool [source:palm/trunk/SCRIPTS/palm_csd palm_csd] tool has been developed in the course of [http://uc2-mosaik.org the MOSAIK project], and which allows to create comprehensive static driver files, but which relies on pre-processed NetCDF data. For the German cities of Berlin and Hamburg the required data can be provided on request (hettrich@muk.uni-hannover.de). You can adapt the script for other cities. For a detailed documentation, see [/palm_csd palm_csd documentation]. |
| | 42 | |
| | 43 | == Preparation of the dynamic driver === |
| | 44 | To create a dynamic driver, PALM 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 domain from DWD-COSMO output and the tool [wiki:doc/app/iofiles/wrf_interface WRF interface], which extracts meteorological and chemical initialization and boundary data from WRF and CAMx outputs. |
| | 45 | |
| | 46 | == Preparation of the virtual measurements driver === |
| | 47 | To create a setup file for virtual measurements, you can use the [source:palm/trunk/SCRIPTS/palm_cvd palm_cvd] script. |
