split example notebooks

.gitignore

@@ -6,7 +6,10 @@ config*.json
 .hyperopt
 logfile.txt
 hyperopt_trials.pickle
-user_data/
+user_data/*
+!user_data/notebooks
+user_data/notebooks/*
+!user_data/notebooks/*example.ipynb
 freqtrade-plot.html
 freqtrade-profit-plot.html
 
@@ -80,7 +83,7 @@ docs/_build/
 target/
 
 # Jupyter Notebook
-.ipynb_checkpoints
+*.ipynb_checkpoints
 
 # pyenv
 .python-version
@@ -94,4 +97,4 @@ target/
 .mypy_cache/
 
 #exceptions
-!user_data/noteboks/*example.ipynb
+!*.gitkeep

docs/data-analysis.md

@@ -1,30 +1,96 @@
-# Analyzing bot data
+# Analyzing bot data with Jupyter notebooks  
 
-You can analyze the results of backtests and trading history easily using Jupyter notebooks. A sample notebook is located at `user_data/notebooks/analysis_example.ipynb`. For usage instructions, see [jupyter.org](https://jupyter.org/documentation).
+You can analyze the results of backtests and trading history easily using Jupyter notebooks. Sample notebooks are located at `user_data/notebooks/`.  
 
-*Pro tip - Don't forget to start a jupyter notbook server from within your conda or venv environment or use [nb_conda_kernels](https://github.com/Anaconda-Platform/nb_conda_kernels)*
+## Pro tips  
 
-## Example snippets
+* See [jupyter.org](https://jupyter.org/documentation) for usage instructions.
+* Don't forget to start a jupyter notbook server from within your conda or venv environment or use [nb_conda_kernels](https://github.com/Anaconda-Platform/nb_conda_kernels)*
+* Copy the example notebook so your changes don't get clobbered with the next freqtrade update.
+
+## Fine print  
+
+Some tasks don't work especially well in notebooks. For example, anything using asyncronous exectution is a problem for Jupyter. Also, freqtrade's primary entry point is the shell cli, so using pure python in a notebook bypasses arguments that provide required parameters to functions.
+
+## Recommended workflow  
+
+| Task | Tool |  
+  --- | ---  
+Bot operations | CLI  
+Repetative tasks | shell scripts
+Data analysis & visualization | Notebook  
+
+1. Use the CLI to
+    * download historical data
+    * run a backtest
+    * run with real-time data
+    * export results  
+
+1. Collect these actions in shell scripts
+    * save complicated commands with arguments
+    * execute mult-step operations  
+    * automate testing strategies and prepareing data for analysis
+
+1. Use a notebook to
+    * import data
+    * munge and plot to generate insights
+
+## Example utility snippets for Jupyter notebooks  
+
+### Change directory to root  
+
+Jupyter notebooks execute from the notebook directory. The following snippet searches for the project root, so relative paths remain consistant.
+
+```python
+# Change directory
+# Modify this cell to insure that the output shows the correct path.
+# Define all paths relative to the project root shown in the cell output
+import os
+from pathlib import Path
+
+project_root = "somedir/freqtrade"
+i=0
+try:
+    os.chdirdir(project_root)
+    assert Path('LICENSE').is_file()
+except:
+    while i<4 and (not Path('LICENSE').is_file()):
+        os.chdir(Path(Path.cwd(), '../'))
+        i+=1
+    project_root = Path.cwd()
+print(Path.cwd())
+```
+
+### Watch project for changes to code
+
+This scans the project for changes to code before Jupyter runs cells.
+
+```python
+# Reloads local code changes
+%load_ext autoreload
+%autoreload 2
+```
+
+## Load existing objects into a Jupyter notebook
+
+These examples assume that you have already generated data using the cli. These examples will allow you to drill deeper into your results, and perform analysis which otherwise would make the output very difficult to digest due to information overload.
 
 ### Load backtest results into a pandas dataframe
 
 ```python
-from freqtrade.data.btanalysis import load_backtest_data
 # Load backtest results
+from freqtrade.data.btanalysis import load_backtest_data
 df = load_backtest_data("user_data/backtest_data/backtest-result.json")
 
 # Show value-counts per pair
 df.groupby("pair")["sell_reason"].value_counts()
 ```
 
-This will allow you to drill deeper into your backtest results, and perform analysis which otherwise would make the regular backtest-output very difficult to digest due to information overload.
-
 ### Load live trading results into a pandas dataframe
 
 ``` python
-from freqtrade.data.btanalysis import load_trades_from_db
-
 # Fetch trades from database
+from freqtrade.data.btanalysis import load_trades_from_db
 df = load_trades_from_db("sqlite:///tradesv3.sqlite")
 
 # Display results
@@ -33,55 +99,78 @@ df.groupby("pair")["sell_reason"].value_counts()
 
 ### Load multiple configuration files
 
-This option can be usefull to inspect the results of passing in multiple configs in case of problems
+This option can be useful to inspect the results of passing in multiple configs
 
 ``` python
+# Load config from multiple files
 from freqtrade.configuration import Configuration
 config = Configuration.from_files(["config1.json", "config2.json"])
-print(config)
-```
 
-## Strategy debugging example
+# Show the config in memory
+import json
+print(json.dumps(config, indent=1))
+```
 
-Debugging a strategy can be time-consuming. FreqTrade offers helper functions to visualize raw data.
+### Load exchange data to a pandas dataframe
 
-### Import requirements and define variables used in analyses
+This loads candle data to a dataframe
 
 ```python
-# Imports
+# Load data using values passed to function
 from pathlib import Path
-import os
 from freqtrade.data.history import load_pair_history
-from freqtrade.resolvers import StrategyResolver
 
-# You can override strategy settings as demonstrated below.
+ticker_interval = "5m"
+data_location = Path('user_data', 'data', 'bitrex')
+pair = "BTC_USDT"
+candles = load_pair_history(datadir=data_location,
+                            ticker_interval=ticker_interval,
+                            pair=pair)
+
+# Confirm success
+print("Loaded " + str(len(candles)) + f" rows of data for {pair} from {data_location}")
+display(candles.head())
+```
+
+## Strategy debugging example  
+
+Debugging a strategy can be time-consuming. FreqTrade offers helper functions to visualize raw data.
+
+### Define variables used in analyses  
+
+You can override strategy settings as demonstrated below.
+
+```python
 # Customize these according to your needs.
 
 # Define some constants
 ticker_interval = "5m"
 # Name of the strategy class
-strategy_name = 'AwesomeStrategy'
+strategy_name = 'TestStrategy'
 # Path to user data
 user_data_dir = 'user_data'
 # Location of the strategy
 strategy_location = Path(user_data_dir, 'strategies')
 # Location of the data
 data_location = Path(user_data_dir, 'data', 'binance')
-# Pair to analyze 
-# Only use one pair here
+# Pair to analyze - Only use one pair here
 pair = "BTC_USDT"
 ```
 
 ### Load exchange data
 
 ```python
 # Load data using values set above
-bt_data = load_pair_history(datadir=Path(data_location),
+from pathlib import Path
+from freqtrade.data.history import load_pair_history
+
+candles = load_pair_history(datadir=data_location,
                             ticker_interval=ticker_interval,
                             pair=pair)
 
 # Confirm success
-print(f"Loaded {len(bt_data)} rows of data for {pair} from {data_location}")
+print("Loaded " + str(len(candles)) + f" rows of data for {pair} from {data_location}")
+display(candles.head())
 ```
 
 ### Load and run strategy  
@@ -90,31 +179,27 @@ print(f"Loaded {len(bt_data)} rows of data for {pair} from {data_location}")
 
 ```python
 # Load strategy using values set above
+from freqtrade.resolvers import StrategyResolver
 strategy = StrategyResolver({'strategy': strategy_name,
                             'user_data_dir': user_data_dir,
                             'strategy_path': strategy_location}).strategy
 
 # Generate buy/sell signals using strategy
-df = strategy.analyze_ticker(bt_data, {'pair': pair})
+df = strategy.analyze_ticker(candles, {'pair': pair})
 ```
 
 ### Display the trade details
 
 * Note that using `data.head()` would also work, however most indicators have some "startup" data at the top of the dataframe.
-
-#### Some possible problems
-
-* Columns with NaN values at the end of the dataframe
-* Columns used in `crossed*()` functions with completely different units
-
-#### Comparison with full backtest
-
-having 200 buy signals as output for one pair from `analyze_ticker()` does not necessarily mean that 200 trades will be made during backtesting.
-
-Assuming you use only one condition such as, `df['rsi'] < 30` as buy condition, this will generate multiple "buy" signals for each pair in sequence (until rsi returns > 29).
-The bot will only buy on the first of these signals (and also only if a trade-slot ("max_open_trades") is still available), or on one of the middle signals, as soon as a "slot" becomes available.
+* Some possible problems
+    * Columns with NaN values at the end of the dataframe
+    * Columns used in `crossed*()` functions with completely different units
+* Comparison with full backtest
+    * having 200 buy signals as output for one pair from `analyze_ticker()` does not necessarily mean that 200 trades will be made during backtesting.
+    * Assuming you use only one condition such as, `df['rsi'] < 30` as buy condition, this will generate multiple "buy" signals for each pair in sequence (until rsi returns > 29). The bot will only buy on the first of these signals (and also only if a trade-slot ("max_open_trades") is still available), or on one of the middle signals, as soon as a "slot" becomes available.  
 
 ```python
+
 # Report results
 print(f"Generated {df['buy'].sum()} buy signals")
 data = df.set_index('date', drop=True)