Treeverse/Dvc: Data Versioning and ML Experiments

Treeverse's DVC (Data Version Control) is a command line tool and VS Code Extension that versions data and models in cloud storage while keeping version metadata in a Git repo, tracks ML experiments locally without servers, and connects code and data through lightweight pipelines. DVC stores data and model files in a cache outside Git and supports remotes on S3, Azure, Google Cloud and SSH-based on-premise storage, with a VS Code extension from Iterative offering experiment tracking and data management that requires core DVC to be installed separately.

Website https://dvc.org • Docs https://dvc.org/doc • Blog http://blog.dataversioncontrol.com • Tutorial https://dvc.org/doc/get-started • Related Technologies https://dvc.org/doc/user-guide/related-technologies • How DVC works how-dvc-works • VS Code Extension vs-code-extension • Installation installation • Contributing contributing • Community and Support community-and-support Data Version Control or DVC is a command line tool and VS Code Extension vs-code-extension to help you develop reproducible machine learning projects: 1. Version your data and models. Store them in your cloud storage but keep their version info in your Git repo. 2. Iterate fast with lightweight pipelines. When you make changes, only run the steps impacted by those changes. 3. Track experiments in your local Git repo no servers needed . 4. Compare any data, code, parameters, model, or performance plots. 5. Share experiments and automatically reproduce anyone's experiment. Please read our Command Reference https://dvc.org/doc/command-reference for a complete list. A common CLI workflow includes: | Task | Terminal | |---|---| | Track data | $ git add train.py params.yaml $ dvc add images/ | | Connect code and data | $ dvc stage add -n featurize -d images/ -o features/ python featurize.py $ dvc stage add -n train -d features/ -d train.py -o model.p -M metrics.json python train.py | | Make changes and experiment | $ dvc exp run -n exp-baseline $ vi train.py $ dvc exp run -n exp-code-change | | Compare and select experiments | $ dvc exp show $ dvc exp apply exp-baseline | | Share code | $ git add . $ git commit -m 'The baseline model' $ git push | | Share data and ML models | $ dvc remote add myremote -d s3://mybucket/image cnn $ dvc push | We encourage you to read our Get Started https://dvc.org/doc/get-started docs to better understand what DVC does and how it can fit your scenarios. The closest analogies to describe the main DVC features are these: 1. Git for data : Store and share data artifacts like Git-LFS but without a server and models, connecting them with a Git repository. Data management meets GitOps 2. Makefiles for ML: Describes how data or model artifacts are built from other data and code in a standard format. Now you can version your data pipelines with Git. 3. Local experiment tracking : Turn your machine into an ML experiment management platform, and collaborate with others using existing Git hosting Github, Gitlab, etc. . Git is employed as usual to store and version code including DVC meta-files as placeholders for data . DVC stores data and model files https://dvc.org/doc/start/data-management seamlessly in a cache outside of Git, while preserving almost the same user experience as if they were in the repo. To share and back up the data cache , DVC supports multiple remote storage platforms - any cloud S3, Azure, Google Cloud, etc. or on-premise network storage via SSH, for example . DVC pipelines https://dvc.org/doc/start/data-management/data-pipelines computational graphs connect code and data together. They specify all steps required to produce a model: input dependencies including code, data, commands to run; and output information to be saved. Last but not least, DVC Experiment Versioning https://dvc.org/doc/start/experiments lets you prepare and run a large number of experiments. Their results can be filtered and compared based on hyperparameters and metrics, and visualized with multiple plots. To use DVC as a GUI right from your VS Code IDE, install the DVC Extension https://marketplace.visualstudio.com/items?itemName=Iterative.dvc from the Marketplace. It currently features experiment tracking and data management, and more features data pipeline support, etc. are coming soon Note: You'll have to install core DVC on your system separately as detailed below . The Extension will guide you if needed. There are several ways to install DVC: in VS Code; using snap , choco , brew , conda , pip ; or with an OS-specific package. Full instructions are available here https://dvc.org/doc/get-started/install . snap install dvc --classic This corresponds to the latest tagged release. Add --beta for the latest tagged release candidate, or --edge for the latest main version. choco install dvc brew install dvc conda install -c conda-forge mamba installs much faster than conda mamba install -c conda-forge dvc Depending on the remote storage type you plan to use to keep and share your data, you might need to install optional dependencies: dvc-s3, dvc-azure, dvc-gdrive, dvc-gs, dvc-oss, dvc-ssh. pip install dvc Depending on the remote storage type you plan to use to keep and share your data, you might need to specify one of the optional dependencies: s3 , gs , azure , oss , ssh . Or all to include them all. The command should look like this: pip install 'dvc s3 ' in this case AWS S3 dependencies such as boto3 will be installed automatically . To install the development version, run: pip install "dvc @ git+https://github.com/treeverse/dvc" Self-contained packages for Linux, Windows, and Mac are available. The latest version of the packages can be found on the GitHub releases page https://github.com/treeverse/dvc/releases . sudo wget https://dvc.org/deb/dvc.list -O /etc/apt/sources.list.d/dvc.list wget -qO - https://dvc.org/deb/iterative.asc | sudo apt-key add - sudo apt update sudo apt install dvc sudo wget https://dvc.org/rpm/dvc.repo -O /etc/yum.repos.d/dvc.repo sudo rpm --import https://dvc.org/rpm/iterative.asc sudo yum update sudo yum install dvc Contributions are welcome Please see our Contributing Guide https://dvc.org/doc/user-guide/contributing/core for more details. Thanks to all our contributors This project is distributed under the Apache license version 2.0 see the LICENSE file in the project root . By submitting a pull request to this project, you agree to license your contribution under the Apache license version 2.0 to this project. Iterative, DVC: Data Version Control - Git for Data & Models 2020 DOI:10.5281/zenodo.012345 https://doi.org/10.5281/zenodo.3677553 . Barrak, A., Eghan, E.E. and Adams, B. On the Co-evolution of ML Pipelines and Source Code - Empirical Study of DVC Projects https://mcis.cs.queensu.ca/publications/2021/saner.pdf , in Proceedings of the 28th IEEE International Conference on Software Analysis, Evolution, and Reengineering, SANER 2021. Hawaii, USA.