Indicators: Ideal ZigZag - page 2

New comment
 
borilunad:

Do you need a primary indicator?

Yes. Either ZZ or ZZP, as desired.

If yes, how to call it if there is no name for it in the code or is it written only for individual windows?

Via iCustom

And "Taking vertices", if necessary, to insert a code snippet into the EA

Taking vertices is "call" yes, the code snippet should work in the EA (on 4k).

Should I use 2 indicators or one?

One of your choice. ZZ sets the minimum knee in pips, ZZP in percentage of price.

Personally, I use ZZP.

 
TheXpert:

Yes. Either ZZ or ZZP, as desired.

Via iCustom

Taking vertices is "call" yes, the code snippet should work in EA (on 4k).

One to choose from. ZZ sets the minimum knee in pips, ZZP in percentage of price.

I personally use ZZP.

Thanks a lot! That's what I was intending to do, but I was confused by the "Taking vertices" at the beginning:

#property indicator_chart_window
#property indicator_buffers 1

#property indicator_color1 Red
#property indicator_width1 3

And this is not allowed to be inserted into EA! That's why I asked if it could be a separate indicator(?!).

I combined ZZ and ZZP. All the difference is in 3 lines. I'll try them one by one, disconnecting them from //, and choose which one to stop at.

So, I put in what I can from "Taking vertices" and try it. I would very much like not to bother you any more! All the best to you!

 

What the hell... instead of 18 votes, there are now only 7... What's wrong?

My zigzags are also two in the ranking...

And the English part is still missing... Although it's been hanging for more than a week ready for publication and was done at the same time as in the English part....

 
TheXpert:

What the hell... instead of 18 votes, there are now only 7... What's wrong?

My zigzags are also two in the ranking...

And the English part is still missing... Although it's been hanging ready to publish for more than a week now and was done at the same time as in Ru...

I've noticed a strange active addition of votes to many programmes lately. Perhaps, someone tried to gain rating in this way. In the very beginning the rating was easily inflated with adding votes. This was eliminated later. Now clever heads for easy money, perhaps, tried with the help of multiple registrations to profit (this is my assumption) actively adding votes on all programmes in a row. All statistics only spoil ("hackers"). :))

 
tol64:

Ok, I'm waiting for an explanation of the other two confusions )

And there is one more unwritten one -- when sorting by rating it is not sorted by rating at all ))

 

Nice zigzag...just not clear how to use it after calling it from icustom...which buffer is responsible for the zigzag line?

 
Neofit:

Nice zigzag...only it is not clear how to use it after calling from icustom...which of the buffers is responsible for the zigzag line?

There is a sample code there. Especially for iCustom.
 
TheXpert:
There's a sample code there. Especially for iCustom.

Hello.

I've looked at the sample code. As far as I understand, the main role in the example is played by bool GetValue(parameters). I will be very grateful if you decipher the parameters.

Can you please tell me if everything will work if I just analyse the values of the first buffer (0,Maxs,INDICATOR_DATA) and fill my buffer based on the condition for the "break" of the zigzag?

 
Neofit:

I looked at the sample code. As far as I understood, the main role in the example is played by the bool GetValue(parameters). I will be very grateful if you decipher the parameters.

GetValue(double dir,int bar,int prevBar,double &peak,
             int &peakBar,datetime &peakTime,const datetime &T[])

dir -- direction -- current direction

bar -- bar for which the extremum is being searched for

prevBar -- bar of the previous peak (or rather the next one)

peak -- return value of the peak

peakBar -- the returned peak bar

T -- time series for TF and indicator symbol.

Can you please tell me if everything will work if I just analyse the values of the first buffer (0,Maxs,INDICATOR_DATA) and fill my buffer based on the condition for the "break" of the zigzag?

No :) via GetValue is the only option.

 

There are so many algorithms for constructing zigzags. Question for everyone: how to correctly identify the break of a zigzag?

For example, in a perfect zigzag, I would remove half of the breaks (circled in green):

I identify zigzag fractures by the fractures of the mashka. Quite simple and beautiful:

1234
New comment