whydifficult I realize I may be getting a little obnoxious about this, but I think I've found another bug in the backtester. When putting a unix timecode in the "from:" category the program misinterprets it (I think). The timecode is 1367989200 which should translate to 2013-05-08 05:00:00 but instead is read as 2013-08-16 17:00:00. Doing the same on the "to:" time works completely fine. Obviously this isn't a pressing issue, since I can still just edit the CSV files, it's just one I figured you should know about.
I noticed this too and assumed it had to do with UTC/GMT offsets.
Hmm that's very strange, might be the offset but I'll try to verify this. I don't mind at all, please let me know everything you find. I am keeping a list of stuff I need todo for Gekko.
Unfortunatly I have very little spare time right now, as soon as I have some I'll work on some issues with Gekko!Strange, I get the same issue by editing the CSV files to only the dates I want, but only when using daily candles... Hourly candles in the same date range work just fine.
Here is the candles file.
noted, will look into this.
Any plans to adding possibility to trade with non btc pairs as well as altcoin exchanges like cryptsy etc?
Yep, I am working on offering all required trade data for this soon.
---
My current situation offers me very little spare time to work on Gekko, as soon as I have some I will.
I have noted all issues and when I have some spare time I'll look into everything. In the meantime Gekko is open to pull requests, and when you find a bug it would be great if you could describe it as clear as possible, thanks!
I am working on a platform that provides market data for a
lot of different exchanges, the reason I have
some time to work on this and less on Gekko is because Wizbit is going to be part of my graduation project, which means I can do this in university hours so to say (but I don't have a lot of time to work on this either).