correct direction. After that the problem is solved as usual and thus notifying
the user wether the LURD leads to a solvable state. Note that when the LURD is
empty the program behaves like there was no LURD given.
+
+\subsection{Evaluation}
+The assignment was a very interesting and challenging assignment. However, we
+feel that we could not get the most out of it due to several reasons.
+
+First of all it was a hassle to get to know sylvan and to be able to use the
+package. There were some trivial errors in the sylvan package that made
+debugging a lot harder. One of those errors was malformed dot output for
+printing BDDs. In the meantime we have made a pullrequest to fix that.
+
+Secondly, due to the relatively short introduction to BDDs the gap between our
+knowlegde and the knowledge required to build such a solver is quite big. This
+lead to startup problems.
+
+% Maybe something about the complexity of the assignment