Automated Daily Updates isn't working in WLP 5.3
Author: braddono
Creation Date: 2/7/2009 7:56 PM
profile picture

braddono

#1
I upgraded (theoretically!) from 5.1 to 5.3 last week, but I'm having problems I never had in 5.1, and I have not added any new datasets or any new strategies. I'd like to know if anyone else is experiencing these problems, and how to fix them. First, "Automated Daily Updates" isn't working. All week I have had to manually kick-off the data download. Second, when I attempt to chart some symbols, it crashes the software - and there is no information to explain what has caused the problem. Third, I get this message in the Strategy Monitor on some datasets. "Error(4):Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index." This message does not appear consistently - in other words, it's not always the same dataset or strategy that generates the error. If you know what to do, please let me know. Or, if there is a simple backward migrate to 5.1, I'd settle for going back just to be able to get my daily signals. Thanks.
profile picture

Eugene

#2
QUOTE:
First, "Automated Daily Updates" isn't working.

I was under the same impression when testing it yesterday.

QUOTE:
Second, when I attempt to chart some symbols, it crashes the software - and there is no information to explain what has caused the problem.


If you have an SMA with the period greater than bars loaded on the chart, then it's a known issue to be fixed in the upcoming 5.3 patch (among the rest; more details on the home page inside WLP.) Otherwise, we would need to know the symbols, the indicators, your data loading settings et al.

QUOTE:
Third, I get this message in the Strategy Monitor on some datasets. "Error(4):Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index." This message does not appear consistently - in other words, it's not always the same dataset or strategy that generates the error.


Is your dataset up to date? What are your data loading settings? Can you post the strategy code?
profile picture

braddono

#3
Thanks Eugene. My chart has 200SMA among others, so that could be blowing up. But it looks like discontinued symbols may also be a problem. Please try DISCA as an example. Datasets are all up to date, data loading settings are: Daily; All Data; 1000 shares

Here is the code for one strategy experiencing this problem (built using Rules, not built from Code):

CODE:
Please log in to see this code.
profile picture

Eugene

#4
QUOTE:
But it looks like discontinued symbols may also be a problem. Please try DISCA as an example. Datasets are all up to date, data loading settings are: Daily; All Data; 1000 shares

Thanks. No, the error with DISCA couldn't be reproduced. And the stock doesn't look like discontinued as of this Friday.
profile picture

Eugene

#5
QUOTE:
First, "Automated Daily Updates" isn't working. All week I have had to manually kick-off the data download.

Did you have at least one data provider checkbox selected in the list?
profile picture

Eugene

#6
QUOTE:
First, "Automated Daily Updates" isn't working. All week I have had to manually kick-off the data download.


1. Close the Data Manager window when update is scheduled.
2. Give Data Manager the full hour to update.
profile picture

Cone

#7
1a. Close the Data Manager window when update is scheduled.
1b. Or, just start the update yourself since you have the Data Mgr open.

This was actually done by design since the update function somewhat interferes with actions in the Data Manager. Anyway, since it's not intuitive that this is the case, this logic will be removed in the patch.
profile picture

marron

#8
"Second, when I attempt to chart some symbols, it crashes the software - and there is no information to explain what has caused the problem. Third, I get this message in the Strategy Monitor on some datasets. "Error(4):Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index."

-> try increasing the data range/bars set.

"Or, if there is a simple backward migrate to 5.1, I'd settle for going back just to be able to get my daily signals. Thanks. "

-> you can go back to 5.1 only if you save/backup 1.0.0.0 Data folder before you upgrade to 5.3 ( or if you have 5.1 running other system). GO back need not only uninstall 5.3 but also clean/fresh data folder.

Hope it helps.
This website uses cookies to improve your experience. We'll assume you're ok with that, but you can opt-out if you wish (Read more).