I broke my MACD?
#1
Question 
Any idea what I could have done to my linux install that would have broken MACD (and seemingly only that strat)? 

Symptom: GUI Backtesting MACD yields no transactions, regardless of parameters, candles, duration of dataset, etc.

All other default strats seem to work.

I've wiped my Gekko directory, reinstalled, and still nothing. I've force npm reinstalled mathjs, nodejs, and others, but nothing's working. Is there a module I can force update that might fix this? Would appreciate some guidance if anyone has run into this before. I really don't want to wipe my AWS instance. :Smile

Also, I noticed I've been getting this if I try to run varPPO:

Code:
  xxx POST /api/backtest 500 141ms -

  Error: non-error thrown: [object Object]
      at Object.onerror (/home/bitnami/gekko/node_modules/koa/lib/context.js:105:40)
      at process._tickCallback (internal/process/next_tick.js:68:7)


Thanks,
storshun


Attached Files
.png   problem_macd.PNG (Size: 106.2 KB / Downloads: 6)
  Reply
#2
Very strange, unfortunately the current stable release does not properly report errors (when running certain things in the UI). I pushed a logging fix in the develop branch. Would you mind running that and trying again? Instructions are here: https://gekko.wizb.it/docs/installation/...lop-branch

That way we'll be able to see the actual error message. Thanks!
  Reply
#3
Already have that pull, and debug output from node gekko --ui isn't giving anything valuable. Also, the /gekko/logs folder is empty.
  Reply
#4
(08-27-2018, 07:32 AM)ClassicStyleATX Wrote: Already have that pull, and debug output from node gekko --ui isn't giving anything valuable.  Also, the /gekko/logs folder is empty.

Image of debug output.

.png   problem_part_2.PNG (Size: 60.93 KB / Downloads: 5)
  Reply
#5
That's just a warning. And there is nothing at the bottom? Very strange..
  Reply
#6
Yup, that's all. I'm going to try restarting the server in the morning, but after that, I'm kind of out of ideas beyond wiping the instance and starting over... Thanks for the help, Mike.
  Reply
#7
Would you mind running the same backtest over the commandline? That will definitely spit out a more usable error. Here is a guide: https://forum.gekko.wizb.it/thread-57581.html
  Reply
#8
All right, running in CLI, here's what I get:

Code:
   ______   ________  __    __  __    __   ______
  /      \ /        |/  |  /  |/  |  /  | /      \
 /$$$$$$  |$$$$$$$$/ $$ | /$$/ $$ | /$$/ /$$$$$$  |
 $$ | _$$/ $$ |__    $$ |/$$/  $$ |/$$/  $$ |  $$ |
 $$ |/    |$$    |   $$  $$<   $$  $$<   $$ |  $$ |
 $$ |$$$$ |$$$$$/    $$$$$  \  $$$$$  \  $$ |  $$ |
 $$ \__$$ |$$ |_____ $$ |$$  \ $$ |$$  \ $$ \__$$ |
 $$    $$/ $$       |$$ | $$  |$$ | $$  |$$    $$/
  $$$$$$/  $$$$$$$$/ $$/   $$/ $$/   $$/  $$$$$$/

       Gekko v0.6.5
       I'm gonna make you rich, Bud Fox.


2018-08-29 05:28:28 (INFO):     Setting up Gekko in backtest mode
2018-08-29 05:28:28 (INFO):
2018-08-29 05:28:28 (WARN):     The plugin Candle writer does not support the mode backtest. It has been disabled.
2018-08-29 05:28:28 (INFO):     Setting up:
2018-08-29 05:28:28 (INFO):              Trading Advisor
2018-08-29 05:28:28 (INFO):              Calculate trading advice
2018-08-29 05:28:28 (INFO):              Using the strategy: MACD
2018-08-29 05:28:28 (INFO):

2018-08-29 05:28:28 (WARN):     The plugin Mailer does not support the mode backtest. It has been disabled.
2018-08-29 05:28:28 (WARN):     The plugin Trader does not support the mode backtest. It has been disabled.
2018-08-29 05:28:28 (INFO):     Setting up:
2018-08-29 05:28:28 (INFO):              Paper Trader
2018-08-29 05:28:28 (INFO):              Paper trader that simulates fake trades.
2018-08-29 05:28:28 (INFO):

2018-08-29 05:28:28 (INFO):     Setting up:
2018-08-29 05:28:28 (INFO):              Performance Analyzer
2018-08-29 05:28:28 (INFO):              Analyzes performances of trades
2018-08-29 05:28:28 (INFO):

2018-08-29 05:28:28 (WARN):     The plugin Pushbullet does not support the mode backtest. It has been disabled.
2018-08-29 05:28:28 (INFO):     Scanning local history for backtestable dateranges.
2018-08-29 05:28:28 (DEBUG):    Available 48823
2018-08-29 05:28:28 (DEBUG):    Optimal 48822
2018-08-29 05:28:28 (INFO):     Gekko is able to fully use the local history.
2018-08-29 05:28:28 (INFO):     Gekko was able to find a single daterange in the locally stored history:
2018-08-29 05:28:28 (INFO):              from: 2018-07-26 07:44:00
2018-08-29 05:28:28 (INFO):              to: 2018-08-29 05:26:00

2018-08-29 05:28:28 (INFO):             WARNING: BACKTESTING FEATURE NEEDS PROPER TESTING
2018-08-29 05:28:28 (INFO):             WARNING: ACT ON THESE NUMBERS AT YOUR OWN RISK!

2018-08-29 05:28:28 (DEBUG):    calculated MACD properties for candle:
2018-08-29 05:28:28 (DEBUG):             short: 0.27232570
2018-08-29 05:28:28 (DEBUG):             long: 0.27097311
2018-08-29 05:28:28 (DEBUG):             macd: 0.00135260
2018-08-29 05:28:28 (DEBUG):             signal: 0.00198618
2018-08-29 05:28:28 (DEBUG):             macdiff: -0.00063358
2018-08-29 05:28:28 (DEBUG):    In no trend
2018-08-29 05:28:28 (DEBUG):    calculated MACD properties for candle:
2018-08-29 05:28:28 (DEBUG):             short: 0.27188285
2018-08-29 05:28:28 (DEBUG):             long: 0.27101555
2018-08-29 05:28:28 (DEBUG):             macd: 0.00086730
2018-08-29 05:28:28 (DEBUG):             signal: 0.00176241
2018-08-29 05:28:28 (DEBUG):             macdiff: -0.00089510
2018-08-29 05:28:28 (DEBUG):    In no trend


At the end, after letting everything run, there's no performance analysis.  It just ends after the MACD calculation for the final candle.
  Reply


Forum Jump:


Users browsing this thread: