-
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: note that exp run
commits data
#3271
Conversation
other misc edits to Running Exps
`targets` and stage execution (restores the dependency graph, etc.). One | ||
important difference is that changed dependencies are committed to the <abbr>DVC | ||
cache</abbr> when the experiment begins execution, to guarantee the | ||
reproducibility of any recorded experiment. |
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.
One question for this PR's reviewer(s): #2418 was about performance implications. Should this be stressed further here or in the guide?
For now I may just link to
gc
and check whether that ref. mentionsexp gc
(as vice versa).
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.
I think just noting that it is committed is fine
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.
See my comment in #2418 (comment). dvc repro
also commits changed dependencies to the DVC cache, so I don't see a difference here.
I'm having flashbacks to our original discussion about this 😅 . I think this initially came up because dvc exp run
didn't used to commit changed dependencies, but we changed it to behave more like dvc repro
.
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.
this initially came up because dvc exp run didn't used to commit changed dependencies, but we changed it to behave more like dvc repro
Right I just went all the way back to iterative/dvc#5593, iterative/dvc#5859, and #2418 and it seems that's what the change was. So this paragraph about being different to repro
is incorrect... ⌛
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.
OK I updated the changes... PTAL @dberenbaum
I think just noting that it is committed is fine
Yeah that's what I did now. I didn't specifically mention it in the context of queueing, just left generic language that applies to running or queueing ("when preparing the experiment").
84dd0ca
to
7b4b838
Compare
* guide: note that `exp run` commits data and other misc edits to Running Exps * ref: note that `exp run` commits dependencies * ref: udpates to `gc` ref inc. link to `exp gc` * exp run: clarify implicit implications of committing deps per #3271 (review)
and other misc edits to Running Exps, and to the
gc
ref.To close #2418