|
PureBytes Links
Trading Reference Links
|
You could try this if you need the close price later
Myclose = C;
c=v;
plot(macd(12,26),"",4,1);
C = myclose;
<font size=3 color=teal
face="Times New Roman">Cheers,
Graham
<font size=2
color="#339966" face="Times New Roman"><font
color="#339966">http://groups.msn.com/ASXShareTrading
<font size=2
color="#339966" face="Times New Roman"><font
color="#339966">http://groups.msn.com/FMSAustralia
<span
>-----Original Message-----
From: Jayson
[mailto:jcasavant@xxxxxxxxxxxx]
Sent: Thursday, 17 April 2003 9:36
PM
To: amibroker@xxxxxxxxxxxxxxx
Subject: RE: [amibroker] Dynamic
indicators
<font size=2
face="Times New Roman">
<font size=2 color=blue
face=Arial>A
workaround would be
<font size=2
face="Times New Roman">
<font size=2 color=blue
face=Arial>c=v;
<font size=2 color=blue
face=Arial>plot(macd(12,26),"",4,1);
<font size=2
face="Times New Roman">
<font size=2 color=blue
face=Arial>of
course this fails if you need actual closing data elsewhere in the code......
<font size=2
face="Times New Roman">
<font size=2
face="Times New Roman">
<font size=2
face="Times New Roman">
<font size=2 color=blue
face=Arial>Jayson
-----Original Message-----
From: uenal.mutlu@xxxxxxxxxxx [mailto:uenal.mutlu@xxxxxxxxxxx]
Sent: Thursday, April 17, 2003
8:25 AM
To: amibroker@xxxxxxxxxxxxxxx
Subject: [amibroker] Dynamic
indicators
<font size=2
face="Courier New">Hi CS, DT and all,<font
face="Courier New">
I too would like dynamic (user modifyable) args to
internal functions. For example the MACD and
SIGNAL
functions work only on the Close price. It would
be a
plus if user could override the default Close
array it internally uses.
The function prototypes then would look like:
MACD(fastperiod = 12, slowperiod = 26,
sourcearray = Close);
SIGNAL(fastperiod = 12, slowperiod = 26,
signalperiod = 9, sourcearray = Close);
(here the last param was added).
then such things like the following would be
possible:
MACD(12,26,C) > MACD(12,26,EMA(C, 9));
or you could create the MACD for volume etc... :-)
UM
----- Original Message -----
From: "DIMITRIS TSOKAKIS"
<TSOKAKIS@xxxxxxxxx>
To: <amibroker@xxxxxxxxxxxxxxx>
Sent: Thursday, April 17, 2003 2:01 PM
Subject: [amibroker] Re: AmiBroker 4.31.0 BETA
Question
> CS,
> something must be more clear:
> Do you speak for a variable period for
RSI(periods) or for the RSI of
> another function?
> When we write RSI(12), we mean RSI calculated
on Close, periods=12.
> An example of variable period should be like
> per=10+cum(1)%10;
> W=RSI(per);
> It will not work, since built-in RSI() does
not accept variable
> period.
> The second case is to apply the RSI
transformation on another
> function, say Stochastics.
> This is already included through the
RSIA(Array,periods) function,
> but still for a fixed period.
> It would be better to be more specific, which
improvement do you ask.
> DT
> --- In amibroker@xxxxxxxxxxxxxxx,
"CS" <csaxe@xxxx> wrote:
> >
> > Since converting some of my systems to
dynamic parameter input, my
> success (profits) has increased dramatically.
> > Unfortunately, most people don't know
the difference between
> dynamic (variable) and static (constant)
parameter inputs.
> > Simplistic Hint: Static-
RSI(14); Dynamic- RSI( ATR(3) );
> >
> > I have asked TJ to go back and re-work
indicators and functions to
> accept dynamic inputs, but he said that only
three other people had
> asked for the same thing, so it is low on his
priority list. So, I
> have had to resort to manually coding each
indicator/function in
> script, and script sucks. Error messages
while debugging are so
> vague, that they are useless.
> > The recent inclusion of native AFL
looping and flow control will
> help.
> >
> > There are some functions that accept
dynamic input such as HHV,
> LLV, Sum, Ref, AMA, AMA2, WMA, DEMA, TEMA and
MA.
> >
> > It would be nice if all new
functions/indicators created would
> accept dynamic inputs.
> >
> > -CS
> > ----- Original Message -----
> > From: Fred
> > To:
amibroker@xxxxxxxxxxxxxxx
> > Sent: Wednesday, April 16,
2003 4:26 PM
> > Subject: [amibroker] Re:
AmiBroker 4.31.0 BETA Question
> >
> >
> > I believe LinRegSlope takes
as it's second argument a NON time
> > variant argument or a
constant NOT an array like for example AMA
> > would. I don't know but
I supect the code I put in my original
> post
> > won't work any way or if it
has a chance of working I wouldn't
> know
> > how to modify it so it does,
maybe
> >
> > LRS = LinRegSlope(close[ i
], HilbertPeriod[ i ]);
>
>
> ------------------------ Yahoo! Groups
Sponsor ---------------------~-->
Send BUG REPORTS to bugs@xxxxxxxxxxxxx<font
face="Courier New">
Send SUGGESTIONS to suggest@xxxxxxxxxxxxx
-----------------------------------------
Post AmiQuote-related messages ONLY to:
amiquote@xxxxxxxxxxxxxxx
(Web page: <a
href="">http://groups.yahoo.com/group/amiquote/messages/)
--------------------------------------------
Check group FAQ at: <a
href="">http://groups.yahoo.com/group/amibroker/files/groupfaq.html
Your use of Yahoo! Groups is subject to the <a
href="">Yahoo! Terms of Service.
Send
BUG REPORTS to bugs@xxxxxxxxxxxxx<span
>
Send SUGGESTIONS to suggest@xxxxxxxxxxxxx
-----------------------------------------
Post AmiQuote-related messages ONLY to:
amiquote@xxxxxxxxxxxxxxx
(Web page: <a
href="">http://groups.yahoo.com/group/amiquote/messages/)
--------------------------------------------
Check group FAQ at: <a
href="">http://groups.yahoo.com/group/amibroker/files/groupfaq.html
Your use of Yahoo! Groups is subject to the <a
href="">Yahoo! Terms of Service.
Yahoo! Groups Sponsor
ADVERTISEMENT
Send BUG REPORTS to bugs@xxxxxxxxxxxxx
Send SUGGESTIONS to suggest@xxxxxxxxxxxxx
-----------------------------------------
Post AmiQuote-related messages ONLY to: amiquote@xxxxxxxxxxxxxxx
(Web page: http://groups.yahoo.com/group/amiquote/messages/)
--------------------------------------------
Check group FAQ at: http://groups.yahoo.com/group/amibroker/files/groupfaq.html
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|