Design - Improve MAPIE and mlFlow interaction #454
Labels
Enhancement
Type: enhancement (new feature or request)
MAPIE v1
Indicate that the issue will be resolved with the release of MAPIE v1
Other
If no other grey tag is relevant or if issue from the MAPIE team
Source: contributors
Proposed by contributors.
Hi! This is a bit of a general question / suggestion. I have trouble working with MAPIE and mlflow for experiment / model tracking. That is a bit of a pity, because it limits the usability of an otherwise nice library.
Is your feature request related to a problem? Please describe.
The
model.predict()
output ofTuple[Array, Tuple[Array, Array]]
is not super self-explanatory and a bit cumbersome when it comes to further downstream processing, especially withmlflow
experiment tracking / deployment.Suggestion / possible solution (but very open for discussion)
A relatively straight-forwad solution would be to have the model output as
Dict({"mean": Array, "lower": Array, "upper": Array})
. That way it is clear what is what and this is ought to be accepted by the mlflowinfer_signature()
. (I've monkey patched my estimator to check this). To avoid breaking changes, one could add anoutput_format
parameter in the estimator class.Did somebody find other ways to work well with MAPIE and mlflow apart from monkey patching? Appreciate any input :)
Cheers, Simon
The text was updated successfully, but these errors were encountered: