masters-thesis

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README

commit 5d03615d035b5d7fede69ab34a69e11e44dc66ed
parent 71f6e6bd4dc58e16362447b8db0ca263999fe9f4
Author: Silas Brack <s174433@student.dtu.dk>
Date:   Sun, 12 Feb 2023 17:43:02 +0100

Ups.

Diffstat:
Mchapters/preface.tex | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/chapters/preface.tex b/chapters/preface.tex @@ -10,7 +10,7 @@ I definitely had a slow start to the thesis (most people do), since for the firs Looking back, this was a really good idea, since understanding the software ended up being key to solving the problems in this thesis. When I tried to generate some preliminary results, I quickly encountered some roadblocks. As it turned out, though, these issues were quite fundamental to the problem---but my supervisor, S{\o}ren, had found a paper which addressed some of them. -He then invited me to a hackathon with his research group, where they were planning to sit together and try to implenent the methods from the paper. +He then invited me to a hackathon with his research group, where they were planning to sit together and try to implement the methods from the paper. Initially, I was a bit hesitant about going, since I had never been to a research-related hackathon, and I was a bit worried that I would be out of my depth and that I wouldn't be able to contribute. However, after Lorenza helped me get over my fears, I decided to go, and I'm glad I did.