Harmonic Trading - page 358

 

AlgorithmSearchPatterns - a choice of algorithm of the scanner of search of patterns |

// | for a mode of search of patterns of ExtIndicator=11 |

// | = 0 - corresponds to algorithm of ExtIndicator=0 - this algorithm |

// | about 124 ZUP versions in the ExtIndicator=11 mode | were applied

// | = 1 - corresponds to algorithm of ExtIndicator=1 - Alex's zigzag |

// | the size of a beam is set in points |

// | = 2 - corresponds to algorithm of ExtIndicator=1 - Alex's zigzag |

// | the size of a beam is set as a percentage |

// | = 3 - corresponds to algorithm of ExtIndicator=2 |

// | = 4 - corresponds to algorithm of ExtIndicator=4 |

// | = 5 - corresponds to algorithm of ExtIndicator=5 |

// | = 6 - corresponds to algorithm of ExtIndicator=12 |

ExtIndicator- a choice of option of the indicator, on the basis of which |

// | Pesavento's patterns | are under construction

// | 0 - Zigzag from the metatrader, standard, is a little |

// | optimized |

// | 1 - Alex's Zigzag, |

// | 2 - the indicator similar built in Ensign |

// | 3 - ZigZag Ensign with variable minBars value |

// | 4 - ZigZag, developed tauber |

// | 5 - a variation on swings Hannah |

// | 6 - DT-ZigZag with external ZigZag_new_nen3.mq4. In its basis |

// | standard ZigZag |

// | 7 - DT-ZigZag with external DT_ZZ.mq4 (I developed klot) |

// | 8 - DT-ZigZag with external CZigZag.mq4 (I developed Candid) |

// | 10 - DT-ZigZag with external Swing_zz is ExtIndicator=5 |

// | in the DT mode |

// | 11 - includes search of patterns of Gartley on the basis of standard |

// | ZigZag |

// | 12 - ZigZag, developed Talex |

// | 13 - SQZZ a zigzag, were developed by the Commodity researcher |

// | 14 - ZZ_2L_nen, developed wellx (autocalculation of levels - nen)

 
poruchik:
AlgorithmSearchPatterns - a choice of algorithm of the scanner of search of patterns |

// | for a mode of search of patterns of ExtIndicator=11 |

// | = 0 - corresponds to algorithm of ExtIndicator=0 - this algorithm |

// | about 124 ZUP versions in the ExtIndicator=11 mode | were applied

// | = 1 - corresponds to algorithm of ExtIndicator=1 - Alex's zigzag |

// | the size of a beam is set in points |

// | = 2 - corresponds to algorithm of ExtIndicator=1 - Alex's zigzag |

// | the size of a beam is set as a percentage |

// | = 3 - corresponds to algorithm of ExtIndicator=2 |

// | = 4 - corresponds to algorithm of ExtIndicator=4 |

// | = 5 - corresponds to algorithm of ExtIndicator=5 |

// | = 6 - corresponds to algorithm of ExtIndicator=12 |

ExtIndicator- a choice of option of the indicator, on the basis of which |

// | Pesavento's patterns | are under construction

// | 0 - Zigzag from the metatrader, standard, is a little |

// | optimized |

// | 1 - Alex's Zigzag, |

// | 2 - the indicator similar built in Ensign |

// | 3 - ZigZag Ensign with variable minBars value |

// | 4 - ZigZag, developed tauber |

// | 5 - a variation on swings Hannah |

// | 6 - DT-ZigZag with external ZigZag_new_nen3.mq4. In its basis |

// | standard ZigZag |

// | 7 - DT-ZigZag with external DT_ZZ.mq4 (I developed klot) |

// | 8 - DT-ZigZag with external CZigZag.mq4 (I developed Candid) |

// | 10 - DT-ZigZag with external Swing_zz is ExtIndicator=5 |

// | in the DT mode |

// | 11 - includes search of patterns of Gartley on the basis of standard |

// | ZigZag |

// | 12 - ZigZag, developed Talex |

// | 13 - SQZZ a zigzag, were developed by the Commodity researcher |

// | 14 - ZZ_2L_nen, developed wellx (autocalculation of levels - nen)

Which is the open and close price Zig Zag?

 

Grandaevus, i would like to see on H4/D1 Time frame but when i enter 55*6=330 in maxDepth and 200 in maxBarToD, it doesn't work

(example : SUI30 detects a pattern in D1 with your wsv43 but nothing with wsv45 with parameters (330,200)...)

Ty for sharing !

Edit : I'm wrong, it works finally

330 in maxDepth, 200 maxBartoD works also to H1 to D1

Another question : if we have 2 different patterns in two TF (H4, D1) and we work in D1, which pattern is detected ? is both are painted ?

 

Hi, I've got an idea.

The simplest one pattern finder.

It should have:

-4,5,6 or even more dots.

-work on the history to see if it works.

When someone would find pattern in price and time he published that code on the forum and Grandaevus could put another pattern in the next version.

 
Twan1712:
Grandaevus, i would like to see on H4/D1 Time frame but when i enter 55*6=330 in maxDepth and 200 in maxBarToD, it doesn't work

(example : SUI30 detects a pattern in D1 with your wsv43 but nothing with wsv45 with parameters (330,200)...)

Ty for sharing !

Edit : I'm wrong, it works finally

330 in maxDepth, 200 maxBartoD works also to H1 to D1

Another question : if we have 2 different patterns in two TF (H4, D1) and we work in D1, which pattern is detected ? is both are painted ?
Some useful tips:

I've forgot to say something.

( **** ExtIndicator should be 11 **** )

If you choose DirectionOfSearchMaxMin=false, indicator starts searching patterns from min depth to max depth.

If you choose DirectionOfSearchMaxMin=true, indicator starts searching patterns from max depth to min depth.

you can control max & min depth limits in here

extern int maxDepth = 55;

extern int minDepth = 3;

Default value of DirectionOfSearchMaxMin setting is true but I prefer to use false.

So indicator starts searching from possible short term patterns(short term trend) to long term patterns (long term trend)

Depends on DirectionOfSearchMaxMin setting.

If you want the indicator to search patterns from min depth (short term) to max depth (long term) , you have to choose false

or if you want the indicator to search patterns from max depth (long term) to min depth (short term) , you have to choose true.

In your case, please choose "false" . So indicator searches for patterns from lower time frames to higher time frames.

And you have to increase maxBartoD , when you increase max depth.

 
grandaevus:
Very good idea.

If you have any custom patterns whether it's simple or complex, please share them with us here.

Whatever complex it is, I can add the pattern to the code.

Pattern should be a harmonic pattern not a wave. I'm only interested in harmonic patterns.

What is the difference between a harmonic pattern & a wave?

Min & max D price can be calculated with a fib retracement ratio like (XD or BD) in harmonic patterns.

In waves, it can be anything.

 
xxx-man:
Hi, I've got an idea.

The simplest one pattern finder.

It should have:

-4,5,6 or even more dots.

-work on the history to see if it works.

When someone would find pattern in price and time he published that code on the forum and Grandaevus could put another pattern in the next version.

Very good idea.

I've done lots of modifications to original zupv113 code. Some of them minor, some of them major. Now it's no more zup113. It's much more powerful than that.

Some of our forum members ask me, Why I choose to modify zupv113 but not newer ones like v130 -v135.

Because, I need a light, fast code with less settings, to build up a more complex structure.

A code that can work in limited sources (weak cpu & low memory) like a vps server.

My vps server has got only 1 gb ram and an old celeron cpu but ###ZUP_v113wsv45.mq4 works in 24 opened charts with very high maxdepth settings without any problem.

Starting from zupv120, nen has begun to use arrays to define patterns. This new style of code makes very easy for the programmer or for a user to add new patterns/custom patterns to the program without writing extra codes.

Just open the source code, go the line written below, and add your custom patterns and fibonacci retracements

bool CustomPat_[27];

string namepatterns[27]=

{"Gartley", "Bat", "A Alternate Shark", "A Nen STAR",

"Butterfly", "Crab", "A Shark", "A Cypher",

"A Butterfly", "A Crab", "Shark", "Cypher",

"A Gartley", "A Bat", "Alternate Shark", "Nen STAR",

"Alternate Bat", "Deep Crab", "Black swan",

"max Bat", "max Gartley", "max Butterfly",

"TOTAL 1", "TOTAL 2", "TOTAL 3", "TOTAL 4", "TOTAL"};

Well , what if you've patterns that have non standard fib retracements like cypher pattern (XC retracement) or other patterns (5-0 pattern or 3 Drives) that need a 6 dots = 5 legs check (fib OA) since all original zups can only check maximum 5 dot patterns within standard fibonacci retracements written below.

fibonacci retracements used in original zups:

minXB , maxXB;

minAC , maxAC;

minBD , maxBD;

minXD , maxXD

Or what if, your patterns need special time rules like Navarro 200 or real AB=CD pattern.

Or what if, your patterns need special leg length rules like real AB=CD pattern.

There is only one way. You have to modify zup and write your own code.

In my opinion, If a complete control wanted on pattern definition criterias, writing codes from beginning to end for each pattern is the only way.

By doing this, you can define, max min price and D box time settings for each pattern, you can extend leg search to 6 or even more, and force indicator to check every possible fib retracement variations. Only limit is your mind & imagination.

If you have any custom patterns whether it's simple or complex, please share them with us here.

Whatever complex it is, I can add the pattern to the code.

 

Hi to all,

The idea of ghost patterns of robot trader is very cool i guess.

so if robot trader let us, it can be good to use this feature in grandaevus works.

 
poruchik:
grandaevus

I offer use:

1. XB=1 FTZ=2.618

2. BC=1 FTZ=1.618

Poruchik! Thank you for this picture and image you shared. Did you change any settings in the QTA_v6 & ZigZag_nen1 for this picture? Which version of ZUP did you use for this image also? Any changed settings? Thank you sir! :-)

 

give me link

Reason: