source: JEM-EUSO/esaf_lal/tags/v1_r0/esafdoc/DevelopersGuide/Config.tex @ 117

%------------------------------------------------------------------------------
\section{EsafConfigClass and configuration files}% \ref{Euso Simulation and Analysis Framework, pallas & ddm}
%------------------------------------------------------------------------------

Many \ESAF{} Classes are initialized via config files contained in \path{config/} directory.
The interface between \code{.cfg} files and classes is handled by the \code{Config} singleton and \code{EusoConfigurable} objects.

All the classes inheriting from \code{EusoConfigurable} can access the parameters stored in the \code{.cfg} files  using \code{EusoConfigurable::Conf()} interface.
\code{Conf()} returns a pointer to the correct \code{EusoConfigFileParser} object stored in \code{Config}.
Each class must be properly set to get the correct parser from \code{Conf()}.

This is done adding the following line in the class definition:

\begin{displaycode}
EsafConfigClass(Optics, ParamOpticalSystem)
\end{displaycode}

\code{EsafConfigClass()} macro has two arguments, the first is \code{ClassType} and the second \code{ClassName}.
\code{ClassType} refers to the \path{config/} subdirectory where the class config file is, while \code{ClassName} is the file name.
In \ESAF{} each class has its own config file.% Violations of this rule must be considered exceptional and must always be well motivated.

A detailed description of \ESAF{} configuration system can be found in \cite{bib:esaf}