-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[Tune][Doc] Restructure API reference #32311
Changes from 11 commits
f72240c
4c54757
d08c28f
a740de3
0e37dfb
994b554
0a30fe5
d686153
f8ea993
1d1e9a3
745654d
82b88f6
93503c8
223964f
d5fb516
4d6ee1d
7d095f9
4dabaf0
930e2f2
4892f93
8c69afd
79c2cca
eb3bf64
032e7b4
aaffb05
31ece63
cfb0cf3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -282,7 +282,7 @@ parts: | |
- file: tune/examples/exercises | ||
title: "Exercises" | ||
- file: tune/faq | ||
- file: tune/api_docs/overview.rst | ||
- file: tune/api/api.rst | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Just checking, are you keeping There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yep, for Tune Internals, I wasn't sure how to list out all members/methods with their docstrings if I used autosummary. And since that section is not really meant for external users to search for and use as API calls, I decided to leave it fully expanded. For Tune Client, there was only 1 class, and I think it is fine as is. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ack, though we should probably move I think it would make sense to move
Thoughts? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Moved Callback + PGF to better places. |
||
|
||
- file: serve/index | ||
title: Ray Serve | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
Tune Execution (Tuner) | ||
====================== | ||
|
||
.. _tune-run-ref: | ||
|
||
Tuner | ||
----- | ||
|
||
.. currentmodule:: ray.tune | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
Tuner | ||
Tuner.fit | ||
|
||
Tuner Configuration | ||
~~~~~~~~~~~~~~~~~~~ | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
TuneConfig | ||
|
||
Restoring a Tuner | ||
~~~~~~~~~~~~~~~~~ | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
Tuner.restore | ||
Tuner.can_restore | ||
Tuner.get_results | ||
justinvyu marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
|
||
tune.run_experiments | ||
-------------------- | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
run_experiments | ||
Experiment |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,105 @@ | ||
.. _tune-integration: | ||
|
||
External library integrations for Ray Tune (tune.integration) | ||
============================================================= | ||
|
||
.. currentmodule:: ray | ||
|
||
Comet (tune.integration.comet) | ||
------------------------------------------- | ||
|
||
:ref:`See here for an example. <tune-comet-ref>` | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
air.integrations.comet.CometLoggerCallback | ||
:noindex: | ||
|
||
.. _tune-integration-keras: | ||
|
||
Keras (tune.integration.keras) | ||
------------------------------------------------------ | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
tune.integration.keras.TuneReportCallback | ||
tune.integration.keras.TuneReportCheckpointCallback | ||
|
||
|
||
.. _tune-integration-mlflow: | ||
|
||
MLflow (tune.integration.mlflow) | ||
-------------------------------- | ||
|
||
:ref:`See here for an example. <tune-mlflow-ref>` | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
air.integrations.mlflow.MLflowLoggerCallback | ||
:noindex: | ||
air.integrations.mlflow.setup_mlflow | ||
|
||
|
||
.. _tune-integration-mxnet: | ||
|
||
MXNet (tune.integration.mxnet) | ||
------------------------------ | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
tune.integration.mxnet.TuneReportCallback | ||
tune.integration.mxnet.TuneCheckpointCallback | ||
|
||
|
||
.. _tune-integration-pytorch-lightning: | ||
|
||
PyTorch Lightning (tune.integration.pytorch_lightning) | ||
------------------------------------------------------ | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
tune.integration.pytorch_lightning.TuneReportCallback | ||
tune.integration.pytorch_lightning.TuneReportCheckpointCallback | ||
|
||
.. _tune-integration-wandb: | ||
|
||
Weights and Biases (tune.integration.wandb) | ||
------------------------------------------- | ||
|
||
:ref:`See here for an example. <tune-wandb-ref>` | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
air.integrations.wandb.WandbLoggerCallback | ||
:noindex: | ||
air.integrations.wandb.setup_wandb | ||
|
||
|
||
.. _tune-integration-xgboost: | ||
|
||
XGBoost (tune.integration.xgboost) | ||
---------------------------------- | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
tune.integration.xgboost.TuneReportCallback | ||
tune.integration.xgboost.TuneReportCheckpointCallback | ||
|
||
|
||
.. _tune-integration-lightgbm: | ||
|
||
LightGBM (tune.integration.lightgbm) | ||
------------------------------------ | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
tune.integration.lightgbm.TuneReportCallback | ||
tune.integration.lightgbm.TuneReportCheckpointCallback |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
.. _tune-analysis-docs: | ||
|
||
.. _result-grid-docstring: | ||
|
||
ResultGrid (tune.ResultGrid) | ||
============================ | ||
|
||
.. currentmodule:: ray | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
tune.ResultGrid | ||
tune.ResultGrid.get_best_result | ||
tune.ResultGrid.get_dataframe | ||
|
||
.. _result-docstring: | ||
|
||
Result (air.Result) | ||
------------------- | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
air.Result | ||
|
||
.. _exp-analysis-docstring: | ||
|
||
ExperimentAnalysis (tune.ExperimentAnalysis) | ||
-------------------------------------------- | ||
|
||
.. note:: | ||
|
||
An experiment analysis is the output of the ``tune.run`` API. | ||
It's now recommended to use ``Tuner.fit``, which outputs a ``ResultGrid`` object. | ||
|
||
.. autosummary:: | ||
:toctree: doc/ | ||
|
||
tune.ExperimentAnalysis |
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.
Can these be combined somehow? Special case for the newly added cluster autogenerated files.
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.
@c21 should we conform to one structure? Though it does mess with backwards compatibility for this job submission page.
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.
Yes I think we should conform to one structure (non-blocking for this PR). Let me take a look how easy the change is.
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 was also a discussion about whether we should do
reference/api
orapi/doc
as the standard.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.
Also looks like I can use
/doc/source/**/doc
as wildcard for nested dirs.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.
Talked to @jjyao separately. We can use
api/doc
here. To rename toreference/api
, we plan to have a separate discussion.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.
just keep in mind that
api
leads to shorter URLs, too. but consistency is more important