exp show: Include deps and outs.

[daavoo]

• ❗ I have followed the Contributing to DVC checklist.

• 📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.

iterative/dvc.org#3220

---

Use repo.index.deps / repo.index.outs to collect dependencies / outputss associated with each experiment.

Closes #6434

What's considered a dep

Currently, anything in repo.index.deps that is not a param dependency or an imported .dvc (because if the .dvc is used in the pipeline it would be a duplicated column).

Studio filters git tracked files but I think that showing those files (i.e. src deps) is also valuable.

I think that more complicated internal filtering (i.e. considering removing intermediate deps) it's not worthy and problematic when considering all use cases.

The table can get noisy but we provide the --only-changed flag (we could consider making it the default) and new improved filtering #7141 that should make it easy to customize the table.

JSON output

For --json output, this P.R. adds new deps and outs fields:

{
        "baseline": {
            "data": {
                "deps": {
                    "copy.py": {
                        "hash": "561f068574ab2a132d304dca3dd6510d",
                        "size": 310,
                        "nfiles": None,
                    }
                },
                "metrics": {"metrics.yaml": {"data": {"foo": 1}}},
                "outs": {
                    "model.pkl": {
                        "hash": "fb7792b6596fd12502dd132c0aba0568",
                        "size": 2000,
                        "nfiles": None,
                    }
                },
                "params": {"params.yaml": {"data": {"foo": 1}}},
                "queued": False,
                "running": False,
                "executor": None,
                "timestamp": None,
            }
        }
    }

Table

For the table, it creates a new type of colored columns and shows the hash (let the debate begin).

After some testing, it looks like the optimal value for showing in the data column highly varies between use cases.

Given the limitations of the CLI, I opted for showing hash as it's the value that allows, IMO, to easily identify differences between rows.

From example-get-started:

• dvc exp show --only-changed

• dvc exp show --all-branches --only-changed

Some deps might not be relevant, filtering with #7141 :

• dvc exp show --all-branches --only-changed --drop '.+prepared|model'

[daavoo]

Didn't know how to something like the ANY usage above but for the type of assertions bellow

[dberenbaum]

Looks good so far!

Should deps come at the end (after params)? The noise would be less of an issue if they are on the right.

[daavoo]

Looks good so far!

Should deps come at the end (after params)? The noise would be less of an issue if they are on the right.

Done

[dberenbaum]

Should deps come at the end (after params)? The noise would be less of an issue if they are on the right.

By the way, Studio has data files in between metrics and params, right? Do you know why this order was preferred, and what do you think? I like them at the end, but consistency with Studio makes sense.

[daavoo]

By the way, Studio has data files in between metrics and params, right? Do you know why this order was preferred, and what do you think? I like them at the end, but consistency with Studio makes sense.

I don't know Studio preferences. I think that in our case it makes sense to introduce them at the end as they didn't exist before and table can't get noisy without --only-changed flag.

[dberenbaum]

@daavoo It looks like the data columns are in a random order and it sometimes changes on repeated calls to exp show. Can we sort in alphabetical order or some other predictable way that will make sense to users?

[jorgeorpinel]

or some other predictable way

Curious: what was the sorting in the end? I think the most natural would be as defined in dvc.yaml

[daavoo]

or some other predictable way

Curious: what was the sorting in the end? I think the most natural would be as defined in dvc.yaml

Alphabetical (it is what's currently used in Studio, afaik)