-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
experiments: checkpoints proof of concept #4591
Conversation
78aa2a2
to
9f00578
Compare
9f00578
to
ffc3774
Compare
|
||
EXPERIMENTS_RUN_HELP = ( | ||
"Reproduce complete or partial experiment pipelines." | ||
) | ||
experiments_run_parser = experiments_subparsers.add_parser( |
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.
all experiments run/repro behavior will be moved from dvc repro
to dvc exp run
in a follow-up PR, for now repro -e
is just duplicated here so that checkpoint runs work correctly
(i.e. not yet created)
b509a8d
to
169f5c1
Compare
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.
Great start!
Thank you for the contribution - we'll try to review it as soon as possible. π
Will close #4498.
dvc exp run --checkpoint
can be used to reproduce a checkpoint experiment--always-changed
and with--outs-persist
for the intermediate checkpoint outputsdvc.api.make_checkpoint()
(or generates the appropriate.dvc/tmp/DVC_CHECKPOINT
) signal filedvc exp run --continue <checkpoint_exp_rev>
can be used to resume a prior checkpoint experiment. Execution will be resumed from the tip of the checkpoint branch.dvc exp show
Known issues (needs further investigation after this PR):
repro --params
option)dvc exp show
will not work properly if the table contains checkpoint experiments, but filtering should work as expectedFeatures that will need follow up PR: