intro/intro.tex

   1 \documentclass[../thesis.tex]{subfiles}
   2
   3 \input{subfilepreamble}
   4
   5 \begin{document}
   6 \chapter{Prelude}%
   7 \label{chp:introduction}
   8 \begin{chapterabstract}
   9         This chapter introduces the contents of the thesis and a reading guide.
  10         Furthermore, it provides background material on \glsxtrlong{IOT}, \glsxtrlongpl{DSL}, and \glsxtrlong{TOP}; and a detailed overview of the contributions.
  11 \end{chapterabstract}
  12
  13 There are at least 13.4 billion computers connected to the internet at the time of writing\footnote{\url{https://transformainsights.com/research/tam/market}, accessed on: \formatdate{13}{10}{2022}}.
  14 These devices sense, act, or otherwise interact with people, other computers, and the world surrounding us.
  15 Notwithstanding the substantial variety among these devices, they have one thing in common: they are all require software to operate.
  16
  17 An increasing amount of these connected devices are so-called \emph{edge devices} that operate in the \gls{IOT}.
  18 Typically these edge devices are small microprocessors containing sensors and actuators to interact with the physical world.
  19 The variety within edge devices, and the fact that they differ substantially from other types of devices, makes it complex to program \gls{IOT} systems.\todo{make sentence logical}
  20 Hence, an \gls{IOT} programmer has to program each device and their interoperation using different programming paradigms, programming languages, and abstraction levels resulting in semantic friction.
  21
  22 This thesis introduces research on the many aspects of orchestrating \gls{IOT} systems using \gls{TOP}.
  23 \Gls{TOP} is a novel programming paradigm for programming multi-tier workflow systems using a single declarative specification of the work that needs to be done.
  24 Using advanced compiler technologies, much of the internals and communication of multi-tier applications are automatically generated and the result of compilation is a ready-for-work application.
  25 Unfortunately, because the abstraction level is so high, the hardware requirements are too excessive to be suitable for the average edge device.
  26
  27 This is where \glspl{DSL} come into play.
  28 \Glspl{DSL} are languages created with a specific domain in mind.
  29 Consequently, domain knowledge does not have to be expressed in the language itself but they can be built-in features, thus drastically reducing the hardware requirements even with high levels of abstraction.
  30
  31 \section{Reading guide}
  32 On Wikipedia, a musical rhapsody is defined as follows \citep{wikipedia_contributors_rhapsody_2022}:
  33 \begin{quote}\emph{%
  34         A \emph{rhapsody} in music is a one-movement work that is episodic yet integrated, free-flowing in structure, featuring a range of highly contrasted moods, colour, and tonality.}
  35 \end{quote}
  36 This thesis is structured as a pure functional rhapsody containing three episodes barded by the introduction and conclusion (\cref{chp:introduction,chp:conclusion}).
  37 \Cref{prt:dsl} is a paper-based---otherwise known as cumulative---episode providing insight in advanced \gls{DSL} embedding techniques.
  38 The chapters are readable independently.
  39 \Cref{prt:top} is a monograph showing \gls{MTASK}, a \gls{TOP} \gls{DSL} for the \gls{IOT}.
  40 Hence, the chapters are best read in order.
  41 \Cref{prt:tvt} is a journal article in which quantitative and qualitatively compares traditional tiered \gls{IOT} programming to tierless programming.
  42 The chapter is readable independently.
  43
  44 The following sections provide background material on the \gls{IOT}, \glspl{DSL}, and \gls{TOP} after which a detailed overview of the contributions is presented.
  45 Text typeset as \texttt{teletype} represents source code.
  46 Standalone source code listings are used are marked with the programming language used.
  47 For the \gls{FP} language \gls{CLEAN}, a guide tailored to \gls{HASKELL} programmers is available as in \cref{chp:clean_for_haskell_programmers}.
  48
  49 \section{Internet of things}\label{sec:back_iot}
  50 The \gls{IOT} is growing rapidly and it is changing the way people and machines interact with the world.
  51 While the term \gls{IOT} briefly gained interest around 1999 to describe the communication of \gls{RFID} devices \citep{ashton_internet_1999,ashton_that_2009}, it probably already popped up halfway the eighties in a speech by \citet{peter_t_lewis_speech_1985}:
  52
  53 \begin{quote}
  54         \emph{The \glsxtrlong{IOT}, or \glsxtrshort{IOT}, is the integration of people, processes and technology with connectable devices and sensors to enable remote monitoring, status, manipulation and evaluation of trends of such devices.}
  55 \end{quote}
  56
  57 CISCO states that the \gls{IOT} started when there where as many connected devices as there were people on the globe, i.e.\ around 2008 \citep{evans_internet_2011}.
  58 Today, \gls{IOT} is the term for a system of devices that sense the environment, act upon it and communicate with each other and the world.
  59 These connected devices are already in households all around us in the form of smart electricity meters, fridges, phones, watches, home automation, \etc.
  60
  61 When describing \gls{IOT} systems, a tiered---or layered---architecture is often used to compartmentalize the technology.
  62 The number of tiers heavily depends on the required complexity of the model but for the intents and purposes of this thesis, the four layer architecture as shown in \cref{fig:iot-layers} is used.
  63
  64 \begin{figure}[ht]
  65         \centering
  66         \includestandalone{iot-layers}
  67         \caption{A four-tier \gls{IOT} architecture.}%
  68         \label{fig:iot-layers}
  69 \end{figure}
  70
  71 To explain the tiers, an example \gls{IOT} application---home automation---is dissected accordingly.
  72 Closest to the end-user is the presentation layer, it provides the interface between the user and the \gls{IOT} system.
  73 In home automation this may be a web interface or an app used on a phone or mounted tablet to interact with the edge devices and view the sensor data.
  74
  75 The application layer provides the \glspl{API}, data interfaces, and data storage of the \gls{IOT} system.
  76 A cloud server or local server provides this layer in a typical home automation application.
  77
  78 All layers are connected using the network layer.
  79 In many applications this is implemented using conventional networking techniques such as WiFi or Ethernet.
  80 However, networks or layers on top of it---tailored to the needs of \gls{IOT} systems---have been increasingly popular such as \gls{BLE}, LoRa, ZigBee, LTE-M, or \gls{MQTT}.
  81
  82 The perception layer---also called edge layer---collects the data and interacts with the environment.
  83 It consists of edge devices such as microprocessors equipped with various sensors and actuators.
  84 In home automation this layer consists of all the devices hosting the sensors and actuators such as a smart lightbulb, an actuator to open a door or a temperature and humidity sensor.
  85
  86 Across the layers, the devices are a large heterogeneous collection of different platforms, protocols, paradigms, and programming languages often resulting in impedance problems or semantic friction between layers when programming \citep{ireland_classification_2009}.
  87 Even more so, perception layer itself often is a heterogeneous collections of microprocessors in itself as well, each having their own peculiarities, language of choice, and hardware interfaces.
  88 As the edge hardware needs to be cheap, small-scale, and energy efficient, the microprocessors used to power these devices do not have a lot of computational power, only a soup\c{c}on of memory, and little communication bandwidth.
  89 Typically the devices do not run a full fledged \gls{OS} but a compiled firmware that written in an imperative language.
  90 While devices are getting a bit faster, smaller, and cheaper, they keep these properties to an extent, greatly reducing the flexibility for dynamic systems where tasks are created on the fly, executed on demand, or require parallel execution.
  91 As program memory is mostly flash based and only lasts a couple of thousand writes before it wears out, it is not suitable for rapid reconfiguring and reprogramming.
  92
  93 These problems can be mitigated by dynamically sending code to be interpreted to the microprocessor.
  94 With interpretation, a specialized interpreter is flashed in the program memory once that receives the program code to execute at runtime.
  95 Interpretation always comes with an overhead, making it challenging to create them for small edge devices.
  96 However, the hardware requirements can be reduced by embedding domain-specific data into the programming language to be interpreted, so called \glspl{DSL}.
  97
  98 \section{\texorpdfstring{\Glsxtrlongpl{DSL}}{Domain-specific languages}}\label{sec:back_dsl}
  99 % General
 100 Programming languages can be divided up into two categories: \glspl{DSL}\footnote{Historically this has been called DSEL as well.} and \glspl{GPL} \citep{fowler_domain_2010}.
 101 Where \glspl{GPL} are not made with a demarcated area in mind, \glspl{DSL} are tailor-made for a specific domain.
 102 Writing idiomatic domain-specific code in an \gls{DSL} is easy but this may come at the cost of the \gls{DSL} being less expressive to an extent that it may not even be Turing complete.
 103 \Glspl{DSL} come in two main flavours: standalone and embedded (\cref{sec:standalone_embedded})\footnote{Also called external and internal respectively.} of which \glspl{EDSL} can again be classified into heterogeneous and homogeneous languages (\cref{sec:hetero_homo}).
 104 This hyponymy is shown in \cref{fig:hyponymy_of_dsls}.
 105
 106 \begin{figure}[ht]
 107         \centering
 108         \includestandalone{hyponymy_of_dsls}
 109         \caption{Hyponymy of \glspl{DSL} (adapted from \citet[\citepage{2}]{mernik_extensible_2013})}%
 110         \label{fig:hyponymy_of_dsls}
 111 \end{figure}
 112
 113 \subsection{Standalone and embedded}\label{sec:standalone_embedded}
 114 \glspl{DSL} where historically created as standalone languages, meaning all the machinery is developed solely for the language.
 115 The advantage of this approach is that the language designer is free to define the syntax and type system of the language as they wish, not being restricted by any constraint.
 116 Unfortunately it also means that they need to develop a compiler or interpreter for the language to be usable making standalone \glspl{DSL} costly to create.
 117 Examples of standalone \glspl{DSL} are regular expressions, make, yacc, XML, SQL, \etc.
 118
 119 The dichotomous approach is embedding the \gls{DSL} in a host language, i.e.\ \glspl{EDSL} \citep{hudak_modular_1998}.
 120 By defining the language as constructs in the host language, much of the machinery is inherited and the cost of creating embedded languages is very low.
 121 There is more linguistic reuse~\cite{krishnamurthi_linguistic_2001}.
 122 There are however two sides to the this coin.
 123 If the syntax of the host language is not very flexible, the syntax of the \gls{DSL} may become clumsy.
 124 Furthermore, errors shown to the programmer may be larded with host language errors, making it difficult for a non-expert of the host language to work with the \gls{DSL}.
 125 Pure \gls{FP} languages are especially suitable for hosting embedded \glspl{DSL} because they have strong and versatile type systems, minimal but flexible syntax and offer referential transparency.
 126
 127 \subsection{Heterogeneity and homogeneity}\label{sec:hetero_homo}
 128 \Citet{tratt_domain_2008} applied a notion from metaprogramming \citep{sheard_accomplishments_2001} to \glspl{EDSL} to define homogeneity and heterogeneity of \glspl{EDSL} as follows:
 129
 130 \begin{quote}
 131         \emph{
 132         A homogeneous system is one where all the components are specifically designed to work with each other, whereas in heterogeneous systems at least one of the components is largely, or completely, ignorant of the existence of the other parts of the system.
 133 }
 134 \end{quote}
 135
 136 Homogeneous \glspl{EDSL} are therefore languages that are solely defined as an extension to their host language.
 137 They often restrict features of the host language to provide a safer interface or capture an idiomatic pattern in the host language for reuse.
 138 The difference between a library and a homogeneous \glspl{EDSL} is not always clear.
 139 Examples of homogeneous \glspl{EDSL} are libraries such as ones for sets, \glspl{GUI} creation, LISP's macro system, \etc.
 140
 141 On the other hand, heterogeneous \glspl{EDSL} are languages that are not executed in the host language.
 142 For example, \citep{elliott_compiling_2003} describe the language Pan, for which the final representation in the host language is a compiler that will, when executed, generate code for a completely different target platform.
 143 In fact, \gls{ITASK} and \gls{MTASK} are both heterogeneous \glspl{EDSL} and \gls{MTASK} specifically is a compiling \gls{DSL}.
 144
 145 \section{\texorpdfstring{\Glsxtrlong{TOP}}{Task-oriented programming}}\label{sec:back_top}
 146 \Gls{TOP} is a declarative programming paradigm designed to model interactive systems \citep{plasmeijer_task-oriented_2012}.
 147 \Citet{steenvoorden_tophat_2022} defines two instruments for \gls{TOP}: \gls{TOP} languages and \gls{TOP} engines.
 148 A \gls{TOP} language is a language to specify workflows.\todo{improve sentence}
 149 A \gls{TOP} engine executes such a specification as a ready-for-work application.
 150 Instead of dividing problems into layers or tiers, as is done in \gls{IOT} architectures, it deals with separation of concerns in a novel way.
 151 From the data types, utilising various \emph{type-parametrised} concepts, all other aspects are handled automatically (see \cref{fig:tosd}).
 152 This approach to software development is called \gls{TOSD} \citep{wang_maintaining_2018}.
 153
 154 \begin{figure}[ht]
 155         \centering
 156         \begin{subfigure}[t]{.5\textwidth}
 157                 \centering
 158                 \includestandalone{traditional}
 159                 \caption{Traditional layered approach.}
 160         \end{subfigure}%
 161         \begin{subfigure}[t]{.5\textwidth}
 162                 \centering
 163                 \includestandalone{tosd}
 164                 \caption{\Gls{TOSD} approach.}
 165         \end{subfigure}
 166         \caption{Separation of concerns in a traditional setting and in \gls{TOSD} (adapted from~\cite[\citepage{20}]{wang_maintaining_2018}).}%
 167         \label{fig:tosd}
 168 \end{figure}
 169
 170 \todo{describe relation with \gls{IOT} architecture}
 171 \begin{description}
 172         \item[\Glsxtrshort{UI} (presentation layer):]
 173                 The \gls{UI} of the system is automatically generated from the representation of the type.
 174                 Even though the \gls{UI} is generated from the structure of the datatypes, in practical \gls{TOP} systems it can be tweaked afterwards to suit the specific needs of the application.
 175         \item[Tasks (business layer):]
 176                 A task is an abstract representation of a piece of work that needs to be done.
 177                 It provides an intuitive abstraction over work in the real world.
 178                 Just as with real-life tasks and workflow, tasks can be combined in various ways such as in parallel or in sequence.
 179                 Furthermore, a task is observable which means it is possible to observe a---partial---result during execution and act upon it by for example starting new tasks.
 180                 Examples of tasks are filling in a form, sending an email, reading a sensor or even doing a physical task.
 181         \item[\Glsxtrshortpl{SDS} (resource access):]
 182                 Tasks can communicate using task values but this imposes a problem in many collaboration patterns where tasks that are not necessarily related need to share data.
 183                 Tasks can also share data using \glspl{SDS}, an abstraction over any data.
 184                 An \gls{SDS} can represent typed data stored in a file, a chunk of memory, a database \etc.
 185                 \Glspl{SDS} can also represent external impure data such as the time, random numbers or sensory data.
 186                 Similar to tasks, transformation and combination of \glspl{SDS} is possible.
 187         \item[Programming language (\glsxtrshort{UOD}):]
 188                 The \gls{UOD} from the business layer is explicitly and separately modelled by the relations that exist in the functions of the host language.
 189 \end{description}
 190
 191 \subsection{\texorpdfstring{\Gls{ITASK}}{ITask}}
 192 The concept of \gls{TOP} originated from the \gls{ITASK} framework, a declarative workflow language and \gls{TOP} engine for defining multi-user distributed web applications implemented as an \gls{EDSL} in the lazy pure \gls{FP} language \gls{CLEAN} \citep{plasmeijer_itasks:_2007,plasmeijer_task-oriented_2012}.
 193 From the structural properties of the data types, the entire user interface is automatically generated.
 194
 195 As an example, \cref{lst:enter_person,fig:enter_person} show the \gls{ITASK} code and the corresponding \gls{UI} for a simple task for entering a person.
 196 From the data type definitions (\cref{lst:dt_fro,lst:dt_to}), using generic programming (\cref{lst:dt_derive}), the \glspl{UI} for the data types are automatically generated.
 197 Using task combinators (see \cleaninline{>>!} at \cref{lst:task_comb}), the tasks can be combined in sequence.
 198 Only when the user entered a complete value in the web editor, then the continue button enables and the result can be viewed.
 199 Special combinators (e.g.\ \cleaninline{@>>} at \cref{lst:task_ui}) are available to tweak the \gls{UI} afterwards.
 200
 201 \begin{figure}[ht]
 202         \includegraphics[width=.32\linewidth]{person0}
 203         \includegraphics[width=.32\linewidth]{person1}
 204         \includegraphics[width=.32\linewidth]{person2}
 205         \caption{The \gls{UI} for entering a person in \gls{ITASK}.}%
 206         \label{fig:enter_person}
 207 \end{figure}
 208
 209 \begin{lstClean}[numbers=left,caption={The \gls{UI} and code for entering a person in \gls{ITASK}.},label={lst:enter_person}]
 210 :: Person = { name :: String, gender :: Gender, dateOfBirth :: Date }[+\label{lst:dt_fro}+]
 211 :: Gender = Male | Female | Other String[+\label{lst:dt_to}+]
 212
 213 derive class iTask Person, Gender[+\label{lst:dt_derive}+]
 214
 215 enterPerson :: Task Person
 216 enterPerson
 217         =            Hint "Enter a person:" @>> enterInformation [][+\label{lst:task_ui}+]
 218         >>! \result->Hint "You Entered:"    @>> viewInformation  [] result[+\label{lst:task_comb}+]
 219 \end{lstClean}
 220
 221 \subsection{\texorpdfstring{\Gls{MTASK}}{MTask}}
 222 This thesis uses a novel \gls{TOP} language designed for defining workflows for \gls{IOT} edge devices \citep{koopman_task-based_2018}.
 223 It is written in \gls{CLEAN} as a multi-view \gls{EDSL} and hence there are multiple interpretations of the language of which the byte code compiler is the most relevant for this thesis.
 224 From the terms in the \gls{TOP} language, a very compact binary representation of the work that needs to be done is compiled.
 225 This specification is then sent to a device that runs the \gls{MTASK} \gls{RTS}, a domain-specific \gls{TOP} engine implemented as a feather-light domain-specific \gls{OS}.
 226 \Gls{MTASK} is seamlessly integrated with \gls{ITASK}, it allows the programmer to define all layers of an \gls{IOT} system from a single declarative specification.
 227
 228 \todo[inline]{Example application here, e.g.\ blink?}
 229
 230
 231 \subsection{Other \texorpdfstring{\glsxtrshort{TOP}}{TOP} languages}
 232 While \gls{ITASK} conceived \gls{TOP}, it is not the only \gls{TOP} language and engine.
 233 Some \gls{TOP} languages and systems arose from Master's and Bachelor's thesis projects (e.g.\ \textmu{}Task \citep{piers_task-oriented_2016} and LTasks \citep{van_gemert_task_2022}) or were created to solve a practical problem (e.g.\ Toppyt \citep{lijnse_toppyt_2022} and hTask \citep{lubbers_htask_2022}).
 234 Furthermore, \gls{TOPHAT} is a fully formally specified \gls{TOP} language designed to capture the essence of \gls{TOP} formally \citep{steenvoorden_tophat_2019}.
 235 It is also possible to translate \gls{TOPHAT} code to \gls{ITASK} to piggyback on the \gls{TOP} engine it offers \citep[\citesection{G.3}]{steenvoorden_tophat_2022}.
 236
 237 \section{Contributions}\label{sec:contributions}
 238 This section provides a thorough overview of the relation to publications and the scientific contributions of the episodes and chapters.
 239
 240 \subsection{\nameref{prt:dsl}}
 241 The \gls{MTASK} system is a heterogeneous \gls{EDSL} and during the development of it, several novel basal techniques for embedding \glspl{DSL} in \gls{FP} languages have been found.
 242 This first episode is a cumulative---otherwise known as paper-based---episode consisting of two papers published on novel embedding techniques.
 243 Both papers are readable independently.
 244
 245 \subsubsection*{\Fullref{chp:classy_deep_embedding}}
 246 This chapter is based on the paper: \citeentry{lubbers_deep_2022}\todo{change in-press when published}.
 247
 248 While supervising \citeauthor{amazonas_cabral_de_andrade_developing_2018}'s \citeyear{amazonas_cabral_de_andrade_developing_2018} Master's thesis, focussing on an early version of \gls{MTASK}, a seed was planted for a novel deep embedding technique for \glspl{DSL} where the resulting language is extendible both in constructs and in interpretation using type classes and existential data types.
 249 Slowly the ideas organically grew to form the technique shown in the paper.
 250 The related work section is updated with the research found only after publication.
 251 \Cref{sec:classy_reprise} was added after publication and contains a (yet) unpublished extension of the embedding technique for reducing the required boilerplate.
 252 The research from this paper and writing the paper was solely performed by me.
 253
 254 \subsubsection*{\Fullref{chp:first-class_datatypes}}
 255 This chapter is based on the paper: \citeentry{lubbers_first-class_2022}\todo{change when accepted}.
 256
 257 It shows how to inherit data types from the host language in \glspl{EDSL} using metaprogramming.
 258 It does so by providing a proof-of-concept implementation using \gls{HASKELL}'s metaprogramming system: \glsxtrlong{TH}.
 259 Besides showing the result, the paper also serves as a gentle introduction to using \glsxtrlong{TH} and contains a thorough literature study on research that uses \glsxtrlong{TH}.
 260 The research in this paper and writing the paper was performed by me, though there were weekly meetings with Pieter Koopman and Rinus Plasmeijer in which we discussed and refined the ideas.
 261
 262 \subsection{\nameref{prt:top}}
 263 This is a monograph compiled from several papers and revised lecture notes on \gls{MTASK}, the \gls{TOP} system used to orchestrate the \gls{IOT}.
 264 It provides a gentle introduction to the \gls{MTASK} system elaborates on \gls{TOP} for the \gls{IOT}.
 265 \todo[inline]{outline the chapters}
 266
 267 \begin{itemize}
 268         \item \citeentry{koopman_task-based_2018}
 269
 270                 This is the initial \gls{TOP}/\gls{MTASK} paper.
 271                 It provides an overview of the initial \gls{MTASK} language and shows first versions of a pretty printer, an \gls{ITASK} simulation and a \gls{C} code generation view.
 272                 \paragraph{Contribution}
 273                 Pieter Koopman wrote it, I helped with the software and research.
 274         \item \citeentry{lubbers_task_2018}
 275
 276                 This paper was an extension of my Master's thesis \citep{lubbers_task_2017}.
 277                 It shows how a simple imperative variant of \gls{MTASK} was integrated with \gls{ITASK}.
 278                 While the language was a lot different than later versions, the integration mechanism is still used in \gls{MTASK} today.
 279                 \paragraph{Contribution}
 280                 The research in this paper and writing the paper was performed by me, though there were weekly meetings with Pieter Koopman and Rinus Plasmeijer in which we discussed and refined the ideas.
 281         \item \citeentry{lubbers_multitasking_2019}\footnote{%
 282                 This work acknowledges the support of the ERASMUS+ project ``Focusing Education on Composability, Comprehensibility and Correctness of Working Software'', no. 2017--1--SK01--KA203--035402
 283                 }
 284
 285                 This paper was a short paper on the multitasking capabilities of \gls{MTASK} in contrast to traditional multitasking methods for \gls{ARDUINO}.
 286                 \paragraph{Contribution}
 287                 The research in this paper and writing the paper was performed by me, though there were weekly meetings with Pieter Koopman and Rinus Plasmeijer.
 288         \item \citeentry{koopman_simulation_2018}\footnotemark[\value{footnote}]\todo{change when published}
 289
 290                 These revised lecture notes are from a course on the \gls{MTASK} simulator was provided at the 2018 \gls{CEFP}/\gls{3COWS} winter school in Ko\v{s}ice, Slovakia.
 291                 \paragraph{Contribution}
 292                 Pieter Koopman wrote and taught it, I helped with the software and research.
 293         \item \citeentry{lubbers_writing_2019}\footnotemark[\value{footnote}]\todo{change when published}
 294
 295                 These revised lecture notes are from a course on programming in \gls{MTASK} provided at the 2019 \gls{CEFP}/\gls{3COWS} summer school in Budapest, Hungary.
 296                 \paragraph{Contribution}
 297                 Pieter Koopman prepared and taught half of the lecture and supervised the practical session.
 298                 I taught the other half of the lecture, wrote the lecture notes, made the assignments and supervised the practical session.
 299         \item \citeentry{lubbers_interpreting_2019}
 300
 301                 This paper shows an implementation for \gls{MTASK} for microcontrollers in the form of a compilation scheme and informal semantics description.
 302                 \paragraph{Contribution}
 303                 The research in this paper and writing the paper was performed by me, though there were weekly meetings with Pieter Koopman and Rinus Plasmeijer.
 304         \item \citeentry{crooijmans_reducing_2022}\todo{change when published}
 305
 306                 This paper shows how to create a scheduler so that devices running \gls{MTASK} tasks can go to sleep more automatically.
 307                 \paragraph{Contribution}
 308                 The research was carried out by \citet{crooijmans_reducing_2021} during his Master's thesis.
 309                 I did the daily supervision and helped with the research, Pieter Koopman was the formal supervisor and wrote most of the paper.
 310         \item \emph{Green Computing for the Internet of Things}\footnote{
 311                 This work acknowledges the support of the Erasmus+ project ``SusTrainable---Promoting Sustainability as a Fundamental Driver in Software Development Training and Education'', no. 2020--1--PT01--KA203--078646}\todo{change when published}
 312
 313                 \paragraph{Contribution}
 314                 These revised lecture notes are from a course on sustainable programming using \gls{MTASK} provided at the 2022 SusTrainable summer school in Rijeka, Croatia.
 315                 Pieter prepared and taught a quarter of the lecture and supervised the practical session.
 316                 I prepared and taught the other three quarters of the lecture, made the assignments and supervised the practical session\todo{writing contribution}.
 317 \end{itemize}
 318
 319 \subsection{\nameref{prt:tvt}}
 320 \Cref{prt:tvt} is based on a journal paper that quantitatively and qualitatively compares traditional \gls{IOT} architectures with \gls{IOT} systems using \gls{TOP} and contains a single chapter.
 321 This chapter is based on the journal paper: \citeentry{lubbers_could_2022}\todo{change when published}\footnote{This work is an extension of the conference article: \citeentry{lubbers_tiered_2020}\footnotemark{}}.
 322 \footnotetext{This paper was partly funded by the Radboud-Glasgow Collaboration Fund.}
 323
 324 It compares programming traditional tiered architectures to tierless architectures by showing a qualitative and a quantitative four-way comparison of a smart-campus application.
 325
 326 \paragraph{Contribution}
 327 Writing the paper was performed by all authors.
 328 I created the server application, the \gls{CLEAN}/\gls{ITASK}/\gls{MTASK} implementation (\glsxtrshort{CWS}) and the \gls{CLEAN}/\gls{ITASK} implementation (\glsxtrshort{CRS})
 329 Adrian Ramsingh created the \gls{MICROPYTHON} implementation (\glsxtrshort{PWS}), the original \gls{PYTHON} implementation (\glsxtrshort{PRS}) and the server application were created by \citet{hentschel_supersensors:_2016}.
 330
 331 \input{subfilepostamble}
 332 \end{document}