`exp show`: add output of `params diff` & `metrics diff` to `workspace` entry within `--show-json`
See original GitHub issueIn the VS Code extension we recently added in a feature to our experiments table which highlights params and metrics which have changed with respect to the previous commit.
Example (example-dvc-experiments)
Given:
dvc params diff --show-json={"params.yaml": {"train.epochs": {"old": 10, "new": 11, "diff": 1}}}dvc metrics diff --show-json={}
Then we will show:

The current cli implementation means that we now have to run 3 commands to get the required data for our table. These are:
dvc exp show --show-jsondvc params diff --show-jsondvc metrics diff --show-json
We are still running into repo locks when trying to run any of the above commands. Also, having to run all three is slower.
Ideally I’d like to include the output of 2 & 3 within the workspace dict of 1 but open to other suggestions.
Note: If we pushed this data into exp show then we would also be able to highlight the same records in the cli table.
Related issues:
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
exp diff | Data Version Control - DVC
Without arguments, this command compares all the params and metrics referenced in dvc.yaml files present in the workspaceworkspace with the latest committed ...
Read more >dvc Changelog - pyup.io
Exp show md (6799) daavoo - machine: Add a new command `dvc machine status` (6649) karajan1001 - exp/metrics/params diff: Replaced `Old/New` with ...
Read more >Diff files - Helix Core Command-Line (P4) Guide
Helix Server allows you to diff (compare) revisions of text files. By diffing files, you can display: Changes that you made after opening...
Read more >GGIR configuration parameters
Argument (parameter) Used in GGIR part Parameter object
datadir 1, 2, 4, 5 not in parameter objects
f0 1, 2, 3, 4, 5 not in...
Read more >Collecting metrics on UML models - IBM
You can run a UML Metrics analysis configuration on a UML model to collect several different types of numerical information about the model....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Showing/highlighting deltas in the
exp showtable can already be implemented as UI on top of the existing available data in both DVC and the vscode extension (since both the original and new params/metrics values are already exposed in the existingexp show --show-jsondata).I think @mattseddon is asking for the deltas to also be included in the json in addition to the existing data, which IMO is a separate discussion from any spinoff issue for displaying the deltas in the DVC CLI table (#6783)
On re-implementing DVC internals, handling the git ref mechanics of HEAD vs EXEC_BASELINE should be unnecessary on the vscode extension side (since
exp showalready accounts for it, and returns all the data needed in place of the original 3 commands that vscode was using)You shouldn’t need the extra
params diffandmetrics diffcalls. The original commit data should already be available inexp showin<orig_commit_sha>.baseline.datain this example
00071eis the original commit SHA (master) and5d1639is the exp SHA (exp-8dd71) So diffing00071e.baseline.data.paramsand00071e.5d1639.data.params(using the full SHAs as keys) should give you the same information you get fromparams diff(and the same fordata.metricsandmetrics diff)