search

askmike / gekko

A bitcoin trading bot written in node - https://gekko.wizb.it/
MIT License
10.07k stars 3.95k forks source link

EMA *calculation* interval #6

Closed siergiej closed 11 years ago

siergiej commented 11 years ago

A lot can happen in an hour. Just look at the drop on mtgox a few hours ago. I don't know much about EMAs, but wouldn't it help to do the calculations more often? I'm not talking about decreasing the timeframe of the candle, just redoing the calculations for the last 100 ticks every few minutes with every tick lasting 1h.

One other thing to consider - what is the safe interval to not get banned by mtgox for to many requests.

Or this could be pure nonsense ;)

askmike commented 11 years ago

I can't find any documentation about rate limits on something other then the ticker in the Mt Gox V2 API (the one Gekko is using). I have an instance of Gekko running in advice mode with an interval of 1 minute on the same system as a Mt. Gox trading Gekko is running. They are requesting Mt. Gox for a couple of days non-stop now and I don't notice anything.

So you are suggesting to recalculate (or store) all EMAs for example every five minutes with all data from candles the interval before the 5 minute mark you are testing now? (so at 12:00 test against 11:00, 10:00 and at 12:05 test against 11:05 and 10:05...)

The current trading method is supposed to react slowly to new trends (EMA is always lagging behind the price) to make sure we aren't deciding on noise. The newer versions of the popular tradebots for chrome even have functions implemented so that the bot only sells after x thresholds all indicated the trend.

I think your proposal would cause more trades, but I don't see any way how this could improve the quality of the decisions made by Gekko?

This could be something for a new trading method, I don't think I should put this in the current one (the config is complicated enough as is).

siergiej commented 11 years ago

Ok, thanks fot the explanation. Time to close the issue :)