All the hardcoded paths can be moved to an .env file and can be loaded using load_dotenv() method of the python-dotenv library. Since other users may not have the same paths.
Thanks Sunayana,
I will look into both suggestions:
you are right; having an .env file might be useful because everyone has a different logic to store the input data.
creating a docstring is on my to-do list, I just have to figure out how to set it up (I know it's not complicated), but that's the reason for the text blocks in the function section of the notebook; I was thinking about converting them to docstrings after editing the code.
Data Setup
.env
file and can be loaded usingload_dotenv()
method of the python-dotenv library. Since other users may not have the same paths.Misc
@GvdDool In general the code was understandable. I did not have more time to dig further.