live: Revisit output names

[daavoo]

can we rename it? is it a default name? it's a bit confusing to have dvclive dir, dvclive/scalars which are actually plots and dvclive.json that is actually scalars ... how can we improve this naming? cc @dberenbaum @daavoo wdyt?

Originally posted by @shcheklein in iterative/vscode-dvc#1618 (comment)

[dberenbaum]

Related conversation: iterative/dvc.org#3147 (comment)

[dberenbaum]

My take:

• scalars seems too technical to me. Can we rename to trends to align with VS Code and Studio?
• dvclive.json we can probably rename to metrics.json. We have also discussed moving it inside dvclive/metrics.json, which I think makes sense although I think there are a few technical hurdles to overcome for how to track everything inside dvclive.

Edit: If we move more inside dvclive, we could also add a subdir for plots so it looks like:

$ tree dvclive
├── metrics.json # renamed from "dvclive.json" and moved inside the dir
├── plots # align subdir names with VS Code
│   ├── data_series # renamed from "plots"
│   │   └── roc.json
│   ├── images
│   │   └── img.png
│   └── trends # renamed from "scalars"
│       └── acc.tsv
└── report.html

[daavoo]

Can we rename to trends to align with VS Code and Studio?

It sounds appealing and more clear than scalars.

However, trends in VSCode are based on DVC checkpoints, and in Studio are based on commits.
The .tsv files we would be saving in plots/trends would be shown as Data Series in VScode and as Plots in Studio.

I don't know if this would be confusing for users or not.

dvclive.json we can probably rename to metrics.json. We have also discussed moving it inside dvclive/metrics.json, which I think makes sense although I think there are a few technical hurdles to overcome for how to track everything inside dvclive.

Moving dvclive.json to dvclive/metrics.json + creating a plots folder sounds good.

[dberenbaum]

Okay, maybe we can hold off on trends for now or think of another name.

[dberenbaum]

Okay, maybe we can hold off on trends for now or think of another name.

How about metrics, so that it looks like:

$ tree dvclive
├── metrics.json # renamed from "dvclive.json" and moved inside the dir
├── params.yaml # new
├── plots # align subdir names with VS Code
│   ├── data_series # renamed from "plots"
│   │   └── roc.json
│   ├── images
│   │   └── img.png
│   └── metrics # renamed from "scalars"
│       └── acc.tsv
└── report.html

[daavoo]

Would be nice to also address iterative/dvc.org#3994 (comment)