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

[EquisMetaStock Group] Thanks for the zigzag code warning, Roy



PureBytes Links

Trading Reference Links

Thanks for the help on the code, Roy. I hope to have a pretty good 
working code shortly.

I'm aware of the dynamic nature of the zigzag, especially on EOD 
data. I've read dozens of articles on it and various ways to handle 
the problems it can create. On intraday screens like 1, 5, 15 and 30 
minute time frames, I've tracked a zigzag function based on peak and 
trough bars and have found the movement of the indicator to be 
reasonable at the shorter distances between the price and the swing 
point, 1%, 2%, etc. The false readings and shifts seemed to be 
minimal. Obviously on those small distances you would get a lot of 
false trend changes. In this case 1% is my starting point. For what 
I'm doing it may drop to as low as 0.25%. 

On a few occasions I have recorded the first sign of the zigzag 
signal and then how many stayed stable intially and then how long it 
took for the rest to find their stablility point. Basically, the data 
I have collected seems to suggest that at the short distances and in 
tighter time frames, the dynamic nature of the indicator does not 
pose much of a problem. (At least that's what I've come up with. I 
may not have done my data collection properly. It's a little tricky.)

Based on that and the fact that this portion of the expert is not 
giving entry signals, just approximate price changes, I thought it 
would work well enough in this application. However, I would like to 
find another method of doing the same thing, if I can work out the 
code. 

I'll keep playing around with what you've given me and see where I 
can take it. I'm not the best programmer. Everything has to be 
learned by trial and error because the information MS provides is so 
minimal. 

I certainly agree with you that the zigzag should never be used on 
EOD and for back testing a system. That's worthless. However, I have 
noticed a lot of commentary on this board and other boards that lead 
me to believe a lot of people have a negative view of the peak, 
trough and zigzag, yet they don't really understand under what 
context their views should apply. I guess everyone interprets 
whatever they've read as gospel without doing any application testing 
themselves. I suppose the topic is always debatable. I've read a few 
comments that have lead me to believe the debate is over, and all the 
definitive analysis has been done--end of story. I don't think so, 
but I'll never change their minds.

Those invisible zigzag signals are always hard to deal with, but one 
of the tests I've done is to capture live charts with the peak and 
trough function alone and with validated peak and trough functions 
for comparison. Those results are interesting.

Thanks again for helping. I'm getting to be a better all the time but 
it's slow going. I have a lot ideas I can't code up yet so I have to 
do things in a much less efficient way.

Jack




--- In equismetastock@xxxxxxxxxxxxxxx, "Roy Larsen" <rlarsen@xxxx> 
wrote:
> Jack
> 
> I don't think using ZigZag is a good idea. Even if you get code 
that appears
> to do just what you want the dynamic nature of ZZ makes it 
virtually useless
> IMO.
> 
> I feel that using rock solid code like that below to track prices 
moving
> favourably is a better way to go. I haven't cracked how to signal 
moves
> across new 1% boundaries yet, but once the entry price is locked in 
it's
> just a technicality. The solution won't be too far away.
> 
>   {Long Trade Move}
> N:=If(Fml("PS Fractal Entry")>0,C,0);
> X:=If(Fml("PS Fractal Exit")>0,C,0);
> Tl:=If(PREV<=0,N,If(C>PREV,Max(C,PREV),If(X>0,0,PREV)));
> El:=Valuewhen(1,Tl>0 and Alert(Tl=0,2),Tl);
> Tl; El;
>   {Short Trade Move}
> Ts:=If(PREV=0,X,If(C<PREV,Min(C,PREV),If(N>0,0,PREV)));
> Es:=Valuewhen(1,Ts>0 and Alert(Ts=0,2),Ts);
> Ts; Es;
> 
> Roy
> 
> > The problem with what I wrote is it doesn't produce an exact
> > crossover at the grid lines. In other words it passes across a 
grid
> > line without ever having an exact value of 1.0, for example. The
> > reason is the time frame. If it's a five minute chart the next 
bar on
> > a five minute chart is five minutes away which means the indicator
> > value jumps from where it was at bar1 to where it is at bar2, five
> > minutes apart. It makes it tough to find a formula that captures 
the
> > right values.
> >
> > For whatever reason the indicator does not work on a 1 minute 
chart,
> > so that's not an option. It works good on 10 min and 15 min 
charts.
> >
> > What do you think!
> >
> > Jack
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > equismetastock-unsubscribe@xxxxxxxxxxxxxxx
> >
> >
> >
> > Your use of Yahoo! Groups is subject to 
http://docs.yahoo.com/info/terms/
> >
> >
> >


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Free shipping on all inkjet cartridge & refill kit orders to US & Canada. Low prices up to 80% off. We have your brand: HP, Epson, Lexmark & more.
http://www.c1tracking.com/l.asp?cid=5510
http://us.click.yahoo.com/GHXcIA/n.WGAA/ySSFAA/BefplB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
equismetastock-unsubscribe@xxxxxxxxxxxxxxx

 

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