| Maisie | |
| Maisie Sphinx Theme | |
| Documentation | |
| PyPI | |
| DockerHub |
Could archiving, storing, managing and organizing machine learning models be done efficiently and with great focus on user experience? Sure, Maisie does just that.
Maisie is a friendly, easy to use assistant that consists of:
It integrates seamlessly with your favorite tools and provides you with all the important data, such as:
You can get the most current package from PyPI
$ pip install MaisieUsing it in your training environment is fairly straightforward:
import maisie
from sklearn.externals import joblib
# Define your model here
model.fit(X, y)
model_filename = "example_model.pkl"
joblib.dump(model, model_filename)
# Define your metrics, fetch parameters and hyperparameters
models = maisie.Models()
models.upload(
name="My first uploaded model",
filename=model_filename,
dataset_name="Singly Identifying Dataset Name",
metrics={"accuracy": accuracy},
hyperparameters=hyperparameters,
parameters=parameters,
)This repository provides a pre-configured docker-compose.yml file that contains sensible default options.
Before starting the containers, you should create a local .env file using the included .env.sample.
To start up all services, run:
$ docker-compose upTo stop your services, you can press Ctrl+C/Ctrl+D. If you started the services in the background using docker-compose up -d, the correct way to do this would be:
$ docker-compose stopYou can learn more about Docker Compose by clicking here.
Both frontend and backend images are automatically published to Docker Hub as soon as new stable release is made available.
Links
For reference, you can look at the sample Ansible playbook that deploys all containers to a specified host using the locally configured .env file.
develop branch$ git clone -b develop [email protected]:nokia-wroclaw/innovativeproject-ml-models-management.git$ pre-commit install$ docker-compose upissue-[number]-[short description] derived from the develop branch, for example$ git checkout -b issue-42-project-removal-permissions developWhen implementing new features, you should start by creating a new branch named feature-[short description] derived from the develop branch, for example
$ git checkout -b feature-new-user-profile developTo run all tests and check whether all required pre-commit githooks are satisfied, run
$ pre-commit run --all-filesYour commit message should briefly summarize the changes (if possible) in plain English. To learn how to write a proper commit message, check out this article.
When ready, create a new pull request compared with the develop branch set as a base branch.
For the lastest stable release, the documentation can be seen at docs.maisie.dev.