MJ - My Indicators

ok yes I will look forward to this with interest as even with open values it should still get the job done...lol I went through your thread before as you first began piecing it together but found myself ( I must sheepishly admit) kind of lost to begin with..lol but as I went back just now and read through and really process everything ...it really began to make sense to me...

Yes, there also some other reasons for MTF indies. If I base it on Bar open value it does not 'wiggle' repaint so many bars backwards - as some of the ' other MTF indies out there do'.

Anyway: I keep you posted. I plan to write to each indi a small pdf with the input parameters shortly explained.


There is one thing I would like to know more in detail:

How do you use the ZZ Semafor: Do you really make use of the 3 different ZZ.

the zz sempahors kind of aid in telling of 123 patterns...and one way that i've learned to use it is for determining the trend with higher lows and lower highs and such and also when you get the big 3 or on my charts it would be the big white star...than it will often times if confluent with support and resistance levels/divergence or whatever confluence from the higher time frames say the four hour or daily than it can often depict or tell of a reversal before it occurs...a leading indicator if used correctly..

Ok: I used in the past my own ZZ: http://www.forexfactory.com/showthre...49#post4788349

It, coloured the direction and added info if it was a HH / LL //HL /LH etc... also how much % of the previous ect.. quite useful stuff. I might redo it for my new system not sure yet.

Last stuff I was working on:

Plots FRACKind Filtered by an SMA / EMA: A bit similar idea as the Alligator indicator from BillWilliams

For UP FRACTALS: if the Fractals is above the MA it will be plotted,
For DOWN Fractals if the Fractals is below the MA it will be plotted


BTW: in most of my indies default color: Red = UP, Blue = DOWN

Updated the first post to reflect the new indicators.

NEW START WITH UPLOAD:

I will now start again uploading some of my indicators: note: all of them have a small pdf explaining the most important things.

This are not much tested in real trading so I guess there might be still some issues I will have to resolve later on.

as I prepare for the new indi package release I just came across a typical common error - so I thought I post it.

Actually the pic below has TWO common problems

1. the drop of the sma for a couple of bars:

This is because I deactivated the: bExtStartDelay

and has to do with what I mentioned in the: IndicatorCounted() Twice all Bars? http://www.forexfactory.com/showthread.php?t=285687

and because I calculate past data only once.



2. LAST-MT4-ERROR: <4002> - array index is out of range

This error occurs quite frequently and has most of the time (but not always) to do with not having enough history data.

How to solve it: look at each indicator info file for some tips.

4. IMPORTANT: Quite often errors will be related to not having the right or enough History data. Often it is enough to open the Charts with all the needed TimeFrames and restart the terminal.



Pic 2 a similar error on the MTF 8MA indicator

COMMON ERRORS: I try to fetch many possible errors.

1. One of the more annoying errors is when one tries to attach an indicator and two things are already exist:
   1. 1. when a same Unique indicator name exists: see the info for input parameter: sExtUniquePrefix.
      1. This can be because an other indicator in the terminal( can also be on an other chart) has already created them and this is a warning for you to change the: sExtUniquePrefix
      2. BUT sometimes there are other reasons and it must be removed manually from the global variables to be able to attach the indicator: Terminal: Tools>GlobalVariables
         1. From MT4 doc: Global variables are kept in the client terminal within 4 weeks since the last access, then they will be deleted automatically.
         2. BTW: If all works correctly I clean up my own indicators Global Variables: but sometimes the hang.

   2. 2. the second common error is very much related to the one above but is only across the same chart. When the special 3 ERR/INF objects (ErrWarnBottom, ErrWarnTop, Inf:: sometimes also a couple of others)) already exist with the same name.
      1. Again: This can be because an other indicator in the terminal( can also be on an other chart) has already created them and this is a warning for you to change the: sExtUniquePrefix
      2. BUT sometimes there are other reasons and they must be removed manually from the global variables to be able to attach the indicator: Terminal: Charts>Objects>Objects List

   3. TIP for the 2 Errors above:
      1. in case the indicator can not be applied - before giving up try this:
         1. Close all charts of the Terminal
         2. Remove all GlobalVariables: Tools>GlobalVariables
         3. Restart the terminal and open one chart and try to add the indicator. This should do the trick in 99 % of cases. (Make sure you have enough data for the pair and all needed TimeFrames (in case of an MTF indicator)
            1. NOTE: this does not mean you will not get any other errors because of wrong User input or not enough data in the charts history etc.. - but this should be more easily resolved afterwards.

1. 3. NOTE TEMPLATES: Most templates which use my indicator do NOT work out of the box: Reason is that there are individual settings which can greatly differ from one pc to another: e.g. sExtMT4InstallationPath
   1. usually one can still use the template but must adjust such individual settings correctly. Actually there are only a couple of them: the most important is the: sExtMT4InstallationPath

1. VERY IMPORTANT: When creating templates usually the objects mentioned above are referred to within the template file.
   1. if one applies such a template one gets on occasions an error that the objects already exist. TWO solutions:
      1. 1. The cleanest: remove from the template the objects: I usually use a simple text editor like: (geany) to remove them: search for start tag:" <object> and the end tag: </object> ".
      2. 2. Most of the time it will also work if one just changes the chart period back and forth or restart the terminal so that the indicator is deinitialization (but I don't like that for proper templates).

MTF display don't be fooled:

after a new MTF bar starts most of the time the display seems suddenly much steeper - especially if one compares it to a normal chart version on the higher timeframe. see pic below.

The H1 chart version seem to continue quite smoothly from the previous bar (Red Line) where as the MTF version seems to suddenly turn down.

This is quite simple the case because the previous MTF bar is split into 60 chart bars which are much broader on the time line.

Where as after the new MTF bar the it is only split into a couple of chart bars.


Most of the time people are aware of it: but one has still to take care a lot not to misinterpret it - especially using very hight MTF on small chart periods.

Most MTF indies I know who use proper interpolation do not paint till the last chart bar - so it was not so much obvious.

hi pmullin86,

I just wrote the info file for the Ma alert and had to take some screenshots.

I thought I post it here as it shows what I was talking about the Vline Alert in separate SubWindow: simulating a Bar indicator.
If one uses that option really really a lot in live trading it might be better to make a own version with real Bar display and not Vlines.

But for the general puurpose: especially only backdata testing this should be a good option in addition to the existing once with WriteToFile ect...


This uses my simple: EmptySubWindow indicator which has a small text option too.

Seeing it visually it does make sense and the option is indeed a good one to have of one would have a lot of different alerts being set...

20110829 - FIRST INDICATOR PACKAGE RELEASE (untested so expect mistakes)

1___INDICATORS__FINISHED___1__20110 829.zip
2___INDICATORS__FINISHED___2__20110 829.zip

What does it contain:

* 86 individual indicators: BUT many of them overlapping a lot

* 31 individual indicator help files.


Download from first post.

For the FRACKind (Kind of FRACTALS) indicators I also wanted to post the official definition I forgot it in the zip files: with the next update I add it there.

SOME INFO ABOUT CREATING TEMPLATES:

I was asked about creating templates: this is what I do for myself.

1. Add the indicator to the chart.
Make sure it works: maybe even restart the terminal to see it also works after that.

2. Save the template

3. Adjust the template.
I use the text editor: geany http://www.geany.org/

* Search for objects: objects start with the tag: <object> and end with </object>.

in geany one can search in the whole document and also gets the line numbers. if one clicks on it one finds the line immediately. see pic 1.

I usually search for the end tag: </object> and remove all lines above till the open tag: <object> see pic 2.

Basically I remove all such objects from the template files. (take care not to remove other important stuff


Attached: final template: opSMA_0_00_Example.tpl needs the opSMA_0.00.ex4 indi from the package I posted.

NOTE: this template might not work for you for a couple of reasons: I also check for the MT4 installation path: so if you have your MT4 somewhere else installed you get an error: something like:

[email protected] >>> OWN-ERROR: sExtMT4InstallationPath: <Crogram FilesMT4d>. It seems it does not exist. Take also care if it contains spaces: one to much is often not so easily spotted.

( I added a d in the end: MT4d which is not a valid installation path on my pc)

in the example template this is:
sExtMT4InstallationPath=Crogram FilesMT4


Anyway I hope this helps a bit for creating templates and what I do for myself.

TIP: usually if you save the template while the StartDelay runs you have much less objects to remove 'as most of the stuff is afterwards created.

Once this process is completed than one should not have any problems loading up the templates right...and this is juat done one time after saving the template is that also correct?

pmullin86:and this is juat done one time after saving the template is that also correct?

Yes: it is done only once.

pmullin86: Once this process is completed than one should not have any problems loading up the templates right

YES and NO

Yes: in most cases it should be working.

No: because as you know it also depends a bit what indicators are used on the other charts (in case one has multiple charts open) or if there some GlobalVariables are hanging around from some previous mistakes.


With this indicators it is not only simple adding it (sometimes it works but most of the time one has to plan a bit what one wants and than do it.

Thanks

Choosing the best suitable indicator for a task: example:

1. TAKS: 1 SMA Chart version is needed.
- Only option is to use the: opSMA_0.00.ex4

2. TAKS: 3 SMA Chart version are needed.
- option: 3 single SMA: opSMA_0.00.ex4
- best choice: op3MA_0.00.ex4 and use MAMethod 0=SMA

3. TAKS: 3 SMA MTF (all are using the same MTF Interval) are needed.
- option: apply 3 single opSMA_MTF_0.00.ex4
- option: use: op3MA_MTF_0.00.ex4 and for all 3 the same MTFResourceInterval
- best choice: op3MA_MTFSame_0.00.ex4 MAMethod 0=SMA

Why does it matter to choose the best suited indicator if the final results the same:

1. configuration comfort is most of the time easier.

2. PC resources and speed.

Pic below uses a 1 MONTH MTF stochatic on a 1 Minut Chart.
- TIP if you use the width setting from the input tap one can apply much higher values: which is not possible with the drop-down menu (the MT4 doc does not support higher values but it works at least for me
NOTE: all my indies use all such settings from within the input tap - so I never switch to the Colors tap at all.)

MTF: 1 MONTH MTF stochatic on a 1 Minut Chart.
NOTE: MTF indicators can be a bit slow at times depending on the setting: one of the reason is - they repaint.

e.g. pic below: uses as STOk8 a MONTH Interval 43200=MN1 on a M1 chart. which means at one point in time it repaints for one new tick 43200 past candles. ( which is a lot imagine you applied 8 or 20 such indicators.)
basically: MTFInterval / ChartInterval (+ couple more) is more or less the max amount of past bars which are repainted for a new tick.
But the real number of repainted bars is always changing starting with as low as 1 or 2 and than goes up to the max amount and than restarts again etc..)


In the future I might try to improve some of this things