-
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: revisit Checkpoints guide(s?) #2769
Comments
It might be worth adding a mention about how to properly Share Checkpoints with The current content finishes without sharing the checkpoints and the last section Adding checkpoints to git will squash the checkpoint commits making them not usable later. We kind of already have the Sharing Experiments guide but it doesn't mention Checkpoints at all. |
This comment has been minimized.
This comment has been minimized.
As new Checkpoint specific issues appear (#2797) I think it would make more sense to have a dedicated Checkpoints section on each individual Experiment guide (Running, Sharing, etc.), like https://dvc.org/doc/user-guide/experiment-management/running-experiments#checkpoint-experiments . |
I think that's a good idea. |
Would probably need both its own guide and a small Checkpoints section in each Exps guide. |
For the standalone checkpoints guide, I would recommend replacing the This would reduce the number of unrelated details that are in the current guide. |
Should we merge this issue with #2432? |
@daavoo want to repurpose this to include checkpoint charing info for now? Per #2769 (comment) Otherwise this looks stale (see #2432 (comment) and #2568 (comment)) and could be closed (updating the doc in question will be a natural result of updating the core feature anyway). |
Trying to make it broader (more general) yet shorter, and cover all the usage details (extract from cmd ref) in a structured way.
dvc exp push
(here or in the Sharing Exps guide)(See guide: revisit Checkpoints guide(s?) #2769 (comment))
Decide on these:
The text was updated successfully, but these errors were encountered: