dvc experiments in a DVC repository (remote or local).
usage: dvc experiments list [-h] [-q | -v] [--rev <rev>] [--all] [git_remote] positional arguments: git_remote Optional Git remote name or repo URL
Prints a list of experiments found in the current repository, and the branch/tag
or commit they're based on. This is similar to
dvc exp show --no-pager, but
limited to experiment names and with very simple formatting. See also
dvc exp run.
If a working
git_remote name (e.g.
origin) or valid Git repo's URL is
provided, lists experiments in that repository instead (if any,
based on the
dvc remote default).
Note that this utility doesn't require an existing DVC project to run from when a
git_remoteURL is given.
Only experiments derived from the
HEAD commit are listed by default (see the
Note that checkpoints are not listed, only the parent experiment.
--rev <commit>- list experiments derived from the specified Git commit (instead of
--all- list all experiments in the repository (overrides
--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 run 3 experiments in our project. You can quickly list the available experiments with this command:
$ dvc exp list --all 10-bigrams-experiment: exp-e6c97 exp-1dad0 exp-1df77
Contrast this with the full table displayed by
dvc exp show.
You can also list experiments in any DVC repo with
dvc exp list:
$ dvc exp list --all email@example.com:iterative/example-get-started.git 10-bigrams-experiment: exp-e6c97 exp-86dd6
We can see that two experiments are available in (the DVC repo).
If we're currently in a local clone of the repo, we can also use Git remote name instead:
$ git remote -v origin firstname.lastname@example.org:iterative/example-get-started.git $ dvc exp list --all origin 10-bigrams-experiment: exp-e6c97 exp-86dd6