changed chapter structure

This commit is contained in:
hannes.kuchelmeister
2020-03-23 16:53:50 +01:00
parent 546fbe1f47
commit ba2d72c81a

View File

@@ -7,15 +7,6 @@ All possible valid configurations will be generate for one use case i.e. all pos
Generate groups with preferences (explicit preferences) and configuration state (which would be for example the currently existing forest). Generate groups with preferences (explicit preferences) and configuration state (which would be for example the currently existing forest).
\section{Group Types During Evaluation}
\label{sec:Evaluation:GroupTypes}
\begin{itemize}
\item Groups shall be generated with random preferences
\item With grouped preferences: people adhere more or less to one profile (Forest Owner, Athlete, Consumer, Environmentalist)
\item Group of only one profile type: rather homogenous group
\end{itemize}
\section{Metric} \section{Metric}
\label{sec:Evaluation:Metrics} \label{sec:Evaluation:Metrics}
@@ -34,7 +25,10 @@ For the evaluation a metric to evaluate by is needed. The proposed metric for us
\section{Effect of Stored Finished Configurations} \section{Effect of Stored Finished Configurations}
\label{sec:Evaluation:EffectFinishedConfiguration} \label{sec:Evaluation:EffectFinishedConfiguration}
When evaluating just a subset of stored finished configurations it is important to avoid outliers. This is the reason why a process inspired by cross validation is be used. The configuration database is randomly ordered and sliced into sub databases of the needed size. As an example, if the evaluated stored data size is 20, a configuration database containing 100 configurations is split into five sub databases of size 20. Now the evaluation is done on each of the sub databases and as a result the average is taken. When evaluating just a subset of stored finished configurations it is important to avoid outliers. This is the reason why a process inspired by cross validation is used. The configuration database is randomly ordered and sliced into sub databases of the needed size. As an example, if the evaluated stored data size is 20, a configuration database containing 100 configurations is split into five sub databases of size 20. Now the evaluation is done on each of the sub databases and as a result the average is taken.
\section{Use Case}
\label{sec:Evaluation:UseCase}
\section{Generating Data} \section{Generating Data}
@@ -42,6 +36,13 @@ When evaluating just a subset of stored finished configurations it is important
The whole process explained in this section is visualized in \autoref{fig:Evaluation:GeneratingDataProcess}. The whole process explained in this section is visualized in \autoref{fig:Evaluation:GeneratingDataProcess}.
\begin{figure}
\centering
\includegraphics[width=1\textwidth]{./figures/60_evaluation/bpmn_evaluation_input_data_generation.pdf}
\caption{The process used for generating data for the evaluation.}
\label{fig:Evaluation:GeneratingDataProcess}
\end{figure}
\subsection{Generating Unfinished Configurations} \subsection{Generating Unfinished Configurations}
Unfinished configurations are generated using all finished configurations and taking a subset of the contained characteristics. This way all generated configurations will be valid and lead to valid solutions. For the results that are presented in this chapter around $\frac{1}{7} \approx 15\%$ of characteristics is kept. Unfinished configurations are generated using all finished configurations and taking a subset of the contained characteristics. This way all generated configurations will be valid and lead to valid solutions. For the results that are presented in this chapter around $\frac{1}{7} \approx 15\%$ of characteristics is kept.
@@ -80,19 +81,21 @@ For the forest use case, the idea is that there are multiple types of user profi
\label{fig:Evaluation:DataGeneration} \label{fig:Evaluation:DataGeneration}
\end{figure} \end{figure}
These user profiles can be used to generate rather homogenous groups but also to create groups that have interests that are more conflicting. For completely random groups a uniform distribution is used to create more chaotic groups. The whole process is shown in \autoref{fig:Evaluation:GeneratingDataProcess}. These user profiles can be used to generate rather homogenous groups but also to create groups that have interests that are more conflicting. The following group types are generated:
\begin{itemize}
\item random groups (preferences are uniformly random)
\item heterogeneous groups (people adhere to one preference profile like forest owner, athlete, consumer, environmentalist)
\item homogeneous groups (only one preference profile for all group members which in this evaluation is the forest owner)
\end{itemize}
\todo[inline]{explain preference profiles}
\begin{figure} \section{Hypothesis}
\centering \label{sec:Evaluation:Scenario}
\includegraphics[width=1\textwidth]{./figures/60_evaluation/bpmn_evaluation_input_data_generation.pdf}
\caption{The process used for generating data for the evaluation.}
\label{fig:Evaluation:GeneratingDataProcess}
\end{figure}
\section{Results} \section{Results}
\label{fig:Evaluation:Results} \label{sec:Evaluation:Results}
\subsection{Choosing Happiness and Unhappiness Parameter} \subsection{Choosing Happiness and Unhappiness Parameter}