Add experiment checkpoints model #1281
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mattseddon
force-pushed
the
add-has-checkpoint
branch
2 times, most recently
from
fcac5d4 to
c863a29
Compare
mattseddon
force-pushed
the
add-has-checkpoint
branch
from
c863a29 to
9f4f65a
Compare
sroy3
approved these changes
Feb 3, 2022
rogermparent
approved these changes
Feb 3, 2022
|
Code Climate has analyzed commit af4466f and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (85% is the threshold). This pull request will bring the total coverage in the repository to 96.4% (0.0% change). View more on Code Climate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1/3
master<- this <- #1282 <- #1284This PR adds a checkpoints model which we will pass
dvc.yamldata in order to determine if the experiments present will have checkpoints or not. We are doing this in order to mitigate the second issue brought up in #1277.