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

Re: Metastock Pro + Patch PRO652B.EXE



PureBytes Links

Trading Reference Links

<x-html><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;I guess since you CC'd it to the list you want some feedback......
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [snips]
<p>Essan Soobratty wrote:
<blockquote TYPE=CITE>&nbsp;
<br>Problem 1:
<br>-----------
<p>(A) The most current bar of the 60min chart is incomplete.&nbsp; i.e.
it will only reflect the data from the time I open the chart rather than
from the beginning of the data that has been collected.</blockquote>
I too had this problem until I a) installed the Pro652B and B) bought a
new machine.&nbsp; Both were done basically at the same time so I was unsure
as to which was the fix. &lt;g>&nbsp;&nbsp; Anyway, point being I don't
seem to have that problem anymore.
<blockquote TYPE=CITE>&nbsp;
<br>(B) The most current bar of the daily chart (constructed from 60min
data) <i>overwrites</i> the previous bar.&nbsp; To display a correct chart
I have to wait until after 10:30am an then force the chart to re-draw.</blockquote>
&nbsp;I've seen that on occasion but I've always been able to correct it
simply by closing/re-opening the chart at no time in particular.
<br>&nbsp;
<blockquote TYPE=CITE>Problem 2:
<br>-----------
<br>I do not think the following problem existed pre-patch....
<p>Lets say I am collecting SnP data from 9:30am est and I have configured
collection in 60min bars.&nbsp; Now lets say that I have to re-boot my
pc for some reason at 1:15pm.&nbsp; So I close open charts, close metastock,
close the file server and then the data server.&nbsp; But the problem that
I have is that the data for the partial 60min bar 12:30pm - 1:15pm is lost!!!!&nbsp;
Pre-patch I am almost certain that when "writing from cache to disk" on
closing the file server, metastock would capture the partial bar.</blockquote>
This always happens???&nbsp; Once is more than enough.&nbsp; I haven't
noticed this and until very recently (for about a month) I've had my share
of interruptions due to rain. (Finally got a good GTE tech who solved the
problem.)&nbsp; So I think I would have seen this. I guess you actually
looked in the Downloader to see if it captured the data?&nbsp; The reason
I asked is that once or twice, under exactly what circumstances I don't
recall, when I restored a chart the most current bars did not display but
they <i>were</i> captured in the Downloader.&nbsp; I don't think closing/re-opening
the chart helped, but I seem to recall that creating a temporary new chart
on the fly did work.&nbsp; The original chart was fine the next time I
opened Metastock.
<blockquote TYPE=CITE>ALSO: At the end of last week I was exchanging emails
with equis support on the issue on not being able to compress data into
bars of say 4hr (240min) intervals.&nbsp; I was hoping that this ball was
still in the air.&nbsp; Please advise.</blockquote>
We all want/need this.&nbsp; There's a huge gulf between 60 minutes and
daily bars. They gotta provide this.
<p>Good luck,
<br>Ken
<br>&nbsp;</html>
</x-html>From ???@??? Tue Jun 15 06:48:01 1999
Received: from listserv.equis.com (204.246.137.2)
	by mail05.rapidsite.net (RS ver 1.0.4) with SMTP id 08875;
	Tue, 15 Jun 1999 07:31:02 -0400 (EDT)
Received: (from majordom@xxxxxxxxx)
	by listserv.equis.com (8.8.7/8.8.7) id FAA27782
	for metastock-outgoing; Tue, 15 Jun 1999 05:10:28 -0600
X-Authentication-Warning: listserv.equis.com: majordom set sender to owner-metastock@xxxxxxxxxxxxx using -f
Received: from freeze.metastock.com (freeze.metastock.com [204.246.137.5])
	by listserv.equis.com (8.8.7/8.8.7) with ESMTP id FAA27779
	for <metastock@xxxxxxxxxxxxxxxxxx>; Tue, 15 Jun 1999 05:10:25 -0600
Received: from hme0.mailrouter02.sprint.ca (hme0.mailrouter02.sprint.ca [207.107.250.60])
	by freeze.metastock.com (8.8.5/8.8.5) with ESMTP id FAA03024
	for <metastock@xxxxxxxxxxxxx>; Tue, 15 Jun 1999 05:23:49 -0600 (MDT)
Received: from walter (spc-isp-mtl-58-6-177.sprint.ca [149.99.143.177])
	by hme0.mailrouter02.sprint.ca (8.8.8/8.8.8) with SMTP id HAA16593
	for <metastock@xxxxxxxxxxxxx>; Tue, 15 Jun 1999 07:11:30 -0400 (EDT)
Message-ID: <002f01beb720$1a125c80$b18f6395@xxxxxx>
From: "Walter Lake" <wlake@xxxxxxxxx>
To: "Metastock bulletin board" <metastock@xxxxxxxxxxxxx>
Subject: Volatility bands on Osc's
Date: Tue, 15 Jun 1999 07:13:30 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Sender: owner-metastock@xxxxxxxxxxxxx
Precedence: bulk
Reply-To: metastock@xxxxxxxxxxxxx
X-Loop-Detect: 1
X-UIDL: 2cf67ad782a1982ee7f64df29c5b562a.12

Walter - Here is the ELA for the indicator: RSI & Vol Bands:

{Hi Lenny ... Thanks for the code. The square brackets should probably be
round brackets. The code uses square brackets for yesterday [1], the day
before [2], etc.}

Input: Coefdwn[2.1],Coefup[2.3];

{Is there a range of coefficients given in her book? The
CoefficientDown(2.1) and CoefficientUp(2.3) get inserted into the formulas
below, just like in Metastock.}

Plot1[[Average[[RSI[Close,14]],6]]+[Coefup*[Average[TrueRangeCustom[[RSI[Clo
se
,14]],[RSI[Close,14]],[RSI[Close14]]],15]]],"Plot1"];

{The code separates True Range into 2 parts: first the True Range then the
Average. Whereas in Metastock you only use ATR. What is the input for the
average and the ATR? 6 and 15?}

Plot2[[Average[[RSI[Close,14]],6]]-[Coefdwn*[Average[TrueRangeCustom[[RSI[Cl
os
e,14]],[RSI[Close,14]],[RSI[Close,14]]],15]]],"Plot2"];

{As Adam suggested, the ATR will probably be calculated on the price and
then applied to the RSI indicator}

Plot3[[RSI[Close,14]],"Plot3"];

{Dump all the rest for the time being}

If CheckAlert Then Begin
  If Plot1 Crosses Above Plot2 or Plot1 Crosses Below Plot2
or Plot1 Crosses Above Plot3 or Plot1 Crosses Below Plot3
or Plot2 Crosses Above Plot3 or Plot2 Crosses Below Plot3
  Then Alert = True;
End;

I hope I transposed this correctly - Lenny