None of these modules are part of the main code-base, they are not used (nor useful) for any calculations or functionality, and are not directly user-facing either. All data is generated on pre-defined samples, so a user cannot really do anything useful with that data. Instead, they just provide example data which can be useful in a tutorial/example situation. Which is also how they are used at the moment (in a Jupyter notebook).
Given these functions are all a bit special, as described above, it would at least be helpful to visually separate them from the HOGBEN code itself, and thus put them in their own directory. This would make it more clear which modules are part of HOGBEN itself, and make the repository a bit more readable. I also have a feeling these could be generalised a bit in a refactor, but that could perhaps lead to more trouble than it's worth. At least in the immediate short term.
The following modules visualises and optimises predetermined samples, and save this in a results folder:
None of these modules are part of the main code-base, they are not used (nor useful) for any calculations or functionality, and are not directly user-facing either. All data is generated on pre-defined samples, so a user cannot really do anything useful with that data. Instead, they just provide example data which can be useful in a tutorial/example situation. Which is also how they are used at the moment (in a Jupyter notebook).
Given these functions are all a bit special, as described above, it would at least be helpful to visually separate them from the HOGBEN code itself, and thus put them in their own directory. This would make it more clear which modules are part of HOGBEN itself, and make the repository a bit more readable. I also have a feeling these could be generalised a bit in a refactor, but that could perhaps lead to more trouble than it's worth. At least in the immediate short term.