Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure DVC experiment from DVCLive #311

Closed
dberenbaum opened this issue Sep 27, 2022 · 2 comments · Fixed by #366
Closed

Configure DVC experiment from DVCLive #311

dberenbaum opened this issue Sep 27, 2022 · 2 comments · Fixed by #366
Labels
A: dvc DVC integration p1-important Include in the next sprint

Comments

@dberenbaum
Copy link
Collaborator

dberenbaum commented Sep 27, 2022

Follow up to #310

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.

Originally posted by @dberenbaum in #310 (comment)

@dberenbaum
Copy link
Collaborator Author

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.

@daavoo
Copy link
Contributor

daavoo commented Nov 18, 2022

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.

Originally posted by @dberenbaum in iterative/dvc#8408 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: dvc DVC integration p1-important Include in the next sprint
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants