#3. "Runtime error: Index was out of range. Must be non-negative and less than the size of the collection". Do you, KrMitso, or anybody find out something aobut this?!! I got the same problem on static datasource folder when scanning. However, when i check the specific symbol which got runtime error on Strategy Window, it works fine.
Size:
Color:
Which Strategy? Data provider? Was your DataSet up to date? What about the DataSource composition? Data loading settings i.e. what number of bars are you loading? This, in short, is what welcomed when properly
Reporting a Problem?Without collecting all of that, it's harder to get to the root of the problem because this error per se is generalized (but has to do with the data). Assuming that you run a different WLP build than KrMitsos did half-year ago, your problem might be altogether different.
Size:
Color:
My strategy, simple less than 100 line. Fidel data provider. Yes, data uptodate. I scan on native 30-minutes datasource. Data -range is set 50+ on top of what my strategy required.
Size:
Color:
Well, given that I could suggest to double-check the strategy code.
Size:
Color:
Hi. When I back tested my intraday( 15 min bars) strategy on WLP, I got an error message box open up listing a bunch of symbols, and saying their "Index out of range" message. The back test seemed to finish consequently, and gave me the results. But are the results that I got erroneous because of this "error" that occurred in the process? And what does that message really mean?
Size:
Color:
Size:
Color: