Architectural redesign

[eduardstan]

We should change the architectural design of the entire framework.

Before we had 4 layers in mind, each one on top of the other representing a dependence (i.e., the next layer depends on the previous one):

• SoleData, for data manipulation and wrangling;
• SoleModels, for models, meta-models, etc;
• SolePostProcessing, for post-processing needs such as interpretability;
• SoleDeploy, to deploy models.

Now the entire architecture should be redesigned in the following repositories:

• SoleBase, which should include SoleData, SoleLogics (i.e., logics like HS and variants), and SoleModels;
• SoleModelling, for putting beautifully altogether to do modelling tasks;
• SolePostProcessing, as before;
• Sole, which encompasses all.

The dependence order should be maintained as before, that is, Sole depends on SolePostProcessing that depends on SoleModelling which depends on SoleBase.

Finally, at this point of our understanding of the problem on how to do things elegantly, other two repositories should be made:

• SoleVisualization, for beautiful visualizations of all kinds of things in the framework;
• SoleDeploy, to deploy models, as before.

Concluding, this issue represents a major change, and should probably represent the first release of the framework.

[eduardstan]

It should also be desirable to have a package called SoleUtils that, to some extent, contains heterogeneous utilities (i.e., applicable to many cases, not to specific ones, if possible). For example, it could contain the Loggers.