Raise some custom leaspy exceptions so to better handle them downstream
Type: Feature-request / code best practices
Requested by Severine (PredictMA project)
Tasks:
1/ define a few dedicated Leaspy exceptions (should be nested):
Proposal:
-
LeaspyError
(base Leaspy exception)-
LeaspyInputError
-
LeaspyInputModelError
(bad model parameters) -
LeaspyInputAlgoError
(bad algo params) - ...
-
-
LeaspyProcessingError
? -
LeaspyOutputError
?
-
2/ Replace raised exceptions in Leaspy by the newly defined ones
& reference the possibly raised exceptions within the Raises
category of concerned docstrings