Website โข Docs โข Community Slack
NannyML is an open-source python library that allows you to estimate post-deployment model performance (without access to targets), detect data drift, and intelligently link data drift alerts back to changes in model performance. Built for data scientists, NannyML has an easy-to-use interface, interactive visualizations, is completely model-agnostic and currently supports all tabular use cases, classification and regression.
The core contributors of NannyML have researched and developed multiple novel algorithms for estimating model performance: confidence-based performance estimation (CBPE) and direct loss estimation (DLE). The nansters also invented a new approach to detect multivariate data drift using PCA-based data reconstruction.
If you like what we are working on, be sure to become a Nanster yourself, join our community slack and support us with a GitHub star โญ.
NannyML closes the loop with performance monitoring and post deployment data science, empowering data scientist to quickly understand and automatically detect silent model failure. By using NannyML, data scientists can finally maintain complete visibility and trust in their deployed machine learning models. Allowing you to have the following benefits:
- End sleepless nights caused by not knowing your model performance ๐ด
- Analyse data drift and model performance over time
- Discover the root cause to why your models are not performing as expected
- No alert fatigue! React only when necessary if model performance is impacted
- Painless setup in any environment
NannyML Resources | Description |
---|---|
โ๏ธ NannyML 101 | New to NannyML? Start here! |
๐ฎ Performance estimation | How the magic works. |
๐ Real world example | Take a look at a real-world example of NannyML. |
๐ Key concepts | Glossary of key concepts we use. |
๐ฌ Technical reference | Monitor the performance of your ML models. |
๐ Blog | Thoughts on post-deployment data science from the NannyML team. |
๐ฌ Newsletter | All things post-deployment data science. Subscribe to see the latest papers and blogs. |
๐ New in v0.8.1 | New features, bug fixes. |
๐งโ๐ป Contribute | How to contribute to the NannyML project and codebase. |
Join slack | Need help with your specific use case? Say hi on slack! |
When the actual outcome of your deployed prediction models is delayed, or even when post-deployment target labels are completely absent, you can use NannyML's CBPE-algorithm to estimate model performance for classification or NannyML's DLE-algorithm for regression. These algorithms provide you with any estimated metric you would like, i.e. ROC AUC or RSME. Rather than estimating the performance of future model predictions, CBPE and DLE estimate the expected model performance of the predictions made at inference time.
NannyML can also track the realised performance of your machine learning model once targets are available.
To detect multivariate feature drift NannyML uses PCA-based data reconstruction. Changes in the resulting reconstruction error are monitored over time and data drift alerts are logged when the reconstruction error in a certain period exceeds a threshold. This threshold is calculated based on the reconstruction error observed in the reference period.
NannyML utilises statistical tests to detect univariate feature drift. We have just added a bunch of new univariate tests including Jensen-Shannon Distance and L-Infinity Distance, check out the comprehensive list. The results of these tests are tracked over time, properly corrected to counteract multiplicity and overlayed on the temporal feature distributions. (It is also possible to visualise the test-statistics over time, to get a notion of the drift magnitude.)
NannyML uses the same statistical tests to detected model output drift.
Target distribution drift is monitored by calculating the mean occurrence of positive events in combination with the 2-sample chi-squared test. Bear in mind that this operation requires the presence of actuals.
Because NannyML can estimate performance, it is possible to weed out data drift alerts that do not impact expected performance, combatting alert fatigue. Besides linking data drift issues to drops in performance it is also possible to prioritise alerts according to other criteria using NannyML's Ranker.
NannyML depends on LightGBM. This might require you to set install additional OS-specific binaries. You can follow the official installation guide.
From PyPI:
pip install nannyml
From Conda:
conda install -c conda-forge nannyml
Running via Docker:
docker -v /local/config/dir/:/config/ run nannyml/nannyml nml run
Here be dragons! Use the latest development version of NannyML at your own risk:
python -m pip install git+https://github.com/NannyML/nannyml
The following snippet is based on our latest release.
import nannyml as nml
from IPython.display import display
# Load synthetic data
reference, analysis, analysis_target = nml.load_synthetic_binary_classification_dataset()
display(reference.head())
display(analysis.head())
# Choose a chunker or set a chunk size
chunk_size = 5000
# initialize, specify required data columns, fit estimator and estimate
estimator = nml.CBPE(
y_pred_proba='y_pred_proba',
y_pred='y_pred',
y_true='work_home_actual',
metrics=['roc_auc'],
chunk_size=chunk_size,
problem_type='classification_binary',
)
estimator = estimator.fit(reference)
estimated_performance = estimator.estimate(analysis)
# Show results
figure = estimated_performance.plot(kind='performance', metric='roc_auc', plot_reference=True)
figure.show()
# Define feature columns
feature_column_names = [
col for col in reference.columns if col not in [
'timestamp', 'period', 'work_home_actual', 'identifier'
]]
# Let's initialize the object that will perform the Univariate Drift calculations
univariate_calculator = nml.UnivariateDriftCalculator(
column_names=feature_column_names,
chunk_size=chunk_size,
continuous_methods=['kolmogorov_smirnov', 'jensen_shannon'],
categorical_methods=['chi2'],
)
univariate_calculator = univariate_calculator.fit(reference)
univariate_results = univariate_calculator.calculate(analysis)
# Plot drift results for all continuous columns
for column_name in univariate_calculator.continuous_column_names:
figure = univariate_results.plot(
kind='drift',
method='jensen_shannon',
column_name=column_name,
plot_reference=True
)
figure.show()
# Plot drift results for all categorical columns
for column_name in univariate_calculator.categorical_column_names:
figure = univariate_results.plot(
kind='drift',
method='chi2',
column_name=column_name,
plot_reference=True
)
figure.show()
ranker = nml.Ranker.by('alert_count')
ranked_features = ranker.rank(univariate_results, only_drifting = False)
display(ranked_features)
# Let's initialize the object that will perform Data Reconstruction with PCA
rcerror_calculator = nml.DataReconstructionDriftCalculator(
column_names=feature_column_names,
chunk_size=chunk_size
).fit(reference_data=reference)
# let's see Reconstruction error statistics for all available data
rcerror_results = rcerror_calculator.calculate(analysis)
figure = rcerror_results.plot(kind='drift', plot_reference=True)
figure.show()
- Performance monitoring
- Drift detection
We want to build NannyML together with the community! The easiest to contribute at the moment is to propose new features or log bugs under issues. For more information, have a look at how to contribute.
The best place to ask for help is in the community slack. Feel free to join and ask questions or raise issues. Someone will definitely respond to you.
If you want to stay up to date with recent changes to the NannyML library, you can subscribe to our release notes. For thoughts on post-deployment data science from the NannyML team, feel free to visit our blog. You can also sing up for our newsletter, which brings together the best papers, articles, news, and open-source libraries highlighting the ML challenges after deployment.
Curious what we are working on next? Have a look at our roadmap. If you have any questions or if you would like to see things prioritised in a different way, let us know!
NannyML is distributed under an Apache License Version 2.0. A complete version can be found here. All contributions will be distributed under this license.