-
Notifications
You must be signed in to change notification settings - Fork 3.9k
TULIP indicators could not be loaded #1505
Comments
Also have this issue. Win 10 bash. Installed as per: https://gekko.wizb.it/docs/installation/installing_gekko_on_windows_with_bash_on_windows_10.html |
@Mexxwelll @EdTheProfet |
Also have this issue with |
What is the issue? |
@cmroche |
Please follow the instructions here: https://gekko.wizb.it/docs/strategies/tulip_indicators.html @alieonsido if you have trouble installing tulind please create a new issue (as it's different from the one described here). And please post the output of the npm installation command as well! Thanks. |
@askmike |
my error is : |
That's a python error, that cannot come from gekko as it is not written in
python.
…On Mon, 30 Jul 2018, 15:53 seyedsaeedmortazavi, ***@***.***> wrote:
my error is :
Traceback (most recent call last):
File "transys_ts_test.py", line 6, in
from tulip import transys as trs
ImportError: cannot import name transys
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1505 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA7MDwoC8N1m9EDNmdjYk2mSvGHN_KhLks5uLruTgaJpZM4REyJS>
.
|
Note: for support questions, please join our Discord server
I'm submitting a ...
[X] bug report
[ ] feature request
[ ] question about the decisions made in the repository
Action taken (what you did)
Running headless Gekko (also tested with developer), dong backtest with Tulip-* strat. Comes back with error: 2017-12-17 21:18:31 (WARN): TULIP indicators could not be loaded, they will be unavailable.
npm install tulip
└── tulip@0.0.0
Expected result (what you hoped would happen)
Just some backtest results
Actual result (unexpected outcome)
2017-12-17 21:18:31 (WARN): TULIP indicators could not be loaded, they will be unavailable.
Other information
I was also having issue's with the Talib indicators, i fixed this part by running this command:
npm install talib@1.0.2
The text was updated successfully, but these errors were encountered: