+- Gekko Forum (https://forum.gekko.wizb.it)
+-- Forum: Gekko (https://forum.gekko.wizb.it/forum-13.html)
+--- Forum: Technical Discussion (https://forum.gekko.wizb.it/forum-23.html)
+--- Thread: Crippled timespan in backtest graph (/thread-57429.html)
Pages:
1
2
Crippled timespan in backtest graph - bitbot - 07-24-2018
I've performed a couple of backtests but something is wrong with the results' time frame. My database timespan should be 1 year, but somehow the results I get on the graph are depicted as a couple of hours long (see screenshot). I have tried different pairs with different exchanges and strategies, but all gave me the same kind of crippled result. The attached screenshot illustrates the problem (i.e. the X-axis shows minutes instead of months). Please also note the low volume of trades (only 60) in the supposedly 12 month period. Any help is appreciated (I'm using Gekko v.0.6.2 by the way).
RE: Crippled timespan in backtest graph - askmike - 07-24-2018
Looking into it!
RE: Crippled timespan in backtest graph - askmike - 07-24-2018
I'm testing a fix here: https://github.com/askmike/gekko/pull/2360
If you want to try it out, see here: https://gekko.wizb.it/docs/installation/updating_gekko.html#Updating-the-develop-branch (also see recompiling the frontend)
RE: Crippled timespan in backtest graph - bitbot - 07-24-2018
(07-24-2018, 09:09 AM)askmike Wrote: I'm testing a fix here: https://github.com/askmike/gekko/pull/2360
If you want to try it out, see here: https://gekko.wizb.it/docs/installation/updating_gekko.html#Updating-the-develop-branch (also see recompiling the frontend)
Thanks a lot. Just to inform you that the roundtrips table seems to follow suit with the graph, so I believe it should also be fixed.
RE: Crippled timespan in backtest graph - askmike - 07-24-2018
I'm not able to reproduce that. Can you post another screenshot?
RE: Crippled timespan in backtest graph - bitbot - 07-24-2018
(07-24-2018, 02:29 PM)askmike Wrote: I'm not able to reproduce that. Can you post another screenshot?
Here you go! Just to be clear: What I meant was that there should be a lot more roundtrips in a 12 month period. The transactions shown are, apparently, related to a shorter timeframe, both in the graph and table. The dates in the table are also wrong (1970, instead of 2017?).
RE: Crippled timespan in backtest graph - askmike - 07-24-2018
(1970 means a second timestamp was parsed as a millisecond timestamp)
What browser and what OS are you using?
RE: Crippled timespan in backtest graph - bitbot - 07-24-2018
(07-24-2018, 04:05 PM)askmike Wrote: (1970 means a second timestamp was parsed as a millisecond timestamp)
What browser and what OS are you using?
Ok, sorry for the confusion. I'm using Firefox on MacOS 10.12.6.
RE: Crippled timespan in backtest graph - askmike - 07-25-2018
I think I know the reason of 1970 in the roundtrip table, that was a bug that was fixed between 0.6.2 and 0.6.3, can you try latest stable? If you try develop (and recompile the frontend, see here) your chart bug should be gone too!
RE: Crippled timespan in backtest graph - bitbot - 07-25-2018
(07-24-2018, 05:10 PM)bitbot Wrote:(07-24-2018, 04:05 PM)askmike Wrote: (1970 means a second timestamp was parsed as a millisecond timestamp)
What browser and what OS are you using?
Ok, sorry for the confusion. I'm using Firefox on MacOS 10.12.6.
I have upgraded my gekko version as instructed, and now my roundtrip table seems to be ok. However, the graph still remains offset.