Update snapshot

README.md

 # The code accompaning `Application of pre-trained transformers to estimate the difficulty of closed questions using question and choice text`
 
 
-This contains the code used to produce the results in the paper.
+This contains the code used to produce the results in the thesis..
 It contains a number of subdirectories that are somewhat separate and somewhat interdependent.
 
 Most of the subdirectories have their own `README.md`.
 
-One thing that almost all directories have in common is their general Python toolchain.
+One thing that almost all directories have in common is their general [Python toolchain](#common-python-toolchain).
 
 ## Common Python toolchain
 
@@ -51,9 +51,9 @@ Path:       /usr
 Executable: /usr/bin/python3.11
 ```
 
-For example, with my Visual Studio code (vscode) that has the Python extension installed, "all I have to do" to get completions, documentation on mouse hover, and other niceties for my dependencies (numpy, tensorflow, etc) is to open the project in a vscode instance, then click on the number in the lower right corner of the editor (after "Python"), then click `+ enter interpreter path`, and then copy and paste the (first) `Executable` path from `poetry env info` into there (so `/home/<user>/.cache/pypoetry/virtualenvs/qde-model-code-9-Jx55oZ-py3.11/bin/python`).
+For example, with my Visual Studio code (vscode) that has the Python extension installed, "all I have to do" to get completions, documentation on mouse hover, and other niceties for my dependencies (numpy, tensorflow, etc) is to open the project in a vscode instance, then click on the number in the lower right corner of the editor (after "Python"), then click `+ enter interpreter path`, and then copy and paste the (first) `Executable` path from `poetry env info` into there (so in this case `/home/<user>/.cache/pypoetry/virtualenvs/qde-model-code-9-Jx55oZ-py3.11/bin/python`).
 
-These instructions are all untested and do not include pictures, so good luck to those trying to do expecially the last part here without some prior knowledge, but frankly I think I've already done a lot more here than other people would.
+These instructions are all untested and do not include pictures, so good luck. Sadly I had to limit the resources to spend on this documentation in favour of the main work.
 
 Don't be intimidated by all the big words being thrown around here.
 You don't need to understand most of them at first, and eventually you'll develop an understanding for them.

generate_repos_snapshot.sh

@@ -19,14 +19,18 @@ fi
 
 cd ../..
 
-# my filesystem is btrfs. Its a copy on write filesystem. 
+# my filesystem is btrfs. Its a copy on write (COW) filesystem. 
 # Because of that it copies the 50GB of enem raw data just like that, glorious thing.
-cp -r common_py data_explore enem_aggregate moodle_extract qde_model_code raw_data README.md LICENSE meta/monorepo
+# If your filesystem doesnt use COW (NTFS, fat - both windows - and ext4 - more usual Linux FS - do not, I dunno about apple) 
+# then this may be slow, and you may want to look for an alternative.
+cp -r common_py data_explore enem_aggregate moodle_extract qde_model_code raw_data meta/monorepo
 
 cd meta/monorepo || exit
 
+# "remove" the individual repositories, otherwise git wants to make them submodules.
 rm -rf ./**/.git
 
+# old code that recreated the repository each time
 # git init --initial-branch=main
 
 git add .