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).
I have gekko on two different computers to test a few things such as this. On both computers I have imported a few coin pairs. On one computer when I backtest (logging values on .update() while) and compare the low+high+close/3 of any candle, it appears to not match TradingView candles by usually a few tenths of a decimal. On the other computer it matches up exactly. The value differences happen on all calculations so it appears that the timeframe of the candles are mismatched or data within is. It is causing my paper trading to show different buy/sell times then what my other computers gekko/tradingView shows for buy/sell.
The not lite version? I had some dependency errors about stuff being deprecated when installing. Will attempt again to gather error message, or do I need lite?
Hello. I'm a new gekko user. I've performed a couple of backtests but something is wrong with the results' time frame. My database range is 3 months, but somehow the results I get on the graph are always depicted as only 1 day long. I have tried different pairs (all from Poloniex) with different strategies, but all gave me the same error. The attached screenshot illustrates the results. Please note the low volume of trades (37) in the supposedly 3 month period. Any help is deeply appreciated.
Weird thing is when I remove the coin pair data so that I get all the data from the exchange, I don't have the error. This happens with other coin pairs as well.
--UPDATE--
The error was coming from:
line 464: var state = stream._writableState;
in gekko-stable\node_modules\are-we-there-yet\node_modules\readable-stream\lib\_stream_writable.js.
I updated the line to just be = true and I no longer get the error. Can someone tell me why this is happening? My normal language is C# and this doesn't make sense to me. Also, anyone know the correct fix to make for it?
I'm looking for some advice on how to get this strat to log in CLI the current indicator values & current price on every candle tick. I have included the strat code below, if someone could help me i would appreciate it massively...
When running imports from the Web UI I was getting data stored in the \history folder. When running imports using commandline via node gekko --config config.js --import, it doesn't appear that data is being saved anywhere. Am I doing something wrong? The data is showing trades being processed and eventually gets to "Done importing!".
So, I have been doing a lot of research regarding setting up trading bots and algorithmic trading.
I have seen a few times, mentioned mostly in random forum posts, that javascript should be avoided for financial applications, due to floating point numbers. The responses would rather suggest the use of Python, or C++ for trading bot.
My question is, has javascript evolved to now be able to handle floating point numbers? (which i think are decimals?)
If not, how does Gekko work around this?
Thanks in advance, this topic has got me interested more than anything else has in my 23 years of life.