summaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
authormjkwiatkowski <mati.rewa@gmail.com>2026-06-27 17:18:48 +0200
committermjkwiatkowski <mati.rewa@gmail.com>2026-06-27 17:18:48 +0200
commitcaf75aad39580fd3c8536fb0d21ea94368c6c130 (patch)
tree3c68fab0f00b670c94e20e1275b91a239339a32b /content
parent577d8de6f8847ac562aa3c02c52c54f1956a756c (diff)
feat: removed the PhD template class in favour of a much simpler setup
Diffstat (limited to 'content')
-rw-r--r--content/conclusion.tex4
-rw-r--r--content/design.tex4
-rw-r--r--content/discussion.tex4
-rw-r--r--content/evaluation.tex8
-rw-r--r--content/intro.tex5
-rw-r--r--content/overview.tex8
-rw-r--r--content/preamble/glossary.tex21
-rw-r--r--content/related.tex2
8 files changed, 16 insertions, 40 deletions
diff --git a/content/conclusion.tex b/content/conclusion.tex
index 9ca221f..dcfd203 100644
--- a/content/conclusion.tex
+++ b/content/conclusion.tex
@@ -2,8 +2,8 @@
\todo{
-Briefly summarize your contributions, and share a glimpse of the implications of
-this work for future research.
+ Briefly summarize your contributions, and share a glimpse of the implications of
+ this work for future research.
}
diff --git a/content/design.tex b/content/design.tex
index 175ec1b..693f3d9 100644
--- a/content/design.tex
+++ b/content/design.tex
@@ -2,8 +2,8 @@
\todo{
-In this section, you would provide a high-level description of the system or
-solution and explain your design choices.
+ In this section, you would provide a high-level description of the system or
+ solution and explain your design choices.
}
diff --git a/content/discussion.tex b/content/discussion.tex
index 62129fc..2d792de 100644
--- a/content/discussion.tex
+++ b/content/discussion.tex
@@ -2,8 +2,8 @@
\todo{
-Here you put your results in context (possibly grouped by research question). Usually, this section focuses on analyzing the
-implications of the proposed work for current and future research and for practitioners.
+ Here you put your results in context (possibly grouped by research question). Usually, this section focuses on analyzing the
+ implications of the proposed work for current and future research and for practitioners.
}
diff --git a/content/evaluation.tex b/content/evaluation.tex
index 3b65dff..3329bba 100644
--- a/content/evaluation.tex
+++ b/content/evaluation.tex
@@ -2,10 +2,10 @@
\todo{
-Discuss the design of your experiments, the results you obtained, and how they
-help in evaluating the claims you made in the introduction. You may also use the
-evaluation results in this section to justify your design choices or assess the
-contributions of different aspects of your design towards the overall goals.
+ Discuss the design of your experiments, the results you obtained, and how they
+ help in evaluating the claims you made in the introduction. You may also use the
+ evaluation results in this section to justify your design choices or assess the
+ contributions of different aspects of your design towards the overall goals.
}
diff --git a/content/intro.tex b/content/intro.tex
index 093a863..c0fd08c 100644
--- a/content/intro.tex
+++ b/content/intro.tex
@@ -72,11 +72,8 @@ Downtime, which is the result of failures, disturbs the users and produces unful
% DT's merge both simulation and telemetry to develop a holistic virtual representation of the system, bridging both the physical and virtual worlds.
However, predicting datacenter behaviour quickly and reliably is a non-trivial problem that remains insufficiently unaddressed in the existing \gls{dcdt} architectures ~\cite{DBLP:conf/wosp/SumanCNTMI24, DBLP:journals/computer/AthavaleBBMMPS24} and deployments~\cite{DBLP:conf/sc/BrewerMKWBHSGGW24}.
-
\section{Problem statement}\label{s:problem-statement}
-
-
We envision \gls{dcdt}'s as systems indispensable in future datacenters, actively interacting with the real-world facility, lowering operational costs and predicting hardware failure and software faults.
In this work, we address the lack of a unified \gls{dcdt} system model and the absence of predictive capabilities in existing \gls{dcdt} system designs.
We argue that the current state-of-the-art \gls{dcdt}'s lack sufficient predictive capabilities that are essential to real-time facility management of a modern datacenter.
@@ -142,7 +139,7 @@ We define the correct experiment setup(s) and perform the experiments on a speci
\item \textbf{Conceptual}:
\begin{enumerate}[label=\emph{C\textsubscript{\arabic*}}, align=left, labelsep=0pt]
- \item We conduct a systematic literature review and detailed analysis of existing works on digital twinning in the scientific research community.
+ \item We conduct a comprehensive literature review and detailed analysis of existing works on digital twinning in the scientific research community.
We collect and organize the \gls{dcdt}'s characteristics and based on our findings we propose a unified system model of the design space.
\item We propose the design of \gls{my_system}, a discrete-event \gls{dcdt} for reliable and timely failure prediction in datacenters.
\gls{my_system} includes a set of novel system components which leverage \gls{oda} and discrete-event simulation.
diff --git a/content/overview.tex b/content/overview.tex
index 869cea5..d50154d 100644
--- a/content/overview.tex
+++ b/content/overview.tex
@@ -2,10 +2,10 @@
\todo{
-This section provides a high-level outline of the proposed system or solution.
-It typically illustrates the system architecture or the interactions between the
-different solution components (via a “boxes-and-arrows” diagram) from a user’s
-perspective.
+ This section provides a high-level outline of the proposed system or solution.
+ It typically illustrates the system architecture or the interactions between the
+ different solution components (via a “boxes-and-arrows” diagram) from a user’s
+ perspective.
}
diff --git a/content/preamble/glossary.tex b/content/preamble/glossary.tex
deleted file mode 100644
index 91df2b6..0000000
--- a/content/preamble/glossary.tex
+++ /dev/null
@@ -1,21 +0,0 @@
-% this file is called up by thesis.tex
-% content in this file will be fed into the main document
-
-% Glossary entries are defined with the command \nomenclature{1}{2}
-% 1 = Entry name, e.g. abbreviation; 2 = Explanation
-% You can place all explanations in this separate file or declare them in the middle of the text. Either way they will be collected in the glossary.
-
-% required to print nomenclature name to page header
-%\markboth{\MakeUppercase{\nomname}}{\MakeUppercase{\nomname}}
-
-
-% ----------------------- contents from here ------------------------
-
-
-%\nomenclature{LSY}{ehbfuefebbfbjkjkebfjbfbfw}
-%\nomenclature{DEPC}{diethyl-pyro-carbonate; used to remove RNA-degrading enzymes (RNAases) from water and laboratory utensils}
-%\nomenclature{DMSO}{dimethyl sulfoxide; organic solvent, readily passes through skin, cryoprotectant in cell culture}
-%\nomenclature{EDTA}{Ethylene-diamine-tetraacetic acid; a chelating (two-pronged) molecule used to sequester most divalent (or trivalent) metal ions, such as calcium (Ca$^{2+}$) and magnesium (Mg$^{2+}$), copper (Cu$^{2+}$), or iron (Fe$^{2+}$ / Fe$^{3+}$)}
-
-
-
diff --git a/content/related.tex b/content/related.tex
index 7a8f517..545b6bc 100644
--- a/content/related.tex
+++ b/content/related.tex
@@ -2,7 +2,7 @@
\todo{
-Describe here scientific papers similar to your experiment, both in terms of goal and methodology. One paragraph for each paper (we expect about 5-8 papers to be discussed). Each paragraph contains: (i) a brief description of the related paper and (ii) a black-on-white description about how your work differs from the related paper. You may place this section immediately after the Background section, if necessary.
+ Describe here scientific papers similar to your experiment, both in terms of goal and methodology. One paragraph for each paper (we expect about 5-8 papers to be discussed). Each paragraph contains: (i) a brief description of the related paper and (ii) a black-on-white description about how your work differs from the related paper. You may place this section immediately after the Background section, if necessary.
}