You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While implementing the prototype, I tried to make strict separation between the model and the different algorithms (load approximation, cycle funder, ...). The idea was that the model should not contain any data that is computed by an algorithm.
However, this is not a 1st design choice. So currently, there is a mix between this design choice and the previous one (algorithms that modify the model directly). It is the case, for example, for the UncertainLoad approximator
Those modules should be refactor to reflect the last design (or reflect the one selected while addressing #3 )
The text was updated successfully, but these errors were encountered:
While implementing the prototype, I tried to make strict separation between the model and the different algorithms (load approximation, cycle funder, ...). The idea was that the model should not contain any data that is computed by an algorithm.
However, this is not a 1st design choice. So currently, there is a mix between this design choice and the previous one (algorithms that modify the model directly). It is the case, for example, for the UncertainLoad approximator
Those modules should be refactor to reflect the last design (or reflect the one selected while addressing #3 )
The text was updated successfully, but these errors were encountered: