-
Notifications
You must be signed in to change notification settings - Fork 406
Closed
Labels
A: docsArea: user documentation (gatsby-theme-iterative)Area: user documentation (gatsby-theme-iterative)C: guideContent of /doc/user-guideContent of /doc/user-guidestatus: staleYou've been groomed!You've been groomed!
Description
As shown in https://github.com/iterative/dvc-checkpoints-mnist under "Switch between scenarios," there are multiple different ways to integrate checkpoints into a project:
- Using dvclive
- Using make_checkpoint
- Using a manually created signal file
- Only including
checkpoints: trueindvc.yamlwithout any in-code checkpoints (but this seems like an unlikely scenario that might be unnecessary or useful just to show the basics of how checkpoints work - see Document checkpoints without make_checkpoint() #2292)
There is already a link in https://dvc.org/doc/user-guide/experiment-management to that example repo. Is this sufficient for now? Should the user guide provide more explanation rather than leave it in the readme of the example repo?
Metadata
Metadata
Assignees
Labels
A: docsArea: user documentation (gatsby-theme-iterative)Area: user documentation (gatsby-theme-iterative)C: guideContent of /doc/user-guideContent of /doc/user-guidestatus: staleYou've been groomed!You've been groomed!