Sorry, I want to clarify that I think there's some confusion, ambiguity, and miscommunication:

The config.js (old code) in gekko is a liar:

In the original gekko code (which I forked) there is a "DEMA.js", and some related configuration options which are all completely mislabeled. It is not clear what "that thing" (method or algorithm) even is. One thing is clear though: THAT (old) CODE IS NOT AN ACTUAL DEMA of any kind whatsoever...

... and until this past 48 hours when I wrote a real DEMA implementation, gekko didn't actually implement DEMA at all. The "actually a DEMA-based calculation" code had to be named "x2 " such as "x2MACD" so it wouldn't be confused with the older, (mislabeled, wrongly named) "DEMA.js" based code.

---

This is why I've been spending so much time on bugfixes and code audits. There are some things in the code which are outright confusing or inaccurately named, despite the fact that they CAN technically be used generate valid advice or even do trading. It's just a peve, and mislabeling something which isn't DEMA as such is kinda weird. Moving forward, as I audit, document, bufix, and clean up everything, I really might just rebrand the forked codebase "lizardbot" or something.

At that point, one of the first things I'll do is delete DEMA.js and all the references to it since it's not actually DEMA:

http://www.investopedia.com/articles/trading/10/double-exponential-moving-average.asp

^ I really did implement some actual DEMA code in the past 48 hours... I didn't call it that though, since it conflicted with the ... thing (whatever it is)

so yes and no.

DEMA works, but I had to call it something else *facepalm*

whatever