Adding project template files

data/readme.md

@@ -0,0 +1,26 @@
+## Data
+Keep your data (e.g. from evaluations here)
+
+
+* If you involved human subjects in any form, you will require ethical permission.
+    * Keep records of all items related to ethics in `data/ethics`. There are templates for scripts, guidance provided.
+    * **You must have scanned PDFs of signed checklists in this folder**, or PDFs of ethics confirmations from other sources
+    * Ensure you remain GDPR compliant. In general:
+        * Never collect personally identifiable information if at all possible. 
+        * Pseudonymise identifiers for subjects. 
+        * Use coarse demographic values unless you need specific information (for example, if you need age ranges, collect ranges, not specific ages)
+        * Ensure you have explicit consent for the storage and use of data from human subjects
+        * DO NOT STORE PERSONALLY IDENTIFIABLE INFORMATION ON REMOTE SERVERS (no Dropbox, Github, etc.)
+
+* Keep a written description of the data, what is contained, and how it was captured in `data/readme.md`
+* Record all raw data as an immutable store. **Never modify captured data.** 
+    * Keep this under `data/raw`
+    * This could be logs, questionnaire responses, computation results
+
+* Write scripts to produced processed data from these (e.g. tidy dataframes, excel sheets, csv files, HDF5 files, sqlite databases)
+* Write scripts that process these into results, visualisations, tables that you include in your project.
+* If you use Jupyter/RStudio notebooks, place these in `data/notebooks` and name them carefully (not "Untitled1", "Untitled2").
+
+* You may need to remove the `data/` folder from version control if the data size is too large or you are bound by confidentiality.
+* If you do so **make sure you have good backups**
+

dissertation/.gitignore

@@ -0,0 +1,247 @@
+## Core latex/pdflatex auxiliary files:
+*.aux
+*.lof
+*.log
+*.lot
+*.fls
+*.out
+*.toc
+*.fmt
+*.fot
+*.cb
+*.cb2
+.*.lb
+l4proj*.pdf
+
+test/
+
+bad_l4proj*.*
+
+## Intermediate documents:
+*.dvi
+*.xdv
+*-converted-to.*
+# these rules might exclude image files for figures etc.
+# *.ps
+# *.eps
+# *.pdf
+
+## Generated if empty string is given at "Please type another file name for output:"
+.pdf
+
+## Bibliography auxiliary files (bibtex/biblatex/biber):
+*.bbl
+*.bcf
+*.blg
+*-blx.aux
+*-blx.bib
+*.run.xml
+
+## Build tool auxiliary files:
+*.fdb_latexmk
+*.synctex
+*.synctex(busy)
+*.synctex.gz
+*.synctex.gz(busy)
+*.pdfsync
+
+## Auxiliary and intermediate files from other packages:
+# algorithms
+*.alg
+*.loa
+
+# achemso
+acs-*.bib
+
+# amsthm
+*.thm
+
+# beamer
+*.nav
+*.pre
+*.snm
+*.vrb
+
+# changes
+*.soc
+
+# cprotect
+*.cpt
+
+# elsarticle (documentclass of Elsevier journals)
+*.spl
+
+# endnotes
+*.ent
+
+# fixme
+*.lox
+
+# feynmf/feynmp
+*.mf
+*.mp
+*.t[1-9]
+*.t[1-9][0-9]
+*.tfm
+
+#(r)(e)ledmac/(r)(e)ledpar
+*.end
+*.?end
+*.[1-9]
+*.[1-9][0-9]
+*.[1-9][0-9][0-9]
+*.[1-9]R
+*.[1-9][0-9]R
+*.[1-9][0-9][0-9]R
+*.eledsec[1-9]
+*.eledsec[1-9]R
+*.eledsec[1-9][0-9]
+*.eledsec[1-9][0-9]R
+*.eledsec[1-9][0-9][0-9]
+*.eledsec[1-9][0-9][0-9]R
+
+# glossaries
+*.acn
+*.acr
+*.glg
+*.glo
+*.gls
+*.glsdefs
+
+# gnuplottex
+*-gnuplottex-*
+
+# gregoriotex
+*.gaux
+*.gtex
+
+# htlatex
+*.4ct
+*.4tc
+*.idv
+*.lg
+*.trc
+*.xref
+
+# hyperref
+*.brf
+
+# knitr
+*-concordance.tex
+# TODO Comment the next line if you want to keep your tikz graphics files
+*.tikz
+*-tikzDictionary
+
+# listings
+*.lol
+
+# makeidx
+*.idx
+*.ilg
+*.ind
+*.ist
+
+# minitoc
+*.maf
+*.mlf
+*.mlt
+*.mtc[0-9]*
+*.slf[0-9]*
+*.slt[0-9]*
+*.stc[0-9]*
+
+# minted
+_minted*
+*.pyg
+
+# morewrites
+*.mw
+
+# nomencl
+*.nlg
+*.nlo
+*.nls
+
+# pax
+*.pax
+
+# pdfpcnotes
+*.pdfpc
+
+# sagetex
+*.sagetex.sage
+*.sagetex.py
+*.sagetex.scmd
+
+# scrwfile
+*.wrt
+
+# sympy
+*.sout
+*.sympy
+sympy-plots-for-*.tex/
+
+# pdfcomment
+*.upa
+*.upb
+
+# pythontex
+*.pytxcode
+pythontex-files-*/
+
+# thmtools
+*.loe
+
+# TikZ & PGF
+*.dpth
+*.md5
+*.auxlock
+
+# todonotes
+*.tdo
+
+# easy-todo
+*.lod
+
+# xmpincl
+*.xmpi
+
+# xindy
+*.xdy
+
+# xypic precompiled matrices
+*.xyc
+
+# endfloat
+*.ttt
+*.fff
+
+# Latexian
+TSWLatexianTemp*
+
+## Editors:
+# WinEdt
+*.bak
+*.sav
+
+# Texpad
+.texpadtmp
+
+# Kile
+*.backup
+
+# KBibTeX
+*~[0-9]*
+
+# auto folder when using emacs and auctex
+./auto/*
+*.el
+
+# expex forward references with \gathertags
+*-tags.tex
+
+# standalone packages
+*.sta
+
+# generated if using elsarticle.cls
+*.spl

dissertation/README.md

@@ -0,0 +1,20 @@
+# UofG SoCS Level 4 Project LaTeX template
+
+Provides `l4proj.cls`, the standard LaTeX template for Honours Individual Projects.
+
+![Preview of the layout](images/l4proj.png)
+
+## Notes on formatting
+
+The first page, abstract and table of contents are numbered using Roman numerals and are not
+included in the page count. 
+
+The first Chapter should start on page 1. You are allowed 40 pages for a 40 credit project and 30 pages for a 
+20 credit report. This includes everything numbered in Arabic numerals (excluding front matter) up
+to but excluding the appendices and bibliography.
+
+**You must not alter font, text size (it is currently 10pt), margins or spacing.**
+
+## LaTeX
+This template has been tested with `pdflatex`. It should also work with `xelatex` and `lualatex`. Note that on Linux you may need to copy the contents of the `fonts/` folder to `~/.fonts/`.
+

dissertation/l4proj.bib

@@ -0,0 +1,46 @@
+@inproceedings{Pey17,
+  author    = {Simon {Peyton Jones}},
+  title     = {How to Write a Great Research Paper},
+  booktitle = {2017 Imperial College Computing Student Workshop, {ICCSW} 2017, September
+               26-27, 2017, London, {UK}},
+  pages     = {1:1--1:1},
+  year      = {2017},    
+  
+}
+
+@book{Wil09,
+  title={Style: the basics of clarity and grace},
+  author={Williams, Joseph M and Bizup, Joseph},
+  year={2009},
+  publisher={Pearson Longman}
+}
+
+@book{Pin15,
+  title={The sense of style: The thinking person's guide to writing in the 21st century},
+  author={Pinker, Steven},
+  year={2015},
+  publisher={Penguin Books}
+}
+
+@book{StrWhi07,
+  title={The Elements of style},
+  author={Strunk, William and Whyte, EB},
+  year={2007},
+  publisher={Penguin}
+}
+
+@book{Von80,
+  title={How to write with style},
+  author={Vonnegut, Kurt},
+  year={1980},
+  publisher={International Paper Company}
+}
+
+@incollection{Orw68,
+  title={Politics and the {English} language},
+  author={Orwell, George},
+  booktitle={The collected essays, journalism and letters of George Orwell},
+  pages={127--140},
+  year={1968},
+  publisher={Harcourt, Brace, Javanovich}
+}

dissertation/l4proj.cls

@@ -0,0 +1,295 @@
+% =============================================================================
+% l4proj.cls
+%
+% Template for final year projects in the School of Computing Science at the
+% University of Glasgow. Adapted from the level 3 project template originally
+% provided by Colin Perkins <csp@dcs.gla.ac.uk>.
+%
+% =============================================================================
+
+\ProvidesClass{l4proj}[%
+2009/01/09 Colin Perkins <csp@dcs.gla.ac.uk>.%
+2009/09/16 Modified by Tim Storer <tws@dcs.gla.ac.uk> to support non pdf modes.%
+2011/02/15 Modified by Gregg Hamilton <hamiltgr@dcs.gla.ac.uk> for use in final year projects.%
+2012/10/18 Modified by Patrick Prosser, use geometry to control margins, simplified.%
+2018/09/14 Modified by John Williamson, improve typographic appearance%
+]
+\DeclareOption*{\PassOptionsToClass{\CurrentOption}{report}}
+
+\ProcessOptions
+\LoadClass[10pt,a4paper]{report}
+
+% Monospace font is Fira Mono Sans
+% the body font used is FBB (Bembo)
+
+\usepackage{iftex}
+
+\ifPDFTeX
+  \usepackage{fbb}
+  \usepackage{FiraMono}
+  \usepackage{FiraSans}
+  \usepackage{textcomp}
+  \usepackage[english]{babel}
+  \usepackage[T1]{fontenc}
+\else
+  % make sure the fonts are actually set
+  \usepackage{fontspec}
+  \usepackage{polyglossia}
+  \setromanfont[Path=./fonts/, BoldFont=fbb-Bold, UprightFont=fbb-Regular, ItalicFont=fbb-Italic, BoldItalicFont=fbb-BoldItalic]{fbb}
+  \setmonofont[Path=./fonts/, BoldFont=FiraMono-Bold, UprightFont=FiraMono-Regular]{FiraMono.ttf}
+  \setsansfont[Path=./fonts/, BoldFont=FiraSans-Bold, UprightFont=FiraSans-Regular, ItalicFont=FiraSans-Italic, BoldItalicFont=FiraSans-BoldItalic]{FiraSans.ttf}
+\fi
+
+\usepackage[libertine,bigdelims,vvarbb]{newtxmath} % bb from STIX
+\usepackage[cal=boondoxo]{mathalfa} % mathcal
+
+\usepackage{microtype} % improve typography
+\usepackage{anyfontsize} % allow any size of font
+\usepackage{amsmath,amsfonts,amsbsy,amssymb}
+\usepackage[style]{abstract} % abstract styling
+
+% set bibliography styling
+\usepackage{natbib}
+\bibpunct{(}{)}{;}{a}{}{;}
+
+
+\usepackage{etoolbox}
+\usepackage[compact]{titlesec} % section heading formatting
+\usepackage{color} % colors
+\usepackage[table,svgnames]{xcolor}
+\usepackage{parskip} % adjustable line spacing
+\usepackage{listings} % nice code listings
+
+% remove dots from ToC
+\usepackage[titles]{tocloft} 
+\renewcommand{\cftdot}{}
+\usepackage[nottoc]{tocbibind}
+
+% from: https://gist.github.com/FelipeCortez/10729134
+% set up listings for prettier output
+\definecolor{bluekeywords}{rgb}{0.13, 0.19, 0.7}
+\definecolor{greencomments}{rgb}{0.1, 0.5, 0.2}
+\definecolor{redstrings}{rgb}{0.8, 0.15, 0.1}
+\definecolor{graynumbers}{rgb}{0.5, 0.5, 0.5}
+\definecolor{subtlegray}{rgb}{0.98, 0.98, 0.98}
+\usepackage{lstautogobble}
+\usepackage{listings}
+\lstset{
+    autogobble,    
+    columns=fullflexible,
+    showspaces=false,
+    showtabs=false,
+    breaklines=true,
+    showstringspaces=false,
+    breakatwhitespace=true,
+    escapeinside={(*@}{@*)},
+    rulecolor=\color{lightgray},
+    backgroundcolor=\color{subtlegray},
+    commentstyle=\color{greencomments},
+    keywordstyle=\color{bluekeywords},
+    stringstyle=\color{redstrings},
+    numberstyle=\color{graynumbers},
+    basicstyle=\ttfamily\linespread{1.15}\footnotesize,
+    frame=tb,
+    framesep=12pt,
+    framexleftmargin=12pt,
+    tabsize=4,
+    captionpos=b
+}
+%% ---
+
+% nice number printing
+\usepackage{numprint}
+
+% allow PDF graphics
+\usepackage{graphicx}
+
+% allow section styling
+%\usepackage{sectsty}
+
+% make all cross-references clickable
+\usepackage[hidelinks]{hyperref}
+
+% enable styled captions
+\usepackage[format=plain,
+labelfont={bf,it},
+textfont=it,tableposition=above]{caption}
+
+\newcommand{\secfont}{\normalfont\sffamily}
+% % style the sections and the abstract
+% \allsectionsfont{\secfont}
+
+
+\renewcommand{\abstractnamefont}{\Large\secfont}
+\renewcommand{\abstitlestyle}[1]{{{\let\clearpage\relax \chapter*{#1}}}}
+
+\usepackage[toc]{appendix}
+
+% allow subfloats
+\usepackage{subcaption}
+
+
+% fix the margins and linespacing
+\usepackage[top=3.5cm,bottom=4.0cm,left=3.5cm,right=3.5cm]{geometry}
+\setlength{\parskip}{5pt plus 2pt}
+
+% define the title page
+\renewcommand\maketitle{
+  \begin{titlepage}%
+      \definecolor{UniBlue}{HTML}{00355F}
+        
+      \let\footnotesize\small
+      \let\footnoterule\relax
+      \let\footnote \thanks
+
+      % the logo, full page width
+      \vspace{1in}
+      \includegraphics[width=\linewidth]{images/CompSci_colour.pdf}
+      \vskip 0.5em
+      \color{UniBlue}
+      {\large \sffamily Honours Individual Project Dissertation}\\ 
+
+      % title and author
+      
+      \vspace{2cm}
+        \Large
+        \vskip 8em%
+      
+        \begin{center}
+          
+          \color{UniBlue}
+            \noindent
+            {\Huge \scshape  \@title \par}%
+            
+            
+            
+            
+          
+        \end{center}
+        \vfill
+        {\Large
+        \textbf{\@author}\\
+        \@date}
+            
+
+    
+  \end{titlepage}%
+
+  \setcounter{footnote}{0}%
+  \global\let\thanks\relax
+  \global\let\maketitle\relax
+  \global\let\@thanks\@empty
+  \global\let\@author\@empty
+  \global\let\@date\@empty
+  \global\let\@consentname\@empty
+  \global\let\@consentdate\@empty
+
+  \global\let\@title\@empty
+  \global\let\title\relax
+  \global\let\author\relax
+  \global\let\date\relax
+  \global\let\and\relax
+}
+\usepackage{booktabs}
+% set up headers and footers
+% no footer, page numbers at top-right
+\usepackage{fancyhdr}
+\pagestyle{fancy}
+\fancyhead{}
+\fancyfoot{}
+\fancyhead[R]{\thepage}
+\renewcommand{\headrulewidth}{0pt}
+\fancypagestyle{plain}{%
+    \renewcommand{\headrulewidth}{0pt}%
+    \fancyhf{}%
+    \fancyhead[R]{\thepage}%
+}
+
+\usepackage{titlesec}
+% set up chapter headings
+\usepackage{xstring}
+\titleformat{\chapter}[display]
+  % only show numbers if they aren't Chapter 0 (i.e. front matter)
+  {\normalfont}{}{0pt}{
+    \huge\bfseries\secfont
+    \IfInteger{\thechapter}{\ifnum0=0\thechapter\relax\else\relax {\Huge \thechapter}\ \rule[-0.25em]{0.5pt}{1.5em}\ \fi}
+    {\thechapter \ \rule[-0.25em]{0.5pt}{1.5em}\ }}
+  %[\titlerule]
+  \titlespacing*{\chapter}      
+  {0pt}{0pt}{15pt}  
+
+% Educational consent form
+\newcommand{\educationalconsent}{
+    \ifdefined\consentname
+          \newpage
+          \chapter*{Education Use Consent}
+
+          I hereby grant my permission for this project to be stored, distributed and shown to other
+          University of Glasgow students and staff for educational purposes. 
+          \textbf{Please note that you are under no obligation to sign 
+          this declaration, but doing so would help future students.}
+
+          \begin{tabular}{@{}llll}
+                &                     &            &                     \\
+                &                     &            &                     \\
+          Signature: & \consentname & Date: & \consentdate \\
+                &                     &            &                     \\
+                &                     &            &                     \\
+          \end{tabular}
+    \else
+    \newpage
+        \chapter*{Education Use Consent}
+        Consent for educational reuse withheld. Do not distribute.
+    \fi 
+
+}
+
+% highlight boxes
+\usepackage{tcolorbox}
+\newenvironment{highlight}
+{\begin{tcolorbox}[notitle,boxrule=0pt,colback=green!10,colframe=green!10]}
+{
+\end{tcolorbox}
+}
+
+\newenvironment{highlight_title}[1]
+{\begin{tcolorbox}[title=#1,boxrule=2pt,colback=green!10,colframe=green!20,coltitle=black,fonttitle=\bfseries]}
+{
+\end{tcolorbox}
+}
+
+
+
+% adjust margins
+\setlength{\parindent}{0pt}
+
+
+% use (a) in figures
+\captionsetup{subrefformat=parens}
+
+% Algorithm typesetting package
+\usepackage[plain, noline, shortend, linesnumberedhidden]{algorithm2e}
+\SetAlFnt{\sffamily \small}
+
+% adjust spacing
+\titlespacing{\section}{10pt}{1.5\baselineskip}{8pt plus 3pt minus 3pt}
+\titlespacing{\subsection}{10pt}{\baselineskip}{8pt plus 4pt minus 1pt}
+\titleformat{\subsubsection}[runin]{\bfseries }{}{}{}[]
+\titlespacing{\chapter}{0pt}{0pt}{40pt plus 10pt minus 5pt} 
+
+% switch to roman numeral for frontmatter
+\pagenumbering{roman}
+
+% fix itemise so it looks reasonable
+\renewcommand{\@listI}{%
+      \leftmargin=25pt
+      \rightmargin=0pt
+      \labelsep=5pt
+      \labelwidth=20pt
+      \itemindent=0pt
+      \listparindent=0pt
+      \topsep=0pt plus 2pt minus 4pt
+      \partopsep=0pt plus 1pt minus 1pt
+      \parsep=1pt plus 1pt
+      \itemsep=\parsep}
+

dissertation/l4proj.tex

@@ -0,0 +1,479 @@
+% REMEMBER: You must not plagiarise anything in your report. Be extremely careful.
+
+\documentclass{l4proj}
+
+    
+%
+% put any additional packages here
+%
+
+\begin{document}
+
+%==============================================================================
+%% METADATA
+\title{Level 4 Project Report Template}
+\author{John H. Williamson}
+\date{September 14, 2018}
+
+\maketitle
+
+%==============================================================================
+%% ABSTRACT
+\begin{abstract}
+    Every abstract follows a similar pattern. Motivate; set aims; describe work; explain results.
+    \vskip 0.5em
+    ``XYZ is bad. This project investigated ABC to determine if it was better. 
+    ABC used XXX and YYY to implement ZZZ. This is particularly interesting as XXX and YYY have
+    never been used together. It was found that  
+    ABC was 20\% better than XYZ, though it caused rabies in half of subjects.''
+\end{abstract}
+
+%==============================================================================
+
+% EDUCATION REUSE CONSENT FORM
+% If you consent to your project being shown to future students for educational purposes
+% then insert your name and the date below to  sign the education use form that appears in the front of the document. 
+% You must explicitly give consent if you wish to do so.
+% If you sign, your project may be included in the Hall of Fame if it scores particularly highly.
+%
+% Please note that you are under no obligation to sign 
+% this declaration, but doing so would help future students.
+%
+%\def\consentname {My Name} % your full name
+%\def\consentdate {20 March 2018} % the date you agree
+%
+\educationalconsent
+
+
+%==============================================================================
+\tableofcontents
+
+%==============================================================================
+%% Notes on formatting
+%==============================================================================
+% The first page, abstract and table of contents are numbered using Roman numerals and are not
+% included in the page count. 
+%
+% From now on pages are numbered
+% using Arabic numerals. Therefore, immediately after the first call to \chapter we need the call
+% \pagenumbering{arabic} and this should be called once only in the document. 
+%
+% Do not alter the bibliography style.
+%
+% The first Chapter should then be on page 1. You are allowed 40 pages for a 40 credit project and 30 pages for a 
+% 20 credit report. This includes everything numbered in Arabic numerals (excluding front matter) up
+% to but excluding the appendices and bibliography.
+%
+% You must not alter text size (it is currently 10pt) or alter margins or spacing.
+%
+%
+%==================================================================================================================================
+%
+% IMPORTANT
+% The chapter headings here are **suggestions**. You don't have to follow this model if
+% it doesn't fit your project. Every project should have an introduction and conclusion,
+% however. 
+%
+%==================================================================================================================================
+\chapter{Introduction}
+
+% reset page numbering. Don't remove this!
+\pagenumbering{arabic} 
+
+
+Why should the reader care about what are you doing and what are you actually doing?
+\section{Guidance}
+
+\textbf{Motivate} first, then state the general problem clearly. 
+
+\section{Writing guidance}
+\subsection{Who is the reader?}
+
+This is the key question for any writing. Your reader:
+
+\begin{itemize}
+    \item
+    is a trained computer scientist: \emph{don't explain basics}.
+    \item
+    has limited time: \emph{keep on topic}.
+    \item
+    has no idea why anyone would want to do this: \emph{motivate clearly}
+    \item
+    might not know \emph{anything} about your project in particular:
+    \emph{explain your project}.
+    \item
+    but might know precise details and check them: \emph{be precise and
+    strive for accuracy.}
+    \item
+    doesn't know or care about you: \emph{personal discussions are
+    irrelevant}.
+\end{itemize}
+
+Remember, you will be marked by your supervisor and one or more members
+of staff. You might also have your project read by a prize-awarding
+committee or possibly a future employer. Bear that in mind.
+
+\subsection{References and style guides}
+There are many style guides on good English writing. You don't need to
+read these, but they will improve how you write.
+
+\begin{itemize}
+    \item
+    \emph{How to write a great research paper} \cite{Pey17} (\textbf{recommended}, even though you aren't writing a research paper)
+    \item
+    \emph{How to Write with Style} \cite{Von80}. Short and easy to read. Available online.
+    \item
+    \emph{Style: The Basics of Clarity and Grace} \cite{Wil09} A very popular modern English style guide.
+    \item
+    \emph{Politics and the English Language} \cite{Orw68}  A famous essay on effective, clear writing in English.
+    \item
+    \emph{The Elements of Style} \cite{StrWhi07} Outdated, and American, but a classic.
+    \item
+    \emph{The Sense of Style} \cite{Pin15} Excellent, though quite in-depth.
+\end{itemize}
+
+\subsubsection{Citation styles}
+
+\begin{itemize}
+\item If you are referring to a reference as a noun, then cite it as: ``\citet{Orw68} discusses the role of language in political thought.''
+\item If you are referring implicitly to references, use: ``There are many good books on writing \citep{Orw68, Wil09, Pin15}.''
+\end{itemize}
+
+There is a complete guide on good citation practice by Peter Coxhead available here: \url{http://www.cs.bham.ac.uk/~pxc/refs/index.html}. 
+If you are unsure about how to cite online sources, please see this guide: \url{https://student.unsw.edu.au/how-do-i-cite-electronic-sources}.
+
+\subsection{Plagiarism warning}
+
+\begin{highlight_title}{WARNING}
+    
+    If you include material from other sources without full and correct attribution, you are commiting plagiarism. The penalties for plagiarism are severe.
+    Quote any included text and cite it correctly. Cite all images, figures, etc. clearly in the caption of the figure.
+\end{highlight_title}
+
+
+%==================================================================================================================================
+\chapter{Background}
+What did other people do, and how is it relevant to what you want to do?
+\section{Guidance}
+\begin{itemize}    
+    \item
+      Don't give a laundry list of references.
+    \item
+      Tie everything you say to your problem.
+    \item
+      Present an argument.
+    \item Think critically; weigh up the contribution of the background and put it in context.    
+    \item
+      \textbf{Don't write a tutorial}; provide background and cite
+      references for further information.
+\end{itemize}
+
+%==================================================================================================================================
+\chapter{Analysis/Requirements}
+What is the problem that you want to solve, and how did you arrive at it?
+\section{Guidance}
+Make it clear how you derived the constrained form of your problem via a clear and logical process. 
+
+%==================================================================================================================================
+\chapter{Design}
+How is this problem to be approached, without reference to specific implementation details? 
+\section{Guidance}
+Design should cover the abstract design in such a way that someone else might be able to do what you did, but with a different language or library or tool.
+
+%==================================================================================================================================
+\chapter{Implementation}
+What did you do to implement this idea, and what technical achievements did you make?
+\section{Guidance}
+You can't talk about everything. Cover the high level first, then cover important, relevant or impressive details.
+
+
+
+\section{General points}
+
+These points apply to the whole dissertation, not just this chapter.
+
+
+
+\subsection{Figures}
+\emph{Always} refer to figures included, like Figure \ref{fig:relu}, in the body of the text. Include full, explanatory captions and make sure the figures look good on the page.
+You may include multiple figures in one float, as in Figure \ref{fig:synthetic}, using \texttt{subcaption}, which is enabled in the template.
+
+
+
+% Figures are important. Use them well.
+\begin{figure}
+    \centering
+    \includegraphics[width=0.5\linewidth]{images/relu.pdf}    
+
+    \caption{In figure captions, explain what the reader is looking at: ``A schematic of the rectifying linear unit, where $a$ is the output amplitude,
+    $d$ is a configurable dead-zone, and $Z_j$ is the input signal'', as well as why the reader is looking at this: 
+    ``It is notable that there is no activation \emph{at all} below 0, which explains our initial results.'' 
+    \textbf{Use vector image formats (.pdf) where possible}. Size figures appropriately, and do not make them over-large or too small to read.
+    }
+
+    % use the notation fig:name to cross reference a figure
+    \label{fig:relu} 
+\end{figure}
+
+
+\begin{figure}
+    \centering
+    \begin{subfigure}[b]{0.45\textwidth}
+        \includegraphics[width=\textwidth]{images/synthetic.png}
+        \caption{Synthetic image, black on white.}
+        \label{fig:syn1}
+    \end{subfigure}
+    ~ %add desired spacing between images, e. g. ~, \quad, \qquad, \hfill etc. 
+      %(or a blank line to force the subfigure onto a new line)
+    \begin{subfigure}[b]{0.45\textwidth}
+        \includegraphics[width=\textwidth]{images/synthetic_2.png}
+        \caption{Synthetic image, white on black.}
+        \label{fig:syn2}
+    \end{subfigure}
+    ~ %add desired spacing between images, e. g. ~, \quad, \qquad, \hfill etc. 
+    %(or a blank line to force the subfigure onto a new line)    
+    \caption{Synthetic test images for edge detection algorithms. \subref{fig:syn1} shows various gray levels that require an adaptive algorithm. \subref{fig:syn2}
+    shows more challenging edge detection tests that have crossing lines. Fusing these into full segments typically requires algorithms like the Hough transform.
+    This is an example of using subfigures, with \texttt{subref}s in the caption.
+    }\label{fig:synthetic}
+\end{figure}
+
+\clearpage
+
+\subsection{Equations}
+
+Equations should be typeset correctly and precisely. Make sure you get parenthesis sizing correct, and punctuate equations correctly 
+(the comma is important and goes \textit{inside} the equation block). Explain any symbols used clearly if not defined earlier. 
+
+For example, we might define:
+\begin{equation}
+    \hat{f}(\xi) = \frac{1}{2}\left[ \int_{-\infty}^{\infty} f(x) e^{2\pi i x \xi} \right],
+\end{equation}    
+where $\hat{f}(\xi)$ is the Fourier transform of the time domain signal $f(x)$.
+
+\subsection{Algorithms}
+Algorithms can be set using \texttt{algorithm2e}, as in Algorithm \ref{alg:metropolis}.
+
+% NOTE: line ends are denoted by \; in algorithm2e
+\begin{algorithm}
+    \DontPrintSemicolon
+    \KwData{$f_X(x)$, a probability density function returing the density at $x$.\; $\sigma$ a standard deviation specifying the spread of the proposal distribution.\;
+    $x_0$, an initial starting condition.}
+    \KwResult{$s=[x_1, x_2, \dots, x_n]$, $n$ samples approximately drawn from a distribution with PDF $f_X(x)$.}
+    \Begin{
+        $s \longleftarrow []$\;
+        $p \longleftarrow f_X(x)$\;
+        $i \longleftarrow 0$\;
+        \While{$i < n$}
+        {
+            $x^\prime \longleftarrow \mathcal{N}(x, \sigma^2)$\;
+            $p^\prime \longleftarrow f_X(x^\prime)$\;
+            $a \longleftarrow \frac{p^\prime}{p}$\;
+            $r \longleftarrow U(0,1)$\;
+            \If{$r<a$}
+            {
+                $x \longleftarrow x^\prime$\;
+                $p \longleftarrow f_X(x)$\;
+                $i \longleftarrow i+1$\;
+                append $x$ to $s$\;
+            }
+        }
+    }
+    
+\caption{The Metropolis-Hastings MCMC algorithm for drawing samples from arbitrary probability distributions, 
+specialised for normal proposal distributions $q(x^\prime|x) = \mathcal{N}(x, \sigma^2)$. The symmetry of the normal distribution means the acceptance rule takes the simplified form.}\label{alg:metropolis}
+\end{algorithm}
+
+\subsection{Tables}
+
+If you need to include tables, like Table \ref{tab:operators}, use a tool like https://www.tablesgenerator.com/ to generate the table as it is
+extremely tedious otherwise. 
+
+\begin{table}[]
+    \caption{The standard table of operators in Python, along with their functional equivalents from the \texttt{operator} package. Note that table
+    captions go above the table, not below. Do not add additional rules/lines to tables. }\label{tab:operators}
+    %\tt 
+    \rowcolors{2}{}{gray!3}
+    \begin{tabular}{@{}lll@{}}
+    %\toprule
+    \textbf{Operation}    & \textbf{Syntax}                & \textbf{Function}                            \\ %\midrule % optional rule for header
+    Addition              & \texttt{a + b}                          & \texttt{add(a, b)}                                    \\
+    Concatenation         & \texttt{seq1 + seq2}                    & \texttt{concat(seq1, seq2)}                           \\
+    Containment Test      & \texttt{obj in seq}                     & \texttt{contains(seq, obj)}                           \\
+    Division              & \texttt{a / b}                          & \texttt{div(a, b) }  \\
+    Division              & \texttt{a / b}                          & \texttt{truediv(a, b) } \\
+    Division              & \texttt{a // b}                         & \texttt{floordiv(a, b)}                               \\
+    Bitwise And           & \texttt{a \& b}                         & \texttt{and\_(a, b)}                                  \\
+    Bitwise Exclusive Or  & \texttt{a \textasciicircum b}           & \texttt{xor(a, b)}                                    \\
+    Bitwise Inversion     & \texttt{$\sim$a}                        & \texttt{invert(a)}                                    \\
+    Bitwise Or            & \texttt{a | b}                          & \texttt{or\_(a, b)}                                   \\
+    Exponentiation        & \texttt{a ** b}                         & \texttt{pow(a, b)}                                    \\
+    Identity              & \texttt{a is b}                         & \texttt{is\_(a, b)}                                   \\
+    Identity              & \texttt{a is not b}                     & \texttt{is\_not(a, b)}                                \\
+    Indexed Assignment    & \texttt{obj{[}k{]} = v}                 & \texttt{setitem(obj, k, v)}                           \\
+    Indexed Deletion      & \texttt{del obj{[}k{]}}                 & \texttt{delitem(obj, k)}                              \\
+    Indexing              & \texttt{obj{[}k{]}}                     & \texttt{getitem(obj, k)}                              \\
+    Left Shift            & \texttt{a \textless{}\textless b}       & \texttt{lshift(a, b)}                                 \\
+    Modulo                & \texttt{a \% b}                         & \texttt{mod(a, b)}                                    \\
+    Multiplication        & \texttt{a * b}                          & \texttt{mul(a, b)}                                    \\
+    Negation (Arithmetic) & \texttt{- a}                            & \texttt{neg(a)}                                       \\
+    Negation (Logical)    & \texttt{not a}                          & \texttt{not\_(a)}                                     \\
+    Positive              & \texttt{+ a}                            & \texttt{pos(a)}                                       \\
+    Right Shift           & \texttt{a \textgreater{}\textgreater b} & \texttt{rshift(a, b)}                                 \\
+    Sequence Repetition   & \texttt{seq * i}                        & \texttt{repeat(seq, i)}                               \\
+    Slice Assignment      & \texttt{seq{[}i:j{]} = values}          & \texttt{setitem(seq, slice(i, j), values)}            \\
+    Slice Deletion        & \texttt{del seq{[}i:j{]}}               & \texttt{delitem(seq, slice(i, j))}                    \\
+    Slicing               & \texttt{seq{[}i:j{]}}                   & \texttt{getitem(seq, slice(i, j))}                    \\
+    String Formatting     & \texttt{s \% obj}                       & \texttt{mod(s, obj)}                                  \\
+    Subtraction           & \texttt{a - b}                          & \texttt{sub(a, b)}                                    \\
+    Truth Test            & \texttt{obj}                            & \texttt{truth(obj)}                                   \\
+    Ordering              & \texttt{a \textless b}                  & \texttt{lt(a, b)}                                     \\
+    Ordering              & \texttt{a \textless{}= b}               & \texttt{le(a, b)}                                     \\
+    % \bottomrule
+    \end{tabular}
+    \end{table}
+\subsection{Code}
+
+Avoid putting large blocks of code in the report (more than a page in one block, for example). Use syntax highlighting if possible, as in Listing \ref{lst:callahan}.
+
+\begin{lstlisting}[language=python, float, caption={The algorithm for packing the $3\times 3$ outer-totalistic binary CA successor rule into a 
+    $16\times 16\times 16\times 16$ 4 bit lookup table, running an equivalent, notionally 16-state $2\times 2$ CA.}, label=lst:callahan]
+    def create_callahan_table(rule="b3s23"):
+        """Generate the lookup table for the cells."""        
+        s_table = np.zeros((16, 16, 16, 16), dtype=np.uint8)
+        birth, survive = parse_rule(rule)
+
+        # generate all 16 bit strings
+        for iv in range(65536):
+            bv = [(iv >> z) & 1 for z in range(16)]
+            a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p = bv
+
+            # compute next state of the inner 2x2
+            nw = apply_rule(f, a, b, c, e, g, i, j, k)
+            ne = apply_rule(g, b, c, d, f, h, j, k, l)
+            sw = apply_rule(j, e, f, g, i, k, m, n, o)
+            se = apply_rule(k, f, g, h, j, l, n, o, p)
+
+            # compute the index of this 4x4
+            nw_code = a | (b << 1) | (e << 2) | (f << 3)
+            ne_code = c | (d << 1) | (g << 2) | (h << 3)
+            sw_code = i | (j << 1) | (m << 2) | (n << 3)
+            se_code = k | (l << 1) | (o << 2) | (p << 3)
+
+            # compute the state for the 2x2
+            next_code = nw | (ne << 1) | (sw << 2) | (se << 3)
+
+            # get the 4x4 index, and write into the table
+            s_table[nw_code, ne_code, sw_code, se_code] = next_code
+
+        return s_table
+
+\end{lstlisting}
+
+%==================================================================================================================================
+\chapter{Evaluation} 
+How good is your solution? How well did you solve the general problem, and what evidence do you have to support that?
+
+\section{Guidance}
+\begin{itemize}
+    \item
+        Ask specific questions that address the general problem.
+    \item
+        Answer them with precise evidence (graphs, numbers, statistical
+        analysis, qualitative analysis).
+    \item
+        Be fair and be scientific.
+    \item
+        The key thing is to show that you know how to evaluate your work, not
+        that your work is the most amazing product ever.
+\end{itemize}
+
+\section{Evidence}
+Make sure you present your evidence well. Use appropriate visualisations, reporting techniques and statistical analysis, as appropriate.
+
+If you visualise, follow the basic rules, as illustrated in Figure \ref{fig:boxplot}:
+\begin{itemize}
+\item Label everything correctly (axis, title, units).
+\item Caption thoroughly.
+\item Reference in text.
+\item \textbf{Include appropriate display of uncertainty (e.g. error bars, Box plot)}
+\item Minimize clutter.
+\end{itemize}
+
+See the file \texttt{guide\_to\_visualising.pdf} for further information and guidance.
+
+\begin{figure}
+    \centering
+    \includegraphics[width=1.0\linewidth]{images/boxplot_finger_distance.pdf}    
+
+    \caption{Average number of fingers detected by the touch sensor at different heights above the surface, averaged over all gestures. Dashed lines indicate
+    the true number of fingers present. The Box plots include bootstrapped uncertainty notches for the median. It is clear that the device is biased toward 
+    undercounting fingers, particularly at higher $z$ distances.
+    }
+
+    % use the notation fig:name to cross reference a figure
+    \label{fig:boxplot} 
+\end{figure}
+
+
+%==================================================================================================================================
+\chapter{Conclusion}    
+Summarise the whole project for a lazy reader who didn't read the rest (e.g. a prize-awarding committee).
+\section{Guidance}
+\begin{itemize}
+    \item
+        Summarise briefly and fairly.
+    \item
+        You should be addressing the general problem you introduced in the
+        Introduction.        
+    \item
+        Include summary of concrete results (``the new compiler ran 2x
+        faster'')
+    \item
+        Indicate what future work could be done, but remember: \textbf{you
+        won't get credit for things you haven't done}.
+\end{itemize}
+
+%==================================================================================================================================
+%
+% 
+%==================================================================================================================================
+%  APPENDICES  
+
+\begin{appendices}
+
+\chapter{Appendices}
+
+Typical inclusions in the appendices are:
+
+\begin{itemize}
+\item
+  Copies of ethics approvals (required if obtained)
+\item
+  Copies of questionnaires etc. used to gather data from subjects.
+\item
+  Extensive tables or figures that are too bulky to fit in the main body of
+  the report, particularly ones that are repetitive and summarised in the body.
+
+\item Outline of the source code (e.g. directory structure), or other architecture documentation like class diagrams.
+
+\item User manuals, and any guides to starting/running the software.
+
+\end{itemize}
+
+\textbf{Don't include your source code in the appendices}. It will be
+submitted separately.
+
+\end{appendices}
+
+%==================================================================================================================================
+%   BIBLIOGRAPHY   
+
+% The bibliography style is abbrvnat
+% The bibliography always appears last, after the appendices.
+
+\bibliographystyle{abbrvnat}
+
+\bibliography{l4proj}
+
+\end{document}

plan.md

@@ -0,0 +1,40 @@
+# Plan
+
+* PROJECT TITLE
+* YOUR NAME
+* STUDENT ID
+* SUPERVISOR NAME
+
+Week-by-week plan for the whole project. Update this as you go along.
+
+## Winter semester
+
+* **Week 1**
+* **Week 2**
+* **Week 3**
+* **Week 4**
+* **Week 5**
+* **Week 6**
+* **Week 7**
+* **Week 8**
+* **Week 9**
+* **Week 10**
+* **Week 11 [PROJECT WEEK]**
+* **Week 12 [PROJECT WEEK]** Status report submitted.
+
+## Winter break
+
+## Spring Semester
+
+* **Week 13**
+* **Week 14**
+* **Week 15**
+* **Week 16**
+* **Week 17**
+* **Week 19**
+* **Week 20**
+* **Week 21**
+* **Week 22**
+* **Week 23 [TERM ENDS]**
+* **Week 24** Dissertation submission deadline and presentations.
+

presentation/readme.md

@@ -0,0 +1,4 @@
+# Presentation
+
+Include your presentation slides here. You should include the slides in the original format you authored them in (e.g. PowerPoint, Keynote), *and*
+a `pdf` version of the slides. Any necessary videos, audio, images, figures, etc. should be present.

src/manual.md

@@ -0,0 +1,3 @@
+# User manual 
+
+Describe how to use your software, if this makes sense for your code. Almost all projects should have at least some instructions on how to run the code. More extensive instructions can be provided here.

src/readme.md

@@ -0,0 +1,41 @@
+# Readme
+
+Put a brief description of your code here. This should at least describe the file structure.
+
+## Build instructions
+
+**You must** include the instructions necessary to build and deploy this project successfully. If appropriate, also include 
+instructions to run automated tests. 
+
+### Requirements
+
+List the all of the pre-requisites software required to set up your project (e.g. compilers, packages, libraries, OS, hardware)
+
+For example:
+
+* Python 3.7
+* Packages: listed in `requirements.txt` 
+* Tested on Windows 10
+
+or another example:
+
+* Requires Raspberry Pi 3 
+* a Linux host machine with the `arm-none-eabi` toolchain (at least version `x.xx`) installed
+* a working LuaJIT installation > 2.1.0
+
+### Build steps
+
+List the steps required to build software. 
+
+Hopefully something simple like `pip install -e .` or `make` or `cd build; cmake ..`. In
+some cases you may have much more involved setup required.
+
+### Test steps
+
+List steps needed to show your software works. This might be running a test suite, or just starting the program; but something that could be used to verify your code is working correctly.
+
+Examples:
+
+* Run automated tests by running `pytest`
+* Start the software by running `bin/editor.exe` and opening the file `examples/example_01.bin`
+

status_report/exemplar/status_report_exemplar.tex

@@ -0,0 +1,120 @@
+    
+\documentclass[11pt]{article}
+\usepackage{times}
+    \usepackage{fullpage}
+    
+    \title{Audio feedback for gesture recognition}
+    \author{John Williamson 9804750w}
+
+    \begin{document}
+    \maketitle
+    
+    
+     
+
+
+
+\section{Proposal}\label{proposal}
+
+\subsection{Motivation}\label{motivation}
+
+Gesture recognition offers the opportunity to add controls to a myriad of sensing
+devices, particularly on mobile devices with limited control inputs. However, the
+resulting interfaces are hard to interpret. Adding auditory feedback to indicate
+the progress and success of gesture recognition could improve the usability of
+gesture recognition systems.
+
+
+\subsection{Aims}\label{aims}
+
+This project will develop a software framework for systematically exploring
+audio feedback options for gesture recognition. This will be a modular visual
+programming environment that allows various gesture recognisers to be configured
+and their output processed and fed to audio synthesis devices. The effectiveness
+of the project in improving gesture usability will be experimentally validated.
+
+\section{Progress}\label{progress}
+
+\begin{itemize}
+    \tightlist
+\item Language and GUI framework chosen: project will be implemented in Java,
+using Swing for GUI development.
+\item Software architecture outlined and basic class structure written.
+\item  Background research conducted on gesture recognition technologies and
+feedback mechanisms.
+\item  Interfacing to inertial sensing unit in Java completed.
+\item  Initial version of GUI developed, which allows basic signal processing to
+be applied to mouse input, with interchangable blocks.
+\item  Basic finite state machine gesture recogniser implemented.
+\item  Initial MIDI note based output implemented and working. Limited to
+pitch mapping.
+\end{itemize}
+
+\section{Problems and risks}\label{problems-and-risks}
+
+\subsection{Problems}\label{problems}
+
+The following issues were encountered in the project so far.
+\begin{itemize}
+    \tightlist
+\item Inertial sensing unit had unsupported and out-of-date drivers. Some tricky
+fixes had to be applied to get inputs.
+\item Many different types of gesture recognition; not clear which ones to focus
+on.
+\item Implemented FSM recogniser is not robust.
+\item Significant latency issues in rendering audio via Java with default audio
+generation libraries.
+\end{itemize}
+
+\subsection{Risks}\label{risks}
+
+\begin{itemize}
+\tightlist
+\item   Many different gesture recognisers to explore. \textbf{Mitigation}: will narrow
+down to three possibilities by start of next semester.
+\item Unclear how to evaluate success of the project. \textbf{Mitigation}: will do
+background research to investigate how success of audio recognition has
+been performed in the research literature.
+\item Inertial sensing device seems to be unreliable. \textbf{No clear mitigation available at this stage}
+\end{itemize}
+    
+\section{Plan}\label{plan}
+
+\subsection{Semester 2}
+
+\begin{itemize}
+    \tightlist
+    \item
+      Week 1-2: develop visual programming interface. \textbf{Deliverable:}
+      complete interface that allows components to be added, removed and
+      rearranged.
+    \item
+      Week 3-5: implement three recognisers and test them with a standard
+      recognition task. \textbf{Deliverable:} tested recognisers with
+      initial performance metrics and integration with visual programming
+      environment.
+    \item
+      Week 6: research on how to best evaluate performance of final system.
+      \textbf{Deliverable:} detailed evaluation plan, with participant
+      numbers, information sheet and analysis plan.
+    \item
+      Week 7-9: final implementation and improvements to audio rendering.
+      \textbf{Deliverable: polished software ready, passing basic tests,
+      ready for evaluation stage.}
+    \item
+      Week 9: evaluation experiments run. \textbf{Deliverable: quantitative
+      measures of usability and qualitative measures of effectiveness for at
+      least ten users.}
+    \item
+      Week 8-10: Write up. \textbf{Deliverable: first draft submitted to
+      supervisor two weeks before final deadline.}
+    \end{itemize}
+    
+
+\section{Ethics}
+
+This project will involve tests with human users.  These will be user studies
+using standard hardware, and require no personally identifiable information to be captured.
+I have verified that the experiments I plan to do comply with the Ethics Checklist.
+
+\end{document}

status_report/status_report_template.tex

@@ -0,0 +1,68 @@
+    
+\documentclass[11pt]{article}
+\usepackage{times}
+    \usepackage{fullpage}
+    
+    \title{ {{cookiecutter.project_title}}
+    \author{ {{cookiecutter.student_name}} - {{cookiecutter.student_id}} }
+
+    \begin{document}
+    \maketitle
+    
+    
+     
+
+\section{Status report}
+
+\subsection{Proposal}\label{proposal}
+
+\subsubsection{Motivation}\label{motivation}
+
+\emph{{[}Clearly motivate the purpose of your project; why someone would
+care about what you are doing{]}}
+
+\subsubsection{Aims}\label{aims}
+
+\emph{{[}Clearly state what the project is intended to do. This should
+be something which is measurable; it should be possible to tell if you
+succeeded{]}}
+
+\subsection{Progress}\label{progress}
+
+\emph{{[}Briefly state your progress so far, as a bulleted list{]}}
+
+\subsection{Problems and risks}\label{problems-and-risks}
+
+\subsubsection{Problems}\label{problems}
+
+\emph{{[}What problems have you had so far, that have held up the
+project?{]}}
+
+\subsubsection{Risks}\label{risks}
+
+\emph{{[}What problems do you foresee in the future and how will you
+mitigate them?{]}}
+
+\subsection{Plan}\label{plan}
+
+\emph{{[}Time plan, in roughly weekly to monthly blocks, up until
+submission week{]}}
+
+    
+\subsection{Ethics and data}\label{ethics}
+\emph{Specify what ethical approval you need to do your evaluation and how you are approaching it. This is mandatory. 
+Specify what data you expect to collect in your evaluation. Explain how this data will help you evaluate your project.
+}
+
+Options for ethics:
+\item This project does not involve human subjects or data. No approval required.
+\item I have verified that the ethics checklist will apply to any evaluation I need to do. I will sign and complete the checklist.
+\item I have sought ethical guidance from the School's ethics convener and I will:
+\begin{itemize}
+    \item Proceed under specific instructions from the Ethics convener (e.g. modified checklist).
+    \item Apply for College Ethics Board approval.
+    \item Other procedure (give details)
+\end{itemize}    
+
+
+\end{document}

summer/readme.md

@@ -0,0 +1,17 @@
+# Summer work
+
+* PROJECT NAME
+* YOUR NAME
+* STUDENT_ID
+* SUPERVISOR NAME
+
+Use this file to keep a report stating what you completed over the summer. The following is an *template* that you can use as a basis. 
+
+## Research completed
+
+## Ideas developed
+
+## Concerns or risks identified
+
+
+

timelog.md

@@ -0,0 +1,26 @@
+# Timelog
+
+* Text-generation with rhyme and rhythm
+* Ans Farooq
+* 2390370f
+* Jake Lever
+
+## Guidance
+
+* This file contains the time log for your project. It will be submitted along with your final dissertation.
+* **YOU MUST KEEP THIS UP TO DATE AND UNDER VERSION CONTROL.**
+* This timelog should be filled out honestly, regularly (daily) and accurately. It is for *your* benefit.
+* Follow the structure provided, grouping time by weeks.  Quantise time to the half hour.
+
+## Week 1
+
+### 19 Oct 2019
+
+* *4 hours* Read the project guidance notes
+* *0.5 hour* Created GitLab repository and cloned the cookiecutter for the projects
+* *1 hour* Modified dissertation template, compiled  
+
+## 20 Oct 2019
+
+* *1 hour* meeting with supervisor
+* *2 hours* writing initial version of test harness