-
Notifications
You must be signed in to change notification settings - Fork 16
Docs Content Part 2: Concepts #449
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
base: main
Are you sure you want to change the base?
Conversation
…rehensive getting started with dependency details, and expanded concepts page with Monarch, Services, TorchStore, and RL workflows
Co-authored-by: Svetlana Karslioglu <[email protected]>
Co-authored-by: Svetlana Karslioglu <[email protected]>
Co-authored-by: Svetlana Karslioglu <[email protected]>
Co-authored-by: Svetlana Karslioglu <[email protected]>
Co-authored-by: Svetlana Karslioglu <[email protected]>
Co-authored-by: Svetlana Karslioglu <[email protected]>
- Enhanced homepage with Monarch foundation emphasis, technology stack highlights, validated examples, and clear navigation paths - Expanded getting started with detailed dependency explanations (Monarch, vLLM, TorchTitan, TorchStore, PyTorch Nightly) - Converted installation and verification steps to numbered lists for better readability - Removed FAQ references as FAQ page has been removed - Fixed GPU/process terminology in code examples
- Split long concepts page into: Concepts (overview), Architecture (Monarch/Services/TorchStore), Technology Stack (dependencies), and RL Workflows (writing algorithms) - Added nested toctree under concepts for better navigation in sidebar - Each page focuses on a single aspect with clear cross-references - Improved readability and maintainability of documentation - Fixed GPU/process terminology throughout architecture and workflow examples
Can you fix the warnings: https://github.com/meta-pytorch/forge/actions/runs/18580111434/job/52973145035?pr=449#step:11:109 ? |
**Ephemeral Infrastructure** | ||
: Services are created with your job and torn down when finished. Want to try a new reward model? Change your Python code. No standing deployments to maintain, no infrastructure to provision ahead of time. | ||
|
||
## TorchStore: Distributed Weight Storage |
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 all looks good to me, but cc @LucasLLC in case of any desired big changes
@@ -0,0 +1,120 @@ | |||
# Technology Stack |
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 have this slide I'll use at PTC: https://docs.google.com/presentation/d/1owgUNluoyHoPmhg-cKG9di_SgDVTC7wI/edit?slide=id.g38d9e7ea0be_1_421#slide=id.g38d9e7ea0be_1_421
in case we want to show a visualization here too
I split the docs work into 2 PRs, this is the second.
It builds on #448, so let's merge that first.