help with Localized Stairstepping Heatmap indi | Page 7 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

Please help to make this indi into a Multiple Time Frame (MTF) indi 3 replies

Coder needed for small fee- fixing every Indi/Idea for Indi 2 replies

Repainting indi into Non-Repainting Indi - Help 2 replies

Consecutive candles indi combined with volume & spread indi 13 replies

Need help to convert this indi into MTF indi 3 replies

Attachments: help with Localized Stairstepping Heatmap indi
Exit Attachments

help with Localized Stairstepping Heatmap indi

  • #121
  • Apr 23, 2012 8:46am Apr 23, 2012 8:46am
Quoting forexhard
More trouble (maybe) with the Ignore Box...
This is because the cz formed across the weekend and the label is at the midpoint of the edge times and not the median. Computing the median seems an overkill on processing time and complexity to address a minor and infrequent display bug. I am going to skip this and continue on the more serious bugs you have noted. The squalou indicator has the exact same display bug and it has managed ok.

In addition to your bugs I am also realizing the entire box frame refresh has issues that I am addressing. Also there is a serious bug if you have no fractals that cross the threshold there is a zero divide error that crashes the indicator. You can temporarily work around the by setting your fractal threshold lower.
  • #122
  • Apr 23, 2012 9:05am Apr 23, 2012 9:05am
Quoting forexhard
There will be a couple of places where the codes overlap and we get redundancies. In these cases we will need to figure out which codes to give the function over to.

Both indis can make CZ boxes, for example. So in this case we should have the Sq. indi performing this function, and delete all competeing codes from the 3-in-1. So from now on only the Sq. codes should be locating and painting CZ's, and it will be connected to the CZ Heatmap so the heatmap can use that data for its display.

FYI, I don't have an actual preference of one set...

I am not sure how you made this post in between my reply to your previous post but I never saw it. Looks like the 2 features you want are the buffer/beams and the signal arrows.


In my manual box code I already have my own way to do the box markup that is easy to add to any code and keeps the CZ calculations separate from the display code. I will be adding this feature so you can see if it is good enough for you.

I also can add the signal arrows since I am using this logic as part of my EA and will need to develop my own code for this.
  • #123
  • Apr 23, 2012 10:03am Apr 23, 2012 10:03am
Here is a new version with some major bug fixes.

Also has new ability to draw CZ Markups. CZ Frequency is printed and shows in the expert tab.
Attached File(s)
File Type: mq4 !ParadoxSr_v1.09.mq4   29 KB | 324 downloads
  • #124
  • Apr 23, 2012 10:35am Apr 23, 2012 10:35am
Not really a bug, just more of an idea to keep the chart from getting too cluttered and crowded with artifacts...
Attached Image (click to enlarge)
Click to Enlarge Name: extd.gif Size: 166 KB
To improve is to change. To perfect, is to change often.
  • #125
  • Apr 23, 2012 10:37am Apr 23, 2012 10:37am
Quoting Paradox
CZ Frequency is printed and shows in the expert tab.
Any way you can just copy Squalou's corner info graph????
To improve is to change. To perfect, is to change often.
  • #126
  • Apr 23, 2012 10:42am Apr 23, 2012 10:42am
...
Attached Image (click to enlarge)
Click to Enlarge Name: label.gif Size: 34 KB
To improve is to change. To perfect, is to change often.
  • #127
  • Apr 23, 2012 10:46am Apr 23, 2012 10:46am
Quoting forexhard
Not really a bug, just more of an idea to keep the chart from getting too cluttered and crowded with artifacts...
Sure I actually had it this way. I just changed it to extend to CZ form time so it would be more like the squalou indicator.
  • #128
  • Apr 23, 2012 10:49am Apr 23, 2012 10:49am
Quoting forexhard
...
Yes it is. Please read my previous post today. I am not addressing this now since it is also a bug in squalou and is farely minor issue at the moment.
  • #129
  • Apr 23, 2012 10:49am Apr 23, 2012 10:49am
...
Attached Image (click to enlarge)
Click to Enlarge Name: extd2.gif Size: 27 KB
To improve is to change. To perfect, is to change often.
  • #130
  • Apr 23, 2012 10:52am Apr 23, 2012 10:52am
Quoting forexhard
Any way you can just copy Squalou's corner info graph????
I probably can at some point. laying out labels is such a pain though. Also with the histogram display there is really not as easy a place to put this.
  • #131
  • Apr 23, 2012 10:52am Apr 23, 2012 10:52am
Quoting Paradox
Yes it is. Please read my previous post today. I am not addressing this now since it is also a bug in squalou and is farely minor issue at the moment.
OK, so we figured out the issue. That's all that matters. I'm just doing my small part as an extra set of eyes for this project. I can't help with the coding, so I'm being extra vigilant with the de-bugging.
To improve is to change. To perfect, is to change often.
  • #132
  • Apr 23, 2012 10:53am Apr 23, 2012 10:53am
Quoting Paradox
I probably can at some point. laying out labels is such a pain though. Also with the histogram display there is really not as easy a place to put this.
Just make it corner-selectable.
To improve is to change. To perfect, is to change often.
  • #133
  • Apr 23, 2012 11:55am Apr 23, 2012 11:55am
Ok unless there is a major bug this is the last version for today. I have not had a chance to make the entry arrows and stats.

I think most of your other requests are in there though.

I also added multi CZ criteria since I am always bugged that I can't find specific CZ sizes with out overly loosening my settings and ruining the stats.

You can now specify multiple values for these 2 variables. Make sure they have the same count.

CZBoxLengths = "40,30";
CZBoxRanges = "30,20";
Attached File(s)
File Type: mq4 !ParadoxSr_v1.10.mq4   33 KB | 344 downloads
  • #134
  • Apr 23, 2012 2:46pm Apr 23, 2012 2:46pm
The problem I was anticipating back in post #116 is happening. The 2 indicators aren't lining up even though they both have the same CZ settings...
Attached Image (click to enlarge)
Click to Enlarge Name: sq_cz.gif Size: 57 KB
To improve is to change. To perfect, is to change often.
  • #135
  • Apr 23, 2012 4:04pm Apr 23, 2012 4:04pm
Quoting forexhard
The problem I was anticipating back in post #116 is happening. The 2 indicators aren't lining up even though they both have the same CZ settings...
I already guaranteed to you they will not line up and gave you specific highlight examples in post #117. Without your feedback on exactly what is wrong with my CZs and what the logic is that makes the correct box I can't do anything about this.
  • #136
  • Apr 23, 2012 5:06pm Apr 23, 2012 5:06pm
OK, so we both see a misalignment between the indis. But as you know I can't help with coding logic.
To improve is to change. To perfect, is to change often.
  • #137
  • Apr 23, 2012 6:34pm Apr 23, 2012 6:34pm
Quoting forexhard
OK, so we both see a misalignment between the indis. But as you know I can't help with coding logic.
It doesn't have anything to do with coding logic. A CZ still has a logic around it and it is one that you defined yourself. To me I thought BoxLength and BoxSize meant that that many bars (BoxLength) the highs and lows have to to fit into a range of no more than (BoxSize ) and the CZ box is drawn to the exact minimum height that covers the high and low of the box.

You can see in the squalou indicator that it draws boxes that have areas that are untouched by any high and low. It also allows the high and lows to penetrate the CZ without ending it. Both of these issues are circled in my #117 post and I do not understand the idea or philosophy that is behind these boxes. You will have to explain what makes them correct if you want me to be able to line my code up exactly.
  • #138
  • Apr 23, 2012 6:51pm Apr 23, 2012 6:51pm
Quoting Paradox
It doesn't have anything to do with coding logic. A CZ still has a logic around it and it is one that you defined yourself. To me I thought BoxLength and BoxSize meant that that many bars (BoxLength) the highs and lows have to to fit into a range of no more than (BoxSize ) and the CZ box is drawn to the exact minimum height that covers the high and low of the box.

You can see in the squalou indicator that it draws boxes that have areas that are untouched by any high and low. It also allows the high and lows to penetrate the CZ without ending it....
In that case I would say that your code is the better of the two.

The CZ logic is that the base parameters of N pips tall and N bars wide would be the absolute maximum that a CZ could ever be. And the CZ's must be allowed to become shorter and/or add bars at the same time. Your code does this. I had never noticed that the Squalou codes didn't. If the Sq. codes only create static-sized boxes that never get shorter, or never add extra bars, then that is an oversight.
To improve is to change. To perfect, is to change often.
  • #139
  • Apr 24, 2012 5:27am Apr 24, 2012 5:27am
I've double-checked all my inputs. There's no reason for this to be happening...
Attached Image (click to enlarge)
Click to Enlarge Name: heat.gif Size: 45 KB
To improve is to change. To perfect, is to change often.
  • #140
  • Apr 24, 2012 6:52am Apr 24, 2012 6:52am
Quoting forexhard
I've double-checked all my inputs. There's no reason for this to be happening...
Yep that was probably the 1.09 release that had the major bug fixes. Between the refreshing of the WindowBox calculations and the double counting potential in the the 2 map algorithms you might have some changes that make you re-evaluate your settings.

Sorry with all the refreshing I do these kind of bugs don't show up. I test large time running with simulator and that works fine but I got a bit lax.

You or anyone using this code should do their own due diligence with some basic spot checking. With your defaults for fractals this is the same as the inbuilt fractal indicator so you can just draw a horizontal line and count the hits. Same with CZ counts. You can make your bar settings lower which makes it easier too do manually.

I think you will find that the latest version is the most accurate. But maybe not so let me know if you find an accuracy issue.
0 traders viewing now