Some small comments regarding Code Structure and Code Formatting

[AKuederle]

Overall the code quality looks great, but here are a couple of smaller things that could be improved:

• [x] Use of Path instead of strings for file/folder paths -> This will solve a bunch of issues caused by the differences between operating systems. For example it would make .replace('\\', '/') obsolote in the example
• [ ] At the moment the files are huge. It might help overall readibility to split the large files into logical chunks
• [x] "random" and repeated comments (For example at the beginning of the individual file)
• [x] Inconsistent and unusuale formatting choices (in particular the space before the opening bracket of a function) can be confusing. I would highly recommend to stick to official code guidelines and enforce them by using ruff or black

[Aminsinichi]

Thank you @AKuederle for these suggestions. I have a few questions to make sure I grasp this correctly:

• [x] For the Path suggestion, do you mean doing this?

In the beginning, define the path like this:

from pathlib import Path 

pp = "P25"
path = Path("COPY-YOUR-ADDRESS-HERE")
conditions = ['sitting', 'arithmetic', 'recovery']
devices = ["kyto", "empatica", "vu"]
criterion = "vu"

Then, I also need modify the functions slightly to incorporate this. For instance, in the individual.import_data() function, instead of path_vu = path + pp + '_' + "vu" + '.txt', I modify it to path_vu = path / f"{pp}_vu.txt".

Is this what you are suggesting to be done?

• [ ] Could you also elaborate on what you mean by huge files, and how I can turn them into smaller logical chunks?
• [X] I improved the readability of the code using ruff and black in VS code, in accordance with PEP8. Related commits: commit1, and commit2.

[AKuederle]

Regarding the path thing:

I would usggest to use Path internally everywhere and all functions that can take a file-path or directory as input, to support both str and Path. So when the user passes as str you convert it to path. This makes sure that you don't have to deal with OS differences internally and you allow the user to also benefit from using Path (but they don't have to)

[AKuederle]

Regarding huge files: While this is a matter of preference, most people structure their functions in multiple smaller files based on categories (e.g. plotting, utils, io, loading, stats, ...). And then depending on the project, the relevant methods are reexported in user facing files to separate the internal structure from the import structures for users. For example see scikit-learn: https://github.com/scikit-learn/scikit-learn/tree/main/sklearn/cluster

Here the implementaiton is split in smaller files to easier find things, but then user facing functions are re-imported in the top-level init to provide more convenient import syntax

[Aminsinichi]

• [x] Thank you! path has been replaced everywhere, internally in each function, with Path; related commit.