[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Another calculation question



PureBytes Links

Trading Reference Links

> I had to move COMHCY7 to another indicator because COMH-BASICS reached its
> limit of 20 variables and shut me down.  That's why it was in the indicator
> with COMHACR.  The reason it wouldn't plot was because I made a typo in
> moving some indicators around after I had tested them.  The COMHCYY variable
> had a typo in it.  Fixed that and everything worked fine.

COMHCY7 {if an existing indicator} should then have been refenced according to
the fml() call function, eg Fml("COMHCY7") instead of my indicator's variable-assumption
FmlVar("COMH-BASICS","COMHCY7").

> Once I finish the conversion, I'm happy, it's just getting there that causes
> me all these problems.

It's part of the learning curve {+extra's} that many have to go through, pain at first, but
great in the end. { If you want to be that beautifull, you'll have to suffer for it too }.
It's good to see you getting there.......with your babes.

Regards,
Ton Maas
ms-irb@xxxxxxxxxxxxxxxx
Dismiss the ".nospam" bit (including the dot) when replying.
Homepage  http://home.planet.nl/~anthmaas


----- Original Message ----- 
From: "Guy Tann" <grt@xxxxxxxxxxxx>
To: <metastock@xxxxxxxxxxxxx>
Sent: maandag 21 augustus 2000 9:35
Subject: RE: Another calculation question


> Ton,
> 
> I had to move COMHCY7 to another indicator because COMH-BASICS reached its
> limit of 20 variables and shut me down.  That's why it was in the indicator
> with COMHACR.  The reason it wouldn't plot was because I made a typo in
> moving some indicators around after I had tested them.  The COMHCYY variable
> had a typo in it.  Fixed that and everything worked fine.
> 
> I also went through and deleted a bunch of old stuff to clean things out.
> I'll continue to delete historical indicators.
> 
> The latest problem that I'm working on is that I have several indicators
> that appear to calculate properly, up to a point.  What I mean is that the
> output of my Clipper program and MS' calculations are in total agreement,
> except for the last two days.  The calculations agree to 4 decimal places
> from 12/10/99 to 8/9/00.  For 8/10/00 and 8/11/00, the MS results are
> slightly off.  For the life of me I can't figure out what's happening here.
> I'm totally confused (again).  To insure complete compatibility I downloaded
> my MS data into a Clipper database.  This was to insure that both test data
> sets were identical.  I went back and checked the input data and they were
> in agreement.  Tomorrow, I'm going to go back and verify each individual
> variable again from the beginning to try to figure out what's happening.
> It's frustrating to say the least.  Every time I try to switch something
> into MS it turns into a hernia provoking exercise.  Once I finish the
> conversion, I'm happy, it's just getting there that causes me all these
> problems.
> 
> Thanks,
> 
> Guy
> 
> Never be afraid to try something new. Remember, amateurs built the ark,
> professionals built the Titanic.
> 
> -----Original Message-----
> From: owner-metastock@xxxxxxxxxxxxx [mailto:owner-metastock@xxxxxxxxxxxxx]On
> Behalf Of A.J. Maas
> Sent: Sunday, August 20, 2000 5:15 PM
> To: Metastock-List
> Subject: Re: Another calculation question
> 
> The formula contains an assigning of the variable COMHACR and now this
> variable contains a call to COMHCY7, which neither is a valid previously
> assigned
> variable COMHCY7 , nor is it possibly a call on a valid function COMHCY7.
> 
> Adjusted for this, then the below will plot :
> 
> COMHACR:= (
>                            FmlVar("COMH-BASICS","COMHCRR") +
>                            FmlVar("COMH-BASICS","COMHCYY") +
>                            FmlVar("COMH-BASICS","COMHCY4") +
>                            FmlVar("COMH-BASICS","COMHCR4") +
>                            FmlVar("COMH-BASICS","COMHCR7") +
>                            FmlVar("COMH-BASICS","COMHCY7")
>                          )
>                          / 3;
> COMHACR
> 
> Limitations are explained in the manual+help
> 
> -20 digits max for name positions/variable(p229)
> -20 functions max for assigned variables/indicator(p229)
> -1000 indicators max for custom indicators/PC(p284)
> 
> Regards,
> Ton Maas
> ms-irb@xxxxxxxxxxxxxxxx
> Dismiss the ".nospam" bit (including the dot) when replying.
> Homepage  http://home.planet.nl/~anthmaas
> 
> 
> ----- Original Message -----
> From: "Guy Tann" <grt@xxxxxxxxxxxx>
> To: "Metastock User Group" <metastock-list@xxxxxxxxxxxxx>
> Sent: zondag 20 augustus 2000 8:30
> Subject: Another calculation question
> 
> 
> > All and Ton, Martin, et al:
> >
> > Well, I'm moving along with my programming thanks to Ton, Martin and all
> > other contributors, but I've reached an impasse trying to get to one of my
> > more difficult calculations.  I am debugging each one of my calculations
> and
> > plotting its individual result in MS and comparing it to a debugging
> program
> > I've written in Clipper.  I feel that if I debug each individual
> > calculation, when I get to the end, everything should work.
> >
> > Well, that worked for while, until I reached the following calculation.
> > Something about the best laid plans of mice and men. :)
> >
> > COMHACR:= ( FmlVar("COMH-BASICS","COMHCRR") +
> > FmlVar("COMH-BASICS","COMHCYY") +  FmlVar("COMH-BASICS","COMHCY4") +
> > FmlVar("COMH-BASICS","COMHCR4") +  FmlVar("COMH-BASICS","COMHCR7") +
> > COMHCY7 ) / 3;
> > COMHACR;
> >
> > I have previously debugged COMHCRR, COMHCYY, COMHCY4, COMHCR4, COMHCR7,
> and
> > COMHCY7 and they all calculate properly and will plot if I set it up.
> This
> > calculation simply adds the six values and divides the total by 3.
> Nothing
> > sophisticated at all.  I then moved this variable calculation to another
> > blank indicator to try it.  It still didn't work, so I then tried to
> comment
> > out everything but one of the components and that didn't work either
> > (COMHCRR) but when I go back to that variable and set it up to plot, it
> > works fine.  I'm terminally confused here.
> >
> > The only thing I can think is that I've exceeded MS programming
> > capabilities, but you would think I would at least get an error message.
> I
> > mean we're not talking brain surgery here, so I assume that I'm doing
> > something stupid.  :) For instance, when I reached the point that I had
> > exceeded the calculations one indicator can support (something about
> binary
> > but I didn't write it down) I moved a bunch of the calculations to another
> > indicator.
> >
> > Is there a limit on the number of indicators that you can program in MS?
> I
> > wouldn't think I'm near any limit, but???  I have a bunch of old
> > calculations and system testers out there.  I hadn't planned on it, but
> > should I go out and delete them to make room for the newer stuff?
> >
> > TIA,
> >
> > Guy
> >
> > Never be afraid to try something new. Remember, amateurs built the ark,
> > professionals built the Titanic.
> >
> >
> >
>