usage: dvc exp pull [-h] [-q | -v] [-f] [--no-cache] [-r <name>] [-j <number>] [--run-cache] git_remote experiment positional arguments: git_remote Git remote name or repo URL experiment Experiment to pull
git fetchdon't work with
dvc experimentsbecause these are saved under custom Git references. See How does DVC track experiments? in
dvc exp runto learn more about DVC experiment storage.
git_remote name (e.g.
origin) or valid Git repo's URL is required,
as well as an
experiment name or hash (see
dvc exp run) to pull.
The first action of
dvc exp pull is to download the
experiment so it's
available in the local repository (equivalent to
git fetch <git_remote> refs/exps/<experiment>). Use
dvc exp show to explore
your local experiments.
By default, this command will also try to pull
all cached data associated with the experiment to DVC
remote storage, unless
--no-cache is used.
The default remote is used (see
dvc remote default) unless a specific one is
💡 Note that
git push <git_remote> --delete <experiment>can be used to delete a pushed experiment.
--force- rewrite the
experimentcommit if it already exists in the local repo. Equivalent to
git push --force(rewrites history)
--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 to.
--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(). For SSH remotes, the default is
4. 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 origin master: exp-e6c97 $ dvc exp pull origin exp-e6c97 Pulled experiment 'exp-e6c97' from Git remote 'origin'.
We can now see that the experiment exists in the local repo:
$ dvc exp list --all master: exp-e6c97