Gekko - a javascript trading bot and backtesting platform

[ewibit]

That's a bug in Gekko, if you could let me know some details (like are you running the latest version, what exchange and interval) I will look into it!

I have updated now

Code:

git pull https://github.com/askmike/gekko.git && npm update

and I am on Bitstamp
interval is 30

still the same

Code:

ADVICE is to HOLD @ 85.810 (NaN)

which part of config.js do you need?

(BTW: is there any possibility to git pull without to fill out config.js every time new? - I rename the existent to .bak and copy/paste the settings in the new one)

[jago25_98]

Code:

module.js:337
    throw new Error("Cannot find module '" + request + "'");
          ^
Error: Cannot find module 'moment'
    at Function._resolveFilename (module.js:337:11)
    at Function._load (module.js:279:25)
    at Module.require (module.js:359:17)
    at require (module.js:375:17)
    at Object.<anonymous> (/home/pi/src/gekko/gekko.js:20:14)
    at Module._compile (module.js:446:26)
    at Object..js (module.js:464:10)
    at Module.load (module.js:353:32)
    at Function._load (module.js:311:12)
    at Array.0 (module.js:484:10)

Code:

$ ls -R
.:
config.js  docs  exchanges  gekko.js  logger.js  log.js  mailer.js  methods  package.json  portfolioManager.js  README.md  util.js

./docs:
Advanced_features.md  Backtesting.md  Configuring_gekko.md  Exchanges.md  installing_gekko_on_windows.md  Known_problems.md

./exchanges:
bitcoincharts.js  bitstamp.js  btce.js  mtgox.js

./methods:
exponential-moving-averages.js  historical-candle-fetcher.js  realtime-candle-fetcher.js

(following fresh git checkout)

Any ideas?

[whydifficult]

Code:

ADVICE is to HOLD @ 85.810 (NaN)

which part of config.js do you need?

I just looked into this and Bitstamp has changed their API, Gekko asks for data in a format not supported anymore (old API, new API). This means that Gekko currently does not work on Bitstamp. I am looking into a fix and hope to resolve this ASAP.

(BTW: is there any possibility to git pull without to fill out config.js every time new? - I rename the existent to .bak and copy/paste the settings in the new one)

Well the main reason is that the config is not solid, the settings may change and using an old settings file can result in Gekko crashing. You could place the config somewhere else (or rename like you did) and make a small script with `node gekko config=config.js.bak` to force Gekko to use another file as config. You can read more about that here, though I would advice against this.

Any ideas?

Gekko has dependencies (like momentjs), you can install them by running `npm install` in Gekko's directory.

[jago25_98]

It worked before. Queer.

I've been running it on a Raspberry Pi with Raspberian successfully... hmm, what's changed.... I had a external HDD fail but that wasn't the O/S and just data... did a reset... perhaps I had upgraded something which wasn't active until reboot...

Code:

npm ERR! Error: No compatible version found: mtgox-apiv2@'>=1.0.0- <1.1.0-'
npm ERR! No valid targets found.
npm ERR! Perhaps not compatible with your version of node?
npm ERR!     at installTargetsError (/usr/share/npm/lib/cache.js:488:10)
npm ERR!     at next_ (/usr/share/npm/lib/cache.js:438:17)
npm ERR!     at next (/usr/share/npm/lib/cache.js:415:44)
npm ERR!     at /usr/share/npm/lib/cache.js:408:5
npm ERR!     at saved (/usr/share/npm/lib/utils/npm-registry-client/get.js:147:7)
npm ERR!     at Object.oncomplete (/usr/lib/nodejs/graceful-fs.js:230:7)
npm ERR! You may report this log at:
npm ERR!     <http://bugs.debian.org/npm>
npm ERR! or use
npm ERR!     reportbug --attach /home/pi/src/gekko/npm-debug.log npm
npm ERR! 
npm ERR! System Linux 3.6.11+
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/pi/src/gekko
npm ERR! node -v v0.6.19
npm ERR! npm -v 1.1.4
npm ERR! message No compatible version found: mtgox-apiv2@'>=1.0.0- <1.1.0-'
npm ERR! message No valid targets found.
npm ERR! message Perhaps not compatible with your version of node?

I would guess that using npm -v 1.1.4 with mtgox-apiv2 would probably be ok... just searching for a way to bypass...
recovered node_modules dir from broken HDD and just copied this over, now working...)

In the mean-time I'll try using a debian box to test as well... now compiling nodejs...
( https://sekati.com/etc/install-nodejs-on-debian-squeeze )

...perhaps run 2 lots of gekko at the same time as a backup - if one already trades then the other will just be doubling up on it anyway

[whydifficult]

I would guess that using npm -v 1.1.4 with mtgox-apiv2 would probably be ok... just searching for a way to bypass...
recovered node_modules dir from broken HDD and just copied this over, now working...)

In the mean-time I'll try using a debian box to test as well... now compiling nodejs...
( https://sekati.com/etc/install-nodejs-on-debian-squeeze )

...perhaps run 2 lots of gekko at the same time as a backup - if one already trades then the other will just be doubling up on it anyway

If you are still running into trouble I would suggest updating node, v0.6.19 is really old and I think a lot of dependencies need a newer version.

You can run two gekkos (you just have to copy over the config and point one Gekko to the copied and changed config). But once you start Gekko node will load and parse the files and won't use the files on disk anymore at all (they are kept in memory). So with the exception of an error inside nodejs/raspberry or a really strange API response that Gekko cannot handle I won't see any difference in running two of them (unless you want to monitor multiple exchanges, etc.)

[jago25_98]

Thanks for your help. I've sent a ( tiny :/ ) tip as thanks.

My idea was to run Gekko on 2 different servers, then if one goes down the other will be doing the same thing anyway as backup.

 It seems Raspberian O/S nodejs is out of date. Debian on the other hand required compiling nodejs but that wasn't too bad. Gentoo was more straightforward

edit, found this:

Code:

terminate called after throwing an instance of 'std::bad_alloc'                 
  what():  std::bad_alloc

on debian with compile nodejs, running again now, but wonder how to get more debug info

[Mogumodz]

Been running it for a few days, tweaking it ever so slightly and watching the results.

One thing I've noticed is a profit calculation hasn't been shown afaik for me in the time I've been running the bot in simulation mode.

http://imgur.com/S3ik8WH

Any known reason for this I've missed.

[whydifficult]

Been running it for a few days, tweaking it ever so slightly and watching the results.

One thing I've noticed is a profit calculation hasn't been shown afaik for me in the time I've been running the bot in simulation mode.

http://imgur.com/S3ik8WH

Any known reason for this I've missed.

I heard a couple of things like this, I'll look in to this.

--

I don't have as much free time as I had last month. I am still working on Gekko, however not on the daily basis I was before.

[jago25_98]

What values do you run it at?
Always seems to buy low and sell high for me... but it did catch the more major dips so far which is handy

Been running it for a few days, tweaking it ever so slightly and watching the results.

One thing I've noticed is a profit calculation hasn't been shown afaik for me in the time I've been running the bot in simulation mode.

http://imgur.com/S3ik8WH

Any known reason for this I've missed.

[Timbo925]

What values do you run it at?
Always seems to buy low and sell high for me... but it did catch the more major dips so far which is handy

Been running it for a few days, tweaking it ever so slightly and watching the results.

One thing I've noticed is a profit calculation hasn't been shown afaik for me in the time I've been running the bot in simulation mode.

http://imgur.com/S3ik8WH

Any known reason for this I've missed.

That is what it suppose to do. It follows the flow of the market so if the 'flow' changes a lot in a short time you will lose some money.
But once the market moves big in a certain way for a longer time period you will be on the right side.

[jago25_98]

What I mean is that at a setting of 0.80/-0.80 I find that it tends to get to miss the very small timescale(daily), get it wrong on the short timescale(weekly) but get it right on the medium (monthly) scale.

This is of course very general and it hasn't been tested enough. The short weekly timescale is a shame. For example in the log here I have:

2013-07-15 20:14:53 (INFO):     ADVICE is to BUY @ 99.914 (0.990)
2013-07-15 20:14:56 (INFO):     attempting to BUY BTC at Mt. Gox
2013-07-15 20:15:29 (INFO):     BUY was succesfull
 2013-07-18 07:10:25 (INFO):    ADVICE is to SELL @ 89.700 (-1.055)
2013-07-18 07:10:27 (INFO):     attempting to SELL BTC at Mt. Gox
2013-07-18 07:10:58 (INFO):     SELL was succesfull
2013-07-19 19:10:25 (INFO):     ADVICE is to BUY @ 94.700 (0.894)
2013-07-19 19:10:26 (INFO):     attempting to BUY BTC at Mt. Gox
2013-07-19 19:10:58 (INFO):     BUY was succesfull

Which of course is the very opposite of what you want right!

Now, come to think of it, I remember why it caught the 70 dip - it was because I manually intervened and then used the bot to buy if anything changes.

I was hoping that I could use the EMA to catch those very large changes and basically create a less speculative more stable level but it doesn't seem to do that and just holding USD would be better at that.

Anyone had any wins with EMA?
Even though it's made losses I somehow how feel safer thinking that something less human is watching some coins for me. I'm not sure if it's too early to say experiment failed.

What values do you run it at?
Always seems to buy low and sell high for me... but it did catch the more major dips so far which is handy

Been running it for a few days, tweaking it ever so slightly and watching the results.

One thing I've noticed is a profit calculation hasn't been shown afaik for me in the time I've been running the bot in simulation mode.

http://imgur.com/S3ik8WH

Any known reason for this I've missed.

That is what it suppose to do. It follows the flow of the market so if the 'flow' changes a lot in a short time you will lose some money.
But once the market moves big in a certain way for a longer time period you will be on the right side.

[whydifficult]

Anyone had any wins with EMA?

Well I think a trading bot following a strategy is way better than its human counter part. But finding a good strategy is pretty hard. I would suggest using the backtesting to verify that your current settings would have made profit in the past.

You can also use Gekko to do paper/simulation trading (with a bunch of settings simultaneously for example), this way you know whether a strategy is currently effective. Do note that you are always looking a the success after a while, in which case the success lies in the history and won't guarantee anything anymore for the future.

EMA is a indicator that you can use to ride the trend (buy low - sell high), however because it uses moving averages to verify the trend it is always lagging behind. This in combination that trends can reverse at any time makes it so that you don't always make profit while trying to ride the trend.

To answer your question: I am currently on a 10% profit measured in BTC in a little over one month.

[Diabolicus]

This is a big step towards implementing a system that supports over a 100 different indicators (ta-lib) because it needs to get candles fed.

May I ask how far are you with the ta-lib implementation?
Also, could you make it somewhat similar to the code that cryptotrader.org accepts?
It would be so much easier if one could just simply copy&paste coffescript snippets back and forth.

[whydifficult]

This is a big step towards implementing a system that supports over a 100 different indicators (ta-lib) because it needs to get candles fed.

May I ask how far are you with the ta-lib implementation?
Also, could you make it somewhat similar to the code that cryptotrader.org accepts?
It would be so much easier if one could just simply copy&paste coffescript snippets back and forth.

I was pretty far. But because of the API changes in both bitcoincharts (BTC-e data) and bitstamp I probably have to change core. I want to have the core stabilised before I'm adding all the advanced stuff.

I was planning to do something similar for a while, I am not a fan of coffeescript myself. I think plain javascript is a lot easier for most people, as it's very similar to a lot of big languages like Java and C. But adding coffeescript ofcourse is a piece of cake since Gekko is a js project, so this will make it in.

I don't think I can make it exactly the same (with all function calls, etc). But I'll see what I can do

[conquerorofbits]

Gekko doesn't show Profit Reports, so I think there is a bug in logger.js:

logger.js, Line 37 ...

Code:

// log advice
Logger.prototype.inform = function(what, price, meta) {
  if(!this.verbose && what !== 'SELL' && !this.config.backtest)
    return;

  if(!this.verbose && what === 'HOLD' && this.config.backtest)
    return;

should be:

Code:

// log advice
Logger.prototype.inform = function(what, price, meta) {
  if(!this.verbose && what !== 'SELL' && !this.config.backtest.enable)
    return;

  if(!this.verbose && what === 'HOLD' && this.config.backtest.enabled)
    return;

Same thing at Line 94 ...

[ErebusBat]

May I ask how far are you with the ta-lib implementation?
Also, could you make it somewhat similar to the code that cryptotrader.org accepts?
It would be so much easier if one could just simply copy&paste coffescript snippets back and forth.

FYI...  Apparently you can use CoffeeScript pretty easy in node: http://stackoverflow.com/questions/4679782/can-i-use-coffeescript-instead-of-js-for-node-js#4683431

[ewibit]

Code:

realtime-candle-fetcher.js:98
    throw 'Failed to load historical trades from ' + this.watcher.name;
                                                   ^
Failed to load historical trades from bitcoincharts

[ErebusBat]

Code:

realtime-candle-fetcher.js:98
    throw 'Failed to load historical trades from ' + this.watcher.name;
                                                   ^
Failed to load historical trades from bitcoincharts

I have been getting this all weekend for Bitstamp too. 

[San1ty]

Code:

realtime-candle-fetcher.js:98
    throw 'Failed to load historical trades from ' + this.watcher.name;
                                                   ^
Failed to load historical trades from bitcoincharts

I have been getting this all weekend for Bitstamp too. 

That's normal, Bitstamp fucked up their API without any notice.

[lky_svn]

Hi,

Using MtGox, I get NaN errors when using EUR...
USD seems to be working fine.

Enabled verbose to check what's going on. With USD I get:

Code:

2013-07-30 09:59:29 (DEBUG):    calced EMA properties for new candle:
2013-07-30 09:59:29 (DEBUG):             short ema 101.048
2013-07-30 09:59:29 (DEBUG):             long ema 101.037
2013-07-30 09:59:29 (DEBUG):             diff ema 0.010
2013-07-30 09:59:29 (DEBUG):    fetching new trades for new bucket at Mt. Gox
2013-07-30 09:59:31 (DEBUG):    calculated candle: 0
2013-07-30 09:59:31 (DEBUG):    calced EMA properties for new candle:
2013-07-30 09:59:31 (DEBUG):             short ema 101.038
2013-07-30 09:59:31 (DEBUG):             long ema 101.033
2013-07-30 09:59:31 (DEBUG):             diff ema 0.005
2013-07-30 09:59:31 (DEBUG):    we are currently not in an up or down trend @ 100.981 (0.005)

When changing to EUR, I get something like:

Code:

2013-07-30 10:04:03 (DEBUG):    calculated candle: 1
2013-07-30 10:04:03 (DEBUG):    calced EMA properties for new candle:
2013-07-30 10:04:03 (DEBUG):             short ema NaN
2013-07-30 10:04:03 (DEBUG):             long ema NaN
2013-07-30 10:04:03 (DEBUG):             diff ema NaN
2013-07-30 10:04:03 (DEBUG):    fetching new trades for new bucket at Mt. Gox
2013-07-30 10:04:04 (DEBUG):    calculated candle: 0
2013-07-30 10:04:04 (DEBUG):    calced EMA properties for new candle:
2013-07-30 10:04:04 (DEBUG):             short ema NaN
2013-07-30 10:04:04 (DEBUG):             long ema NaN
2013-07-30 10:04:04 (DEBUG):             diff ema NaN
2013-07-30 10:04:04 (DEBUG):    we are currently not in an up or down trend @ 75.500 (NaN)

This is the config I changed:

Code:

config.normal = {
  enabled: true,
  exchange: 'MtGox', // 'MtGox', 'BTCe' or 'Bitstamp'
  currency: 'EUR',
  asset: 'BTC',
  tradingEnabled: false,

Simply changed the currency in there - and then the error appears.


Anybody had this issue?