Update on local

IEEE-conference-template-062824.tex

@@ -13,7 +13,8 @@
 \usepackage{subcaption}
 \begin{document}
 
-\title{Intermittent Systems with Small Scale: Model and Design Guidelines \\
+% \title{Intermittent Systems with Small Scale: Model and Design Guidelines \\
+\title{Intermittent Systems in Small Scale: Execution Model and Design Guidelines \\
 % \thanks{Identify applicable funding agency here. If none, delete this.}
 }
 

sections/Introduction.tex

@@ -5,6 +5,19 @@ Intermittent system consists of hardware and software.
 \begin{figure}
     \centering
     \includegraphics[width=\linewidth]{figs/intermittent_computing.pdf}
-    \caption{caption}
+    \caption{Traditional execution model of intermittent systems.}
     \label{fig:introduction}
-\end{figure}
+\end{figure}
+
+
+Intermittent systems require software support to maintain volatile system states across power failures.
+Software designers rely on an \emph{execution model}, which abstracts the operations in the hardware and describes how intermittent system works.
+Fig.~\ref{fig:introduction} shows this model.
+The voltage of energy storage increases while the system collects energy from environmental sources.
+When the capacitor voltage reaches a certain threshold voltage, the computing system is powered on and executes.
+When the capacitor voltage hits a power-off threshold later, the computing system is powered off and energy starts to be collected again.
+The goal of software designers is to implement techniques to sustain system states across power failures with minimal overhead under such execution model.
+
+The model is not precise enough for recent techniques that aim power failures with frequency of several tens of milliseconds or even in nanosecond scale.
+The major source of error is the decoupling capacitors in the system.
+To achieve millisecond-level execution time, the system should adopt a tiny capacitor, whose size is comparable to the decoupling capacitors.

sections/OurModel.tex

@@ -8,20 +8,49 @@
     \centering
     \begin{subfigure}{\linewidth}
         \includegraphics[width=\textwidth]{figs/plot_expr_8a_cropped.pdf}
-        \caption{Solar energy trace.}
+        \caption{Trace of one power cycle.}
         % \label{fig:eval_voltage_trace}
     \end{subfigure}
     \begin{subfigure}{\linewidth}
         \includegraphics[width=\textwidth]{figs/plot_expr_8b_cropped.pdf}
-        \caption{The number of finished tasks over time.}
+        \caption{Detailed trace.}
         % \label{fig:eval_adaptivenss_finished_tasks}
     \end{subfigure}
-    % \caption{Evaluating adaptability of \textproc{FastTrack}.}
+    \caption{Voltage of the capacitor and Vdd, sampled 470uF and 1.5mA.}
     % \label{fig:}
 \end{figure}
 
+Three key observations that affect software designer's decision.
+
+\begin{itemize}
+    \item \textbf{O1}: The capacitor voltage drops quickly to charge decoupling capacitor when system wakes-up ($t1$--$t2$).
+    \item \textbf{O2}: The system executes at sub-voltage using the decoupling capacitor, even after power supply stops ($t4$--$t5$).
+    \item \textbf{O3}: The decoupling capacitor discharges while the system is powered-off (after $t5$).
+\end{itemize}
+
+\begin{figure}
+    \centering
+    \includegraphics[width=\linewidth]{figs/detailed_execution_model.pdf}
+    \caption{Traditional execution model of intermittent systems.}
+    \label{fig:detailed_execution_model}
+\end{figure}
+
 \subsection{Impact on Power Efficiency}
 
+\begin{figure}
+    \centering
+    \includegraphics[width=\linewidth]{figs/plot_expr_5_cropped.pdf}
+    \caption{caption}
+    % \label{fig:introduction}
+\end{figure}
+
 \subsection{Impact on Predicting Power Failures}
 
+\begin{figure}
+    \centering
+    \includegraphics[width=\linewidth]{figs/plot_expr_6_cropped.pdf}
+    \caption{caption}
+    % \label{fig:introduction}
+\end{figure}
+
 Show percentage of execution time executed after power supply stops.