Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restyle Update data-pipelines.md #1646

Closed
wants to merge 2 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 7 additions & 10 deletions content/docs/start/data-pipelines.md
Original file line number Diff line number Diff line change
Expand Up @@ -292,17 +292,14 @@ prepare:
DVC pipelines (`dvc.yaml` file, `dvc run`, and `dvc repro` commands) solve a few
important problems:

- _Automation_ - run sequence of steps in a "smart" way that makes iterating on
the project faster. It automatically determines which parts of a project need
to be run, it caches "runs" and results — all to avoid running the same stage
again.
- _Reproducibility_ - it can describe and capture what data should be used and
what commands to run to produce an ML model, for example. It's described and
captured in way that is easy to put into Git. It means that it's easy to
version and share.
- _Automation_ - run a sequence of steps in a "smart" way to iterate on your
project faster. DVC caches "runs" and results in stages to avoid unnecessary
re-runs.
- _Reproducibility_ - YAML files describe and capture what data to use and what
commands to run to produce an ML model. Storing these files in Git makes it
easy to version and share.
- _Continuous Delivery and Continuous Integration (CI/CD) for ML_ - describing
project in way that it can be reproduced (built) is the fist necessary step
before introducing CI/CD systems.
reproducible ML pipelines (builds) facilitates CI/CD systems.

## Visualize

Expand Down