-
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 #2752
Conversation
…g into iesahin/ug-exp-run-2675
…g into iesahin/ug-exp-run-2675
per #2690 (review)
When you create an experiment, DVC generates a Git-like SHA-1 hash from its | ||
contents. This is shown when you [queue experiments] with `--queue`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From #2690 (comment)
This is actually different from the hash generated after the experiments is committed, so I'm not sure it makes sense to mention it here.
Queued experiment '6518f17' for future execution. | ||
``` | ||
|
||
After running queued experiment, DVC uses the regular name mentioned earlier. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From #2690 (comment)
The experiment name should show in dvc exp show even for queued experiments now.
@@ -1,5 +1,18 @@ | |||
# Experiment Management |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From #2690 (comment)
I guess I'm the reason for this new section? I'm okay with leaving this in Running experiments depending on what others think. It does seem a bit disjointed as is. I think we need to at least link here from Running experiments so it's clear how to see and compare experiments.
For
I have #2737. I think I can also create issues for other items as well. |
Yeah @iesahin I created this one based on #2690 (review) before noticing your Exp Compare ticket. I think it could be included in this guide for now, as comparing them is probably a basic need to manage them. May not even need an explicit section but rather implied throughout this guide. |
@iesahin should we close this and turn it into an issue? |
Done @jorgeorpinel |
Thanks @iesahin ! |
Extracted from #2690 (review)
exp show/compare
)Maybe also include (if natural)