- Notifications
You must be signed in to change notification settings - Fork36
Capture all information throughout your model's development in a reproducible way and tie results directly to the model code!
License
capitalone/rubicon-ml
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
rubicon-ml is a data science tool that captures and stores model training andexecution information, like parameters and outcomes, in a repeatable andsearchable way. Itsgit
integration associates these inputs and outputsdirectly with the model code that produced them to ensure full auditability andreproducibility for both developers and stakeholders alike. While experimenting,the dashboard makes it easy to explore, filter, visualize, and sharerecorded work.
p.s. If you're looking for Rubicon, the Java/ObjC Python bridge, visitthis instead.
rubicon-ml is composed of three parts:
- A Python library for storing and retrieving model inputs, outputs, andanalyses to filesystems that’s powered by
fsspec
- A dashboard for exploring, comparing, and visualizing logged data built with
dash
- And a process for sharing a selected subset of logged data with collaboratorsor reviewers that leverages
intake
Userubicon_ml
to capture model inputs and outputs over time. It can beeasily integrated into existing Python models or pipelines and supports bothconcurrent logging (so multiple experiments can be logged in parallel) andasynchronous communication with S3 (so network reads and writes won’t block).
Meanwhile, periodically review the logged data within the Rubicon dashboard tosteer the model tweaking process in the right direction. The dashboard lets youquickly spot trends by exploring and filtering your logged results andvisualizes how the model inputs impacted the model outputs.
When the model is ready for review, Rubicon makes it easy to share specificsubsets of the data with model reviewers and stakeholders, giving them thecontext necessary for a complete model review and approval.
Check out theinteractive notebooks in this Binderto tryrubicon_ml
for yourself.
Here's a simple example:
fromrubicon_mlimportRubiconrubicon=Rubicon(persistence="filesystem",root_dir="/rubicon-root",auto_git_enabled=True)project=rubicon.create_project("Hello World",description="Using rubicon to track model results over time.")experiment=project.log_experiment(training_metadata=[SklearnTrainingMetadata("sklearn.datasets","my-data-set")],model_name="My Model Name",tags=["my_model_name"],)experiment.log_parameter("n_estimators",n_estimators)experiment.log_parameter("n_features",n_features)experiment.log_parameter("random_state",random_state)accuracy=rfc.score(X_test,y_test)experiment.log_metric("accuracy",accuracy)
Then explore the project by running the dashboard:
rubicon_ml ui --root-dir /rubicon-root
For a full overview, visit thedocs. Ifyou have suggestions or find a bug,please open anissue.
The Python library is available on Conda Forge viaconda
and PyPi viapip
.
conda config --add channels conda-forgeconda install rubicon-ml
or
pip install rubicon-ml
The project uses conda to manage environments. First, installconda.Then use conda to setup a development environment:
conda env create -f environment.ymlconda activate rubicon-ml-dev
Finally, installrubicon_ml
locally into the newly created environment.
pip install -e".[all]"
The tests are separated into unit and integration tests. They can be rundirectly in the activated dev environment viapytest tests/unit
orpytest tests/integration
. Or by simply runningpytest
to execute all of them.
Note: some integration tests are intentionallymarked
to control when theyare run (i.e. not during CICD). These tests include:
Integration tests that write to physical filesystems - local and S3. Localfiles will be written to
./test-rubicon
relative to where the tests are run.An S3 path must also be provided to run these tests. By default, thesetests are disabled. To enable them, run:pytest -m "write_files" --s3-path "s3://my-bucket/my-key"
Integration tests that run Jupyter notebooks. These tests are a bit slowerthan the rest of the tests in the suite as they need to launch Jupyter servers.By default, they are enabled. To disable them, run:
pytest -m "not run_notebooks and not write_files"
Note: When simply running
pytest
,-m "not write_files"
is thedefault. So, we need to also apply it when disabling notebook tests.
Install and configure pre-commit to automatically runblack
,flake8
, andisort
during commits:
- install pre-commit
- run
pre-commit install
to set up the git hook scripts
Nowpre-commit
will run automatically on git commit and will ensure consistentcode format throughout the project. You can format without committing viapre-commit run
or skip these checks withgit commit --no-verify
.
About
Capture all information throughout your model's development in a reproducible way and tie results directly to the model code!