usage: dvc exp pull [-h] [-q | -v] [-A] [--rev <commit>] [-n <num>] [-f] [--no-cache] [-r <name>] [-j <number>] [--run-cache] git_remote [experiment ...] positional arguments: git_remote Git remote name or Git URL experiment Experiment to pull
git fetchdon't work with experiments because these are saved under custom Git references. See How does DVC track experiments? in DVC Experiments Overview to learn more about DVC experiment storage.
git_remote name (e.g.
origin) or Git URL is required. Experiments
derived from the
HEAD commit are pulled by default (see the options below).
The first action of
dvc exp pull is to download the
experiments from the Git
remote so they are available in the local repository (equivalent to
git fetch <git_remote> refs/exps/<experiment>). Use
dvc exp show to explore
your local experiments.
--all-commits- pull all experiments in the repository (overrides
--rev <commit>- pull experiments derived from the specified
<commit>as baseline (HEAD by default).
--num <num>- pull experiments from the last
numcommits (first parents) starting from the
--revbaseline. Give a negative value to include all first-parent commits (similar to
git log -n).
--force- rewrite the experiment if it already exists in the local repo.
--no-cache- do not pull cached files files associated with this experiment from DVC remote storage.
--remote <name>- name of the
dvc remoteto pull cached files from.
--run-cache- downloads all available history of stage runs from the
dvc remote(to the cache only, like
dvc fetch --run-cache). Note that
dvc exp run <stage_name>is necessary to checkout these files.
--jobs <number>- parallelism level for DVC to upload data to remote storage. The default value is
4 * cpu_count(). Note that the default value can be set using the
jobsconfig option with
dvc remote modify. Using more jobs may improve the overall transfer speed.
--help- shows the help message and exit.
--quiet- do not write anything to standard output. Exit with 0 if no problems arise, otherwise 1.
--verbose- displays detailed tracing information from executing the
This example is based on our Get Started, where you can find the actual source code.
Let's say we have cloned a DVC repository, and would like to fetch an experiment
that someone else shared (see also
dvc exp list).
$ dvc exp list --all-commits origin main: lurid-air $ dvc exp pull origin Pulled experiment 'lurid-lair' from Git remote 'origin'.
We can now see that the experiment exists in the local repo:
$ dvc exp list --all-commits main: 5cdc6a9 [lurid-air]