-
Notifications
You must be signed in to change notification settings - Fork 387
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
user-guide: add "folders" way of experimentation #159
Comments
I think we should keep a single way in get started, mention other ways in user-guide and make a link to it. I'm switching get started to use tags now to avoid merging and other complicated ugly stuff. |
Maybe we can make a use-case for this. Context:
This may also be related: #72 |
👍 @dashohoxha it can be a more general |
Related: iterative/dvc#2324 |
The last step of this lesson mentions something about using different folders for different pipelines: |
@dashohoxha Feels like it would be suitable to describe that more formally, hence why I was mentioning "user guide" and not "get-started" or "tutorial". |
@efiop Right. But some things are better explained with a working example. It may also be easier for the users to understand it. And an example can also be complemented by formal and generalized descriptions. |
I reviewed all docs and he term "experiment" is not mentioned in the User Guide at all, and only once in Use Cases (in Shared Development Server). Otherwise we mainly talk about experiments in command references and tutorials. So it seems this new Managing Experiments is still a valid enhancement. Please note we should use the term "directory" instead of "folder" though. |
@jorgeorpinel are you working on it? |
I'm not. I was just reviewing the validity of some older issues. |
Closing in favor of #816 |
Currently, we only mention branches as a way of experimentation (in Get Started), but it is not ideal and we've seen users use folders as an alternative. Need to mention it in our docs.
The text was updated successfully, but these errors were encountered: