Home

Context Navigation

Version 3 (modified by kanani, 7 years ago) (diff)
--

PALM Program control

How to set up and run the model, how to process and interpret model output....

The main goal of WP-M3 will be the internal validation of PALM-4U during its entire development process, involving several steps of a well-defined testing procedure, in close discussion with the coordinator (WP-C). These include code revision as well as testing of functionality of the different PALM-4U components and their interactions. Further, continuous performance checks (benchmarking) of the new components will be performed on supercomputer systems, optimizations PALM-4U with respect to computing time and scalability of the code on large numbers of processor cores.

Feedback of the testing process will be returned to the PALM-4U developers, who will incorporate the revisions during the further code development. The workflow of this entire process is visualized in Fig. 1.
An essential goal of MOSAIK is to demonstrate that PALM-4U is able to run with limited computer resources – as it is the case e.g. in city-planning applications. These tests will be done on a demonstration PC with a reasonable number of processor cores. Besides these more technical tests, a verification of PALM-4U against the VDI requirements and a comparison with results from existing urban climate models will be part of WP-M3.

The testing procedure requires a pre-definition of specific simulation set-ups, covering the main application scenarios. A documentation of the set-ups will be provided on the Trac server, and selected PALM-4U results will be added there at the end of the project.

Model setup

Control parameters
- Initialization
- Runtime

Optional parameter packages
'Alphabetical list of all parameters'

Model operation

Launching a simulation (mrun, mrungui, example of minimum configuration file, Interactive mode and debugging)
Monitoring a simulation (Monitoring batch jobs: PALM watchdog)
Simulation chains (Initialization and restart runs)