<commit_before>=========================================================
Things to note if you intend to work with this code base:
=========================================================

 - None of the classes belonging to ReqTracker itself are threadsafe, even
   though some code in the current application accesses them concurrently.

 - The gui code has a very non-trivial control flow, that also currently leads
   to all gui elements being initialized twice
   (see https://github.com/uv48uson/amos-ss15-proj3/issues/121).

 - While some parts of the application were redesigned to use paths in the
   current HEAD commit, some others use (by now deprecated) logic that
   aggregates over the set of all diffs that were ever commited, most notably
   the tracibility matrix functionality is still using the old CommitFile class.

 - The current code contains no possibility of generating database tables and
   the content of the requirements table (which is needed for requirement titles
   and descriptions).

 - The current logic for querying sources of linkage is both quite slow and
   complex, refactoring that part of the code base will require a large effort
   (essentially a rewrite) but is needed for extensibility.

======================
Important open issues:
======================

 - If large amounts of data were stored in the database, performance would
   suffer, because currently the code uses one Hibernate session per query<commit_msg>Correct grammar in NOTES.txt<commit_after>=========================================================
Things to note if you intend to work with this code base:
=========================================================

 - None of the classes belonging to ReqTracker itself are threadsafe, even
   though some code in the current application accesses them concurrently.

 - The gui code has a very non-trivial control flow, that also currently leads
   to all gui elements being initialized twice
   (see https://github.com/uv48uson/amos-ss15-proj3/issues/121).

 - While some parts of the application were redesigned to use paths in the
   current HEAD commit, some others use (by now deprecated) logic that
   aggregates over the set of all diffs that were ever commited, most notably
   the tracibility matrix functionality is still using the old CommitFile class.

 - The current code contains no possibility of generating database tables and
   the content of the requirements table (which is needed for requirement titles
   and descriptions).

 - The current logic for querying sources of linkage is both quite slow and
   complex, refactoring that part of the code base will require a large effort
   (essentially a rewrite) but is needed for extensibility.

======================
Important open issues:
======================

 - If large amounts of data were to be stored in the database, performance would
   suffer, because currently the code uses one Hibernate session per query
{'fraction_non_alphanumeric': 0.13561041596212378, 'fraction_numerical': 0.005410889414947582, 'mean_word_length': 4.528971962616822, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '993790', 'n_tokens_mistral': 683, 'n_tokens_neox': 620, 'n_words': 382}