feat: applied Dante's comments to the implementation

1 files changed, 11 insertions, 13 deletions

diff --git a/content/background.tex b/content/background.tex
index 6e39e6d..3e0a5cf 100644
--- a/content/background.tex
+++ b/content/background.tex
@@ -160,11 +160,11 @@ In this subsection, we describe the methods for collecting relevant scientific a
 
 \begin{enumerate}[label=\textbf{\arabic*.}]
 	\item \textbf{Review Strategy}\\
-	      The most common methods for conducting literature surveys are \begin{enumerate*}[label=(\arabic*)]
+	      According to Suman \etal~\cite{DBLP:conf/wosp/SumanCNTMI24}, the most common methods for conducting literature surveys are \begin{enumerate*}[label=(\arabic*)]
 		      \item random traversal of the related literature,
 		      \item snowballing~\cite{ACM:article/Webster2002},
 		      \item systematic literature survey as proposed by Kitchenham \etal~\cite{DBLP:journals/infsof/KitchenhamPBBTNL10}
-	      \end{enumerate*}~\cite{DBLP:conf/wosp/SumanCNTMI24}
+	      \end{enumerate*}.
 	      Random traversal encompasses surveying the field by following suggestions from portals like Google Scholar and randomly querying the different databases.
 	      It is an unstructured way to conduct the literature review, and requires little effort.
 	      Snowballing is similar to random traversal, but it is more structured.
@@ -259,7 +259,14 @@ Kalibre takes the best of both \gls{ml} and \gls{cfd} approaches and achieves su
 % What is more, Microsoft already offers digital twinning as a service https://azure.microsoft.com/en-us/products/digital-twins/
 % Documentation: https://learn.microsoft.com/en-us/azure/digital-twins/
 % Moreover, NVIDIA is doing too as well https://www.nvidia.com/en-sg/omniverse/
-
+\begin{figure}[t]
+	\centering
+	\includegraphics[width=0.95\linewidth]{images/system_model.png}
+	\caption[A system model for datacenter digital twins.]{A generic system model for datacenter digital twin deployments.
+		The design of DyTwin~\cite{DBLP:conf/sc/TaheriBPRHDEWPM24}  indirectly incorporates in its architecture a ``virtual-to-virtual`` digital thread between different digital twins.
+		Zhao \etal likewise present key elements to the digital thread in their architecture~\cite{DBLP:conf/AppliedEnergy/Zhao20}. We add the \emph{Digital Thread} to our model explicitly.}
+	\label{fig:system_model}
+\end{figure}
 \subsection{System Model for Datacenter Digital Twinning}
 \label{ss:system_model_for_dcdts}
 In \Cref{fig:system_model} we present a holistic model of \gls{dcdt}s from \Cref{sss:advanced_dts}.
@@ -316,15 +323,6 @@ We distinguish 3 core elements of every \gls{dcdt}:
 	      In order to adhere to the holistic view of \gls{dcdt}s, and to fulfill the \gls{nasem}'s definition, the system must contain all 3 of these elements.
 \end{enumerate}
 
-\begin{figure}[t]
-	\centering
-	\includegraphics[width=0.95\linewidth]{images/system_model.png}
-	\caption[A system model for datacenter digital twins.]{A generic system model for datacenter digital twin deployments.
-		The design of DyTwin~\cite{DBLP:conf/sc/TaheriBPRHDEWPM24}  indirectly incorporates in its architecture a ``virtual-to-virtual`` digital thread between different digital twins.
-		Zhao \etal likewise present key elements to the digital thread in their architecture~\cite{DBLP:conf/AppliedEnergy/Zhao20}. We add the \emph{Digital Thread} to our model explicitly.}
-	\label{fig:system_model}
-\end{figure}
-
 %To summarize, many \gls{dcdt}'s model the cooling systems inside the warehouse, because in a typical datacenter cooling accounts for more than 40\% of total electricity usage~\cite{DBLP:conf/AppliedEnergy/Zhao20}.
 %Since the cooling subsystem is mainly airflow-based, \gls{dt} designers often opt for a \gls{cfd} approach to model the facility.
 %The reason why a digital twin might be needed for a cooling subsystem is primarily because of inefficient operational strategy.
@@ -347,4 +345,4 @@ We distinguish 3 core elements of every \gls{dcdt}:
 
 %In your work, consider adding such an endpoint, albeit explain in future work that you envision \emph{implementing} this endpoint in the future.
 
-\section{Discussion}\label{ss:background_discussion}
+%\section{Discussion}\label{ss:background_discussion}