# OPAL++

This page collects information which is specific to OPAL++, written by Laszlo Daroczy.

If you are using this tool for a publication, cite this reference:
Daróczy, L., Janiga, G. and Thévenin, D., Systematic analysis of the heat exchanger arrangement problem using Multi-Objective Genetic Optimization. Energy 65, (2014) 364-373.

## Where to find information

Gabor, Robin, Sebastian, Kristin, and Emeel

## Where to find Install media

• Binaries for the PC-Cluster and Neumann can be found in this directory on the PC-Cluster
/global/shared/INSTALLATION/OPAL2/Distro.tar.gz

# Pages tagged with OPAL++

list created automatically

# Pages in Namespace OPAL

Below, you find an automatically created list of pages existing in the namespace opal, and its subnamespaces. This list may contain dublicate pages as the tagged pages. However insuffiently tagged pages are recovered.

list created automatically

# Notes on OPAL++

## OPAL2S and OPAL2S.NATIVE

OPAL2S commands run only if individual is still valid to that point of the simulation script commands run in any case even if the individual is invalid, e.g. for clean up, or log processes

Detailed explanation:

Click to display ⇲

Click to hide ⇱

copied from the manual
The NUMERIC simulation script interpreter is a dual interpreter, i.e. every command has two different versions. For the first variant OPAL2S is the main module, while for the second OPAL2S.NATIVE is the main module. Every command and sub-module is available in both groups. OPAL2S behaves, as if all commands would be placed in an if(valid) command endif branch, i.e., these commands are executed if and only if the individual is valid at that point of the evaluation. During evaluation of elements several problems and errors can occur. E.g. meshing problems can occur during the evaluation of the individual. In such a case executing all commands is meaningless (e.g. we cannot start the simulation without a mesh). To ease the setup of the optimizations, when using OPAL2S interpreter, commands are only executed, if the individual is still valid at the point of execution. Invalidating an individual is the task of the user. However, if a command has to be executed always (e.g. clean-up operation), it can be accessed in the OPAL2S.NATIVE interpreter. For most users, the first variant is enough, that’s why it has a shorter form. In what follows, all commands will be detailed only once.