summaryrefslogtreecommitdiff
path: root/notes/24_06_2026.txt
diff options
context:
space:
mode:
Diffstat (limited to 'notes/24_06_2026.txt')
-rw-r--r--notes/24_06_2026.txt66
1 files changed, 66 insertions, 0 deletions
diff --git a/notes/24_06_2026.txt b/notes/24_06_2026.txt
new file mode 100644
index 0000000..8bede01
--- /dev/null
+++ b/notes/24_06_2026.txt
@@ -0,0 +1,66 @@
+==__==
+Typically atLarge is a bit more lenient when it comes to deadlines.
+You can submit your thesis until 15 of July by the faculty, but by atLarge you can submit it even later.
+Make sure you tell your supervisor when you plan to hand in your thesis.
+
+For the findings and the experiment section really try to follow the format that we have tried to teach you:
+1) Show what the main findings are
+2) Show the main setup
+3) Have multiple plots or tables to show your finding
+
+Recipe to explain experiments:
+How to evaluate something?
+Real world setting, simulation, mathematical analysis etc.
+Argue that --> "We do simulation based experiments".
+For experimental approach -- checklist:
+1) Workload --> I should explain what I run on my system and why that makes sense.
+You have a simulator run something, or you will inject failures, or you will expose the system to something.
+Is it realistic to expose the system to this workload?
+Does it make sense?
+
+2) Environment --> For a simulator: on what machine do you run the simulator, does it make sense to run this kind of experiment on the machine.
+
+3) (System-under-test) -> How did you configure OpenDC? What settings did you configured to run it? How did you configure redis?
+How did you configure the Kafka filters? Why does these settings make sense?
+
+4) Metrics --> why are you measuring these metrics? Why does this make sense?
+Why are the metrics representative.
+
+If the experiment setup is standard --> you can skip over it.
+You can say that you did a look through the literature about the kinds of use-cases your work can be beneficial for.
+One of the use-cases is an experiment that this related work, (DyTwin) did.
+Through my work I designed and Implemented this to be something that you can experiment with easily instead, not one-off.
+DyTwin was a one-off system. My system allows experimentation like this much more convenient, and NOT one-off.
+DyTwin was one-off system, now using our system can do this much more easily and not one-off.
+We IMPROVE on the work of DyTwin.
+
+We replicate their experiment, we get practically the same results, that validates THEIR work and YOUR OWN work.COMPARE on the same slide THEIR results, and OUR results.
+
+A lot of questions will be about the soundness of your approach.
+There will NOT be a lot of questions about the technical details.
+The more senior people in the room will ask more questions about the methodological approach.
+You DESIGN-ed a system: "what method did you follow for system design?"
+"Why did you choose that method? How did you follow it?"
+"How do you argue that you answers for research questions are good?"
+"Are your research questions good? Why are they good? Why do they align with the rest of the thesis?"
+"Argue why your research questions are challenging, why are they scientific?"
+
+Approach, research questions, methodology, the analysis of experiments.
+Frequent experiment analysis questions: "Why just the mean?" "Is there performance variability?" "Do you always get the same results?" "What can we learn if we look at the distribution?" "How many times did you repeat your experiments?" "What is the standard deviation?"
+
+SHOW IN YOUR ANSWERS YOU HAVE A JUSTIFICATION FOR THESE QUESTIONS.
+Explain that you have though about things.
+
+If you do not know the answer say: "Let me speculate..."
+Indicate honestly that you do not know, and then try to answer.
+
+As a presenter: be there just that day.
+Ask questions during other presentations.
+Support your team.
+Be there for the entire day or your slot perhaps.
+The rest of the day is appreciated, the entire slot is mandatory.
+Agree with the supervisor whether you passed or failed the presentation.
+It never happened that we let someone present and THEN fail.
+Usually they tell them that they have to do on more or two more things.
+Once you have some answer to your research questions, it is heavily unlikely you will fail.
+