many many updates

[phd-thesis.git] / top / green.tex

diff --git a/top/green.tex b/top/green.tex
index 2ba1ffd..83734fe 100644 (file)
--- a/top/green.tex
+++ b/top/green.tex
@@ -2,6 +2,8 @@
 
 \input{subfilepreamble}
 
+\setcounter{chapter}{6}
+
 \begin{document}
 \input{subfileprefix}
 \chapter{Green computing with \texorpdfstring{\gls{MTASK}}{mTask}}%
@@ -193,7 +195,7 @@ Evaluating a task earlier should not change its result but just consumes more en
 \end{equ}
 
 \subsubsection{Sequential combinators}
-For the step combinator (\cref{R:step})---and all other derived sequential combinators---the refresh rate of the left-hand side task is taken since that is the only task that is rewritten.
+For the step combinator (\cref{R:step})---and all other derived sequential combinators\nobreak---\nobreak\hskip0ptthe refresh rate of the left-hand side task is taken since that is the only task that is rewritten.
 Only after stepping, the combinator rewrites to the right-hand side.
 
 \subsubsection{Repeating combinators}
@@ -348,7 +350,7 @@ timedPulseNaive = declarePin D0 PMOutput \d0->
        }
 \end{lstClean}
 
-\section{Task scheduling in the \texorpdfstring{\gls{MTASK}}{mTask} engine}
+\section{Task scheduling in the \texorpdfstring{\gls{MTASK}}{mTask} engine}\label{sec:scheduling}
 The rewrite rates from the previous section only tell us how much the next evaluation of the task can be delayed.
 An \gls{IOT} edge devices executes multiple tasks may run interleaved.
 In addition, it has to communicate with a server to collect new tasks and updates of \glspl{SDS}.
@@ -585,5 +587,8 @@ Evaluating interrupt task node in the task tree is trivial because all of the wo
 The task emits the status of the pin as a stable value if the information in the task shows that it was triggered.
 Otherwise, no value is emitted.
 
+\section{Conclusion}
+\todo[inline]{Conclusion}
+
 \input{subfilepostamble}
 \end{document}