Re: Problem: "Sell three days after bought...."

["Von Hef" <VonHef@xxxxxxxxxxxxx>]

 Nicholas,
   I have also dealt with this problem....here is what I usually do:
For every condition that is used for an entry, I set as a binary signal,
An example:
                       "Bs1:=If(Cross(C,Mov(c,13,e)),
                                  {then}1,
                                  {else}0);"

I would do this for all 3 then use the following for an exit:

                        "BarsSince(Bs1=1)>=3 and BarsSince(Bs2=1)>=3 and
BarsSince(Bs3=1)>=3"

Of course there are other ways to do this, I just used this example to spark
your
creative juices <g>.

  Adam Hefner


----- Original Message -----
From: Nicholas Kormanik <nkormanik@xxxxxxxxxx>
To: <metastock@xxxxxxxxxxxxx>
Sent: Wednesday, September 08, 1999 3:39 AM
Subject: Problem: "Sell three days after bought...."


>
> Another plea for help....  In the System Tester, the enter long signal I'm
> trying to study is actually a complicated **set** of signals.
>
> The exit long signal I want, just for testing purposes, is to "sell three
> days after buying."
>
> Hey, folks, seems pretty simple, doesn't it?  But MetaStock wants to make
> life difficult.
>
> If the enter long signal were one isolated indicator crossing, I could
> simply use the ref(signal, +3), to exit the trade.  But....  I have a
> complicated **set** of signals for entry, not one isolated indicator
> crossing.
>
> Now, how about using ref(**set**, +3)?  Seems a simple solution.
> Unfortunately, MetaStock doesn't apparently allow one to name a **set** of
> indicators like that; instead the System Tester seems to want me to state
> each sub-component separately, and do the ref(sub-signal, +??) for each.
It
> becomes really convoluted and messy.
>
> Do you folks have any help on this one?  Hopefully there's an easier way.
>
> Thanks,
> Nicholas
>
>