[TUT] Backtesting with gekkoga

[Gryphon]

I think the fault is that the gekko shows the error when executing the command 

node –max-old-space-size=8192 server.js 

http://prntscr.com/ikuaew

I'd forgotten about that - I got the same error, but as I wanted to run gekko as the UI, I skipped that command and replaced it with "node gekko --ui" to get gekko running.

I'll update the tutorial

[gigirk]

Thank you very much, but I still get this problem and I do not know that you should also try to copy your file completely to avoid errors, but I always get the error of this type


http://prntscr.com/ilcc49

and 

http://prntscr.com/ilccg9


Thx 

---

I tried to place the strategy name of the file and I also tried the strategy name in the app but without results

[Gryphon]

Making Progress!

The error is being thrown after gekko tries to find data for backtesting. In your gekkoga config file have you checked that the exchange, currency and asset fields match local data that you have downloaded for backtesting?

[FeRm00]

First of all, thank so much for your great job!!! Also a great tutorail!!

I'm having a problem, Im not able to solve when I start running gekkoga about "Error:  socket hang up"

I paste a picture with the error. Any idea?

https://prnt.sc/ilicks

Thanks!

[gigirk]

That's good thanks to you! Look, let's go, shortly after, you cut with this error
http://prntscr.com/ilig7i

[Gryphon]

First of all, thank so much for your great job!!! Also a great tutorail!!

I'm having a problem, Im not able to solve when I start running gekkoga about "Error:  socket hang up"

I paste a picture with the error. Any idea?

https://prnt.sc/ilicks

Thanks!

You're welcome I think that error might be the timeout on gekko... another bit I missed from the first post! I'll add it now.

If you open gekko/web/vue/UIConfig.js you'll see the timeout setting. If the backtest takes longer than this period you'll get the socket freeze. I have set mine to 480000 which is 8 minutes.

That's good thanks to you! Look, let's go, shortly after, you cut with this error
http://prntscr.com/ilig7i

I'd have to see the gekko error log too, the gekkoga one doesn't tell us much there... Failing once started normally means an invalid parameter has been passed to gekko. Are your random generator limits all sensible?

[gigirk]

I have the timaut parameter removed as it says the configuration for the gekko server, should I replace it better than the 480000?

[donkykong017]

I have the timaut parameter removed as it says the configuration for the gekko server, should I replace it better than the 480000?

i put it back in even with the sever config. as i understand it it was added in later updates and not updated in the documentation site.

i set it at some high value, like 4h or something

[gigirk]

to see if this log will help

http://prntscr.com/iltuwk

thx

[Gryphon]

to see if this log will help

http://prntscr.com/iltuwk

thx

That happens when you have gekkoga set to scan for data, but in your local data you have two different date ranges. You either need to import data to bridge the date ranges available, as defined in the gekko log above, or specify the date range you want to test over in your gekkoga config file. I find it best to test within an hour or so of your data start and cut off points - sometimes it would crash if I tested to the exact times.