In the strategy ranking window, backtests always seem to do a data update before executing the first strategy, even when Update Data on Demand is unchecked. Is there a way to avoid this?
Size:
Color:
Thank you for reporting. We're aware of the issue. Since it seems to happen only with Yahoo and MSN DataSets, try switching to Fidelity data for Rankings until it's fixed.
Size:
Color:
Very strange. I only use Fidelity as the data provider, never Yahoo or MSN. Anything else I should check?
Size:
Color:
QUOTE:
In the strategy ranking window, backtests always seem to do a data update
You said "always seems to". I'm observing that an on-demand update occurs with Fidelity DataSets in Rankings even when on-demand is disabled, implying that the update occurs only once, not always. Is that what you´re seeing?
Size:
Color:
No, when I hit "Begin" in the Strategy Ranking Window the bottom of the window always signals "Updating Data for:(DataSeries)". On a large data set it takes a long time (10 minutes) to change to the signal "Running Strategy: (Strategy Name). When I run the strategy in a Code Window, it "Collects the Data" in about 10 seconds and executes the strategy. Again, this is using only Fidelity data.
Size:
Color:
1. What's the scale of the DataSet?
2. What time of day are you running Rankings?
Either way, I'd appreciate it if you created a Support ticket for tracking and follow up. tia.
Size:
Color:
Dataset is Daily all data. I ran many tests over the weekend when the markets were closed and that's when it first occurred to me that something was up. I'll open a ticket.
Size:
Color:
Perhaps the problem occurs only on weekends and holidays then. Do you experience the problem during the week? That could be why I didn't see it when testing yesterday.
Size:
Color:
No, I just ran a Ranking using Fidelity static data and it requested updates for an outdated DataSet. Although the markets are still closed, it's worth noting that today is not a holiday/weekend.
Size:
Color:
Now I see it. It appears that it does the on-demand update only if the symbol isn't already up-to-date. We'll have to get it fixed in 5.5. Do we have a ticket for this one yet?
Size:
Color:
QUOTE:
Do we have a ticket for this one yet?
I don't think so.
Size:
Color:
Sorry guys. I've been out of town all week and BTW my windows system is dead and I am in re-install hell so if you still need the ticket let me know and I'll send it on as soon as I can. Thanks.
Size:
Color:
Please enter one, but no hurry. We're already too late for the 5.4 cut off.
Size:
Color: