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.

Sign up for GitHub

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

ref: clarify that exp run isn't exactly like repro #2365

Closed
wants to merge 2 commits into from
Closed

ref: clarify that exp run isn't exactly like repro #2365

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
01d6b21
ref: clarify that exp run isn't exactly like repro
jorgeorpinel Apr 7, 2021
d3feaf0
ref: revert note on exp run discarding changes
jorgeorpinel Apr 8, 2021
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
7 changes: 0 additions & 7 deletions .gitpod.yml
View file
Open in desktop

This file was deleted.

5 changes: 3 additions & 2 deletions content/docs/command-reference/exp/run.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,9 @@ directories, etc.

> `dvc exp run` is equivalent to `dvc repro` for <abbr>experiments</abbr>. It
> has the same behavior when it comes to `targets` and stage execution (restores
> the dependency graph, etc.). See the command [options](#options) for more on
> the differences.
> the dependency graph, etc.). An important difference is that changes in the
> working tree are discarded by `dvc exp run`. See the command
> [options](#options) for more on the differences.
jorgeorpinel marked this conversation as resolved.
Show resolved Hide resolved

Before running an experiment, you'll probably want to make modifications such as
data and code updates, or <abbr>hyperparameter</abbr> tuning. For the latter,
Expand Down