X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=report1%2Feval.tex;h=77d924fb4dcf265fc6b1b8dd72e010747e257e91;hb=61c7d98a49feb742307aed59fb3ea18c96119425;hp=131029e21fde835699fe736a2d77e6920ac96b92;hpb=65064c86ccd584dce8bff8927dda8d8bc2e9d408;p=mc1516pa.git

diff --git a/report1/eval.tex b/report1/eval.tex
index 131029e..77d924f 100644
--- a/report1/eval.tex
+++ b/report1/eval.tex
@@ -1,11 +1,23 @@
 \section{Conclusion}
-Detailed benchmarking and thorough comparison of the results still has to be done.
-%thoughts on the performance of the object-centered approach are needed here
-The coordinate-based approach revealed that the following factors affect the feasibility of solving a particular sokoban field:
+Detailed benchmarking and thorough comparison of the results still has to be
+done.
+
+The object-based approach shows to heavily depend on the number of boxes.
+Describing the goal state for $n$ boxes needs a formula of $n!$ size. The size
+of the encoding also increases with the number of free blocks. When a screen is
+circular the parser also parses the blocks on the sides to be free spaces
+whereas they can never be reached. By improving the parser to disregard those
+positions we can increase the performance too.
+
+The coordinate-based approach revealed that the following factors affect the
+feasibility of solving a particular \emph{sokoban} field:
 \begin{itemize}
   \item Overall size of a field
   \item Proximity of boxes to the man
   \item Number of boxes (to a lesser extent)
 \end{itemize}
-A possible improvement for the coordinate-based approach is the elimination of outer walls, which can reduce overal field sizes.\\
-In total, the material obtained by implementing two different ways to encode a sokoban solver might give the us the ability to approach the next assignment in a more elaborate way.
+A possible improvement for the coordinate-based approach is the elimination of
+outer walls, which can reduce overall field sizes.\\
+In total, the material obtained by implementing two different ways to encode a
+\emph{sokoban} solver might give the us the ability to approach the next
+assignment in a more elaborate way.