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

[amibroker] Re: Brain fried, How do I plot a zero line on my MACD



PureBytes Links

Trading Reference Links

Dennis,

For the record I have also encountered this problem.
Essentially, SBR can only be used to 'increase' the number of bars 'on the fly'. Lets pretend you have a conditional statement at the end of your code...

if (Param1)
{
SetBarsRequired(200,0)
}else{
SetBarsRequired(1000,0)
}

If you try this, by changing said parameter 'on the fly' you will see that once SBR is used to 'increase' the number of bars to 1,000 then it cannot be reduced again 'on the fly' without "restarting" the chart again.

SBR currently only allows on-the-fly change in one direction.
Shame because I have use to move it up and down on code depending on some value occasionally.

--- In amibroker@xxxxxxxxxxxxxxx, "bruce1r" <brucer@xxx> wrote:
>
> Dennis -
> 
> Close, but not quite.  If you were going to use SetBarsRequired() to
> control the lookback, it is CRITICAL that it be the LAST statement in
> the program.  If it is not, subsequent statements ( such as HHV() ) may
> add to the requirement.  If you want to see a detailed explanation of
> this, refer to Tomasz's QuickAFL article in the KB.
> 
> Regarding the issues that you described in your previous response to me,
> there are a couple of ways to deal with the issue that you are
> describing.  When the teenagers go to bed and its quiet later, I'll try
> to outline one.
> 
> -- BruceR
> 
> --- In amibroker@xxxxxxxxxxxxxxx, Dennis Brown <see3d@> wrote:
> >
> > Yes Tony,
> >
> > This is close to what I was referring to as the array solution, though
> > I would probably write it like this to make it symmetrical:
> >
> > minmax = LastValue( HHV( abs( m ), r ) );
> >
> > It would be interesting if we could have a faster operation such that
> > if we used a SetBarsRequired( r, 0 ) in the preceding statement to
> > reduce the range so the the range equaled the number of bars
> > specified, that the returned value would be a single number of the
> > result.  Hmmmmm.  If that mode were available, it would look like
> this:
> >
> > m = MACD();
> >
> > fb = Status("FirstVisibleBar");
> > lb = Status("LastVisibleBar");
> > r = lb - fb;
> >
> > SetBarsRequired( r, 0 )
> > maximum = HHV( abs( m ), r );
> > Plot( m, "MACD", colorRed, styleOwnScale, -maximum, maximum );
> > Plot(0, "", colorBlack, styleOwnScale, -maximum, maximum);
> >
> > Just a little brainstorming.
> >
> > BR,
> > Dennis
> >
> > On Jun 28, 2009, at 8:31 AM, Tony Grimes wrote:
> >
> > >
> > >
> > > Try this solution, array style:
> > >
> > > m = MACD();
> > >
> > > fb = Status("FirstVisibleBar");
> > > lb = Status("LastVisibleBar");
> > > r = lb - fb;
> > >
> > > minimum = LastValue( LLV( m, r ) );
> > > maximum = LastValue( HHV( m, r ) );
> > >
> > > Plot( m, "MACD", colorRed, styleOwnScale, minimum, maximum );
> > > Plot(0, "", colorBlack, styleOwnScale, minimum, maximum);
> > >
> > >
> > > On Sat, Jun 27, 2009 at 11:16 AM, Dennis Brown see3d@
> > > wrote:
> > >
> > >
> > > Maybe not...
> > >
> > > Through this discussion, the problem has been reduced to aligning
> the
> > > min/max range of a MACD styleOwnScale plot to another zero line
> > > styleOwnScale plot statement. Therefore, the only way to do this is
> > > to find the min/max values of the MACD function in the visible bars
> > > range and use those numbers in both plot statements, or make the
> MACD
> > > range symmetrical and then the zero line statement can be any
> > > symmetrical range.
> > >
> > > I am happy with my dual colored plot line at this point. However, to
> > > complete the original idea, I could use a simple loop to find the
> min/
> > > max numbers of the MACD, but I am now wondering if there is a
> "faster"
> > > execution way using array logic instead?
> > >
> > > It seems like a waist of time to create an array of the Min/Max over
> > > that range for all bars, then just use the last value. I use loops
> > > when I only want a single number result related to the Min/Max value
> > > over the last n bars only (like the visible bar range). Am I missing
> > > an opportunity to approach this in a more efficient way?
> > >
> > > BR,
> > > Dennis
> > >
> > >
> > >
> > > On Jun 27, 2009, at 9:06 AM, gmorlosky wrote:
> > >
> > > > maybe....
> > > >
> > > > IF ( MACDline == Signalline) // histogram value equals zero
> > > > X = lastvalue(MACDline-Signalline);
> > > > Plot (X,"", colorblack);
> > > >
> > > > --- In amibroker@xxxxxxxxxxxxxxx, Dennis Brown see3d@ wrote:
> > > >>
> > > >> Yes, I have it set to 100%. The absolute values of the indicator
> > > >> will
> > > >> vary wildly, depending on the price and volatility of the stock.
> I
> > > >> plot ES, so the values are quite large at times.
> > > >>
> > > >> BR,
> > > >> Dennis
> > > >>
> > > >> On Jun 26, 2009, at 5:58 PM, monitorit wrote:
> > > >>
> > > >>> If that's all you needed, the color change would be best. But, I
> > > >>> think the solution I suggested would work... you would still
> plot/
> > > >>> see value very high or low just within a section defined by
> > > pane*1/
> > > >>> minvalue [at least it has for me]. BTW, presently what is the
> > > upper
> > > >>> and lower bounds of the MACD in relationship to the height of
> the
> > > >>> pane? Is it 100% of the pane height?
> > > >>> Dan
> > > >>>
> > > >>> --- In amibroker@xxxxxxxxxxxxxxx, Dennis Brown <see3d@> wrote:
> > > >>>>
> > > >>>> Dan,
> > > >>>>
> > > >>>> This is what I usually do for indicators when I know the range
> of
> > > >>>> values. However, MACD is an unbounded indicator, so I don't
> know
> > > >>>> how
> > > >>>> large the values are. It is only the zero crossings and
> relative
> > > >>>> peaks that are useful info here.
> > > >>>>
> > > >>>> I just thought there would be some simple shortcut to actually
> > > >>>> scanning the visible bars for the min/max values to use in the
> > > plot
> > > >>>> statements. I think I will just switch colors of the MACD from
> > > red
> > > >>>> to
> > > >>>> green if it is above or below zero instead of resorting to yet
> > > >>>> another
> > > >>>> loop.
> > > >>>>
> > > >>>> Thanks,
> > > >>>> Dennis
> > > >>>>
> > > >>>>
> > > >>>> On Jun 26, 2009, at 4:40 PM, monitorit wrote:
> > > >>>>
> > > >>>>> Dennis,
> > > >>>>> Hi. You might try this- Place a value in minvalue section but
> > > >>>>> none
> > > >>>>> in maxvalue section [I think maybe a value like 2 equates to
> 1/2
> > > >>>>> pane height] of your MACD and zero plot statements.
> > > >>>>> Also,styleNoRescale in the zero plot statement. This worked
> for
> > > >>>>> me
> > > >>>>> when I wanted to plot a histogram and a dot on the top of the
> > > >>>>> histogram. Not sure if it works with a line. If it doesn't,
> you
> > > >>>>> could try plotohlc with H=max(0,my#) and L=min(0,my#).
> > > >>>>>
> > > >>>>> Dan
> > > >>>>>
> > > >>>>> --- In amibroker@xxxxxxxxxxxxxxx, Dennis Brown <see3d@> wrote:
> > > >>>>>>
> > > >>>>>> Hello,
> > > >>>>>>
> > > >>>>>> This must be simple, but my AFL brain is fried today. I have
> an
> > > >>>>>> MACD
> > > >>>>>> plot on top of my main price chart, and I want to plot a zero
> > > >>>>>> line
> > > >>>>>> over it. It is plotted as StyleOwnScale of course. I can't
> use
> > > >>>>>> StyleLeftAxis because I am using it for something else. I
> > > >>>>>> guess I
> > > >>>>>> could do something to figure out where the visible high and
> low
> > > >>>>>> values
> > > >>>>>> of the MACD are, but it seems like it should be easier than
> > > that.
> > > >>>>>>
> > > >>>>>> TIA,
> > > >>>>>> Dennis
> > > >>>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> ------------------------------------
> > > >>>>>
> > > >>>>> **** IMPORTANT PLEASE READ ****
> > > >>>>> This group is for the discussion between users only.
> > > >>>>> This is *NOT* technical support channel.
> > > >>>>>
> > > >>>>> TO GET TECHNICAL SUPPORT send an e-mail directly to
> > > >>>>> SUPPORT {at} amibroker.com
> > > >>>>>
> > > >>>>> TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
> > > >>>>> http://www.amibroker.com/feedback/
> > > >>>>> (submissions sent via other channels won't be considered)
> > > >>>>>
> > > >>>>> For NEW RELEASE ANNOUNCEMENTS and other news always check
> > > DEVLOG:
> > > >>>>> http://www.amibroker.com/devlog/
> > > >>>>>
> > > >>>>> Yahoo! Groups Links
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>> ------------------------------------
> > > >>>
> > > >>> **** IMPORTANT PLEASE READ ****
> > > >>> This group is for the discussion between users only.
> > > >>> This is *NOT* technical support channel.
> > > >>>
> > > >>> TO GET TECHNICAL SUPPORT send an e-mail directly to
> > > >>> SUPPORT {at} amibroker.com
> > > >>>
> > > >>> TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
> > > >>> http://www.amibroker.com/feedback/
> > > >>> (submissions sent via other channels won't be considered)
> > > >>>
> > > >>> For NEW RELEASE ANNOUNCEMENTS and other news always check
> DEVLOG:
> > > >>> http://www.amibroker.com/devlog/
> > > >>>
> > > >>> Yahoo! Groups Links
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > **** IMPORTANT PLEASE READ ****
> > > > This group is for the discussion between users only.
> > > > This is *NOT* technical support channel.
> > > >
> > > > TO GET TECHNICAL SUPPORT send an e-mail directly to
> > > > SUPPORT {at} amibroker.com
> > > >
> > > > TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
> > > > http://www.amibroker.com/feedback/
> > > > (submissions sent via other channels won't be considered)
> > > >
> > > > For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
> > > > http://www.amibroker.com/devlog/
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> >
>




------------------------------------

**** IMPORTANT PLEASE READ ****
This group is for the discussion between users only.
This is *NOT* technical support channel.

TO GET TECHNICAL SUPPORT send an e-mail directly to 
SUPPORT {at} amibroker.com

TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
http://www.amibroker.com/feedback/
(submissions sent via other channels won't be considered)

For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
http://www.amibroker.com/devlog/

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/amibroker/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/amibroker/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:amibroker-digest@xxxxxxxxxxxxxxx 
    mailto:amibroker-fullfeatured@xxxxxxxxxxxxxxx

<*> To unsubscribe from this group, send an email to:
    amibroker-unsubscribe@xxxxxxxxxxxxxxx

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/