I'm trying to make a strategy that buys and sells but I can not get it to work well, I thought of many strategies ...
I admit that I have very little knowledge in programming
I would like you to do the following or the closest thing, taking advantage of each upload (see attached)
the idea is that you buy and sell according to a percentage X or amount that I define
// Based on the newly calculated
// information, check if we should
// update or not.
strat.check = function(candle)
{
if (candle.close >= candle.close + ( candle.close*( this.percentLower/100.0 )))
I'm having an issue restarting/creating a new gekko in 0.6.4. Short backstory, I was running the paper trader on v0.5.13. It crashed this morning so I decided to upgrade Gekko before restarting it. I did a fresh install and moved my strategy/toml/historydb files over. When I went to recreate the papertrader I received the following error.
"This is an archived Gekko, it is currently not running anymore"
followed by another message, "This is Gekko crashed with the following error {"code": "MODULE_NOT FOUND"}"
When I scroll to the bottom of the page I have an option to "Delete Gekko" which returns me to the Live Gekko page without that papertrader listed. However when I go to recreate the live gekko again I'm presented with the same error.
I see someone on github submitted a bug report with a similar issue (#2341), however my circumstances are slightly different (I'm on Windows 10 if that's helpful). I'm also not on github currently so I can't respond to the existing report.
Is this a bug? Is there a way to remove the archived entry so I can start fresh?
today my gekko crashed after it bougth some coins.
After the restart, my Strategie does not know, that it already bougth,
because the variable was set before the crash.
After the restart the adviced var is false again and will never send a sell advice...
The bug is fixed in the dev branch but i am thinking about an initialisation at startup.
Gekko outputs the "Exposed" value on every startup,
is it possible to use this value in the strategy to check on first run whether
we are exposed or not?
I am opening up this thread to brainstorm and discuss new Gekko code commits which might be of general interest. The goal is to collect feedback before opening a pull request for the main Gekko development branch.
On the way with my crypto gameplan I started with some Postgresql db features (Mike merged them) followed by new Gekko exchange support (HitBTC, HuobiPro and OKEX), a couple of telegram bot improvements like manual, immediate buy/sell support inside a password protected admin area and keyboard-button support for quick telegrambot feature access. Beside this I added some smaller convenience features which simplified my daily Gekko use.
This one adds a new command line option for Gekko to quickly set/override a config setting for the current Gekko CLI run, example:
node gekko --config config-eth.js --backtest --set debug=false
The idea: I often run Gekko with debug messages enabled but during backtest mode I get a better, more useful output without debug messages. So instead of touching the config file for this, it is now possible to override config settings on-the-fly. Of course other config settings can also be changed this way.
Gekko keeps track which plugin is able to run in which Gekko mode, e.g. the Trader plugin does not run in backtest mode but the Paper Trader is used both in realtime and backtest Mode. These modes are configured with property "mode" inside plugins.js file. Gekko will automatically disable a plugin which is not allowed to run within a certain mode. The other way around, there are modes where a certain plugin is mandatory to run this mode. E.g. the Paper Trader is mandatory to run the backtest mode properly. For that reason I added a new plugins.js property "mandatoryOn" to document mandatory plugins for a certain mode. When a plugin is declared to be necessary for a certain mode, it will now automatically be enabled for that certain mode (like automatic disabling when not allowed for a certain mode). This small change gave me a lot of convenience on my live server, since there is no need anymore to touch any config files or to maintain several config files for a quick backtest. It also helps documenting which modes and plugins belong together.
Any thoughts? If you consider it to be of general interest, I could add a pull request.
When I wanted to start my Paper trader I get the error "errno": 5, "code": "SQLITE_BUSY" }. I already deinstalled en reinstalled.
I have changed thePlugins/Sqlite/handle.js
55 lines; change 1500 to 5000~15000.
5000 is 50/50. So, please use over 7000
But this made it only worse
go web/vue/UIconfig.js and change timeout 150000 to 600000 // 1min to 5 min. but this wasn't ether.
I think that i is something with the database that he is already busy with the markt watchter. Which autmatic start with the paper trader is that right ? I tried to only to start the trade paper but this doesn't work.
config.trader was true I changed It to false in my config.sample file. Still the same error SQLITE-BUSY
The problem is I think that the database's must be seperated ? I don't how only and I don't know if that is the answer
in conformity shakra keto diet with dietary manuals, discharge magazines and appearingbelongings. nearby patch anent n acquisition Totally advantageous base prat be a burdensome and leap-span interesting designation. Tribe may counterfeitextensively in the bearing pile for a spacious duration truck
It seems to me that with everything Gekko has to offer ... a fairly logical evolution could be to launch several paper traders against multiple coins.
If any of the coins being traded exhibit favorable conditions for live trading they could call a live trade bot and pass the coin pair to be traded.
For Example
Paper Trade:
XRP-USDT
XLM-USDT
ADA-USDT
EOS-USDT
etc …
Maybe I am using Bull_Bear_RSI and ADA-USDT starts to move in the direction of activating the advice to go long.
Once that condition is met we call a live trade bot and launch it to trade ADA-USDT.
Using this type of setup would maybe evolve into a bot that bounces around from coin to coin depending on indicators like volume and ADX or EMA's
You would hop to whatever is the most potentially profitable scenario … Similar to how I believe a mining pool optimizes it's efforts and focuses on the highest yield mining effort.
If your favorite coin starts to trade sideways you move onto other pairs that are moving up if they are on your watch list or something like that ...
Hi, I'm trying to install the talib in node with the instruction:
Code:
npm install talib
But after compiling sources it fails with the error: gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir '/home/ivan/gekko/gekko/node_modules/talib/build'
gyp ERR! System Linux 4.15.0-20-generic
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure"
gyp ERR! cwd /home/ivan/gekko/gekko/node_modules/talib
gyp ERR! node -v v8.11.3
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! talib@1.0.5 install: node ./src/lib/build.js && node-gyp configure && node-gyp build npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the talib@1.0.5 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in:
I tried it with sudo user with the same result, and changing the permission of the directory to 777, but nothing works, any idea?
