Hi,

does anyone else ever see two strategy updates one after the other as if the 'check' function of your strategy is being called twice instead of once? Looks something like this for me (using NNv2):

2018-08-23 10:42:37 (DEBUG):
       Current market: bear
       Percent change predicted: 0.10299030411228689
       Current price: 0.00077024
       Last buy price: 0
       Current position: short
2018-08-23 10:42:37 (DEBUG):
       Current market: bear
       Percent change predicted: 0.08582525343061481
       Current price: 0.00077024
       Last buy price: 0
       Current position: short

Hi there,

due to me having to restart my bots quite a bit at the moment due to bugs I was wondering if it was possible to pass along the 'exposed' variable or the portfolio using 'portfolioValueChanged' or 'portfolioChanged' events so that my strategy knows whether I am long or not upon restart.

Thanks!

Hi guys,

I tried to use gekko with Kraken and it doesn't work. It tries to start work and after several minutes writes message about error (paper trading and trading bot).

Attached Files

  screen1.JPG (Size: 63.08 KB / Downloads: 15)
  screen2.JPG (Size: 75.63 KB / Downloads: 10)

Hello, 

Please, write the requirements for installing on the Windows 10 with the latest update. 
The requirements must be tested on the Windows 10.

Hi i'm a noob.
I installed Gekko on a VPS with ubuntu.

when i try to run gekko with:

Attached Files

  __bin_—_ssh_coach_142_93_110_16_—_287×95.png (Size: 109.9 KB / Downloads: 10)

Hey guys, i was wondering, since i don't have much space on c:, what should i do to put dataset on external drive and make it run on gekko ?
thanks guys!

I'm trying for a month with gekko, there is an exchange that supports where it can work, where to trade?

I tried with
kraken
binance
bittrex

[I might move this guide into the docs one day]

If you are developing your own strategy or want to gain more insights in what is happening you can easily use the commandline interface (CLI) to run a backtest quickly. By default these backtests include a lot of debugging information which you can use to understand what is going on inside the strategy you are running.

This guide assumes you have historical data available (imported previously or obtained from a live gekko).

Step 1: create a config file

Copy gekko/sample-config.js into gekko/config.js

Step 2: configure your config

Open up the gekko/config.js file with a text editor (sublime is excellent, free and runs on all major OSes).

- Search for "config.watch" and replace exchange, currency and asset with the market you want to backtest over.
- Search for "config.tradingAdvisor" and set method to your strategy, candleSize to the type of candles you want (in minutes, hourly candles means filling in 60).
- [optoinally] Search for "paperTrader" and configure the slippage and spread according to the market. If you are trading on a big market (BTC/USD for example) the defaults are fine.

Step 3: run the backtest

- Open a terminal and navigate to the Gekko directory.
- Run the backtest by typing: node gekko -c config.js -b

Hi friends, my import data is so slow that isn't normal even with small period of time. Im using binance, i should import my API to import data faster ? what should i do to make it more fast ? My internet conection isn't that slow, to import data uses download and not upload right ?
You guys have some suggestion ? or i can download data with another extension ?

thanks! 

Hey All,

I'm having a few issues with gekko respecting the daterange in both UI and CLI. See the screenshots below for what I mean.
The CLI difference could be due to closing 1 candle past the set range, which is fine if this is how it's supposed to work. The UI is definitely wrong.
I'm on Gekko 0.6.5 and UI 0.2.3

UI

  Screen Shot 2018-08-15 at 11.14.10 AM.jpg (Size: 139.93 KB / Downloads: 10)

CLI

  Screen Shot 2018-08-15 at 11.16.01 AM.jpg (Size: 363.2 KB / Downloads: 3)