Skip to content
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

InformativeSample results in an error (InformativePairs not working anymore?) #51

Closed
Theagainmen opened this issue Nov 20, 2019 · 6 comments

Comments

@Theagainmen
Copy link

The problem

The InformativeSample.py doesn't work anymore, it results in errors for backtesting and plotting, both different errors.

System specs

Backtesting

  • The command I run: freqtrade backtesting -c InformativeSample
  • The error: TypeError: get_pair_dataframe() got an unexpected keyword argument 'ticker_interval'
  • Full error: https://pastebin.com/E82ahrVK

Plotting

  • The command I run: freqtrade plot-dataframe -s InformativeSample -p MTH/BTC --timerange=20191105-20191120
  • The error: AttributeError: 'InformativeSample' object has no attribute 'dp'
  • Full error: https://pastebin.com/r0P1S08J
@hroff-1902 hroff-1902 transferred this issue from freqtrade/freqtrade-strategies Nov 20, 2019
@hroff-1902 hroff-1902 transferred this issue from freqtrade/freqtrade Nov 20, 2019
@xmatthias
Copy link
Member

it's fun to move issues around it sems 😆

the issue is due to the change in kwarg - best replace ticker_interval= with timeframe= short-term (we'll fix it in this repo soon).

@hroff-1902
Copy link
Member

it's fun to move issues around it sems 😆

Yeah, "I like to move it, move it..." 😆

the issue is due to the change in kwarg - best replace ticker_interval= with timeframe= short-term (we'll fix it in this repo soon).

It's for the first reported point. What about the second one?

@xmatthias
Copy link
Member

xmatthias commented Nov 20, 2019

the 2nd problem is that it's not there as attribute (currently it's only available for type-hinting ...).

it can be fixed by assigning "None" in interface.py to dp...
or by adding dp within plotting.py/init_plotsccript() ...
either empty, or as fully instantiated dataprovider (look at backtesting.py on how).

I'm not a fan of the 2nd one since datprovider requires exchange to be initialized, which is not necessary for plotting otherwise, and self.dp is checked for existence in all our docs, so the assumption is that it can be "gone".

@Theagainmen
Copy link
Author

Theagainmen commented Nov 20, 2019

the issue is due to the change in kwarg - best replace ticker_interval= with timeframe= short-term (we'll fix it in this repo soon).
This fixes the issue for backtesting :).

For plotting I tried it can be fixed by assigning "None" in interface.py to dp...
dp
This is the only dp: in the interface.py, changing DataProvider to None didn't work, it resulted in the same error. (I'm not sure if that's what you meant though).

@hroff-1902
Copy link
Member

@Theagainmen see the changes made in freqtrade/freqtrade#2560

the second part is to be fixed in the freqtrade codebase. That's why I transferred this issue to that github repo first...

@xmatthias
Copy link
Member

fixed via combination of freqtrade/freqtrade#2560 and #52

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants