You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nothing wrong with the current docs, but would be nice to have a list of the options that are "set-able" via .torchxconfig
What should it say?
Add a section that lists out the possible options and section names. Note that some options (e.g. the types of schedulers available and their respective runopts) are different between Meta-internal and OSS. Having a contextual TorchXConfig DAO-like object with placeholders and generating a docs page by dumping that object would make it possible to capture these differences.
Why?
Currently it is not clear what options can/cannot be set via .torchxconfig, we need a glossary of all the available options along with a help string on what they do and default values (if any)
The text was updated successfully, but these errors were encountered:
FWIW this PR adds scheduler runoptions to each scheduler docs page by using SphinxDirective to query the runopts from the schedulers and generating the docs page. #374
📚 Documentation
Note: not a request for correction of documentation!
Link
https://pytorch.org/torchx/latest/experimental/runner.config.html
What does it currently say?
Nothing wrong with the current docs, but would be nice to have a list of the options that are "set-able" via .torchxconfig
What should it say?
Add a section that lists out the possible options and section names. Note that some options (e.g. the types of schedulers available and their respective runopts) are different between Meta-internal and OSS. Having a contextual
TorchXConfig
DAO-like object with placeholders and generating a docs page by dumping that object would make it possible to capture these differences.Why?
Currently it is not clear what options can/cannot be set via .torchxconfig, we need a glossary of all the available options along with a help string on what they do and default values (if any)
The text was updated successfully, but these errors were encountered: