Matt Seddon

Relates to https://github.com/iterative/vscode-dvc/issues/1649 - Add a refresh button to the plots webviews (consider only missing image) - Only try to fetch revision once

Should be combined with #1444

and https://github.com/iterative/vscode-dvc/issues/2031

> @mattseddon What do we need to unlock this: Naming/renaming experiments after execution? I believe the ticket for that is https://github.com/iterative/vscode-dvc/issues/2055 IMO this ticket needs user input and product decisions....

> Yeah. My question was: How to unlock it? First, we need to decide how high of a priority this is for us. We then need to convey that priority...

Looking at example output data now. Here are some thoughts (cc @pared) ``` "revisions": [ "HEAD::training_logs/scalars/test_accuracy.tsv::test_accuracy", "HEAD::training_logs/scalars/train_accuracy.tsv::train_accuracy", "HEAD::training_logs/scalars/train_loss.tsv::train_loss", "workspace::training_logs/scalars/test_accuracy.tsv::test_accuracy", "workspace::training_logs/scalars/train_accuracy.tsv::train_accuracy", "workspace::training_logs/scalars/train_loss.tsv::train_loss" ] ``` :point_up: I know that we had issues...

Quick update. @pared has been iterating on the API and we have been discussing possible solutions/data structures.

Update: We've verified that flexible plots will not be shown in VS Code (and nothing will break) after the PR is merged. We still need to discuss how we will...

> Would it be possible to divide the color space in two complementary regions? One for each domain? There are potentially more than two domains for each revision. I think...

I'll catch up with @pared and see where we're at 👍🏻.