vscode-dvc
vscode-dvc copied to clipboard
iterative
Improve experiments naming
One of the common feedbacks we are getting is that experiment names are not meaningful w/o metrics in the side panel and in the plots webview.
We need to introduce:
- columns that we can pin (metrics, params, data) and get this information into experiment names, or replaces hash
- names - let's try to generate auto names? similar to how codespace does this. Some short adj + short noun
- tooltips with the full list of metrics, params, full hash, etc
Related discussion on the DVC side: https://github.com/iterative/dvc/discussions/7877
Related https://github.com/iterative/vscode-dvc/issues/1820#issuecomment-1253154206
Apart from improving the display of auto-generated names, would it make sense to allow the user to name an experiment themselves when creating it? E.g., using Modify & Queue. Right now, the UI goes through a sequence of questions to ask for the different parameters values one indicated wanting to modify for the experiment. Why not also ask (maybe as final step) what to name the experiment, or to keep the auto-generated default otherwise?
names - let's try to generate auto names? similar to how codespace does this. Some short adj + short noun
I added a random name generator in DVCLive, mostly out of necessity for the Python-only experiments scenario (it was simpler than changing how DVC currently generates the exp hashes):
https://github.com/iterative/dvclive/pull/366
───────────────────────────────────────────────────────────────
Experiment Created foobar foo.bar step
───────────────────────────────────────────────────────────────
workspace - 4.348 4.0804 5
master 11:40 AM 4.1825 4.7032 4
├── bbddd64 [sworn-snib] 12:06 PM 4.348 4.0804 5
├── 775fb5b [taunt-vina] 12:06 PM 4.297 4.5091 5
├── d08f02e [kraal-jump] 12:06 PM 4.0358 4.0448 5
├── b739189 [color-vega] 12:06 PM 4.9082 4.6159 5
└── 34541c3 [mauve-loss] 12:06 PM 4.3448 4.4993 5
───────────────────────────────────────────────────────────────
With tooltips added to the plots ribbon blocks (#2924) and DVC updating experiment names, are we ready to close this issue or is there more to be done?
