Index: /reasoner/evaluation.tex
===================================================================
--- /reasoner/evaluation.tex	(revision 171)
+++ /reasoner/evaluation.tex	(revision 172)
@@ -75,5 +75,5 @@
 $$
 %
-The traditional measure applied to an IVML model would determine the number of top-level variables and the number of constraints. This can be achieved as follows, i.e., we disable measuring nested variables and expressions, an enable counting constraints and remaining variables by setting the type weight for $cpx_v(e)$ and the constraint weight for $cpx_c(e)$ both to 1. All remaining weights, in particular for constraint expressions are set to 0.
+The traditional measure applied to an IVML model would determine the number of top-level variables and the number of constraints. This can be achieved as follows, i.e., we disable measuring nested variables and expressions, an enable counting constraints and remaining variables by setting the type weight for $cpx_v(e)$ and the constraint weight for $cpx_c(e)$ both to 1. All remaining weights, in particular for constraint expressions are set to 0. The traditional measures can now be expressed by $cpx_c(cfg)/cpx_v(cfg)$ for a given configuration $cfg$.
 %
 $$
@@ -104,12 +104,9 @@
 $$
 
-For short, we enable considering nested variables and the contents of expressions. Compounds and containers are considered with a double weight compared with all other types. Most of the constraint tree nodes are weighted by 1 including access to the actual instance of a compound (\IVMLself{}), except for container iterator operations that we weight by a higher and access to the value of decision variables and constants that we weight by a lower value.
+For short, we enable considering nested variables and the contents of expressions. Compounds and containers are considered with a double weight compared with all other types. Most of the constraint tree nodes are weighted by 1 including access to the actual instance of a compound (\IVMLself{}), except for container iterator operations that we weight by a higher and access to the value of decision variables and constants that we weight by a lower value. For a given IVML model, we just calculate $cpx_v(cfg) + cpx_c(cfg)$ as overall complexity measure.
 
 \subsection{Results}\label{sectResults}
 
-% w(compound) = 2, w(container) = 2, w(variable) = 0.25, w(constant) = 0.25, w(call) = 0, w(iter) = 5
-
-
-\TBD{Keep or remove that section. However, some basic performance evaluations should not be so difficult. All executions need multiple runs, in particular to even out JIT compilation. It seems that this is done during/after the second reasoning run. Potential topics:
+\TBD{Potential topics:
 
 \begin{itemize}