-
Notifications
You must be signed in to change notification settings - Fork 976
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
Fix Documentation in FSDP and DeepSpeed Concept Guide #2725
Conversation
@muellerzr the documentation build failed. I think its because now |
To get around this instead of [ |
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.
Thank you for the follow up PR, @fabianlim!
I added a few small suggestions if they resonate.
@stas00 thank you for your suggestions I have integrated them.
@muellerzr I tried this but it seemed I need to fix the I have also added the links for the FSDP and DS docs 3b1948f. Hope they are added in appropriate places. If not please let me know.
|
@fabianlim can you rebase from |
Co-authored-by: Stas Bekman <[email protected]>
@muellerzr just rebased! |
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
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.
Thanks a bunch for all your hard work!
* address part of stats comments * automatically set sync_module_states if low_cpu_mem is set * Apply suggestions from @stas00 Co-authored-by: Stas Bekman <[email protected]> * add links from fsdp and deepspeed docs. fix deepspeed imports * replace raise in accelerate.launch --------- Co-authored-by: Stas Bekman <[email protected]>
What does this PR do?
Address @stas00's comments that was omitted when we merged #2674
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@stas00 @muellerzr