|
PureBytes Links
Trading Reference Links
|
Guy,
You are most welcome. IMHO, its greatest strength is the ability to specify
that the time from one event(i.e. cross zero, attain a certain value, etc)
must be more(or less) than the time for another event. Hence the abilty to
arange the firing order. In short and sum, I use it all the time.
Jim
-----Original Message-----
From: Guy Tann <grtann@xxxxxxxxxxx>
To: metastock@xxxxxxxxxxxxx <metastock@xxxxxxxxxxxxx>
Date: Saturday, August 22, 1998 1:13 PM
Subject: RE: formula/exploration help
>Jim
>
>Thanks for that insight. Never even knew what this one did. Maybe I can
>figure out some way to cut down on my code.
>
>Guy
>
>
>> -----Original Message-----
>> From: owner-metastock@xxxxxxxxxxxxx
>> [mailto:owner-metastock@xxxxxxxxxxxxx]On Behalf Of Jim DeWilder
>> Sent: Saturday, August 22, 1998 9:48 AM
>> To: metastock@xxxxxxxxxxxxx
>> Subject: Re: formula/exploration help
>>
>>
>> Paul,
>>
>> Try using the Bars Since command (barssince) to accomplish your
>> exploration. The command is on page 220 of the MetaStock 6.0 manual. This
>> command allows you to specifically determine firing order of your
>> oscillators as well as whether each oscillator is true at the time the
>> conditions are met.
>>
>>
>>
>> From: Paul <drjeep@xxxxxxxxxxx>
>> To: Metastock@xxxxxxxxxx Com <metastock@xxxxxxxxxxxxx>
>> Date: Friday, August 21, 1998 6:23 PM
>> Subject: formula/exploration help
>>
>>
>> >howdy guys,
>> >
>> >I need to create an exploration filter in which a few conditions must
>> happen
>> >one by one.
>> >For example:
>> >within the last two weeks the following things happened in this
>> particular
>> >order
>> >1) secret oscillatorA fired, THEN
>> >2) super-secret oscB fired, THEN
>> >3) super-ultra-duper systemC fired
>> >
>> >Explorer checks for #1 then (and only then) #2 and so on
>> >
>> >Is that possible in MetaStock?
>> >
>> >thank you
>> >Paul
>> >
>>
>
|