Let me start by saying that Index-Lab is very useful and the results are interesting. I have noticed a gross usage challenge. I am trying to use Index-Lab with 30 minute data. I have multiple overlapping symbol sets, and multiple Index-Lab entries. What I notice is that it "updates" the symbols for every Index-Lab entry's every symbol. This takes a significant time. Is there a way to avoid having Index Lab try to update the same symbol multiple times?
Size:
Color:
Which Data Provider are you using for the constituent symbols, and, is on-demand off?
Size:
Color:
I am using Fidelity's data, 30 min bars, and on-demand is off. I start from the DataManager using the DataSets tab. Click on the Index-Lab 30-Minute datagroup. Then I click the "Update DataSet (Pricing) at the top of the screen.
I am doing 6 different index computations on 5 overlapping datasets. It happens that AAPL is in 4 of the 5 datasets. According to the output log that I just created, the code tried to update AAPL 24 times. After the updates were completed, then the index computations were done.
Size:
Color:
This issue was worked for Version 6.2. Are you using 6.2?
Size:
Color:
WealthLabPro 6.2.34.0 64-bit Edition running on Windows 7 home premium.
Size:
Color:
I just re-read your first post, and what I'm reading is that you have the same symbol in different DataSets and want to avoid multiple updates for the same symbol.
First thing is that it's my understanding (which can change) thatIndex-Lab should respect On-Demand. If On-Demand is disabled, it shouldn't be trying to update symbols.
However, if you run scripts that use Index-Lab symbols on different DataSets, one update/check will occur during the execution of the first symbol of each DataSet. Consequently, it follows that the same symbol could be updated/checked for each DataSet that contains it.
Size:
Color:
So if AAPL was check 4 times (once for each dataset) that might make sense. However, updating the dataset for each Index-Lab-Computation on a single data set makes it 6x4=24 times. I am hoping that there is a smarter way to do this on my part and/or a fix that makes this 6x more usagle.
Size:
Color:
QUOTE:
First thing is that it's my understanding (which can change) thatIndex-Lab should respect On-Demand. If On-Demand is disabled, it shouldn't be trying to update symbols.
Even with on demand updates completely suppressed (Y! provider v1.3.20), it happens as well.
However, the developers could have a good reason for making it work like that vs. aggregating symbols by provider, requesting updates in bulk, and only then updating custom indices.
Size:
Color: