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

Re: [Norton AntiSpam] Re: maxbarsback ?



PureBytes Links

Trading Reference Links

Bob and Clyde,

Thanks for the input. Clyde, what I am working with is just a cycle length,
not continually growing. Plotting in arrears is not really necessary I don't
think for monthly data, however the same code I use for daily and intraday,
with holidays, etc. So it's easier to do history after all the holidays are
known. Bob, what you described is what I feared. I guess what I need to do
is rewrite the code to work without history...or...:-) ... I may have
outfoxed them... By copying the dow eod data file (since '29) to whatever
other file name, then reloading the file on startup, I get history since
1929 that works for outsmarting the barsback engine, and for my purpose, the
data doesn't matter. Seems to work so far.

Best,
Chris


----- Original Message ----- 
From: "Bob Fulks" <bfulks@xxxxxxxxxxxx>
To: "Chris Cheatham" <chris@xxxxxxxxxxxxxxxxxx>
Sent: Saturday, January 07, 2006 5:37 PM
Subject: [Norton AntiSpam] Re: maxbarsback ?


> It sets it to the maximum of the number of bars back you could reference
either in a look-back loop or plotting back in time even if your code would
never do that.
>
> For example,
>
> if LastBarOnChart then begin
>    Plot[100](Close, "C");
> end;
>
> will require a MaxBarsBack setting of 100 even though might have 1000 bars
of data on the chart.
>
> Very painful! I wish they would dynamically determine the MaxBarsBack
requirement and simply give a run-time error message if you violate it...
>
> Bob Fulks
>
>
> At 03:38 PM 1/7/2006, you wrote:
>
> >I am having an issue with maxbarsback. It is requiring far more bars back
> >than logically it should per the code. Further the indicator in question
> >uses monthly charts, where data sufficiency is an issue, and so I can't
just
> >add more bars to solve it.
> >
> >The biggest issue seems to be arising out of a loop that plots past
values
> >in arrears after a period of time has passed. The code never does this on
> >currentbar=1, but maxbarsback appears to be allowing for a  maximum
> >"plotting in arrears"  at cb=1 that never happens nonetheless. It does
not
> >matter whether it is set to auto or manual. Removing this section of code
> >helps some, however even with this out it is taking several years of
monthly
> >bars more than it should.
> >
> >Does anyone have a list of what maxbackbars checks? Any ideas? I am
clearly
> >missing something.
>
>