hiro/ray
1
0
Fork 0
mirror of https://github.com/vale981/ray synced 2025-03-06 02:21:39 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

[ci/docs] Fix broken linkcheck URL (#24777)

Browse source 
The hyperband blogpost URL is broken, link to other blog post
This commit is contained in:
Kai Fricke 2022-05-13 15:58:36 +01:00 • committed by GitHub
parent a92ce9721c
commit 06ef672699
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/source/tune/api_docs/schedulers.rst
View file

@ -64,7 +64,7 @@ HyperBand Implementation Details
Implementation details may deviate slightly from theory but are focused on increasing usability.
Note: ``R``, ``s_max``, and ``eta`` are parameters of HyperBand given by the paper.
See `this post <https://homes.cs.washington.edu/~jamieson/hyperband.html>`_ for context.
See `this post <https://blog.ml.cmu.edu/2018/12/12/massively-parallel-hyperparameter-optimization/>`_ for context.
1. Both ``s_max`` (representing the ``number of brackets - 1``) and ``eta``, representing the downsampling rate, are fixed.
In many practical settings, ``R``, which represents some resource unit and often the number of training iterations,
@ -82,7 +82,7 @@ HyperBand configurations that are not very intuitive:
The implementation takes the same configuration as the example given in the paper
and exposes ``max_t``, which is not a parameter in the paper.
2. The example in the `post <https://homes.cs.washington.edu/~jamieson/hyperband.html>`_ to calculate ``n_0``
2. The example in the `post <https://blog.ml.cmu.edu/2018/12/12/massively-parallel-hyperparameter-optimization/>`_ to calculate ``n_0``
is actually a little different than the algorithm given in the paper.
In this implementation, we implement ``n_0`` according to the paper (which is `n` in the below example):

4
python/ray/tune/schedulers/hyperband.py
View file

@ -57,7 +57,7 @@ class HyperBandScheduler(FIFOScheduler):
Note that Tune's stopping criteria will be applied in conjunction with
HyperBand's early stopping mechanisms.
See also: https://homes.cs.washington.edu/~jamieson/hyperband.html
See also: https://blog.ml.cmu.edu/2018/12/12/massively-parallel-hyperparameter-optimization/
Args:
time_attr: The training result attr to use for comparing time.
@ -78,7 +78,7 @@ class HyperBandScheduler(FIFOScheduler):
the difference is between bracket space-time allocation ratios.
stop_last_trials: Whether to terminate the trials after
reaching max_t. Defaults to True.
"""
""" # noqa: E501
_supports_buffered_results = False