Rank: Advanced Member
Groups: Registered, Registered Users, Subscribers
Joined: 7/25/2005(UTC)
Posts: 1,042
Was thanked: 57 time(s) in 54 post(s)
|
Hi to anyone at Equis who can shed a little light on this situation.
I've just run across a problem that I can only assume is a bug in MetaStock 9.1 EOD, or it's the result of a deliberate change somewhere along the road.
My symptom is that the generic piece of code for "last bar", LastValue(Cum(1))=Cum(1) , does not return a TRUE when run on a WEEKLY periodicity exploration (EOD data) unless the last bar specified for the exploration is the real last bar of the underlying data. With data loaded for 29 March and the exploration date set to 28 March I have the problem. When the explorer is set to "Most recent date" or 29 March everything works as it should, but changing to a specific date (other than 29 March) introduces the problem.
Since noticing the problem this morning I've established that MS 7.03 EOD does not fail in this way. I've also established that daily explorations do not exhibit the problem on either 7.03 or 9.1.
This exploration should always report 1.000 in column A, regardless of date or periodicity, just as it should always report a TRUE on the last data bar of a chart.
ColA:
LastValue(Cum(1))=Cum(1);
Is this a known bug with MS 9.1, and is it fixed with the new free update?
Thanks.
Roy
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users, Subscribers
Joined: 7/25/2005(UTC)
Posts: 1,042
Was thanked: 57 time(s) in 54 post(s)
|
Well, it seems that someone somewhere along the line might have decided that "even though it aint broke, let's fix it anyway".
I've tested 8.01 and it does exactly the same as 9.1
When the Explorer is running in weekly periodicity (for MS 8.01 and 9.X), setting the date to any day other than the last day of that week (usually Friday) disables the Explorer from treating Monday to Thursday as the last bar in terms of a bar count, unless it genuinely is of course. Only Friday's date is normally recognised as representing the last WEEKLY bar.
This is ludicrous. If I run a weekly scan based on Monday, Tuesday, Wednesday or Thursday data, I expect the scan to report accurately, based on the last weekly bar formed up to the specified date. What I don't expect is for the Explorer to interpret some other date than the one I specified as being the last available date.
I guess the rule for any Trade Equity users doing weekly testing is to use only Friday dates when specifying weekly scans up to a specific date. The "Lb" (last bar) variable does not trigger and execute end-of-data actions on weekly scans unless the specified ending date is also the real end of a week.
If my problem and subsequent findings have not been explained well, I apologise. This has been an uncomfortable day. It would still be nice to hear from someone in the know in due course that this either is a problem or was a problem. I'm curious to know why the Explorer now appears to take precedence over the user when deciding where the last week of EOD data ends.
Thanks.
Roy
|
|
|
|
|
|
| Users browsing this topic |
|
Guest (Hidden)
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
