I'm currently using Gekko to help me automate trading and follow the system that Goomboo posted. I don't know much about trading and there's still so much to learn, but I've noticed something during backtesting that I think is related to the latest posts.
When doing tests, does anyone change the number of initial candles to store? I took the H1 data from the last 5 months at BitcoinCharts (3570 candles), changed the format to what the backtester expects and tried this:
[...]
I'm wondering if there's really a need to change that setting or not. Note the huge change from 200 to 300 candles.
I am looking in to the data as to what kind of difference this makes, but do note:
The EMA method is supposed to start out with a history, the ideal case would be the complete history but since this is not practicle (and the difference decreases exponentially as you remove old history). If you don't start with a big history you aren't using pure EMA as you are not able to calculate the real EMA (a number which is built up using the complete history). Diabolicus
showed the EMA difference in EMA calculation between a big and a small history.
If you are looking at the profit as a result of different histories you are just comparing different kind of EMAs (different levels of pure EMA so to say) which each other. It may the case that an EMA without an history would be the most profitable in a backtest, but it pretty hard to turn that into conclusions.
Hope that this explanation makes sense.
Awesome bot! I love the backtesting feature. I'm getting an error with setting up email though, here's the console:
2013-08-13 23:44:50 (INFO): I'm gonna make you rich, Bud Fox.
2013-08-13 23:44:50 (INFO): Let me show you some Exponential Moving Averages
.
2013-08-13 23:44:50 (INFO): Using normal settings to monitor the live market
2013-08-13 23:44:50 (INFO): NOT trading with real money
2013-08-13 23:44:51 (INFO): Profit reporter active on simulated balance
2013-08-13 23:44:51 (INFO): Calculating EMA on historical data...
2013-08-13 23:44:58 (INFO): ADVICE is to BUY @ 96.709 (0.454)
2013-08-13 23:44:58 (WARN): ERROR SENDING MAIL { [Error: authorization.faile
d]
code: 3,
previous:
{ [Error: bad response on command 'AUTH']
code: 2,
smtp: '334 eyJzdGF0dXMiOiI0MDAiLCJzY2hlbWVzIjoiQmVhcmVyIiwic2NvcGUiOiJodHRw
czovL21haWwuZ29vZ2xlLmNvbS8ifQ==\n' },
smtp: undefined }
Hi,
i got exactly the same error after updating to the latest version.
Darn APIs that keep changing, working on it!