Re: [GT] continuing saga: scan.pl

["Robert A. Schmied" <ras AT acm.org>]

Robert A. Schmied wrote:
> Frank D. Gunseor wrote:
>
> > First off, I would really like to thank everyone whose has been 
> > helping me
> > get my bearing with the Genius Trader system, especially Robert, and
> > Gregory.  It is not always easy breaking into an existing system.
> >  
> > Anyway, here's what I have done to try and get the scan.pl to run for 
> > me..
> >  
> > I used Yahoo! Finance to download historical data and used Excel to 
> > process
> > the data into the correct format.
> >  
> > Here is my scan_symbol file:
> >  
> > SBUX
> > ADPI
> > CAT
> > AMED
> >  
> > Here is my scan_signal file:
> >  
> > Signals:Generic:Decrease {I:Prices CLOSE}
> > S:Generic:And {S:Generic:CrossOverUp {I:SMA 5} {I:SMA
> > 20}}{S:Generic:Increase {I:ADX}}
> > S:Generic:And {S:Generic:Above {I:Prices} {I:EMA 30}} {S:Generic:Above
> > {I:Prices} {I:EMA 150}}

<< big snip >>

> howdy again frank and the rest of you gt'ers ...
>
> well -- once again after monkeying with franks signal description
> not really sure what he was trying to define it dawned on me
>
> the Signals:Generic:Decrease is looking for a numeric value
> to compare against {I:Prices CLOSE}
> but it's being given a boolean signal from the S:Generic:And result

well i guess i shoulda read the pod before shooting my mouth off
-- the signal Signals:Generic:Decrease {I:Prices CLOSE}
is correct -- but the rest of the description is also being
passed to it -- that is what the complaint about bad number
of arguments is about.

if you want you can change the lines like:           VV
   warn "Bad number of arguments given to S:Generic:Increase !" if ($self->{'args'}->get_nb_args() != 1);
to something like
   warn "Bad number of arguments given to S:Generic:Increase\n"
    .   "got " . $self->{'args'}->get_nb_args()
    .   " arguments, expected 1\n"
    if ($self->{'args'}->get_nb_args() != 1);

in both GT/Signals/Generic/ Increase.pm and Decrease.pm.
just be sure to edit the function name in the warning message too.
and make sure to include the perl concatenate operator (.) as shown.
since i dislike the exclamation mark (!) in the orginal message
i removed it from the changed message. suit yourself.

with this change, the complaint will indicate just how many arguments
the signal thinks it's being handed and how many it expected.

frank -- care to describe what kind of signal you're trying to construct?

aloha

ras

<<snip>>