Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 5,591
» Latest member: annahumphries
» Forum threads: 909
» Forum posts: 4,319

Full Statistics

Online Users
There are currently 77 online users.
» 0 Member(s) | 77 Guest(s)

Latest Threads
Howto: auto re-run Gekko ...
Forum: Guides
Last Post: Kaieysen
9 hours ago
» Replies: 5
» Views: 5,497
Custom Strategy ( bounty ...
Forum: Strategy Development
Last Post: AlicCoaldr
06-30-2020, 07:36 AM
» Replies: 5
» Views: 5,053
Chinese ATV Batteries
Forum: General Discussion
Last Post: StvenMartinezz
06-30-2020, 06:55 AM
» Replies: 0
» Views: 40
Best Website Designing Co...
Forum: General Discussion
Last Post: jeewangarg
06-20-2020, 09:58 AM
» Replies: 0
» Views: 106
Bittrex bug fixed?
Forum: General Discussion
Last Post: denvajo
06-19-2020, 11:29 AM
» Replies: 2
» Views: 1,319
Gekko with malware spotte...
Forum: Announcements
Last Post: ArthurJarvis
06-17-2020, 11:37 AM
» Replies: 2
» Views: 3,830
The Framing Effect and Co...
Forum: General Discussion
Last Post: freeforex20
06-14-2020, 01:34 AM
» Replies: 0
» Views: 112
Which game do you love?
Forum: General Discussion
Last Post: lucas21
06-11-2020, 07:13 AM
» Replies: 2
» Views: 451
Gekko Install Issue
Forum: Technical Discussion
Last Post: lordbofadeese
06-09-2020, 06:46 PM
» Replies: 0
» Views: 200
Libonomy Blockchain ( Dap...
Forum: Technical Discussion
Last Post: Taylor007
06-08-2020, 03:48 PM
» Replies: 0
» Views: 89

 
  Issue: 502 Bad Gateway when Backtesting
Posted by: gurkentier - 12-09-2019, 01:33 PM - Forum: Technical Discussion - No Replies

Hello,

I am running Gekko v0.6.8 and Gekko UI v0.2.3 and use Nginx as a reverse proxy.
I am encountering an issue when backtesting on bigger time ranges.
I did a backtest on a 11 month date range for USD <-> XRP on binance.
When I choose a range smaller than 1 month, the backtest works just fine.
If I choose a bigger range, the client gets an 502 Bad Gateway from my nginx.

The nginx error log says:
2019/12/09 08:26:40 [error] 3116#3116: *325 connect() failed (111: Connection refused) while connecting to upstream, client: 46.189.28.77, server: _, request: "GET /app.5e99ecf7.js.map HTTP/1.1", upstream: "http://[::1]:3001/app.5e99ecf7.js.map", host: "censored.com"

2019/12/09 08:26:44 [error] 3116#3116: *236 upstream prematurely closed connection while reading response header from upstream, client: 46.189.28.77, server: _, request: "POST /api/backtest HTTP/1.1", upstream: "http://127.0.0.1:3001/api/backtest", host: "censored.com", referrer: "http://censored.com/"


Using the RSI_BB_ADX_PEAK strategy with following params:
# SMA Trends
SMA_long = 220
SMA_short = 21

# BULL
BULL_RSI = 29
BULL_RSI_high = 76
BULL_RSI_low = 31

# BEAR
BEAR_RSI = 27
BEAR_RSI_high = 55
BEAR_RSI_low = 24

# MODIFY RSI (depending on ADX)
BULL_MOD_high = 7
BULL_MOD_low = -10
BEAR_MOD_high = 21
BEAR_MOD_low = -7

# ADX
ADX = 17
ADX_high = 75
ADX_low = 26

# Stop Loss
Stop_Loss_Percent = 15


With candle size of 5 minutes and a warmup of 220.

Is there anybody having the same issues and / or knowing a solution for it?

Thank you in advance


  Leading Diagonal
Posted by: freeforex20 - 11-25-2019, 04:50 PM - Forum: General Discussion - No Replies

 
Leading Diagonal
When diagonal triangles occur in the wave 5 or C position, they take the 3-3-3-3-3 shape that Elliott described. However, it has recently come to light that a variation on this pattern occasionally appears in the wave 1 position of impulses and in the wave A position of zigzags. The characteristic overlapping of waves 1 and 4 and the convergence of boundary lines into a wedge shape remain as in the ending diagonal triangle. However, the subdivisions are different, tracing out a 5-3-5-3-5 pattern. The structure of this formation (see Figure 1-20) fits the spirit of the Wave Principle in that the five-wave subdivisions in the direction of the larger trend communicate a "continuation" message as opposed to the "termination" implication of the three-wave subdivisions in the ending diagonal. Analysts must be aware of this pattern to avoid mistaking it for a far more common development, a series of first and second waves. The main key to recognizing this pattern is the decided slowing of price change in the fifth subwave relative to the third. By contrast, in developing first and second waves, short term speed typically increases, and breadth (i.e., the number of stocks or subindexes participating) often expands.
 
Figure 1-21 shows a real life example of a leading diagonal triangle. This pattern was not originally discovered by R.N. Elliott but has appeared enough times and over a long enough period that we are convinced of its validity.


  GDAX Users?
Posted by: LoNgTuRd - 11-24-2019, 02:54 AM - Forum: GDAX - No Replies

Is anyone having any sucess with GDAX at all? I understand the importing of data is slow, i have read somewhere that there is a time limit built into the Coinbase API that restricts how often the bot can request data. I cant help but notice that there are only 3 posts in the GDAX section though. Surely there has to be more users. Coinbase is the only US friendly exchange  that supoorts small trades, right?


  Error compiling gekko bot please help!!!!!!
Posted by: kirillkiselev82 - 11-23-2019, 09:23 AM - Forum: Technical Support - Replies (1)

While trying to compile gekko bot under manjaro linux I the error I get please any suggestion?



Attached Files
.jpeg   WhatsApp Image 2019-11-22 at 12.16.18 (1).jpeg (Size: 258.25 KB / Downloads: 20)

  Error compiling gekko bot please help!!!!!!
Posted by: kirillkiselev82 - 11-23-2019, 09:22 AM - Forum: Technical Discussion - Replies (2)

While trying to compile gekko bot under manjaro linux I the error I get please any suggestion?



Attached Files
.jpeg   WhatsApp Image 2019-11-22 at 12.16.18 (1).jpeg (Size: 258.25 KB / Downloads: 15)

  Show OHLC graph when Backtesting
Posted by: peterdehondt - 11-20-2019, 11:21 PM - Forum: Technical Discussion - No Replies

Hi, as far as i can see there is no possibility in the current version to show a OHLC graph when backtesting.
This would really be useful when developing strategies.

Where do i need to look when i want to add a OHLC graph in the code.

As far as i can tell the charts are being made in :

gekko/web/vue/src/d3/chart3.js

so i would need to create a similar setup which renders a OHLC chart.
But from where does the chart3.js function get the data needed to chart?


  How to trade BTC/USDT (so use BTC as currency and USDT as asset?)
Posted by: opoloko - 11-18-2019, 04:49 PM - Forum: General Discussion - No Replies

Hi all

possibly a newbie question but I can't see how to do it (or if it's simply not needed)..I updated the currencies in Gekko (latest) with the script for my exchange, they got updated (Binance by the way) but I can't find a way to select BTC as currency and USDT as asset.

I basically want to accumulate USDT using BTC.

How to do that? I have BTC already on the exchange, so I'd like first trade to be a sell and for Gekko to maximise and calculate my profit/loss considering the USDT amount...


  Extract difficult market situation timeframes
Posted by: mczero - 11-18-2019, 10:34 AM - Forum: Strategy Development - No Replies

Hey crypto trading guys,

I am experimenting a bit with japonicus (brute force strategy parameters with a genetic evolution approach). 
There often seem to be problems with overfitting while using gekko in live trading (I am still only backtesting).


Now I had the idea (link to japonicus issue on github) to improve japonicus to do the following:
not only backtest for a specific timeframe, but also mixing in 5% or 10% into the tests with
timeframes that are particular difficult to handle for strategies. 

For this, we have to get our hands on market times that match this criteria. How do we get there?

Say, we have a strategy relying on the RSI indicator, and parameters for a specific timeframe, three month, one year, whatever.
It is doing extremely good (overfitted?) in that specific timeframe, and when we look at the trading history, 
there are some days (or a week) in the timeframe where it does particularly bad, no matter how good this strategy/parameter pair was
at the end. 

Then we have a second strategy, based on Bollinger Bands, and parameters that are very good for a specific timeframe, too.
But even there are times when the strategy isn't working very good with the market situation.

Perhaps the code of those strategies could be modified to write time periods to CSV when it is not doing a good job.

Then, when some CSVs are collected, they could be run through a script which overlays the data of all CSVs and looks for equality.
The result of this could then be fed to japonicus as particular difficult market times.

Therefore, I am interested in thoughts on this approach and how a strategy could be modified to write out such a CSV.
And perhaps some strategy/parameter pairs that did very well in the past, with the specific timeframe they were used and measured at. 
Can be from 2018/2017, so no one has to reveal his strategy portfolio that he uses today.

Of course it could be that my thinking is too complicated and there is an easier solution for this. I am just beginning with gekko and getting to a
viable live trading solution, so bear with me.

Have a nice week!


  Gekko Email orders
Posted by: Neil - 11-16-2019, 01:59 PM - Forum: General Discussion - Replies (2)

Good morning all,

Do you think it would be possible to trigger the purchase or sale through an email alert, (tradingview alerts for example).

For example as did the developer below :

https://github.com/jsappme/tradingview-a...nce-trader

Thank you in advance for your answers !


  tulip
Posted by: heffzz - 11-14-2019, 11:48 PM - Forum: Technical Support - Replies (1)

Error: non-error thrown: 
   ERROR: Tulip indicators is not enabled
  
      at Object.onerror (/home/pi/gekko/node_modules/koa/lib/context.js:105:40)
      at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:189:7)

uncaughtException TypeError: Cannot read property 'tsf' of null
    at AsyncIndicatorRunner.addTulipIndicator (/home/pi/gekko/plugins/tradingAdvisor/asyncIndicatorRunner.js:145:16)
    at Base.addTulipIndicator (/home/pi/gekko/plugins/tradingAdvisor/baseTradingMethod.js:226:29)
    at Base.bound [as addTulipIndicator] (/home/pi/gekko/node_modules/lodash/dist/lodash.js:729:21)
    at Base.init (/home/pi/gekko/strategies/VmaPredict2.js:75:14)
    at Base.bound [as init] (/home/pi/gekko/node_modules/lodash/dist/lodash.js:729:21)
    at new Base (/home/pi/gekko/plugins/tradingAdvisor/baseTradingMethod.js:69:8)
    at Actor.setupStrategy (/home/pi/gekko/plugins/tradingAdvisor/tradingAdvisor.js:61:19)
    at Actor.bound [as setupStrategy] (/home/pi/gekko/node_modules/lodash/dist/lodash.js:729:21)
    at new Actor (/home/pi/gekko/plugins/tradingAdvisor/tradingAdvisor.js:23:8)
    at load (/home/pi/gekko/core/pluginUtil.js:98:22)