Hi,

I import daily data from a file and would like to use it on an intraday time frame.
I think I am doing something wrong here, because I only get 0 in the plot:

CODE:
Please log in to see this code.

I thought that the DataSeries would be filled on a daily scale and then be synchronized to intraday scale.

I'm afraid Daily to Intraday is another synch bug that's still not resolved. (Internal: 152661)

It seems that there are lots of bugs...not being able to see a bugs-list is not good. I wonder how reliable my backtests are in WLD5.

There are a few bugs that will eventually be worked out - unlike legacy versions, where the bug list is open but these bugs have zero chance of getting fixed. Your backtests are more reliable than in legacy versions for several reasons related to software architecture.

Have you tried the following workaround? Create the series on intraday scale, fill the series using FillSeriesFromFile, then create another one and keep assigning the value from the first series until there's a new item in the file (new data point i.e. new day). In other words, manual synchronization. You could probably merge the two steps if you patch FillSeriesFromFile (no need in two series).

QUOTE:
Have you tried the following workaround?

This depends on how probable the bug will be fixed in the next weeks!?

Edit1:
btw.: Eugene, where is your posting about global memory?

No, it will not be fixed in the next few weeks. Fidelity is working on a new release targeted for this Summer.

Edit1:
I removed it.

regarding your suggested workaround:

this doesn´t make sense to me. Then I could just calculate the series directly. This is something I get from another symbol on a daily scale and I cannot create this on intraday scale.
Any ideas for another workaround?

So, will this be fixed in the summer release?

Here is the solution, not a workaround:

In FillSeriesFromFile, change:

CODE:
Please log in to see this code.

to:

CODE:
Please log in to see this code.

Eugene, very nice. I can confirm that it is working now!

Glad it helped.

In Community.Components v2010.04, I'll add an overloaded call accepting a state of the DateTimeToBar's "exactMatch" parameter. It won't affect strategies that already employ FillSeriesFromFile.