Show multiple versions of plot metrics by overlaying them in a single image. This allows to compare them easily.
usage: dvc plots diff [-h] [-q | -v] [--targets [<paths> [<paths> ...]]] [-t <name_or_path>] [-x <field>] [-y <field>] [--no-header] [--title <text>] [--x-label <text>] [--y-label <text>] [-o <path>] [--show-vega] [--open] [revisions [revisions ...]] positional arguments: revisions Git commits to find metrics to compare
This command is a way to visualize the "difference" between certain metrics among versions of the repository, by overlaying them in a single plot.
Note that unlike
dvc metrics diff, this command does not calculate numeric differences between plots file values.
revisions are Git commit hashes, tags, or branch names. If none are specified,
dvc plots diff compares plots currently present in the workspace
(uncommitted changes) with their latest commit (required). A single specified
revision results in comparing the workspace and that version.
💡 Note that any number of
revisions can be provided (the resulting plot shows
all of them in a single image).
All plots defined in
dvc.yaml are used by default, but specific files can be
specified with the
--targets option (any valid plots file is accepted).
Note that the default behavior of this command can be modified per metrics file with
dvc plots modify.
Another way to display plots is the
dvc plots show command, which just lists
all the current plots, without comparisons.
--targets <paths> - specific plots files to visualize. It accepts
any valid plots file, regardless of whether
dvc.yaml is currently tracking
any plots in them.
When specifying arguments for
revisions, you should use
-- after this option's arguments, e.g.:
$ dvc plots diff --targets t1.json t2.csv -- HEAD v1 v2
-o <path>, --out <path>- name of the generated file. By default, the output file name is equal to the input file name with a
.htmlfile extension (or
-t <name_or_path>, --template <name_or_path>- plot template to be injected with data. The default template is
.dvc/plots/default.json. See more details in
-x <field>- field name from which the X axis data comes from. An auto-generated
indexfield is used by default. See Custom templates for more information on this
indexfield. Column names or numbers are expected for tabular metrics files.
-y <field>- field name from which the Y axis data comes from. The last field found in the
--targetsis used by default. Column names or numbers are expected for tabular metrics files.
--x-label <text>- X axis label. The X field name is the default.
--y-label <text>- Y axis label. The Y field name is the default.
--title <text>- plot title.
--show-vega- produce a Vega specification file instead of HTML. See
dvc plotsfor more info.
--open- opens the generated plot in the browser automatically.
--no-header- lets DVC know that CSV or TSV
--targetsdo not have a header. A 0-based numeric index can be used to identify each column instead of names.
--help- prints the usage/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.
To compare uncommitted changes of a metrics file and its last committed version:
$ dvc plots diff --targets logs.csv --x-label x file:///Users/usr/src/plots/logs.html
Note that we renamed the X axis label with option
Compare two specific versions (commit hashes, tags, or branches):
$ dvc plots diff HEAD 0135527 --targets logs.csv file:///Users/usr/src/plots/logs.csv.html
We'll use tabular metrics file
classes.csv for this example:
predicted,actual cat,cat cat,cat cat,cat dog,cat dinosaur,cat dinosaur,cat bird,cat dog,turtle cat,turtle ...
The predefined confusion matrix
.dvc/plots/confusion.json) shows how metrics comparisons can be faceted by
separate plots. It can be enabled with
$ dvc plots diff -t confusion --targets classes.csv -x predicted file:///Users/usr/src/test/plot_old/classes.csv.html