fix: tidied up the directory

3 files changed, 0 insertions, 50 deletions

diff --git a/notes/.~lock.VU_BSc_Defense_Slides_Mateusz_Kwiatkowski-20260610-annot-jd.pdf# b/notes/.~lock.VU_BSc_Defense_Slides_Mateusz_Kwiatkowski-20260610-annot-jd.pdf#
deleted file mode 100644
index 29ea072..0000000
--- a/notes/.~lock.VU_BSc_Defense_Slides_Mateusz_Kwiatkowski-20260610-annot-jd.pdf#
+++ /dev/null
@@ -1 +0,0 @@
-,matt,frame,11.06.2026 07:28,/home/matt/.local/share/onlyoffice;
\ No newline at end of file
diff --git a/notes/VU_BSc_Defense_Slides_Mateusz_Kwiatkowski-20260610-annot-jd.pdf b/notes/VU_BSc_Defense_Slides_Mateusz_Kwiatkowski-20260610-annot-jd.pdf
deleted file mode 100644
index 4e51e3d..0000000
--- a/notes/VU_BSc_Defense_Slides_Mateusz_Kwiatkowski-20260610-annot-jd.pdf
+++ /dev/null
diff --git a/notes/meeting3.txt b/notes/meeting3.txt
deleted file mode 100644
index f058da1..0000000
--- a/notes/meeting3.txt
+++ /dev/null
@@ -1,49 +0,0 @@
-Jesse -- Latex slides are OK!
-1 slides is 1 to 2 minutes - 5 to 10 slides can work.
-Slide 4: mention the contributions; In the thesis we answer these RQs, for time limitation, we only focus on RQs 1 and 2. For RQ we do a design and then you can ask me about this after the presentation.
-You can skip explaining a RQ.
-Skip material instead of cramming material.
-As you know and as you've seen in the previous presentations today.
-
-**Mention societal impact at least verbally. In slide 2.**
-Avoid audience members thinking ``he forgot that''.
-If you are skipping something -- at least mention that you are skipping it.
-Or that there is an extra slide explaining this.
-
-Before slide 4, the audience must know what predictive analytics is and why is it important to have.
-In the `Problem Statement` slide, say `What is predictive analytics`, `Why is it crucial`.
-Key for you to explain `What is predictive analytics?`
-
-Digital Twins -- a lot of elements are shifting about, there are a lot of ways to model these things, and there seems to not be a fully functioning digital twin out there.
-There does not exist a system that contains the entire feedback loop.
-1) Digital Twins are NOT DONE -- they are actively being developed.
-2) Part of being developed is they lack crucial features, e.g., predictive analytics
-3) Predictive analytics is this and that...
-4) This is important because ...
-
-You may have to remove the table.
-
-Slide 2 -- the idea of complex / extremely complex is too bad.
-The idea might be a bit too high -- throw in some numbers, the scale of modern datacenters.
-Put in some number of different number CPU's, or focus on the number of PETAFLOPS (compute steps per second).
-
-Change the narrative from Moore's law to something else.
-Focus more on the fact that the infrastructure is incredibly large.
-DO NOT SHOW THE DENNARD's scaling graph.
-
-``A single CPU is very complex. (Show ARM Architecture of APPLE MAC) Look, in that something there is this bigger thing, and there is this and there is this bigger thing, and how are we going to simulate this big datacenter, that has so many __layers of complexity__``. A single ARM Architecture Image -- ``This is a complex object''. 
-In datacenters, there are hundreds of thousands of them.
-How do we manage this?''
-
-Connect motivation to problem statement via societal context.
-``We cannot let these systems go down, we CANNOT Experience failures, we cannot experience performance related issues`'' and that bridges to the need of digital twins to be better able to detect and solve issues in this critical infrastructure.
-And that also bridges nicely to predictive analytics.
-``What if we can solve problems before they actually occur?``
-
-You have to be able to explain something well on a graph with dc <-> dt.
-Give a strong motivation for predictive analytics.
-Give a strong motivation for failures, or that Digital Twins are just IoT sensors without Digital Twinning.
-
-Slide 4 add animations to show the research questions.
-``Take home message'' instead of Discussion.
-Add animations -- to the system model for things appearing.