Not Enough Data to display!
Average Overall
| Not Enough Data! / Avg statistics not populated yet. |
|---|
The Kdj strategy is a trading strategy designed for backtesting purposes. Here's a short description of what the strategy does:
Timeframe: The strategy operates on a 5-minute timeframe. Candle Processing: The strategy processes indicators only for new candles.
Order Types: The strategy uses limit orders for both entry and exit, while using a market order for stop-loss.
Stop-loss on the exchange is disabled.
ROI Table: The strategy has predefined returns on investment (ROI) values at different time intervals. Stop Loss: The strategy has a fixed stop-loss value of -0.233. Trailing Stop: The strategy utilizes a trailing stop feature. The trailing stop positive value is 0.176, and it has an offset of 0.213. The trailing stop is based on the offset and does not trigger only when the offset is reached. Indicator and Entry/Exit Logic: Indicator: The strategy calculates the T3 indicator using the close price and assigns it to the 't3' column in the dataframe. Entry Logic: The strategy checks if the current T3 value is greater than the previous T3 value to determine a bullish entry condition. If the condition is met, it sets the 'enter_long' column to 1. Exit Logic: The strategy checks if the current T3 value is less than the previous T3 value to determine an exit condition. If the condition is met, it sets the 'exit_long' column to 1. Please note that the strategy does not provide any informative pairs and does not utilize any additional indicators or entry/exit conditions beyond the T3 indicator comparison.
Order Types: The strategy uses limit orders for both entry and exit, while using a market order for stop-loss.
Stop-loss on the exchange is disabled.
ROI Table: The strategy has predefined returns on investment (ROI) values at different time intervals. Stop Loss: The strategy has a fixed stop-loss value of -0.233. Trailing Stop: The strategy utilizes a trailing stop feature. The trailing stop positive value is 0.176, and it has an offset of 0.213. The trailing stop is based on the offset and does not trigger only when the offset is reached. Indicator and Entry/Exit Logic: Indicator: The strategy calculates the T3 indicator using the close price and assigns it to the 't3' column in the dataframe. Entry Logic: The strategy checks if the current T3 value is greater than the previous T3 value to determine a bullish entry condition. If the condition is met, it sets the 'enter_long' column to 1. Exit Logic: The strategy checks if the current T3 value is less than the previous T3 value to determine an exit condition. If the condition is met, it sets the 'exit_long' column to 1. Please note that the strategy does not provide any informative pairs and does not utilize any additional indicators or entry/exit conditions beyond the T3 indicator comparison.
startup_candle_count : 50 Recursive Analysis found no issues while using 50 startup_candle_count
Traceback (most recent call last): File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connection.py", line 198, in _new_conn sock = connection.create_connection( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/util/connection.py", line 60, in create_connection for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/socket.py", line 962, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ socket.gaierror: [Errno -2] Name or service not known The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 793, in urlopen response = self._make_request( ^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 491, in _make_request raise new_e File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 467, in _make_request self._validate_conn(conn) File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 1099, in _validate_conn conn.connect() File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connection.py", line 616, in connect self.sock = sock = self._new_conn() ^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connection.py", line 205, in _new_conn raise NameResolutionError(self.host, self, e) from e urllib3.exceptions.NameResolutionError:: Failed to resolve 'fapi.binance.com' ([Errno -2] Name or service not known) The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/ftuser/.local/lib/python3.11/site-packages/requests/adapters.py", line 486, in send resp = conn.urlopen( ^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 847, in urlopen retries = retries.increment( ^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/util/retry.py", line 515, in increment raise MaxRetryError(_pool, url, reason) from reason # type: ignore[arg-type] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='fapi.binance.com', port=443): Max retries exceeded with url: /fapi/v1/exchangeInfo (Caused by NameResolutionError(" : Failed to resolve 'fapi.binance.com' ([Errno -2] Name or service not known)")) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/base/exchange.py", line 598, in fetch response = self.session.request( ^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/requests/sessions.py", line 589, in request resp = self.send(prep, **send_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/requests/sessions.py", line 703, in send r = adapter.send(request, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/requests/adapters.py", line 519, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPSConnectionPool(host='fapi.binance.com', port=443): Max retries exceeded with url: /fapi/v1/exchangeInfo (Caused by NameResolutionError(" : Failed to resolve 'fapi.binance.com' ([Errno -2] Name or service not known)")) The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/freqtrade/freqtrade/exchange/exchange.py", line 486, in _load_markets self._markets = self._api.load_markets(params={}) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/base/exchange.py", line 1474, in load_markets markets = self.fetch_markets(params) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/binance.py", line 2736, in fetch_markets promisesRaw.append(self.fapiPublicGetExchangeInfo(params)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/base/types.py", line 34, in unbound_method return _self.request(self.path, self.api, self.method, params, config=self.config) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/binance.py", line 10089, in request response = self.fetch2(path, api, method, params, headers, body, config) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/base/exchange.py", line 3523, in fetch2 return self.fetch(request['url'], request['method'], request['headers'], request['body']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/base/exchange.py", line 651, in fetch raise NetworkError(details) from e ccxt.base.errors.NetworkError: binance GET https://fapi.binance.com/fapi/v1/exchangeInfo
stoploss: -0.233 timeframe: 5m hash(sha256): 0d1fada9fcaaebd9ba6a7610ae563bc6953946cff7e52254f9c1b7a036c73308 indicators: t3 close
No similar strategies found. (based on used indicators)
last change: 2024-04-17 20:12:20