From 01d6b213b243a9ff3ab24bb66eef39e99838b7c8 Mon Sep 17 00:00:00 2001 From: Jorge Orpinel Date: Wed, 7 Apr 2021 15:00:03 -0500 Subject: [PATCH 1/2] ref: clarify that exp run isn't exactly like repro per https://github.com/iterative/dvc/issues/5593#issuecomment-815444772 --- .gitpod.yml | 7 ------- content/docs/command-reference/exp/run.md | 5 +++-- 2 files changed, 3 insertions(+), 9 deletions(-) delete mode 100644 .gitpod.yml diff --git a/.gitpod.yml b/.gitpod.yml deleted file mode 100644 index 300827e3ab..0000000000 --- a/.gitpod.yml +++ /dev/null @@ -1,7 +0,0 @@ -tasks: - - init: yarn install && yarn build - command: yarn develop - -ports: - - port: 8000 - onOpen: open-preview diff --git a/content/docs/command-reference/exp/run.md b/content/docs/command-reference/exp/run.md index bc2c9052a3..4d0abd21e5 100644 --- a/content/docs/command-reference/exp/run.md +++ b/content/docs/command-reference/exp/run.md @@ -27,8 +27,9 @@ directories, etc. > `dvc exp run` is equivalent to `dvc repro` for experiments. 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. Before running an experiment, you'll probably want to make modifications such as data and code updates, or hyperparameter tuning. For the latter, From d3feaf06de00ce6a7e660ab785ba2843d0cc99d5 Mon Sep 17 00:00:00 2001 From: Jorge Orpinel Date: Thu, 8 Apr 2021 10:35:34 -0500 Subject: [PATCH 2/2] ref: revert note on exp run discarding changes per https://github.com/iterative/dvc.org/pull/2365#pullrequestreview-630982377 --- content/docs/command-reference/exp/run.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/content/docs/command-reference/exp/run.md b/content/docs/command-reference/exp/run.md index 4d0abd21e5..bc2c9052a3 100644 --- a/content/docs/command-reference/exp/run.md +++ b/content/docs/command-reference/exp/run.md @@ -27,9 +27,8 @@ directories, etc. > `dvc exp run` is equivalent to `dvc repro` for experiments. It > has the same behavior when it comes to `targets` and stage execution (restores -> 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. +> the dependency graph, etc.). See the command [options](#options) for more on +> the differences. Before running an experiment, you'll probably want to make modifications such as data and code updates, or hyperparameter tuning. For the latter,