Gamestudio Links
Zorro Links
Newest Posts
Sam Foster Sound | Experienced Indie Game Composer for Hire
by titanicpiano14
15 minutes 50 seconds ago
Starting Zorro
by dpt
Today at 16:51
Lost Key
by jcl
Today at 13:58
Aum119 is ready
by Iglarion
Today at 13:09
Zorro on Linux
by Nanitek
Today at 11:08
AUM Magazine
Latest Screens
RPG PARTY
Triton Wing now available on Steam
AckCon'17: Lotter vs The World
Triton Wing
ZeaL
Who's Online
25 registered (JohanAu, Ch40zzC0d3r, Iglarion, dpt, gtell, Dbat, ezaffa, Dalla, firecrest, 2 invisible), 474 Guests and 4 Spiders online.
Key: Admin, Global Mod, Mod
Newest Members
vivekkumar, Hale75, victrades, htj, anufriyev
17781 Registered Users
Topic Options
Rate This Topic
#464855 - 03/15/17 16:01 Suffering from error 111
Joaquin Offline
Newbie

Registered: 04/29/13
Posts: 31
My script gives
Error 111: Crash in script: compramosSpread();

This error only happens after having run an optimization, with the "Train" option and then clicking on "Backtest".

If I comment out the lines
Code:
set(PARAMETERS);
DataSplit = 80;
NumWFOCycles = 10;



then the backtest works ok, no error is shown. I have looked for the obvious: errors in code, wrong array indexes or divisions by zero, but I think I don't have any of these...

I think the problem is in exceeding the stack size, and I think I know why.
This is the optimize line that makes the script fail:

Code:
int lookBacks[5] = {150,300,450,500,700};
LookBack = lookBacks[optimize(0,0,4,1)];



But if I change these lines with this, it doesn't crash:

Code:
int lookBacks[3] = {150,300,450};
LookBack = lookBacks[optimize(0,0,2,1)];



Do this make sense to you? Can I upsize the stack value in Zorro Trader?
I am only optimizing one parameter, with 3 possible values. Is it normal that with 5 possible values the stack gets full and makes the script crash?

Top
#464861 - 03/15/17 18:25 Re: Suffering from error 111 [Re: Joaquin]
jcl Offline

Chief Engineer

Registered: 07/22/00
Posts: 25816
Loc: Frankfurt
You can not exceed the stack size this way, so the problem is somewhere else. But it's a hint that is seems to depend on the lookbacks value. Check for exceeding the length of a series somewhere.

The crash happens inside the compramosSpread function, so it should be easy to find which line it is, by placing watch or print(TO_FILE,..) statements in the function.

Top



Gamestudio download | chip programmers | Zorro platform | shop | resources | magazine | manual | support faq | bugs | beta features

oP group Germany GmbH | Birkenstr. 25-27 | 63549 Ronneburg / Germany | info (at) 3dgamestudio.net