Metadata-Version: 2.1
Name: hydra-ax-sweeper
Version: 1.0.0rc1
Summary: Hydra Ax Sweeper plugin
Home-page: https://github.com/facebookresearch/hydra/
Author: Omry Yadan, Shagun Sodhani
Author-email: omry@fb.com, sshagunsodhani@gmail.com
License: UNKNOWN
Description: # Hydra Ax Sweeper plugin
        This plugin provides a mechanism for Hydra applications to use the [Adaptive Experimentation Platform, aka Ax](https://ax.dev/). Ax can optimize any experiment - machine learning experiments, A/B tests, and simulations. 
        
        Install with:
        
        ```
        pip install hydra_ax_sweeper
        ```
        
        Once installed, override `hydra/sweeper` in your config:
        
        ```yaml
        defaults:
          - hydra/sweeper: ax
        ```
        
        We include an example of how to use this plugin. The file [`example/banana.py`](plugins/hydra_ax/example/banana.py) implements the [Rosenbrock function (aka Banana function)](https://en.wikipedia.org/wiki/Rosenbrock_function). The return value of the function should be the value that we want to optimize.
        
        To compute the best parameters for the Banana function, clone the code and run the following command in the `plugins/hydra_ax_sweeper` directory:
        
        ```
        python example/banana.py -m banana.x=-5:5 banana.y=-5:10.1
        ```
        
        The output of a run looks like:
        
        ```
        [2020-02-09 14:53:07,282][HYDRA] AxSweeper is launching 5 jobs
        [2020-02-09 14:53:07,287][HYDRA] Launching 5 jobs locally
        [2020-02-09 14:53:07,287][HYDRA]    #0 : banana.x=4 banana.y=9.366917353868484
        [2020-02-09 14:53:07,444][__main__][INFO] - Banana_Function(x=4, y=9.366917353868484)=52.997785390411075
        [2020-02-09 14:53:07,447][HYDRA]    #1 : banana.x=3 banana.y=4.2380884230136875
        [2020-02-09 14:53:07,590][__main__][INFO] - Banana_Function(x=3, y=4.2380884230136875)=26.67580186703627
        [2020-02-09 14:53:07,592][HYDRA]    #2 : banana.x=2 banana.y=2.807121509313583
        [2020-02-09 14:53:07,736][__main__][INFO] - Banana_Function(x=2, y=2.807121509313583)=2.4229590935423047
        [2020-02-09 14:53:07,738][HYDRA]    #3 : banana.x=1 banana.y=1.6320534139871592
        [2020-02-09 14:53:07,886][__main__][INFO] - Banana_Function(x=1, y=1.6320534139871592)=0.39949151813282324
        [2020-02-09 14:53:07,888][HYDRA]    #4 : banana.x=2 banana.y=-1.5182482689619063
        [2020-02-09 14:53:08,039][__main__][INFO] - Banana_Function(x=2, y=-1.5182482689619063)=31.45106395790108
        [2020-02-09 14:53:08,112][HYDRA] New best value: 0.39949151813282324, best parameters: {'banana.x': 1, 'banana.y': 1.6320534139871592}
        ```
        
        In this example, we set the range of `x` parameter as an integer in `[-5, 5]` and the range of `y` parameter as a float in `[-5, 10.1]`. Note that in the case of `x`, both the upper and the lower range values are integers, and hence only integers are sampled. In the case of `y`, the lower range value is an int while the upper range value is a float. The lower range value is promoted to float as well, and floating-point numbers are sampled from the range. Other supported formats are fixed parameters (eg `banana.x=5.0`) and choice parameters (eg `banana.x=1,2,3`). 
        
        The values of the `x` and `y` parameters can also be set using the config file `plugins/hydra_ax_sweeper/example/conf/config.yaml`. For instance, the configuration corresponding to the parameter `x` is as follows:
        
        ```
        banana.x:
         type: range
         bounds: [-5, 5]
        
        banana.y:
         type: range
         bounds: [-5, 10.1]
        ```
        
        The `x` parameter takes on a "range" of integer values, between `-5` to `5`. The `y` parameter takes on a range of floating-point values between `-5` to `10.1`. In general, the plugin supports all the [Parameters](https://ax.dev/api/core.html?highlight=range#module-ax.core.parameter) that Ax supports. According to the [Ax documentation](https://ax.dev/api/service.html#ax.service.ax_client.AxClient.create_experiment), the required elements in the config are:
        
        * `name` - Name of the parameter. It is of type string.
        * `type` - Type of the parameter. It can take the following values: `range`, `fixed`, or `choice`.
        * `bounds` - Required only for the `range` parameters. It should be a list of two values, with the lower bound first.
        * `values` - Required only for the `choice` parameters. It should be a list of values.
        * `value` - Required only for the `fixed` parameters. It should be a single value. 
        
        Note that when using the config file, the parameter type (int, float, string, etc.) is set via the [`parameter_type` attribute](https://ax.dev/api/core.html?highlight=range#module-ax.core.parameter). One important thing to note is how mixed types (float + int) are handled. For `y` parameter, the range bounds were set to be `-5` to `10.1`. Both the values were upcasted to a float (irrespective of whether the range was set via the command line or the config file). In case the user provides the `parameter_type` attribute in the config, the attribute is not changed when type casting is done. If the user wants to sample integers in range `-5` to `5`, they need to specify the range as `-5:5` or `[-5, 5]` (in config). If they want to sample floats in range `-5` to `5`, they need to specify the range as `-5.0:5.0` or `[-5.0, 5.0]` (in config). The type casted values, and unchanged attributes are passed to the Ax Client. 
        
        The parameters for the optimization process can also be set in the config file. Specifying the Ax config is optional. The most important parameters are listed below:
        
        ```
        ax_config:
            experiment:
              # Defaults to minimize, set to false to maximize
              minimize: true
        
            early_stop:
              # Number of epochs without a significant improvement from
              # the currently known best parameters
              # An Epoch is defined as a batch of trials executed in parallel
              max_epochs_without_improvement: 100
        
              # An improvement larger than epsilon is considered significant
              epsilon: 0.00001
        ```
Platform: UNKNOWN
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Operating System :: POSIX :: Linux
Description-Content-Type: text/markdown
