|
PureBytes Links
Trading Reference Links
|
At least OR claims so. If the default setting for # bars to load is
still MaxBarsBack, you have to change that to a number large enough
for your indicator. If you had a disparity, you need to retest it
under SP3 and call them for an answer if it still exists. If you
benchmark it against a TS chart and the TS chart has tons of bars,
you may want to reduce the TS chart's number of bars first since RS
would exhaust your virtual memory with that many symbols and could
take 10 hours to load! Be very careful when playing with
firecrackers.
DonC wrote:
> Does this mean that RadarScreen NO LONGER has the problem
> of indicator calculation disparity ?
>
> donc
>
> > Subject: Re: RadarScreen
> > Date: Wed, 01 Dec 1999 15:41:49 -0600
> > From: Alan Mi <ami@xxxxxxxxxxxxxx>
> > To: Howard Jackson <hrjf4@xxxxxxxxx>
> > CC: omegalist <omega-list@xxxxxxxxxx>
> >
> >
> >> .. snip, snip ...
> >
> > I can see from the release notes and their special
> >technical mailings that they were bombarded by inquiries on this
> >issue "calculation result being different from that of TS".
|