- ago
I wanted to do a walk forward analysis today, but unfortunately I can't do it. I always get the error message "Index was out of range. Must be non-negative and less than the size of collection. (Parameter 'index')". I pressed "load historical data" beforehand. However, I have noticed that it always wants to start the in-sample range a few days before the specified period, which is defined in the strategy settings area. Have I overlooked something or am I doing something wrong?


0
369
Solved
9 Replies

Reply

Bookmark

Sort
Glitch8
 ( 9.28% )
- ago
#1
Can you email me the strategy support@wealth-lab.com so I can have a try at reproducing? Can't reproduce using any of my local Strategies.
0
- ago
#2
The e-mail has just been sent to you.
0
- ago
#3
Got your file and looking into it. The strategy emailed has a different opt. parameter than the one on screenshot #2, just in case. I too couldn't reproduce the IOOR exception error message. Neither was I able to make WFO start the in-sample period before backtest's starting date.

However, the DataSet selected belongs to Norgate Data which I don't have. The closest is WealthData so I picked a dynamic DataSet and ran WFO as set in your picture #1 and it went just fine. Could you switch to different data providers and make some tests?
0
- ago
#4
I know that I have sent a different strategy. This is not a problem, as the error occurs with every strategy and with every data set (including the data from WealthLab). Since you can't reproduce it, I suspect the error is in my WealthLab. I have not yet tried whether it occurs without extensions (I suspect that some extension is causing the error - because of the NET8 update - / but it is only a guess). It seems to be related to the postponed start date of the insample period. However, this is generated by WealthLab and I cannot change it manually. Here is another example with one of the sample strategies included in WealthLab:





Or do you have another idea?
0
- ago
#5
It seems to be due to the finantic.optimizers extension I have removed it and it works again. Strange, as this extension has already been adapted to build 77 So there is probably still a bug in the extension.
0
Best Answer
- ago
#6
I have now reinstalled the finantec.optimizers extension and suddenly it works again. Very strange. The extension works again without any problems. Many thanks for the quick help.
0
- ago
#7
I must have been a bit hasty... The Adoescent Run just worked and suddenly this error message appears again. So there seems to be a bug in the extension after all. Best Metric, on the other hand, works.
0
Glitch8
 ( 9.28% )
- ago
#8
I pinged DrKoch on Discord to look into this one.
0
- ago
#9
Thank you Glitch!
0

Reply

Bookmark

Sort