+- Gekko Forum (https://forum.gekko.wizb.it)
+-- Forum: Gekko (https://forum.gekko.wizb.it/forum-13.html)
+--- Forum: Strategy Development (https://forum.gekko.wizb.it/forum-12.html)
+--- Thread: RSI_BULL_BEAR_ADX doesn't work (/thread-57328.html)
RSI_BULL_BEAR_ADX doesn't work - chico - 07-09-2018
Hi,
i'm running gekko in a docker on MAC OS X.
I have installed new strategies and when i do backtest, RSI_BULL_BEAR is working fine.
RSI_BULL_BEAR_ADX doesn't work.
It starts and immediately stop without any result.
Talib and Tulind have been installed
Can somebody help?
Thank you
RE: RSI_BULL_BEAR_ADX doesn't work - chico - 07-10-2018
(07-09-2018, 06:39 PM)chico Wrote: Hi,
i'm running gekko in a docker on MAC OS X.
I have installed new strategies and when i do backtest, RSI_BULL_BEAR is working fine.
RSI_BULL_BEAR_ADX doesn't work.
It starts and immediately stop without any result.
Talib and Tulind have been installed
Can somebody help?
Thank you
this is the error i get:
Error: non-error thrown:
This Gekko instance encountered an error and can't continue
at Object.onerror (/usr/src/app/node_modules/koa/lib/context.js:105:40)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
Any clue?
RE: RSI_BULL_BEAR_ADX doesn't work - chico - 07-10-2018
i also tried to increase the time to 6 hours in UIconfig but still the same
RE: RSI_BULL_BEAR_ADX doesn't work - LordBB - 07-11-2018
You should try:
npm install talib
npm install tulind
npm install mathjs
RE: RSI_BULL_BEAR_ADX doesn't work - chico - 07-12-2018
(07-11-2018, 03:22 PM)LordBB Wrote: You should try:
npm install talib
npm install tulind
npm install mathjs
Thank you LordBB but i talib and tulind were already installed.
Now i got a lot of errors and i will start a fresh installation.
Will see.
RE: RSI_BULL_BEAR_ADX doesn't work - zoranjukic - 07-12-2018
I had the same issues. You should install the latest Indicators here is the link: https://github.com/Gab0/gekko-extra-indicators
RE: RSI_BULL_BEAR_ADX doesn't work - chico - 07-13-2018
(07-12-2018, 06:27 AM)zoranjukic Wrote: I had the same issues. You should install the latest Indicators here is the link: https://github.com/Gab0/gekko-extra-indicators
Thank you for your help, i tried also with the latest ones.
I have re-installed from scretch
UIconfig file amended as told (time to 6 hours)
GCC is working well as command line
extra indicators installed.
Don't know anymore what could be the issue.
I will probably give up on gekko...quite sad
RE: RSI_BULL_BEAR_ADX doesn't work - chico - 07-13-2018
(07-13-2018, 04:38 AM)chico Wrote:(07-12-2018, 06:27 AM)zoranjukic Wrote: I had the same issues. You should install the latest Indicators here is the link: https://github.com/Gab0/gekko-extra-indicators
Thank you for your help, i tried also with the latest ones.
I have re-installed from scretch
UIconfig file amended as told (time to 6 hours)
GCC is working well as command line
extra indicators installed.
Don't know anymore what could be the issue.
I will probably give up on gekko...quite sad
Just now after the last rebuild it looks like the Strategy RSI_BULL_BEAR_ADX works
still have problem with BBRSI though
I check whether there are other indicators to install for that one.
Thank you!
RE: RSI_BULL_BEAR_ADX doesn't work - Rabberzzz - 10-11-2018
Is this post still alive?
I give it a try!
I got the same problem that only the ADX strategie doesn't work. I got the following error:
Error: non-error thrown:
ERROR: I do not know the indicator ADX
at Object.onerror (/home/nick/gekko/node_modules/koa/lib/context.js:105:40)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)
uncaughtException TypeError: Indicators[type] is not a constructor
at Base.addIndicator (/home/nick/gekko/plugins/tradingAdvisor/baseTradingMethod.js:236:34)
at Base.bound [as addIndicator] (/home/nick/gekko/node_modules/lodash/dist/lodash.js:729:21)
at Base.init (/home/nick/gekko/strategies/RSI_BULL_BEAR_ADX.js:47:8)
at Base.bound [as init] (/home/nick/gekko/node_modules/lodash/dist/lodash.js:729:21)
at new Base (/home/nick/gekko/plugins/tradingAdvisor/baseTradingMethod.js:69:8)
at Actor.setupStrategy (/home/nick/gekko/plugins/tradingAdvisor/tradingAdvisor.js:61:19)
at Actor.bound [as setupStrategy] (/home/nick/gekko/node_modules/lodash/dist/lodash.js:729:21)
at new Actor (/home/nick/gekko/plugins/tradingAdvisor/tradingAdvisor.js:23:8)
at load (/home/nick/gekko/core/pluginUtil.js:98:22)
at /home/nick/gekko/node_modules/async/dist/async.js:1156:9
And yes I copied the test_adx + adx .js files to gekko/strategies/indicators directory
What can I do more?
RE: RSI_BULL_BEAR_ADX doesn't work - Rabberzzz - 10-14-2018
(10-11-2018, 07:33 AM)Rabberzzz Wrote: Is this post still alive?
I give it a try!
I got the same problem that only the ADX strategie doesn't work. I got the following error:
Error: non-error thrown:
ERROR: I do not know the indicator ADX
at Object.onerror (/home/nick/gekko/node_modules/koa/lib/context.js:105:40)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)
uncaughtException TypeError: Indicators[type] is not a constructor
at Base.addIndicator (/home/nick/gekko/plugins/tradingAdvisor/baseTradingMethod.js:236:34)
at Base.bound [as addIndicator] (/home/nick/gekko/node_modules/lodash/dist/lodash.js:729:21)
at Base.init (/home/nick/gekko/strategies/RSI_BULL_BEAR_ADX.js:47:8)
at Base.bound [as init] (/home/nick/gekko/node_modules/lodash/dist/lodash.js:729:21)
at new Base (/home/nick/gekko/plugins/tradingAdvisor/baseTradingMethod.js:69:8)
at Actor.setupStrategy (/home/nick/gekko/plugins/tradingAdvisor/tradingAdvisor.js:61:19)
at Actor.bound [as setupStrategy] (/home/nick/gekko/node_modules/lodash/dist/lodash.js:729:21)
at new Actor (/home/nick/gekko/plugins/tradingAdvisor/tradingAdvisor.js:23:8)
at load (/home/nick/gekko/core/pluginUtil.js:98:22)
at /home/nick/gekko/node_modules/async/dist/async.js:1156:9
And yes I copied the test_adx + adx .js files to gekko/strategies/indicators directory
What can I do more?
I couldn't resolve the uncaughtException TypeError: Indicators[type] is not a constructor issue.
But I re-installed everything from scratch and it does work again.
The only thing I did different was clone the files via CLI and move the files from over there to correct directory's.