New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crossover: IndexError: list index out of range (Bad data) #304
Comments
maybe this can help you. not a good fix but it works |
I'm seeing the same thing and noticing that it's retrying. Posting error here just in case it helps Beginning analysis of WTC/BTC |
I think that's actually a separate problem, but it will probably help me track down this one. |
I run the app over all pairs on bittrex and also get the same error. Any fix? Beginning analysis of BCH/BTC |
Choose a different pair like BTC/USDT to make sure it’s not an issue with
the BCH pair.
…On Thu, Apr 4, 2019 at 6:51 AM TG ***@***.***> wrote:
I run the app over all pairs on bittrex and also get the same error. Any
fix?
Beginning analysis of BCH/BTC
No historical data provided returned by exchange.
Invalid data encountered while processing pair BCH/BTC, skipping
No historical data provided returned by exchange.
Invalid data encountered while processing pair BCH/BTC, skipping
No historical data provided returned by exchange.
Invalid data encountered while processing pair BCH/BTC, skipping
No historical data provided returned by exchange.
Invalid data encountered while processing pair BCH/BTC, skipping
No historical data provided returned by exchange.
Invalid data encountered while processing pair BCH/BTC, skipping
Traceback (most recent call last):
File "app.py", line 45, in
main()
File "app.py", line 39, in main
behaviour.run(settings['market_pairs'], settings['output_mode'])
File "/app/behaviour.py", line 63, in run
new_result = self._test_strategies(market_data, output_mode)
File "/app/behaviour.py", line 98, in _test_strategies
new_result[exchange][market_pair]
File "/app/behaviour.py", line 250, in _get_crossover_results
key_indicator =
new_result[crossover_conf['key_indicator_type']][crossover_conf['key_indicator']][crossover_conf['key_indicator_index']]
IndexError: list index out of range
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#304 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfqkCPpzLNBG7qdjSYKK0HbKk4VWQU4Lks5vdgNfgaJpZM4UKNyu>
.
|
Hi @alonsovargas3 , everything goes fine if I only run it over a specific pair like BTC/USDT. Weirdly, the same error occurred on BHC/BTC regardless on which market exchange. |
That's because BCH is no longer a coin - it forked and you have two:
BCHABC/BTC and BCHBV/BTC - I believe they both inherited the BCH historical
data.
…On Thu, Apr 4, 2019 at 7:11 AM TG ***@***.***> wrote:
Hi @alonsovargas3 <https://github.com/alonsovargas3> , everything goes
fine if I only run it over a specific pair like BTC/USDT. Weirdly, the same
error occurred on BHC/BTC regardless on which market exchange.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#304 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfqkCAyA_ntCgJu7BXx15iPASn8sVvF7ks5vdggogaJpZM4UKNyu>
.
|
Today, April 4, these seem to be the correct pairs on Bittrex: BSV/BTC - Bitcoin SV Candle periods: '1m', '5m', '30m', '1h', '1d' |
Good info. Also, in the error message I saw the following:
Invalid data encountered while processing pair HSR/BTC, skipping
Looks like you just need to make sure your config file has the right pairs.
…On Thu, Apr 4, 2019 at 12:32 PM Eduardo Zarate ***@***.***> wrote:
Today, April 4, these seem to be the correct pairs on Bittrex:
BSV/BTC - Bitcoin SV
BCH/BTC - Bitcoin Cash
Candle periods: '1m', '5m', '30m', '1h', '1d'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#304 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfqkCPVVwmHLBY1vUzgxK8tek_0I3tjzks5vdlNigaJpZM4UKNyu>
.
|
So far what I need to do to scan all pairs is to list all pairs in the config except the ones which failed, right? |
The program ignores invalid pairs, It doesn't cause any error because of that. By the way, take a look at the development branch. There are many interesting things in the process. |
After hours of running crypto-signal I get the following error. I assume an error handling could avoid this crossover behaviour when there is bad data.
The text was updated successfully, but these errors were encountered: