-
Notifications
You must be signed in to change notification settings - Fork 394
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
guide: Managing Experiments section(s) #816
Comments
I started the PR #828 to close this issue, but actually I don't have a very clear idea about how to best explain it, so I would appreciate some help from the @iterative/engineering team.
The first two cases are almost clear, and also there are some examples in the Get Started and the Tutorials, which might be summarized on these pages. For the case of managing experiments by directories, there is a very simple example at the end of this interactive tutorial: https://katacoda.com/dvc/courses/basics/pipelines The last case, where we can mix different kinds of experiment management techniques, is even more difficult for me. Conceptually I know how it should work, but it is not so easy to come up with a convincing example, which is both simple and looks kind of realistic. I have no experience with ML, so it is too difficult for me to make up something. If you can think up something suitable please let me know. |
This comment has been minimized.
This comment has been minimized.
I think the original intention was more or less correct in this ticket - User Guide page like this makes sense to me. |
OK but in #72 (comment) you said
but I guess it depends on what/how much content we will have for this topic. Could be in UG at first. |
UPDATE: Skip to #816 (comment)
Add a
User Guidepage that explains how to manage experiments:Documenting first the existing methods may also help the discussions about adding new methods for experiment management (iterative/dvc#2799), because my impression is that most of what is being discussed there can already be accomplished with the existing tools.
Another related issue: #159
The text was updated successfully, but these errors were encountered: