Improvements to hyperopt docs
This commit is contained in:
		| @@ -137,7 +137,7 @@ To avoid naming collisions in the search-space, please prefix all sell-spaces wi | ||||
|  | ||||
| The Strategy class exposes the timeframe value as the `self.timeframe` attribute. | ||||
| The same value is available as class-attribute `HyperoptName.timeframe`. | ||||
| In the case of the linked sample-value this would be `SampleHyperOpt.timeframe`. | ||||
| In the case of the linked sample-value this would be `AwesomeHyperopt.timeframe`. | ||||
|  | ||||
| ## Solving a Mystery | ||||
|  | ||||
| @@ -273,16 +273,15 @@ freqtrade hyperopt --hyperopt <hyperoptname> --strategy <strategyname> --timeran | ||||
| Hyperopt can reuse `populate_indicators`, `populate_buy_trend`, `populate_sell_trend` from your strategy, assuming these methods are **not** in your custom hyperopt file, and a strategy is provided. | ||||
|  | ||||
| ```bash | ||||
| freqtrade hyperopt --hyperopt SampleHyperopt --hyperopt-loss SharpeHyperOptLossDaily --strategy SampleStrategy | ||||
| freqtrade hyperopt --hyperopt AwesomeHyperopt --hyperopt-loss SharpeHyperOptLossDaily --strategy AwesomeStrategy | ||||
| ``` | ||||
|  | ||||
| ### Running Hyperopt with Smaller Search Space | ||||
|  | ||||
| Use the `--spaces` option to limit the search space used by hyperopt. | ||||
| Letting Hyperopt optimize everything is a huuuuge search space. Often it | ||||
| might make more sense to start by just searching for initial buy algorithm. | ||||
| Or maybe you just want to optimize your stoploss or roi table for that awesome | ||||
| new buy strategy you have. | ||||
| Letting Hyperopt optimize everything is a huuuuge search space.  | ||||
| Often it might make more sense to start by just searching for initial buy algorithm. | ||||
| Or maybe you just want to optimize your stoploss or roi table for that awesome new buy strategy you have. | ||||
|  | ||||
| Legal values are: | ||||
|  | ||||
| @@ -427,7 +426,9 @@ These ranges should be sufficient in most cases. The minutes in the steps (ROI d | ||||
|  | ||||
| If you have the `generate_roi_table()` and `roi_space()` methods in your custom hyperopt file, remove them in order to utilize these adaptive ROI tables and the ROI hyperoptimization space generated by Freqtrade by default. | ||||
|  | ||||
| Override the `roi_space()` method if you need components of the ROI tables to vary in other ranges. Override the `generate_roi_table()` and `roi_space()` methods and implement your own custom approach for generation of the ROI tables during hyperoptimization if you need a different structure of the ROI tables or other amount of rows (steps). A sample for these methods can be found in [user_data/hyperopts/sample_hyperopt_advanced.py](https://github.com/freqtrade/freqtrade/blob/develop/freqtrade/templates/sample_hyperopt_advanced.py). | ||||
| Override the `roi_space()` method if you need components of the ROI tables to vary in other ranges. Override the `generate_roi_table()` and `roi_space()` methods and implement your own custom approach for generation of the ROI tables during hyperoptimization if you need a different structure of the ROI tables or other amount of rows (steps).  | ||||
|  | ||||
| A sample for these methods can be found in [sample_hyperopt_advanced.py](https://github.com/freqtrade/freqtrade/blob/develop/freqtrade/templates/sample_hyperopt_advanced.py). | ||||
|  | ||||
| ### Understand Hyperopt Stoploss results | ||||
|  | ||||
|   | ||||
		Reference in New Issue
	
	Block a user