One aspect of the modularity of IMDI consists of the optional activation of the individual tasks of an experiment. If, for example, the parameter "postprocessing" of the setup file is set to "yes", a script will be generated for a previously defined postprocessing task.  Postprocessing instructions for the model have to be included into the system from the beginning. The task (script) may be launched synchronously with the model integration, i.e. after each integration chunk by the run-script, the model output is processed by the postprocessing tasks. Alternatively, the task script can be launched asynchronously after a longer integration period.

The default is that all tasks which are available for the current model are generated and called synchronously.

Possible tasks are

• the task RUN, which is the model integration itself. The corresponding run script (expid.run) is the main script and the experiment is started by its submission.
• the task PRE, the preprocessing task, which provides forcing and input data (expid.pre).
• the task POST, the post processing task, which does the postprocessing of the model output (expid.post)
• the task MON, which allows the user to graphically monitor the experiment execution (expid.mon)
• the task ARCH, which does the archiving of raw and derived data (expid.arch).
• the tasks DBFILL, which fills data into the WDCC/Cera data base archive (expid.dbfill).