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

was: Booleans now: error adding price



PureBytes Links

Trading Reference Links

Thank you Gary and Jim Bronke!  Good point about using numerics as inputs so
you can change them via optimization.

I got the "Error adding price, date is less than previous date." when
pulling up the performance report on a very large (300k+ bars) 1 minute
interval file.  I've searched the purebytes archives (who do I thank?) and
I've found that other people have had the problem also.  There isn't a lot
said about the error other than it goes away if you cut your data file down
to less than about 135,000 bars.  Is there a better solution?

Is 135k bars the most TS2000i can handle for the advanced performance
report?  Has anyone successfully gotten the advanced performance report on a
data file significantly larger than 135k bars?

Aaron Schindler


----- Original Message -----
From: "Gary Fritz" <fritz@xxxxxxxx>
To: "Barrington Bear" <schindlertrading@xxxxxxxxxxx>
Cc: <omega-list@xxxxxxxxxx>
Sent: Thursday, September 20, 2001 5:21 PM
Subject: Re: Booleans


> > Q1.  This doesn't work:
> > upclose = iff(close>open, TRUE, FALSE);
> > The debugger says I need numeric expressions instead of TRUE and
> > FALSE.  Is there any solution other than making my upclose Boolean
> > variable numeric?
>
> iff() can return only numeric values, so you can't use it as you show
> above.  However you don't need it here.
>
> > Q2.  Could I abbreviate the upclose statement as
> > upclose = close>open;
> > like I could in C?
>
> Yes.  That's how I'd do it.
>
> > Q3.  When checking upclose can I say
> > if upclose then ...
> > or do I need to go
> > if upclose = TRUE then ...?
>
> "if upclose then" works fine.
>
> > Q4.  How about for false?  Can I say
> > if !upclose then ... ?
>
> Nope.  There's no negation operator in EL.  Use "if upclose = False".
>
> > Q5.  Should I skip Booleans altogether and just use 1 or 0 in a
> > numeric variable?
>
> Your choice.  I prefer booleans, unless it's an input -- then I often
> use numeric 1/0 values so I can change the value in an optimization.
> (Optimized inputs can only take on numeric values.)
>
> Gary
>
>