Add initial version for conclusion preamble
This commit is contained in:
parent
5ced7ae5c1
commit
8f88cfb86f
@ -2,11 +2,36 @@
|
|||||||
\chapter{Conclusions}\label{ch:conclusions}
|
\chapter{Conclusions}\label{ch:conclusions}
|
||||||
%************************************************
|
%************************************************
|
||||||
|
|
||||||
|
\noindent{}High-level \cmls{} make it easy to express decision problems.
|
||||||
|
They allow the modeller to reason at the level close to the problem, while the tooling of the language is able to create specifications for a range of potential \solvers{}.
|
||||||
|
Although the importance of creating specifications that can be solved efficiently is well-known, changes in the usage of these languages are raising questions about the time required to perform this transformation.
|
||||||
|
First, \constraint{} models are solved using low-level \solvers{}, such as \gls{mip} and \gls{sat}.
|
||||||
|
Because of the level at which these technologies reason, specifications are more sizable and the process to reach them is more complex.
|
||||||
|
Second, we have seen a development of the use of meta-search heuristics.
|
||||||
|
These heuristics incrementally adjust the \constraint{} model, after which it has to be rewritten to be solved.
|
||||||
|
Both these methods put additional pressure on the rewriting process, which can often be a bottle-neck in the overall process.
|
||||||
|
|
||||||
|
In the previous chapters of this thesis, we have explored in detail and presented improvements to the process of rewriting high-level \constraint{} models into \solver{} specifications.
|
||||||
|
These improvements focus both on the performance of the rewriting process in general, and for incremental adjustments of \constraint{} models in particular.
|
||||||
|
Crucially, the proposed improvements in the performance of the rewriting process themselves do not impact the quality of the \solver{} specification constructed.
|
||||||
|
This chapter presents the conclusions of this thesis.
|
||||||
|
We present a summary of the research and its contributions and discuss the future work arising from them.
|
||||||
|
|
||||||
|
\paragraph{Architecture}
|
||||||
|
|
||||||
|
\paragraph{Half Reification}
|
||||||
|
|
||||||
|
\paragraph{Incremental}
|
||||||
|
|
||||||
|
\paragraph{Summary}
|
||||||
|
|
||||||
|
\par\noindent\rule{\textwidth}{0.4pt}
|
||||||
|
|
||||||
This section should probably have the following components:
|
This section should probably have the following components:
|
||||||
|
|
||||||
\begin{itemize}
|
\begin{itemize}
|
||||||
\item Quick restatement of problem/importance/motivation
|
\item Quick restatement of problem/importance/motivation
|
||||||
\item Contributions, preferrably discussed per section. Relate them back to the research objectives.
|
\item Contributions, preferably discussed per section. Relate them back to the research objectives.
|
||||||
\item Limitation and Future work. This can also focus on what my work makes possible, not just what to explore next.
|
\item Limitation and Future work. This can also focus on what my work makes possible, not just what to explore next.
|
||||||
\item Concluding remarks. Maybe a summary of the findings.
|
\item Concluding remarks. Maybe a summary of the findings.
|
||||||
\end{itemize}
|
\end{itemize}
|
||||||
|
Reference in New Issue
Block a user