You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before creating the experiment ref, DVCLive should write to a dvc.yaml file inside the Live directory, which should configure parameters, metrics, and plots logged by DVCLive. This could happen either during logging or at the end before creating the experiment ref. Depends on iterative/dvc#8371.
If DVCLive is run inside of a DVC pipeline, can we detect and skip all of this functionality for now? Long term, it would be nice for DVC pipelines to be able to support this DVCLive-configured dvc.yaml.
If DVCLive is run inside of a DVC pipeline, can we detect and skip all of this functionality for now? Long term, it would be nice for DVC pipelines to be able to support this DVCLive-configured dvc.yaml.
Not sure we need to actually skip writing to dvc.yaml in pipelines. Probably we need an option to choose whether to skip, since if someone has a custom plots configuration, for example, they won't want to use the auto-generated dvc.yaml.
I guess we could have DVCLive auto-generate names for now (related to iterative/vscode-dvc#2457) if it's easier than revisiting how exp names are assigned, but it might be better to track changes across the entire repo instead of only in dvc.lock.
Follow up to #310
Originally posted by @dberenbaum in #310 (comment)
The text was updated successfully, but these errors were encountered: