-
Notifications
You must be signed in to change notification settings - Fork 6k
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
[doc] Add documentation around trial/experiment checkpoint. #28303
Conversation
As this has been a continuous confustion for both OSS and product. Signed-off-by: xwjiang2010 <xwjiang2010@gmail.com>
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.
Looks good, thanks! One nit
Signed-off-by: xwjiang2010 <xwjiang2010@gmail.com>
Signed-off-by: xwjiang2010 <xwjiang2010@gmail.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
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.
Updated with wording, please someone else also take a look after my changes!
can be resumed from if it is interrupted or failed. | ||
It can also be used to analysis tuning results after a Ray Tune finished. | ||
|
||
Trial-level checkpoints capture the per-trial state. They are saved by the trainable itself. |
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.
Should we mention anything about syncing to the driver here?
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.
There is a big section "Checkpointing and synchronization" right below this section, so I think it should be fine.
Co-authored-by: Amog Kamsetty <amogkam@users.noreply.github.com> Signed-off-by: Kai Fricke <krfricke@users.noreply.github.com>
As this has been a continuous confustion for both OSS and product.
Signed-off-by: xwjiang2010 xwjiang2010@gmail.com
Why are these changes needed?
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.