diff options
| author | mjkwiatkowski <mati.rewa@gmail.com> | 2026-07-04 16:06:11 +0200 |
|---|---|---|
| committer | mjkwiatkowski <mati.rewa@gmail.com> | 2026-07-04 16:06:11 +0200 |
| commit | 2c3024b4d22af5aa7df3da27a949d1d9f6f2fd89 (patch) | |
| tree | 0d7d88e0068237b69b99c4fd6a49b0535f4011a5 | |
| parent | 65775b9fe9fe44049a0f1da2b6b9ffbdb9881d1f (diff) | |
fix: fixed the layout to adhere to the AtLarge style
| -rw-r--r-- | content/discussion.tex | 10 | ||||
| -rw-r--r-- | content/implementation.tex | 1 | ||||
| -rw-r--r-- | content/overview.tex | 13 | ||||
| -rw-r--r-- | content/related.tex | 10 | ||||
| -rw-r--r-- | content/threats.tex | 6 | ||||
| -rw-r--r-- | main.tex | 4 |
6 files changed, 0 insertions, 44 deletions
diff --git a/content/discussion.tex b/content/discussion.tex deleted file mode 100644 index 2d792de..0000000 --- a/content/discussion.tex +++ /dev/null @@ -1,10 +0,0 @@ -\chapter{Discussion}\label{s:discussion} - - -\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. -} - - -\lipsum[1-8] diff --git a/content/implementation.tex b/content/implementation.tex index 0decbc3..5d243f6 100644 --- a/content/implementation.tex +++ b/content/implementation.tex @@ -152,4 +152,3 @@ For future work, we envision a system that implements the reference architecture It contains a \code{while True} Python loop which contains the function call to fetch the latest changes to the \code{Redis} stream. Upon update, the \code{MonitoringService} informs the \code{AnalyticsEngine} that new data is awaiting \code{AnalyticsEngine} (\grayCircled{6}). \end{enumerate} - diff --git a/content/overview.tex b/content/overview.tex deleted file mode 100644 index d50154d..0000000 --- a/content/overview.tex +++ /dev/null @@ -1,13 +0,0 @@ -\chapter{Overview}\label{s:overview} - - -\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. -} - - -\lipsum[1-6] - diff --git a/content/related.tex b/content/related.tex deleted file mode 100644 index 545b6bc..0000000 --- a/content/related.tex +++ /dev/null @@ -1,10 +0,0 @@ -\chapter{Related Work}\label{s:related} - - -\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. -} - - -\lipsum[14-17][4-8] - diff --git a/content/threats.tex b/content/threats.tex deleted file mode 100644 index f01c3fb..0000000 --- a/content/threats.tex +++ /dev/null @@ -1,6 +0,0 @@ -\chapter{Threats To Validity}\label{sec:threats} - -\section{Internal Validity} -\section{External Validity} -\section{Construct Validity} -\section{Conclusion Validity} @@ -16,13 +16,9 @@ \input{content/intro} \input{content/background} -%\input{content/overview} \input{content/design} \input{content/implementation} \input{content/evaluation} -\input{content/discussion} -\input{content/threats} -\input{content/related} \input{content/conclusion} \printglossary[type=\acronymtype] |
