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
We would like to integrate xplainable into the MLflow workflow. This involves the following workflows:
If the model is an xplainable model, the model is logged to MLflow and Xplainable Cloud (with the same experiment_id)
If the model is NOT an xplainable model, a surrogate model is created and logged to MLflow and Xplainable Cloud
Key considerations
This should be as uninvasive as possible. We don't want people to have to change their workflow drastically, rather just import xplainable and automate the explainer creation and logging.
Flexibility in approach
Please run with your own creative freedom here. We would love to discuss different approaches, as long as the disruption to user workflow is minimal.
Vision 1
This idea involves implementing a manual logging step. Behind the scenes it will train an xplainable surrogate model and log to both MLflow and Xplainable Cloud.
importxplainableasxpimportmlflow# <- Build any model herewithmlflow.start_run():
signature=infer_signature(X_train, model.predict(X_train))
# <- other logging heremlflow.log_model(
model=model,
signature=signature,
input_example=X_train,
registered_model_name="model-with-xplainable"
)
# This should log to mlflow and to xplainable cloud (if an api key is active)xp.mlflow.log_explanation(model.predict, X)
Vision 2
This is similar to vision 1, but without the need to manually log explainers. It's not clear how this would be achieved, but it is an idea worth fleshing out.
importxplainableasxpimportmlflow# <- Build any model herexp.mlflow.auto_logging=Truewithmlflow.start_run():
signature=infer_signature(X_train, model.predict(X_train))
# <- other logging heremlflow.log_model(
model=model,
signature=signature,
input_example=X_train,
registered_model_name="model-with-xplainable"
) # < -- This should auto-log to mlflow and to xplainable cloud (if an api key is active)
The text was updated successfully, but these errors were encountered:
lashdk
added a commit
to lashdk/xplainable-mlflow-integration
that referenced
this issue
Jan 1, 2024
Dependency
#83
What we want to achieve
We would like to integrate xplainable into the MLflow workflow. This involves the following workflows:
Key considerations
This should be as uninvasive as possible. We don't want people to have to change their workflow drastically, rather just import xplainable and automate the explainer creation and logging.
Flexibility in approach
Please run with your own creative freedom here. We would love to discuss different approaches, as long as the disruption to user workflow is minimal.
Vision 1
This idea involves implementing a manual logging step. Behind the scenes it will train an xplainable surrogate model and log to both MLflow and Xplainable Cloud.
Vision 2
This is similar to vision 1, but without the need to manually log explainers. It's not clear how this would be achieved, but it is an idea worth fleshing out.
The text was updated successfully, but these errors were encountered: