@@ -98,7 +98,7 @@ In the end, we found that the following complications were to blame: <br>
<br>
All the above mentioned points had to be determined and improved in the course of development. This very often set us back in the overall process. <br>
<br>
Unfortunately, there were also problems with the attached files in the [github](https://github.com/debjitpaul/Multi-Hop-Knowledge-Paths-Human-Needs). For example, we kept getting a namespace error "'Namespace' object has no attribute 'txtfile'" for weeks which prevented us from executing the coude, and we could never get rid of it completely. In the Zoom meetings with @debjitpaul we addressed this problem until it turned out that there was a typo in his original file which was responsible for the error. Instead of calling a "txtfile" it should have been "inputfile". We are aware that these are minor issues. However, this accumulation of problems led to significant time losses in our project and we had to put in more time in the last weeks than we had planned for.
Unfortunately, there were also problems with the attached files in the [github](https://github.com/debjitpaul/Multi-Hop-Knowledge-Paths-Human-Needs). For example, we kept getting a namespace error "'Namespace' object has no attribute 'txtfile'" for weeks which prevented us from executing the code, and we could never get rid of it completely. In the Zoom meetings with @debjitpaul we addressed this problem until it turned out that there was a typo in his original file which was responsible for the error. Instead of calling a "txtfile" it should have been "inputfile". We are aware that these are minor issues. However, this accumulation of problems led to significant time losses in our project and we had to put in more time in the last weeks than we had planned for.
<br>
<br>
Due to a lack of capacity on our own computers, we turned to our institute's technology group for cluster access. They got back to us and granted us access. After everything went well here at first, we again reached a point where we lacked the necessary rights to further execute our project while also encountering a number or errors. Unfortunately, despite contacting them several times, we finally did not hear back from the technology group. Because of this, we had to work on our own computers again and start from where we left off. Despite the fact that we divided it among ourselves, the program needed an average of about one hour per sentence to construct a subgraph, while especially long sentences with big context lists took up to 3 hours. Having 400 essays to work through, it took us quite a long time.
