diff options
| -rw-r--r-- | citations/BScAndreadisLongAgo.pdf | bin | 0 -> 1767031 bytes | |||
| -rw-r--r-- | content/background.tex | 73 | ||||
| -rw-r--r-- | content/intro.tex | 2 | ||||
| -rw-r--r-- | images/thesis_structure.png | bin | 496351 -> 507885 bytes | |||
| -rw-r--r-- | main.bib | 159 | ||||
| -rw-r--r-- | sources/thesis_structure.drawio | 22 |
6 files changed, 203 insertions, 53 deletions
diff --git a/citations/BScAndreadisLongAgo.pdf b/citations/BScAndreadisLongAgo.pdf Binary files differnew file mode 100644 index 0000000..06600f1 --- /dev/null +++ b/citations/BScAndreadisLongAgo.pdf diff --git a/content/background.tex b/content/background.tex index 8e63f53..5ab53dc 100644 --- a/content/background.tex +++ b/content/background.tex @@ -1,18 +1,17 @@ \chapter{Background}\label{s:background} - \section{Overview}\label{ss:background_overview} \begin{mynote} The contribution in this chapter is three-fold: \begin{enumerate}[label=\emph{C\textsubscript{\arabic*}}, itemsep=0.2pt] \item We provide a brief overview on datacenter simulation (\Cref{sss:simulation}), compute failures (\Cref{sss:failures}), and digital twinning (\Cref{sss:what_is_digital_twinning}). - \item We survey the state-of-the-art concerning datacenter digital twinning (\Cref{sss:digital_twins_for_datacenters}). + \item We survey the state-of-the-art concerning datacenter digital twinning (\Cref{ss:digital_twins_for_datacenters}). \item We construct a system model for existing datacenter digital twins (\Cref{ss:system_model_for_dcdts}) \end{enumerate} \end{mynote} \section{Datacenters}\label{ss:datacenters} -In this section we provide a short background on datacenter simulation and hardware failures. +In this section we provide a short background on datacenter simulation and compute failures. We find it useful to provide a brief introduction to both topics so as to ensure reader's fullest understanding of subsequent chapters. Since datacenters are important building blocks of the digital society, reliable warehouse management is a key priority for datacenter operators. Incorrect management decisions can lead to missed \gls{sla}s~\cite{DBLP:journals/corr/IosupKLVG22} and even large financial penalties~\cite{DBLP:report/AnnualOutageAnalysis2025}. @@ -41,7 +40,7 @@ Further details about {OpenDC} can be referred to in the linked literature \cite \subsection{Compute Failures}\label{sss:failures} A failure is defined as ``an event that makes a system fail to operate according to its specifications``~\cite{DBLP:journals/jpdc/JavadiKIE13}. -We distinguish 2 failure types: \begin{enumerate*} +We distinguish 2 failure types: \begin{enumerate*}[label=(\arabic*)] \item software failures \item hardware failures. \end{enumerate*} @@ -60,12 +59,6 @@ In summary OpenDC enables experimentation with failures that enables insights th However, the fidelity of failure modeling inside a datacenter simulation is still insufficient to predict in failures in real-time, as they happen in a physical datacenter. Since a datacenter simulator is quite different from a digital twin, we cannot use the same computation methods from simulation to predict real-time failures. Digital twinning is an improvement upon pure simulation. - -\section{Digital Twinning}\label{ss:digital-twinning} -In this section we explore how the datacenter management can be improved using a novel modelling technique, digital twinning. -We present the generic, field-agnostic \gls{dt} definition and investigate how \emph{datacenter} digital twinning applies the definition in practice. - -\subsection{What is Digital Twinning?}\label{sss:what_is_digital_twinning} \begin{figure}[t] \centering \includegraphics[width=0.95\linewidth]{images/five_dimensional_dt.pdf} @@ -73,11 +66,17 @@ We present the generic, field-agnostic \gls{dt} definition and investigate how \ %Fei Tao is a renowned figure with over 62k citations. He is a figure of authority on digital twins.% \label{fig:five_dimensional_dt} \end{figure} +\section{Digital Twinning}\label{ss:digital-twinning} +In this section we explore how the datacenter management can be improved using a novel modelling technique, digital twinning. +We present the generic, field-agnostic \gls{dt} definition and investigate how \emph{datacenter} digital twinning applies the definition in practice. + +\subsection{What is Digital Twinning?}\label{sss:what_is_digital_twinning} + % Here talk a bit about different types of data analytics that are performed in a digital twin. ``A \emph{digital twin} is a set of virtual information constructs that mimics the structure, context and behaviour of a natural, engineered or social system, is dynamically updated with data from its physical twin, has predictive capability, and informs decisions that realize value''~\cite{DBLP:usdoe/report/AP26894}. A crucial characteristic that differentiates digital twinning from simulation and statistical modelling is the \emph{digital thread}: a bi-directional channel that enables continuous interaction between the virtual and physical entities. The longer the \gls{dt} is working, the more accurate its predictions, because a holistic twin aggregates historical patterns together with up-to-date monitoring data. -A generic \gls{dt} architecture is depicted in Figure \ref{fig:five_dimensional_dt} Section \ref{s:intro} from Tao \etal~\cite{DBLP:conf/cirp/TAO2018169}. +A generic \gls{dt} architecture is depicted in Figure \ref{fig:five_dimensional_dt} from Tao \etal~\cite{DBLP:conf/cirp/TAO2018169}. % Why has not anyone done this before? Digital twinning has only recently become feasible because of the developments in \gls{hpc}. @@ -93,10 +92,10 @@ A crucial part any of any \gls{dt} is \emph{predictive modelling}, which drives \label{fig:predictive_analytics} \end{figure} Predictive modelling uses statistics to predict outcomes. -When deployed commercially, for example in datacenters, predictive modelling is often referred to as predictive analytics~\cite{Wikipedia:PredictiveModelling}. -Almost any statistical model can be used for prediction purposes, but nowadays predictive analysis is synonymous with machine learning. +When deployed commercially, for example in datacenters, predictive modelling is often referred to as predictive analytics~\cite{Wikipedia:article/PredictiveModelling}. +Almost any statistical model can be used for prediction purposes, but nowadays predictive analysis is synonymous with \gls{ml}. A primary example of popular analysis type is linear regression. -However, any modelling technique, \eg \emph{discrete-event simulation} can be used to make the predictions. +However, any modelling technique (\eg \emph{discrete-event simulation}) can be used to make the predictions. Predictive analysis belongs to a larger domain of \gls{oda}. \gls{oda} is the ``use of operational data instrumentation, analysis, integration, and archiving, towards effective design, commissioning, and optimization of datacenter operations'' \cite{DBLP:conf/icppw/BourassaJBCJVS19}. @@ -108,15 +107,53 @@ There exist several \gls{oda} frameworks, for example OMNI \cite{DBLP:conf/icppw A major limitation of predictive analytics is that history cannot always predict the future. Using historical data to predict outcomes works only under the assumption that there are certain long lasting patterns in the system. -Additionally, no matter how extensive is the training data, there is always the possibility of new variables that have not been considered or even defined, yet are critical to the outcome of the prediction~\cite{Wikipedia:PredictiveModelling}. +Additionally, no matter how extensive is the training data, there is always the possibility of new variables that have not been considered or even defined, yet are critical to the outcome of the prediction~\cite{Wikipedia:article/PredictiveModelling}. -\subsection{Digital Twins for Datacenters}\label{sss:digital_twins_for_datacenters} +\section{Literature Survey of Digital Twins for Datacenters}\label{ss:digital_twins_for_datacenters} In this section, we survey the work related to datacenter digital twinning. We summarize our results in Table \ref{tab:dt_features_comparison} to compare and contrast the features of existing datacenter digital twins. We select only the digital twins that adhere closest to the \gls{nasem} definition~\cite{DBLP:usdoe/report/AP26894}. +\subsection{Methodology}\label{sss:method} +The aim of this survey is to search and organize the field of \gls{dcdt}s. +In this subsection, we describe the methods for collecting relevant scientific articles and present the design of the system model for generic \gls{dcdt}s. + +\begin{enumerate}[label=\textbf{\arabic*.}, align=left] + \item \textbf{Review Strategy}\\ + 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} + 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. + The surveyor follows references from the relevant articles, and there is a depth limit~\cite{DBLP:conf/wosp/SumanCNTMI24}. + Systematic literature survey is a rigorous, fully-structured process to searching for literature, and it follows the method devised by Barbara Kitchenham~\cite{DBLP:journals/infsof/KitchenhamPBBTNL10}. + In our work, to scope down the project we chose a mix of (1) and (2), with some elements of (3) instead of following solely the systematic literature review process of Kitchenham \etal. + Therefore, our literature cannot be regarded as systematic, instead we can refer to it as comprehensive or semi-structured. + \item \textbf{Analysis of Selected Material}\\ + We borrow the process of Suman \etal conducted during his MSc thesis for a literature survey of \gls{oda}~\cite{DBLP:conf/wosp/SumanCNTMI24}. + The process can be described as follows. + \begin{enumerate*}[label=(\arabic*)] + \item first, search given queries followed by a manual inspection of the context of the article + \item then scan each article, by reading over the abstract, introduction and conclusion and decide whether it applies to \gls{dcdt}s. + \item after selection, extract the details of the \gls{dcdt} from the publication by reading carefully over the article. + \item lastly, interpret the functionality of the \gls{dcdt}s and systematically organize them. + \end{enumerate*} + \item \textbf{Design of the System Model}\\ + Based on the findings of the literature survey, we create a conceptual model of the \gls{dcdt} field. + We decided to create a system model, as the field of \gls{dcdt}s is still under development, and does not include many digital twin deployments. + An alternative to a system model would be a taxonomy. + To create the system model, we first gathered the functionality present in all the \gls{dcdt}s. + For each \gls{dcdt} feature in every article, we evaluated whether this feature is present in other deployments and how important it is for the \gls{dt}. + The result of this process is a set of \gls{dcdt} features that belong to the largest proportion of all \gls{dcdt}s. + Afterwards, for each of the features, we decide how it is interconnected. +\end{enumerate} + \input{sources/dt_features_comparison.tex} +\subsection{Advanced Digital Twins for Datacenters}\label{sss:advanced_dts} ExaDigiT~\cite{DBLP:conf/sc/BrewerMKWBHSGGW24} is an open-source framework for developing digital twins of supercomputers. It consists of 3 modules: \begin{enumerate*}[label=(\arabic*)] @@ -183,7 +220,7 @@ Kalibre takes the best of both \gls{ml} and \gls{cfd} approaches and achieves su % Documentation: https://learn.microsoft.com/en-us/azure/digital-twins/ % Moreover, NVIDIA is doing too as well https://www.nvidia.com/en-sg/omniverse/ -\section{System Model for Datacenter Digital Twinning} +\subsection{System Model for Datacenter Digital Twinning} \label{ss:system_model_for_dcdts} \begin{figure}[t] @@ -210,13 +247,11 @@ Kalibre takes the best of both \gls{ml} and \gls{cfd} approaches and achieves su %Include something about data-preprocessing in the pipeline. %See the article by Fei Tao - %Moreover, a crucial parallel between the work of Zhao \etal and ExaDigiT is the concept of multiple models within a single digital twin. %Brewer \etal argue ExaDigiT is compromised of 5 ``smaller'' twins too. %In Zhang \etal the digital twin can communicate with different other digital twins, as in the work of Taheri \etal. %To do this, the working program has an API, with a specific API endpoint to communicate with other Digital Twins. - %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} diff --git a/content/intro.tex b/content/intro.tex index 69322d4..e907fee 100644 --- a/content/intro.tex +++ b/content/intro.tex @@ -40,7 +40,7 @@ To address this new problem a concept of a datacenter \gls{dt} was proposed~\cit % A digital twin is often called a virtual twin. % The communication between a physical entity and the digital twin is referred to as a digital thread. A \gls{dt} is a virtual model of an intended or actual real-world system that serves as its counterpart for purposes such as simulation, integration, testing, monitoring and maintenance. -The digital twin replicates the physical system to predict failures, prescribe real-time actions for mitigating unexpected events, observing and evaluating the behaviour of the system~\cite{WIKI:page/DigitalTwin}. +The digital twin replicates the physical system to predict failures, prescribe real-time actions for mitigating unexpected events, observing and evaluating the behaviour of the system~\cite{Wikipedia:article/DigitalTwin}. Most modern \gls{dt} usages are related to prognostics and system health management~\cite{DBLP:conf/cirp/TAO2018169}. For example, in aerospace engineering, the \gls{dt} analyzes operational data (\eg temperature, vibration) to predict when a airplane component is likely to fail. diff --git a/images/thesis_structure.png b/images/thesis_structure.png Binary files differindex cb9937c..e64a64d 100644 --- a/images/thesis_structure.png +++ b/images/thesis_structure.png @@ -14,6 +14,9 @@ timestamp = {Mon, 05 Feb 2024 20:18:06 +0100}, biburl = {https://dblp.org/rec/journals/corr/abs-2206-03259.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/corr/abs-2206-03259.html?view=bibtex + }}, } @inproceedings{DBLP:conf/ccgrid/MastenbroekAJLB21, @@ -37,6 +40,9 @@ timestamp = {Wed, 07 Dec 2022 23:07:44 +0100}, biburl = {https://dblp.org/rec/conf/ccgrid/MastenbroekAJLB21.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/ccgrid/MastenbroekAJLB21.html?view=bibtex + }.}, } @inproceedings{DBLP:conf/icdcs/IosupVTETBFMT19, @@ -56,6 +62,9 @@ timestamp = {Fri, 04 Jul 2025 22:07:32 +0200}, biburl = {https://dblp.org/rec/conf/icdcs/IosupVTETBFMT19.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/icdcs/IosupVTETBFMT19.html?view=bibtex} + .}, } @article{DBLP:journals/infsof/KitchenhamPBBTNL10, @@ -74,6 +83,9 @@ timestamp = {Tue, 21 Mar 2023 21:13:31 +0100}, biburl = {https://dblp.org/rec/journals/infsof/KitchenhamPBBTNL10.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/infsof/KitchenhamPBBTNL10.html?view=bibtex + }.}, } @inproceedings{DBLP:conf/date/MilojicicFDR21, @@ -91,16 +103,20 @@ timestamp = {Wed, 21 Jul 2021 10:05:23 +0200}, biburl = {https://dblp.org/rec/conf/date/MilojicicFDR21.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/date/MilojicicFDR21.html?view=bibtex}.}, } -@misc{WIKI:page/DigitalTwin, +@misc{Wikipedia:article/DigitalTwin, author = "{Wikipedia contributors}", title = "Digital twin --- {Wikipedia}{,} The Free Encyclopedia", year = "2026", url = " https://en.wikipedia.org/w/index.php?title=Digital_twin&oldid=1351132391 ", - note = "[Online; accessed 17-May-2026]", + note = "This BibTeX citation comes from \url{ + https://en.wikipedia.org/w/index.php?title=Special:CiteThisPage&page=Digital_twin&id=1359969562&wpFormIdentifier=titleform#BibTeX_entry + }", } @article{DBLP:journals/computer/AthavaleBBMMPS24, @@ -118,6 +134,9 @@ timestamp = {Tue, 22 Oct 2024 21:09:19 +0200}, biburl = {https://dblp.org/rec/journals/computer/AthavaleBBMMPS24.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/computer/AthavaleBBMMPS24.html?view=bibtex + }.}, } @inproceedings{DBLP:conf/icppw/BourassaJBCJVS19, @@ -137,6 +156,9 @@ timestamp = {Mon, 29 Jul 2019 12:39:30 +0200}, biburl = {https://dblp.org/rec/conf/icppw/BourassaJBCJVS19.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/icppw/BourassaJBCJVS19.html?view=bibtex + }}, } @inproceedings{DBLP:conf/hpdc/NettiMGOTO020, @@ -158,6 +180,8 @@ timestamp = {Sun, 04 Aug 2024 19:37:21 +0200}, biburl = {https://dblp.org/rec/conf/hpdc/NettiMGOTO020.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/hpdc/NettiMGOTO020.html?view=bibtex}}, } @inproceedings{DBLP:conf/wosp/SumanCNTMI24, @@ -178,6 +202,8 @@ timestamp = {Fri, 17 May 2024 21:42:59 +0200}, biburl = {https://dblp.org/rec/conf/wosp/SumanCNTMI24.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/wosp/SumanCNTMI24.html?view=bibtex}}, } @inproceedings{DBLP:conf/sc/BrewerMKWBHSGGW24, @@ -198,9 +224,12 @@ timestamp = {Thu, 19 Dec 2024 09:58:08 +0100}, biburl = {https://dblp.org/rec/conf/sc/BrewerMKWBHSGGW24.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/sc/BrewerMKWBHSGGW24.html?view=bibtex}. + }, } -@misc{Wikipedia:PredictiveModelling, +@misc{Wikipedia:article/PredictiveModelling, author = "{Wikipedia contributors}", title = "Predictive modelling --- {Wikipedia}{,} The Free Encyclopedia", year = "2026", @@ -230,6 +259,8 @@ timestamp = {Sun, 04 Aug 2024 19:43:01 +0200}, biburl = {https://dblp.org/rec/conf/acsos/TalluriOVTI21.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/acsos/TalluriOVTI21.html?view=bibtex}.}, } @misc{DBLP:report/AnnualOutageAnalysis2025, @@ -242,8 +273,11 @@ author = {Donnellan, Douglas and Lawrence, Andy and Weinshenk, Rose}, year = {2025}, month = {May}, + note = {This citation has been written by me. The Uptime Institue (see + \url{uptimeinstitute.com}) is a renowned institution that + certifies datacenters. For more information we advise to look at + \url{https://en.wikipedia.org/wiki/451_Group#Uptime_Institute}, }, } - @article{DBLP:conf/cirp/TAO2018169, title = {Digital twin driven prognostics and health management for complex equipment}, @@ -259,6 +293,9 @@ }, author = {Fei Tao and Meng Zhang and Yushan Liu and A.Y.C. Nee}, keywords = {Maintenance, Condition monitoring, Digital twin}, + note = {This BibTeX citation comes from \url{ + https://www.sciencedirect.com/science/article/abs/pii/S0007850618300799?via%3Dihub + }.}, } @inproceedings{DBLP:conf/AIAA/Teugel2012, @@ -267,8 +304,12 @@ Structures, Structural Dynamics and Materials Conference}, year = {2012}, month = {04}, - doi = {https://doi.org/10.2514/6.2012-1812}, + url = {https://doi.org/10.2514/6.2012-1812}, author = {Tuegel, Eric}, + note = {This citation has been created by me. See \url{ + https://arc.aiaa.org/doi/abs/10.2514/6.2012-1812} for more + details about the conference and the article. AIAA is a + world-class aerospace engineering association.}, } @article{DBLP:journal/IJAE/Teugel2011, @@ -284,26 +325,8 @@ url = {https://onlinelibrary.wiley.com/doi/abs/10.1155/2011/154798}, eprint = {https://onlinelibrary.wiley.com/doi/pdf/10.1155/2011/154798}, year = {2011}, -} - - -@proceedings{DBLP:conf/ASME/Bielefeldt2015, - author = {Bielefeldt, Brent and Hochhalter, Jacob and Hartl, Darren}, - title = {Computationally Efficient Analysis of SMA Sensory Particles - Embedded in Complex Aerostructures Using a Substructure Approach - }, - volume = {Volume 1: Development and Characterization of Multifunctional - Materials; Mechanics and Behavior of Active Materials; Modeling - , Simulation and Control of Adaptive Systems}, - series = {Smart Materials, Adaptive Structures and Intelligent Systems}, - pages = {V001T02A007}, - year = {2015}, - month = {09}, - doi = {10.1115/SMASIS2015-8975}, - url = {https://doi.org/10.1115/SMASIS2015-8975}, - eprint = { - https://asmedigitalcollection.asme.org/SMASIS/proceedings-pdf/SMASIS2015/57298/V001T02A007/4457748/v001t02a007-smasis2015-8975.pdf - }, + note = {This BibTeX citation comes from \url{ + https://onlinelibrary.wiley.com/doi/full/10.1155/2011/154798}.}, } @article{DBLP:journals/spe/GuptaDGB17, @@ -322,6 +345,8 @@ timestamp = {Mon, 17 Aug 2020 16:23:50 +0200}, biburl = {https://dblp.org/rec/journals/spe/GuptaDGB17.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/spe/GuptaDGB17.html?view=bibtex}}, } @article{DBLP:journals/spe/CalheirosRBRB11, @@ -340,6 +365,9 @@ timestamp = {Fri, 30 Dec 2022 14:59:15 +0100}, biburl = {https://dblp.org/rec/journals/spe/CalheirosRBRB11.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/spe/CalheirosRBRB11.html?view=bibtex + }}, } @article{DBLP:journals/corr/CasanovaGLQS13, @@ -356,6 +384,9 @@ timestamp = {Mon, 13 Aug 2018 16:47:20 +0200}, biburl = {https://dblp.org/rec/journals/corr/CasanovaGLQS13.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/corr/CasanovaGLQS13.html?view=bibtex + }}, } @inproceedings{DBLP:conf/europar/IosupSE08, @@ -375,6 +406,8 @@ timestamp = {Sun, 02 Jun 2019 21:22:55 +0200}, biburl = {https://dblp.org/rec/conf/europar/IosupSE08.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/europar/IosupSE08.html?view=bibtex}}, } @inproceedings{DBLP:conf/europar/OstermannPPF10, @@ -399,6 +432,9 @@ timestamp = {Mon, 03 Mar 2025 21:04:12 +0100}, biburl = {https://dblp.org/rec/conf/europar/OstermannPPF10.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/europar/OstermannPPF10.html?view=bibtex + }}, } @article{DBLP:journals/grid/NunezVCCCL12, @@ -418,6 +454,9 @@ timestamp = {Sun, 19 Jan 2025 14:31:14 +0100}, biburl = {https://dblp.org/rec/journals/grid/NunezVCCCL12.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/grid/NunezVCCCL12.html?view=bibtex} + }, } @article{DBLP:journals/fgcs/MichonGGUK17, @@ -433,6 +472,9 @@ timestamp = {Tue, 21 Mar 2023 21:06:55 +0100}, biburl = {https://dblp.org/rec/journals/fgcs/MichonGGUK17.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/fgcs/MichonGGUK17.html?view=bibtex} + }, } @article{DBLP:journals/jpdc/CasanovaTKS21, @@ -449,6 +491,9 @@ timestamp = {Thu, 29 Jul 2021 13:41:54 +0200}, biburl = {https://dblp.org/rec/journals/jpdc/CasanovaTKS21.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/jpdc/CasanovaTKS21.html?view=bibtex + }}, } @inproceedings{DBLP:conf/aina/WickremasingheCB10, @@ -467,6 +512,9 @@ timestamp = {Fri, 24 Mar 2023 00:03:53 +0100}, biburl = {https://dblp.org/rec/conf/aina/WickremasingheCB10.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/aina/WickremasingheCB10.html?view=bibtex + }.}, } @inproceedings{DBLP:conf/eScience/ChenD12, @@ -483,6 +531,8 @@ timestamp = {Fri, 24 Mar 2023 00:04:10 +0100}, biburl = {https://dblp.org/rec/conf/eScience/ChenD12.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/eScience/ChenD12.html?view=bibtex}}, } @misc{DBLP:data/11/CasanovaSTPJKAOS20f, @@ -501,6 +551,9 @@ timestamp = {Wed, 18 Jun 2025 15:49:44 +0200}, biburl = {https://dblp.org/rec/data/11/CasanovaSTPJKAOS20f.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/data/11/CasanovaSTPJKAOS20.html?view=bibtex} + }, } @article{DBLP:journals/tcc/HirofuchiLP18, @@ -517,6 +570,9 @@ timestamp = {Sun, 21 Jun 2020 17:41:42 +0200}, biburl = {https://dblp.org/rec/journals/tcc/HirofuchiLP18.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/tcc/HirofuchiLP18.html?view=bibtex} + }, } @inproceedings{DBLP:conf/noms/ZhangZLZWC22, @@ -535,6 +591,8 @@ timestamp = {Wed, 15 Jun 2022 16:45:18 +0200}, biburl = {https://dblp.org/rec/conf/noms/ZhangZLZWC22.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/noms/ZhangZLZWC22.html?view=bibtex}}, } @inproceedings{DBLP:conf/sc/TaheriBPRHDEWPM24, @@ -555,6 +613,9 @@ timestamp = {Thu, 07 May 2026 20:28:31 +0200}, biburl = {https://dblp.org/rec/conf/sc/TaheriBPRHDEWPM24.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/sc/TaheriBPRHDEWPM24.html?view=bibtex}. + }, } @inproceedings{DBLP:conf/sensys/LiW0Z0T23, @@ -574,6 +635,8 @@ timestamp = {Tue, 13 May 2025 13:47:03 +0200}, biburl = {https://dblp.org/rec/conf/sensys/LiW0Z0T23.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/sensys/LiW0Z0T23.html?view=bibtex}}, } @inproceedings{DBLP:conf/sensys/CaoW0022, @@ -593,6 +656,8 @@ timestamp = {Wed, 04 Dec 2024 09:43:28 +0100}, biburl = {https://dblp.org/rec/conf/sensys/CaoW0022.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/sensys/CaoW0022.html?view=bibtex}.}, } @inproceedings{DBLP:conf/sigcomm/HongWDSSHZY21, @@ -611,6 +676,9 @@ timestamp = {Sun, 19 Jan 2025 13:17:55 +0100}, biburl = {https://dblp.org/rec/conf/sigcomm/HongWDSSHZY21.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/sigcomm/HongWDSSHZY21.html?view=bibtex} + .}, } @inproceedings{DBLP:conf/sensys/WangZD0TCWZ20, @@ -629,6 +697,8 @@ timestamp = {Wed, 04 Dec 2024 09:45:46 +0100}, biburl = {https://dblp.org/rec/conf/sensys/WangZD0TCWZ20.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/conf/sensys/WangZD0TCWZ20.html?view=bibtex}}, } @@ -645,6 +715,8 @@ year = {2024}, publisher = {{The National Academies Press}}, address = {Washington, DC}, + note = {This citation has been created by me. See the ISBN for more + details about the publication.}, } @conference{DBLP:modsim24/presentation/Iosup2024, @@ -655,6 +727,8 @@ year = {2024}, publisher = {MODSIM World}, address = {Seattle, US}, + note = {This citation has been created by me. See the URL for more + details about the talk.}, } @@ -673,6 +747,9 @@ author = {Haitao Zhu and Botao Lin}, keywords = {Digital twin, Energy consumption management, Cooling system, Real-time interaction, Genetic algorithm}, + note = {This BibTeX citation comes from \url{ + https://www.sciencedirect.com/science/article/abs/pii/S0306261924012236 + }.}, } @image{DBLP:image/48Microprocessor/Rupp, @@ -685,6 +762,8 @@ url = {https://github.com/karlrupp/microprocessor-trend-data}, year = {2019}, publisher = {K. Rupp}, + note = {This citation has been created by me. See the URL for more + information of Karl Rupp's diagram.}, } @misc{Wikipedia:article/Systems_Thinking, @@ -889,6 +968,9 @@ timestamp = {Mon, 03 Jan 2022 22:04:29 +0100}, biburl = {https://dblp.org/rec/journals/tpds/BorghesiMMB22.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/tpds/BorghesiMMB22.html?view=bibtex + }.}, } @article{DBLP:journals/tc/DemirbagaWNMAGZ22, @@ -907,6 +989,9 @@ timestamp = {Fri, 30 Dec 2022 14:59:15 +0100}, biburl = {https://dblp.org/rec/journals/tc/DemirbagaWNMAGZ22.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/tc/DemirbagaWNMAGZ22.html?view=bibtex + }.}, } @inproceedings{DBLP:conf/ccgrid/ShenBI15, @@ -1024,4 +1109,28 @@ timestamp = {Thu, 04 Mar 2021 17:00:40 +0100}, biburl = {https://dblp.org/rec/journals/corr/abs-2103-02060.bib}, bibsource = {dblp computer science bibliography, https://dblp.org}, + note = {This BibTeX citation comes from \url{ + https://dblp.org/rec/journals/corr/abs-2103-02060.html?view=bibtex + }}, +} + +@article{ACM:article/Webster2002, + author = {Webster, Jane and Watson, Richard T.}, + title = {Analyzing the past to prepare for the future: writing a + literature review}, + year = {2002}, + issue_date = {June 2002}, + publisher = {Society for Information Management and The Management + Information Systems Research Center}, + address = {USA}, + volume = {26}, + number = {2}, + issn = {0276-7783}, + journal = {MIS Q.}, + month = jun, + pages = {xiii–xxiii}, + numpages = {11}, + note = {This BibTeX citation comes from \url{ + https://dl.acm.org/doi/10.5555/2017160.2017162}}, } + diff --git a/sources/thesis_structure.drawio b/sources/thesis_structure.drawio index eef2415..670dc70 100644 --- a/sources/thesis_structure.drawio +++ b/sources/thesis_structure.drawio @@ -1,11 +1,11 @@ <mxfile host="app.diagrams.net"> <diagram name="Page-1" id="8tJIHZG3YGX61DCj7_IM"> - <mxGraphModel dx="977" dy="669" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="850" pageHeight="1100" math="0" shadow="0"> + <mxGraphModel dx="928" dy="636" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="850" pageHeight="1100" math="0" shadow="0"> <root> <mxCell id="0" /> <mxCell id="1" parent="0" /> <mxCell id="MXKTANBymBVMColYor_E-4" parent="1" style="rounded=0;whiteSpace=wrap;html=1;fillColor=#f5f5f5;fontColor=#333333;strokeColor=#666666;" value="<div><b><br></b></div><div><b><br></b></div>" vertex="1"> - <mxGeometry height="110" width="420" x="170" y="400" as="geometry" /> + <mxGeometry height="110" width="542" x="110" y="400" as="geometry" /> </mxCell> <mxCell id="TxTclPCki953P5ZPPJ2z-25" edge="1" parent="1" source="TxTclPCki953P5ZPPJ2z-1" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;" target="TxTclPCki953P5ZPPJ2z-4"> <mxGeometry relative="1" as="geometry" /> @@ -66,17 +66,17 @@ <mxCell id="TxTclPCki953P5ZPPJ2z-29" edge="1" parent="1" source="TxTclPCki953P5ZPPJ2z-20" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0;entryY=0.5;entryDx=0;entryDy=0;" target="TxTclPCki953P5ZPPJ2z-21"> <mxGeometry relative="1" as="geometry" /> </mxCell> - <mxCell id="TxTclPCki953P5ZPPJ2z-20" parent="1" style="rounded=0;whiteSpace=wrap;html=1;fillColor=#FFFFCC;strokeColor=#000000;" value="Section 4.1<br><b><font style="font-size: 11px;">Data Flow</font></b>" vertex="1"> - <mxGeometry height="50" width="120" x="180" y="450" as="geometry" /> + <mxCell id="TxTclPCki953P5ZPPJ2z-20" parent="1" style="rounded=0;whiteSpace=wrap;html=1;fillColor=#FFFFCC;strokeColor=#000000;" value="Section 4.2<br><b><font style="font-size: 11px;">Data Flow</font></b>" vertex="1"> + <mxGeometry height="50" width="120" x="252.5" y="450" as="geometry" /> </mxCell> <mxCell id="TxTclPCki953P5ZPPJ2z-30" edge="1" parent="1" source="TxTclPCki953P5ZPPJ2z-21" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0;entryY=0.5;entryDx=0;entryDy=0;" target="TxTclPCki953P5ZPPJ2z-22"> <mxGeometry relative="1" as="geometry" /> </mxCell> - <mxCell id="TxTclPCki953P5ZPPJ2z-21" parent="1" style="rounded=0;whiteSpace=wrap;html=1;fillColor=#FFFFCC;strokeColor=#000000;" value="Section 4.2<br><b><font style="font-size: 11px;">Extensions to&nbsp;<br>OpenDC</font></b>" vertex="1"> - <mxGeometry height="50" width="120" x="315" y="450" as="geometry" /> + <mxCell id="TxTclPCki953P5ZPPJ2z-21" parent="1" style="rounded=0;whiteSpace=wrap;html=1;fillColor=#FFFFCC;strokeColor=#000000;" value="Section 4.3<br><b><font style="font-size: 11px;">Extensions to&nbsp;<br>OpenDC</font></b>" vertex="1"> + <mxGeometry height="50" width="120" x="387.5" y="450" as="geometry" /> </mxCell> - <mxCell id="TxTclPCki953P5ZPPJ2z-22" parent="1" style="rounded=0;whiteSpace=wrap;html=1;fillColor=#FFFFCC;strokeColor=#000000;" value="Section 4.3<br><b><font style="font-size: 11px;">Python<br>Modules</font></b>" vertex="1"> - <mxGeometry height="50" width="120" x="455" y="450" as="geometry" /> + <mxCell id="TxTclPCki953P5ZPPJ2z-22" parent="1" style="rounded=0;whiteSpace=wrap;html=1;fillColor=#FFFFCC;strokeColor=#000000;" value="Section 4.4<br><b><font style="font-size: 11px;">Python<br>Modules</font></b>" vertex="1"> + <mxGeometry height="50" width="120" x="524.5" y="450" as="geometry" /> </mxCell> <mxCell id="TxTclPCki953P5ZPPJ2z-24" parent="1" style="rounded=0;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#000000;" value="Chapter 6<br><b>Conclusion</b>" vertex="1"> <mxGeometry height="40" width="120" x="320" y="660" as="geometry" /> @@ -126,6 +126,12 @@ <mxCell id="MXKTANBymBVMColYor_E-14" parent="1" style="rounded=0;whiteSpace=wrap;html=1;fillColor=#f8cecc;strokeColor=#000000;" value="Section 5.4<br><span style="font-size: 11px;"><b>Experiment 3</b></span>" vertex="1"> <mxGeometry height="50" width="120" x="524.5" y="580" as="geometry" /> </mxCell> + <mxCell id="1ibH81aFUOVbOoGZI-IO-2" edge="1" parent="1" source="1ibH81aFUOVbOoGZI-IO-1" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0;entryY=0.5;entryDx=0;entryDy=0;" target="TxTclPCki953P5ZPPJ2z-20"> + <mxGeometry relative="1" as="geometry" /> + </mxCell> + <mxCell id="1ibH81aFUOVbOoGZI-IO-1" parent="1" style="rounded=0;whiteSpace=wrap;html=1;fillColor=#FFFFCC;strokeColor=#000000;" value="Section 4.1<br><b style=""><font style="font-size: 11px;">Implementation of <i style="">Sunfish</i></font></b>" vertex="1"> + <mxGeometry height="50" width="117.5" x="120" y="450" as="geometry" /> + </mxCell> </root> </mxGraphModel> </diagram> |
