proposal/p.tex

   1 \documentclass[a4paper]{article}
   2
   3 \usepackage[british]{babel}
   4 \usepackage[british]{isodate}
   5 \usepackage[hidelinks]{hyperref}
   6 \usepackage{booktabs}
   7 \usepackage{geometry}
   8 \usepackage{tabu}
   9
  10 \title{Research Internship Proposal}
  11 \date{\printdate{22.9.2016}}
  12 \author{Mart Lubbers (s4109503)}
  13
  14 \begin{document}
  15 \pagenumbering{gobble}
  16 \thispagestyle{empty}
  17 \clearpage
  18 \maketitle
  19 \subsection*{Practical information}
  20 \begin{table}[h]
  21         \centering
  22         \begin{tabu}{p{8em}X}
  23                 \toprule
  24                 \textbf{Start date} & September 2016\\
  25                 \midrule
  26                 \textbf{End date} & February 2017\\
  27                 \midrule
  28                 \textbf{Research group} & Software Science\\
  29                 \midrule
  30                 \textbf{Supervisors} & Rinus Plasmeijer, Pieter Koopman\\
  31                 \midrule
  32                 \textbf{Topics} & Functional programming, compilers, iTasks, embedded systems\\
  33                 \midrule
  34                 \textbf{Master courses already taken} &
  35                         Advanced Programming, Automated Reasoning,
  36                         Compiler Construction, Design of Embedded Systems,
  37                         ICT in a different culture, Model Checking,
  38                         Natural Computing, Research Seminar Software Science,
  39                         Testing Techniques\\
  40                 \bottomrule
  41         \end{tabu}
  42 \end{table}
  43
  44 \subsection*{Description of the research activities}
  45 In \emph{Task Oriented Programming} (TOP) a program is built out of pieces of
  46 work called \emph{tasks}~\cite{achten_introduction_2015}. Tasks differ from
  47 function in the way that they return a result. A task's return value can change
  48 over time. Task exist in many forms and they can be composed sequentially and
  49 in parallel. Some possible tasks are asking for user input via a web browser,
  50 setting up a TCP connection to another server or combining several tasks. At
  51 the moment there are several types of leaf tasks. A leaf task is a task that
  52 does not consist of tasks itself. Examples of leaf tasks are  the so called
  53 editors.
  54
  55 This proposal describes the effort to add another type of leaf task that
  56 focusses on microcontrollers. Microcontrollers are often not powerful
  57 enough to run a full-fledged task server and therefore there is the need to
  58 introduce special microcontroller tasks. Effort for this is already made by by
  59 the department~\cite{koopman_tasks_2016}. However, communication between the
  60 \emph{mTask} and the iTasks system is still lacking and exactly that will be the
  61 goal of the project. This requires adding a new type of leaf task that allows
  62 the user to run \emph{mTasks} on microcontrollers. The leaf task should
  63 abstract away from communication techniques and it should be relatively easy to
  64 add techniques. Techniques that are interesting to experiment with is Serial
  65 communication, Bluetooth, \textsc{WiFi}, \textsc{GSM} and \textsc{LoRa}.
  66
  67 Similar work has been done in the department on distributing tasks to so-called
  68 \emph{node-servers}~\cite{oortgiese_task_2016}. It might be possible that the
  69 same communication strategy can be used with a slimmed down taskserver on a
  70 microcontroller.
  71
  72 \bibliographystyle{ieeetr}
  73 \bibliography{p}
  74 \end{document}