As already mentioned in project_proposal, our goal of the project was to enable a meaningful mapping of human needs on argumentative data using the concept net graphs. In this report we will present the results of our project and describe problems encountered and findings made.
@@ -36,11 +35,11 @@ In the end, we found that the following complications were to blame: <br>
- the requirement of kerases was not mentioned anywhere, but is a necessity for the execution of the code
- keras version has to be 2.2.4 because everything higher upgrades tensoflow automatically to tenserflow 2.0
- and tensorflow 2.0 has so many technical changes, that it is not compatible with our models
<br>
<br><br>
All the above points we had to determine and improve in the course of development. This very often set us back in the overall process. <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 and could never get rid of it completely. In the Zoom meetings with @debjitpaul we kept addressing this problem until it turned out that there was a typo in his file. Instead of "txtfile" it should be "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 it.
<br>
<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. 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. Despite the fact that we divided it among ourselves, we needed on average about one hour per sentence. Having 400 essays to work through, it took us quite a long time.
<br>
<br><br>
As already mentioned briefly in our project_proposal we wanted to do a textual analysis with the OpenFraming tool. Again, we had already prepared our data to match the model and were ready to work with the tool. Unfortunately, we received an error message right at the first step. After contacting the OpenFraming team, they initially suspected that the error must lie with us. Therefore, they gave us instructions on what the files should look like (csv file, comma separated). But despite several attempts to change the files, the error could not be solved. After weeks, the OpenFraming team determined that it was an internal error that only they could fix. However, they soon realized that it was a slightly bigger problem and offered us the alternative of working with docker files. But even here there were several errors on their part, which is why we no longer got to work with their tool. Although several members of the OpenFraming team contacted us by mail afterwards and let us know that they were working on it, they broke off contact at some point. Unfortunately, the tool is still not working till date (25th march 2021). Of course we don't blame anyone for this. We are well aware that everyone has their own work to do. We only regret that we had invested so much time and effort into the tool and in the end we could not work with it. The textual analysis complementary to our obtained results would have been certainly very interesting.
