Dekker1/dekker-phd-thesis
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add structure for introduction

Browse Source
This commit is contained in:
Jip J. Dekker 2021-06-14 16:24:18 +10:00
parent 55b7a0a9db
commit 90bb70e430
No known key found for this signature in database
GPG Key ID: 517DF4A00618C9C3
2 changed files with 60 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
chapters/1_introduction.tex
View File

@ -2,6 +2,58 @@
\chapter{Introduction}\label{ch:introduction}
%************************************************
\paragraph{Overview preamble}
\jip{
\begin{itemize}
\item Topic and significance
\item Broad known (current literature) and problem - broad
\item Major aim of the thesis
\end{itemize}
}
\section{Motivation}
\jip{
\begin{itemize}
\item Known (self - current literature)
\item Problem statement specific - scope of your study
\end{itemize}
}
\section{Aims /RQs /ROs}
\jip{
\begin{itemize}
\item (description and Method?? )
\end{itemize}
}
\section{Contributions}
\jip{overview (details in the conclusion)(publications?)}
\section{Organisation of the Thesis}
This thesis is partitioned into the following chapters.
Following this introductory chapter, \emph{\cref{ch:background}} presents the background information \ldots{}.
\emph{\Cref{ch:rewriting}}
\emph{\Cref{ch:half-reif}}
\emph{\Cref{ch:incremental}}
Finally, \emph{\Cref{ch:conclusions}} is the concluding chapter of the thesis.
It reiterates the discoveries and contributions of this research to theory and practice, comments on the scope and limitations of the presented system, and presents further avenues for research in this area.
\jip{ Chapter overview – including main focus, (and method??)}
\par\noindent\rule{\textwidth}{0.4pt}
\noindent{}High-level \cmls{}, like \minizinc{}, were originally designed as a convenient input language for \gls{cp} solvers \autocite{marriott-1998-clp}.
A user would write a model consisting of a few loops or comprehensions; given a data file for the parameters, this would be rewritten into a relatively small set of constraints which would be fed whole into the solver.
The existing process for translating \minizinc\ into solver-specific constraints is a somewhat ad-hoc, (mostly) single-pass, recursive unrolling procedure, and many aspects (such as call overloading) are resolved dynamically.

14
dekker_preamble.tex
View File

@ -5,7 +5,7 @@
a4paper,
listof=totoc,
toc=bib,
]{scrbook}
]{scrreprt}
\title{Preamble of A Modern Architecture for High-Level Constraint Modelling Languages}
\author{Jip J. Dekker}
@ -24,19 +24,21 @@ toc=bib,
\begin{document}
\frontmatter{}
% \frontmatter{}
\include{chapters/0_abstract}
\mainmatter{}
% \mainmatter{}
\include{chapters/1_introduction}
\chapter{Rewriting Constraint Models}
\chapter{Background}\label{ch:background}
\input{chapters/2_background_preamble}
\chapter{Rewriting Constraint Modelling Languages}\label{ch:rewriting}
\input{chapters/3_rewriting_preamble}
\chapter{Half Reification}
\chapter{Half Reification}\label{ch:half-reif}
\input{chapters/4_half_reif_preamble}
\chapter{Incremental Processing}
\chapter{Incremental Processing}\label{ch:incremental}
\input{chapters/5_incremental_preamble}
\include{chapters/6_conclusions}