update tuner doc (#4333)

docs/en_US/Tuner/BatchTuner.rst

 Batch Tuner on NNI
 ==================
 
-Batch Tuner
------------
+1. Introduction
+---------------
 
 Batch tuner allows users to simply provide several configurations (i.e., choices of hyper-parameters) for their trial code. After finishing all the configurations, the experiment is done. Batch tuner only supports the type ``choice`` in the `search space spec <../Tutorial/SearchSpaceSpec.rst>`__.
 
 Suggested scenario: If the configurations you want to try have been decided, you can list them in the SearchSpace file (using ``choice``\ ) and run them using the batch tuner.
+
+2. Usage
+--------
+
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: BatchTuner
+
+:raw-html:`<br>`
+
+Note that the search space for BatchTuner should look like:
+
+.. code-block:: json
+
+   {
+       "combine_params":
+       {
+           "_type" : "choice",
+           "_value" : [{"optimizer": "Adam", "learning_rate": 0.00001},
+                       {"optimizer": "Adam", "learning_rate": 0.0001},
+                       {"optimizer": "Adam", "learning_rate": 0.001},
+                       {"optimizer": "SGD", "learning_rate": 0.01},
+                       {"optimizer": "SGD", "learning_rate": 0.005},
+                       {"optimizer": "SGD", "learning_rate": 0.0002}]
+       }
+   }
+
+The search space file should include the high-level key ``combine_params``. The type of params in the search space must be ``choice`` and the ``values`` must include all the combined params values.
\ No newline at end of file

docs/en_US/Tuner/BohbAdvisor.rst

@@ -69,12 +69,35 @@ The sampling procedure (using Multidimensional KDE to guide selection) is summar
 3. Usage
 --------
 
+Installation
+^^^^^^^^^^^^
+
 BOHB advisor requires the `ConfigSpace <https://github.com/automl/ConfigSpace>`__ package. ConfigSpace can be installed using the following command.
 
 .. code-block:: bash
 
    pip install nni[BOHB]
 
+classArgs Requirements
+^^^^^^^^^^^^^^^^^^^^^^
+
+* **optimize_mode** (*maximize or minimize, optional, default = maximize*\ ) - If 'maximize', tuners will try to maximize metrics. If 'minimize', tuner will try to minimize metrics.
+* **min_budget** (*int, optional, default = 1*\ ) - The smallest budget to assign to a trial job, (budget can be the number of mini-batches or epochs). Needs to be positive.
+* **max_budget** (*int, optional, default = 3*\ ) - The largest budget to assign to a trial job, (budget can be the number of mini-batches or epochs). Needs to be larger than min_budget.
+* **eta** (*int, optional, default = 3*\ ) - In each iteration, a complete run of sequential halving is executed. In it, after evaluating each configuration on the same subset size, only a fraction of 1/eta of them 'advances' to the next round. Must be greater or equal to 2.
+* **min_points_in_model**\ (*int, optional, default = None*\ ): number of observations to start building a KDE. Default 'None' means dim+1; when the number of completed trials in this budget is equal to or larger than ``max{dim+1, min_points_in_model}``\ , BOHB will start to build a KDE model of this budget then use said KDE model to guide configuration selection. Needs to be positive. (dim means the number of hyperparameters in search space)
+* **top_n_percent**\ (*int, optional, default = 15*\ ): percentage (between 1 and 99) of the observations which are considered good. Good points and bad points are used for building KDE models. For example, if you have 100 observed trials and top_n_percent is 15, then the top 15% of points will be used for building the good points models "l(x)". The remaining 85% of points will be used for building the bad point models "g(x)".
+* **num_samples**\ (*int, optional, default = 64*\ ): number of samples to optimize EI (default 64). In this case, we will sample "num_samples" points and compare the result of l(x)/g(x). Then we will return the one with the maximum l(x)/g(x) value as the next configuration if the optimize_mode is ``maximize``. Otherwise, we return the smallest one.
+* **random_fraction**\ (*float, optional, default = 0.33*\ ): fraction of purely random configurations that are sampled from the prior without the model.
+* **bandwidth_factor**\ (*float, optional, default = 3.0*\ ): to encourage diversity, the points proposed to optimize EI are sampled from a 'widened' KDE where the bandwidth is multiplied by this factor. We suggest using the default value if you are not familiar with KDE.
+* **min_bandwidth**\ (*float, optional, default = 0.001*\ ): to keep diversity, even when all (good) samples have the same value for one of the parameters, a minimum bandwidth (default: 1e-3) is used instead of zero. We suggest using the default value if you are not familiar with KDE.
+
+*Please note that the float type currently only supports decimal representations. You have to use 0.333 instead of 1/3 and 0.001 instead of 1e-3.*
+
+
+Config File
+^^^^^^^^^^^
+
 To use BOHB, you should add the following spec in your experiment's YAML config file:
 
 .. code-block:: yaml

docs/en_US/Tuner/DngoTuner.rst

+DNGO on NNI
+===========
+
+1. Introduction
+---------------
+
+2. Usage
+--------
+
+Installation
+^^^^^^^^^^^^
+
+classArgs requirements
+^^^^^^^^^^^^^^^^^^^^^^
+
+* **optimize_mode** (*'maximize' or 'minimize'*\ ) - If 'maximize', the tuner will target to maximize metrics. If 'minimize', the tuner will target to minimize metrics.
+* **sample_size** (*int, default = 1000*) - Number of samples to select in each iteration. The best one will be picked from the samples as the next trial.
+* **trials_per_update** (*int, default = 20*) - Number of trials to collect before updating the model.
+* **num_epochs_per_training** (*int, default = 500*) - Number of epochs to train DNGO model.
+
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: DNGOTuner
+     classArgs:
+       optimize_mode: maximize
\ No newline at end of file

docs/en_US/Tuner/EvolutionTuner.rst

 Naive Evolution Tuners on NNI
 =============================
 
-Naive Evolution
+
+1. Introduction
 ---------------
 
 Naive Evolution comes from `Large-Scale Evolution of Image Classifiers <https://arxiv.org/pdf/1703.01041.pdf>`__. It randomly initializes a population based on the search space. For each generation, it chooses better ones and does some mutation (e.g., changes a hyperparameter, adds/removes one layer, etc.) on them to get the next generation. Naive Evolution requires many trials to works but it's very simple and it's easily expanded with new features.
+
+2. Usage
+--------
+
+classArgs Requirements
+^^^^^^^^^^^^^^^^^^^^^^
+
+* 
+  **optimize_mode** (*maximize or minimize, optional, default = maximize*\ ) - If 'maximize', the tuner will try to maximize metrics. If 'minimize', the tuner will try to minimize metrics.
+
+* 
+  **population_size** (*int value (should > 0), optional, default = 20*\ ) - the initial size of the population (trial num) in the evolution tuner. It's suggested that ``population_size`` be much larger than ``concurrency`` so users can get the most out of the algorithm (and at least ``concurrency``\ , or the tuner will fail on its first generation of parameters).
+
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: Evolution
+     classArgs:
+       optimize_mode: maximize
+       population_size: 100
+

docs/en_US/Tuner/GPTuner.rst

 GP Tuner on NNI
 ===============
 
-GP Tuner
---------
+1. Introduction
+---------------
 
 Bayesian optimization works by constructing a posterior distribution of functions (a Gaussian Process) that best describes the function you want to optimize. As the number of observations grows, the posterior distribution improves, and the algorithm becomes more certain of which regions in parameter space are worth exploring and which are not.
 
@@ -11,3 +11,38 @@ GP Tuner is designed to minimize/maximize the number of steps required to find a
 Note that the only acceptable types within the search space are ``randint``\ , ``uniform``\ , ``quniform``\ ,  ``loguniform``\ , ``qloguniform``\ , and numerical ``choice``.
 
 This optimization approach is described in Section 3 of `Algorithms for Hyper-Parameter Optimization <https://papers.nips.cc/paper/4443-algorithms-for-hyper-parameter-optimization.pdf>`__.
+
+2. Usage
+--------
+
+classArgs requirements
+^^^^^^^^^^^^^^^^^^^^^^
+
+* **optimize_mode** (*'maximize' or 'minimize', optional, default = 'maximize'*\ ) - If 'maximize', the tuner will try to maximize metrics. If 'minimize', the tuner will try to minimize metrics.
+* **utility** (*'ei', 'ucb' or 'poi', optional, default = 'ei'*\ ) - The utility function (acquisition function). 'ei', 'ucb', and 'poi' correspond to 'Expected Improvement', 'Upper Confidence Bound', and 'Probability of Improvement', respectively.
+* **kappa** (*float, optional, default = 5*\ ) - Used by the 'ucb' utility function. The bigger ``kappa`` is, the more exploratory the tuner will be.
+* **xi** (*float, optional, default = 0*\ ) - Used by the 'ei' and 'poi' utility functions. The bigger ``xi`` is, the more exploratory the tuner will be.
+* **nu** (*float, optional, default = 2.5*\ ) - Used to specify the Matern kernel. The smaller nu, the less smooth the approximated function is.
+* **alpha** (*float, optional, default = 1e-6*\ ) - Used to specify the Gaussian Process Regressor. Larger values correspond to an increased noise level in the observations.
+* **cold_start_num** (*int, optional, default = 10*\ ) - Number of random explorations to perform before the Gaussian Process. Random exploration can help by diversifying the exploration space.
+* **selection_num_warm_up** (*int, optional, default = 1e5*\ ) - Number of random points to evaluate when getting the point which maximizes the acquisition function.
+* **selection_num_starting_points** (*int, optional, default = 250*\ ) - Number of times to run L-BFGS-B from a random starting point after the warmup.
+
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: GPTuner
+     classArgs:
+       optimize_mode: maximize
+       utility: 'ei'
+       kappa: 5.0
+       xi: 0.0
+       nu: 2.5
+       alpha: 1e-6
+       cold_start_num: 10
+       selection_num_warm_up: 100000
+       selection_num_starting_points: 250
\ No newline at end of file

docs/en_US/Tuner/GridsearchTuner.rst

@@ -4,6 +4,21 @@ Grid Search on NNI
 Grid Search
 -----------
 
+1. Introduction
+---------------
+
 Grid Search performs an exhaustive search through a manually specified subset of the hyperparameter space defined in the searchspace file. 
 
 Note that the only acceptable types within the search space are ``choice``\ , ``quniform``\ , and ``randint``.
+
+2. Usage
+--------
+
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: GridSearch
\ No newline at end of file

docs/en_US/Tuner/HyperbandAdvisor.rst

@@ -34,6 +34,9 @@ If you want to reproduce these results, refer to the example under ``examples/tr
 3. Usage
 --------
 
+Config file
+^^^^^^^^^^^
+
 To use Hyperband, you should add the following spec in your experiment's YAML config file:
 
 .. code-block:: bash
@@ -113,6 +116,28 @@ Here is a concrete example of ``R=81`` and ``eta=3``\ :
 
 For information about writing trial code, please refer to the instructions under ``examples/trials/mnist-hyperband/``.
 
+classArgs requirements
+^^^^^^^^^^^^^^^^^^^^^^
+
+
+* **optimize_mode** (*maximize or minimize, optional, default = maximize*\ ) - If 'maximize', the tuner will try to maximize metrics. If 'minimize', the tuner will try to minimize metrics.
+* **R** (*int, optional, default = 60*\ ) - the maximum budget given to a trial (could be the number of mini-batches or epochs). Each trial should use TRIAL_BUDGET to control how long they run.
+* **eta** (*int, optional, default = 3*\ ) - ``(eta-1)/eta`` is the proportion of discarded trials.
+* **exec_mode** (*serial or parallelism, optional, default = parallelism*\ ) - If 'parallelism', the tuner will try to use available resources to start new bucket immediately. If 'serial', the tuner will only start new bucket after the current bucket is done.
+
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   advisor:
+     builtinAdvisorName: Hyperband
+     classArgs:
+       optimize_mode: maximize
+       R: 60
+       eta: 3
+
 4. Future improvements
 ----------------------
 

docs/en_US/Tuner/HyperoptTuner.rst

@@ -4,6 +4,9 @@ TPE, Random Search, Anneal Tuners on NNI
 TPE
 ---
 
+1. Introduction
+---------------
+
 The Tree-structured Parzen Estimator (TPE) is a sequential model-based optimization (SMBO) approach. SMBO methods sequentially construct models to approximate the performance of hyperparameters based on historical measurements, and then subsequently choose new hyperparameters to test based on this model. The TPE approach models P(x|y) and P(y) where x represents hyperparameters and y the associated evaluation matric. P(x|y) is modeled by transforming the generative process of hyperparameters, replacing the distributions of the configuration prior with non-parametric densities. This optimization approach is described in detail in `Algorithms for Hyper-Parameter Optimization <https://papers.nips.cc/paper/4443-algorithms-for-hyper-parameter-optimization.pdf>`__. ​
 
 Parallel TPE optimization
@@ -11,8 +14,8 @@ Parallel TPE optimization
 
 TPE approaches were actually run asynchronously in order to make use of multiple compute nodes and to avoid wasting time waiting for trial evaluations to complete. The original algorithm design was optimized for sequential computation. If we were to use TPE with much concurrency, its performance will be bad. We have optimized this case using the Constant Liar algorithm. For these principles of optimization, please refer to our `research blog <../CommunitySharings/ParallelizingTpeSearch.rst>`__.
 
-Usage
-^^^^^
+2. Usage
+--------
 
  To use TPE, you should add the following spec in your experiment's YAML config file:
 
@@ -25,19 +28,70 @@ Usage
        parallel_optimize: True
        constant_liar_type: min
 
-**classArgs requirements:**
-
+classArgs requirements
+^^^^^^^^^^^^^^^^^^^^^^
 
 * **optimize_mode** (*maximize or minimize, optional, default = maximize*\ ) - If 'maximize', tuners will try to maximize metrics. If 'minimize', tuner will try to minimize metrics.
+
 * **parallel_optimize** (*bool, optional, default = False*\ ) - If True, TPE will use the Constant Liar algorithm to optimize parallel hyperparameter tuning. Otherwise, TPE will not discriminate between sequential or parallel situations.
+
 * **constant_liar_type** (*min or max or mean, optional, default = min*\ ) - The type of constant liar to use, will logically be determined on the basis of the values taken by y at X. There are three possible values, min{Y}, max{Y}, and mean{Y}.
 
-Random Search
--------------
+Note: We have optimized the parallelism of TPE for large-scale trial concurrency. For the principle of optimization or turn-on optimization, please refer to `TPE document <./HyperoptTuner.rst>`__.
+
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: TPE
+     classArgs:
+       optimize_mode: maximize
+
+RandomSearch
+------------
+
+1. Introduction
+---------------
 
 In `Random Search for Hyper-Parameter Optimization <http://www.jmlr.org/papers/volume13/bergstra12a/bergstra12a.pdf>`__ we show that Random Search might be surprisingly effective despite its simplicity. We suggest using Random Search as a baseline when no knowledge about the prior distribution of hyper-parameters is available.
 
-Anneal
-------
+2. Usage
+--------
+
+Example Configuration
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: Random
+
+Anneal on NNI
+-------------
+
+1. Introduction
+---------------
 
 This simple annealing algorithm begins by sampling from the prior but tends over time to sample from points closer and closer to the best ones observed. This algorithm is a simple variation on random search that leverages smoothness in the response surface. The annealing rate is not adaptive.
+
+2. Usage
+--------
+
+classArgs Requirements
+^^^^^^^^^^^^^^^^^^^^^^
+
+* **optimize_mode** (*maximize or minimize, optional, default = maximize*\ ) - If 'maximize', the tuner will try to maximize metrics. If 'minimize', the tuner will try to minimize metrics.
+
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: Anneal
+     classArgs:
+       optimize_mode: maximize
\ No newline at end of file

docs/en_US/Tuner/MetisTuner.rst

 Metis Tuner on NNI
 ==================
 
-Metis Tuner
------------
+1. Introduction
+---------------
 
 `Metis <https://www.microsoft.com/en-us/research/publication/metis-robustly-tuning-tail-latencies-cloud-systems/>`__ offers several benefits over other tuning algorithms. While most tools only predict the optimal configuration, Metis gives you two outputs, a prediction for the optimal configuration and a suggestion for the next trial. No more guess work!
 
@@ -22,3 +22,22 @@ Metis belongs to the class of sequential model-based optimization (SMBO) algorit
 Note that the only acceptable types within the search space are ``quniform``\ , ``uniform``\ , ``randint``\ , and numerical ``choice``.
 
 More details can be found in our `paper <https://www.microsoft.com/en-us/research/publication/metis-robustly-tuning-tail-latencies-cloud-systems/>`__.
+
+2. Usage
+--------
+
+classArgs requirements
+^^^^^^^^^^^^^^^^^^^^^^
+
+* **optimize_mode** (*'maximize' or 'minimize', optional, default = 'maximize'*\ ) - If 'maximize', the tuner will try to maximize metrics. If 'minimize', the tuner will try to minimize metrics.
+
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: MetisTuner
+     classArgs:
+       optimize_mode: maximize
\ No newline at end of file

docs/en_US/Tuner/NetworkmorphismTuner.rst

@@ -11,6 +11,25 @@ If you want to know more about network morphism trial usage, please see the :git
 2. Usage
 --------
 
+Installation
+^^^^^^^^^^^^
+
+NetworkMorphism requires :githublink:`PyTorch <examples/trials/network_morphism/requirements.txt>`.
+
+classArgs Requirements
+^^^^^^^^^^^^^^^^^^^^^^
+
+* **optimize_mode** (*maximize or minimize, optional, default = maximize*\ ) - If 'maximize', the tuner will try to maximize metrics. If 'minimize', the tuner will try to minimize metrics.
+* **task** (*('cv'), optional, default = 'cv'*\ ) - The domain of the experiment. For now, this tuner only supports the computer vision (CV) domain.
+* **input_width** (*int, optional, default = 32*\ ) - input image width
+* **input_channel** (*int, optional, default = 3*\ ) - input image channel
+* **n_output_node** (*int, optional, default = 10*\ ) - number of classes
+
+
+
+Config File
+^^^^^^^^^^^
+
 To use Network Morphism, you should modify the following spec in your ``config.yml`` file:
 
 .. code-block:: yaml
@@ -30,6 +49,21 @@ To use Network Morphism, you should modify the following spec in your ``config.y
        #modify to fit your number of classes
        n_output_node: 10
 
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: NetworkMorphism
+       classArgs:
+         optimize_mode: maximize
+         task: cv
+         input_width: 32
+         input_channel: 3
+         n_output_node: 10
+
 In the training procedure, it generates a JSON file which represents a Network Graph. Users can call the "json_to_graph()" function to build a PyTorch or Keras model from this JSON file.
 
 .. code-block:: python

docs/en_US/Tuner/PBTTuner.rst

 PBT Tuner on NNI
 ================
 
-PBTTuner
---------
+1. Introduction
+---------------
+
 
 Population Based Training (PBT) comes from `Population Based Training of Neural Networks <https://arxiv.org/abs/1711.09846v1>`__. It's a simple asynchronous optimization algorithm which effectively utilizes a fixed computational budget to jointly optimize a population of models and their hyperparameters to maximize performance. Importantly, PBT discovers a schedule of hyperparameter settings rather than following the generally sub-optimal strategy of trying to find a single fixed set to use for the whole course of training. 
 
@@ -14,6 +15,9 @@ Population Based Training (PBT) comes from `Population Based Training of Neural
 
 PBTTuner initializes a population with several trials (i.e., ``population_size``\ ). There are four steps in the above figure, each trial only runs by one step. How long is one step is controlled by trial code, e.g., one epoch. When a trial starts, it loads a checkpoint specified by PBTTuner and continues to run one step, then saves checkpoint to a directory specified by PBTTuner and exits. The trials in a population run steps synchronously, that is, after all the trials finish the ``i``\ -th step, the ``(i+1)``\ -th step can be started. Exploitation and exploration of PBT are executed between two consecutive steps.
 
+2. Usage
+--------
+
 Provide checkpoint directory
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -40,6 +44,15 @@ Before running a step, a trial needs to load a checkpoint, the checkpoint direct
 
 The complete example code can be found :githublink:`here <examples/trials/mnist-pbt-tuner-pytorch>`.
 
+classArgs requirements
+^^^^^^^^^^^^^^^^^^^^^^
+
+* **optimize_mode** (*'maximize' or 'minimize'*\ ) - If 'maximize', the tuner will target to maximize metrics. If 'minimize', the tuner will target to minimize metrics.
+* **all_checkpoint_dir** (*str, optional, default = None*\ ) - Directory for trials to load and save checkpoint, if not specified, the directory would be "~/nni/checkpoint/\ :raw-html:`<exp-id>`\ ". Note that if the experiment is not local mode, users should provide a path in a shared storage which can be accessed by all the trials.
+* **population_size** (*int, optional, default = 10*\ ) - Number of trials in a population. Each step has this number of trials. In our implementation, one step is running each trial by specific training epochs set by users.
+* **factors** (*tuple, optional, default = (1.2, 0.8)*\ ) - Factors for perturbation of hyperparameters.
+* **fraction** (*float, optional, default = 0.2*\ ) - Fraction for selecting bottom and top trials.
+
 Experiment config
 ^^^^^^^^^^^^^^^^^
 
@@ -54,3 +67,14 @@ Below is an exmaple of PBTTuner configuration in experiment config file. **Note
        optimize_mode: maximize
        all_checkpoint_dir: /the/path/to/store/checkpoints
        population_size: 10
+
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: PBTTuner
+     classArgs:
+       optimize_mode: maximize
\ No newline at end of file

docs/en_US/Tuner/SmacTuner.rst

 SMAC Tuner on NNI
 =================
 
-SMAC
-----
+
+1. Introduction
+---------------
 
 `SMAC <https://www.cs.ubc.ca/~hutter/papers/10-TR-SMAC.pdf>`__ is based on Sequential Model-Based Optimization (SMBO). It adapts the most prominent previously used model class (Gaussian stochastic process models) and introduces the model class of random forests to SMBO in order to handle categorical parameters. The SMAC supported by nni is a wrapper on `the SMAC3 github repo <https://github.com/automl/SMAC3>`__.
 
 Note that SMAC on nni only supports a subset of the types in the `search space spec <../Tutorial/SearchSpaceSpec.rst>`__\ : ``choice``\ , ``randint``\ , ``uniform``\ , ``loguniform``\ , and ``quniform``.
+
+
+2. Usage
+--------
+
+Installation
+^^^^^^^^^^^^
+
+SMAC has dependencies that need to be installed by following command before the first usage. As a reminder, ``swig`` is required for SMAC: for Ubuntu ``swig`` can be installed with ``apt``.
+
+.. code-block:: bash
+
+   pip install nni[SMAC]
+
+classArgs requirements
+^^^^^^^^^^^^^^^^^^^^^^
+
+* **optimize_mode** (*maximize or minimize, optional, default = maximize*\ ) - If 'maximize', the tuner will try to maximize metrics. If 'minimize', the tuner will try to minimize metrics.
+* **config_dedup** (*True or False, optional, default = False*\ ) - If True, the tuner will not generate a configuration that has been already generated. If False, a configuration may be generated twice, but it is rare for a relatively large search space.
+
+Example Configuration
+^^^^^^^^^^^^^^^^^^^^^
+
+.. code-block:: yaml
+
+   # config.yml
+   tuner:
+     builtinTunerName: SMAC
+     classArgs:
+       optimize_mode: maximize
\ No newline at end of file

docs/en_US/builtin_tuner.rst

@@ -21,3 +21,4 @@ Tuner receives metrics from `Trial` to evaluate the performance of a specific pa
     Hyperband <Tuner/HyperbandAdvisor>
     BOHB <Tuner/BohbAdvisor>
     PBT Tuner <Tuner/PBTTuner>
+    DNGO Tuner <Tuner/DngoTuner>