Menu
Sister Sites

Options

Bookmark Thread

First Page First Unread Last Page Last Post

Print Thread

Similar Threads

ALF indicator for most recent versions of MT4 7 replies

Recent Candles indicator 235 replies

Recent Strength indicator 860 replies

Recent Prices indicator 24 replies

Great recent strength indicator needs alert 0 replies

Attachments: Recent SR indicator
Exit Attachments

Recent SR indicator

Quoting craig65
im with pepperstone in australia.
i have autorefresh indi, symphonie auto refresh, from forex factory thread on symphonie thread. but its not very good. switches from 5 min chart to weekly automatically. i good auto refresher indi or script would be well sought after.
Craig,

I managed to get a satisfactory Recent SR plot of gold using Pepperstone MT4 with the parameters shown in the screenshot (BandwidthPips=10, LineWdith=2).

David
Attached Image (click to enlarge)
Click to Enlarge Name: 2012-01-21_0850.jpg Size: 147 KB
ok thanks for helping
Hi David,

As you know I trade SR on this indy.

Is it possible to add a touch alert or proximity alert to the indicator?

Or

Is it possible to make it automatically add a touch alert or proximity alert to the last SR (rectangle/trendline) it creates?


I am sort of thinking that this may be in the too much time required basket. If so that is cool... and thanks anyway for considering it...

All the best,
Josh
Quoting aquaart
Is it possible to add a touch alert or proximity alert to the indicator?
Josh,

I looked at the possibility of alerts a while back, and reached the conclusion that it might be tidier to build them as a separate indy....... but then I got swamped with other work, and never got around to coding it.

I'll revisit the idea when I get some spare time. Not sure when that will be, however.

David
Hi David,

Sometime after I posted my request I thought I had come across an indicator that does the same thing as your reply... ... that is, to have a separate indy that does alerts.

Did some searching and found it, going to test it tonight, maybe you could recommend this indicator at the beginning of this thread, to stop people like me making requests for alerts to be added.

Found one that does just that.

And a second one from the same thread.

Anyway thanks for your consideration again.

Josh.
Quoting aquaart
Did some searching and found it, going to test it tonight, maybe you could recommend this indicator at the beginning of this thread, to stop people like me making requests for alerts to be added.
Josh, your reference to Tesla's indy reminded me that I'd re-worked it in this thread (see earlier posts in the thread for instructions).

FWIW,
David
Just wanted to say thanks for making this awesome indicator! It's just what I been looking for.
Thank you David,

Fantastic indicator.... SR traders should find this extremely useful....

Thanks
lnl
Yes it is a fantastic indicator thanks for sharing.
Is this indy still free from page one or is it now for sale? I'm late to the party sorry hannover
Quoting tommbstone
Is this indy still free from page one or is it now for sale? I'm late to the party sorry hannover
It's still free (I suspect the moderators would have moved it to the commercial forum if it wasn't), but please note the caveats in post #1 regarding running it on Windows 7 or Vista.
Hi All,

Thank you to David for such a great indicator. As David is posting this indicator and has no desire to answer Qs, I was wondering if anyone has had the mq4 shared from David if they could do an edit. I'm not asking you to break David's trust and share the mq4 file....

THE EDIT
When the ray / rectangle is painted on the chart, that you can select the length that the line will be painted for....

e.g
After the last qualifiying point is met, if I were to type in 24*H1, the length of the ray / rectangle would only occur on the charts for 24 1-hour TFs after the last qualifying point.

e.g 2
OR if I were to type in 12*H4, the length of the ray / rectangle would only occur on the charts for 12 4-hour TFs after the last qualifying point.

e.g 3
OR if I were to type in 30*D1, the length of the ray / rectangle would only occur on the charts for 30 daily TFs after the last qualifying point.

etc....

This would make this indicator visually backtestable for me and probably many others....

Regards,
lnl
Quoting lock.n.load
Hi All, .....
@lock.n.load, @everybody,

Had a few spare hours yesterday, so I've overhauled the indicator code. It's been a long time since I last looked at the code, so I hope that it still works OK. I haven't done much in the way of comprehensive testing.

I've also attached the mq4 source file to post #1. Hopefully it gives aspiring programmers some insights as to how to approach coding an indicator of this complexity. Sorry, there are no comments, as I originally wrote the indy for my own use. Please note that for the code to compile correctly, you'll need to include the two .mqh files from the second link in my signature. The Win7 and Vista caveats in post #1 still very much apply: I have indicators that work 100% on my WinXP computer, but behave erratically on my business partner's Win7 computer. Same code, same br0ker (Pepperstone), same MT4 build...... very strange.

The RefreshEveryXMins setting now accepts values like M1, M5, D1, etc.

The LineOrBoxLength setting now accepts three values, separated by commas:

First value is the number of candles. A positive value will plot the line/box from the base QP toward the right of the chart; a negative value will plot it from the base QP to the left. Entering 0 is a special case; it means that the line/box will be plotted from the base QP to the rightmost candle in the chart; the second and third values are effectively ignored (this is to retain compatibility from previous versions).

Second value is which QP to use as the base point for the plot (assuming there are multiple QPs within the same band). Type either L for the leftmost QP in the band, R for the rightmost QP in the band. Upper or lowercase doesn't matter. The default value (if you don't enter anything) is effectively L.

Third value is the timeframe on which the number of candles will be counted. Valid entries are M15, H1, etc; upper or lowercase doesn't matter. If you leave this blank/empty (as opposed to 0), then the chart's timeframe will be used.

Example #1: 10,R,H4 will plot a line/box starting at the rightmost QP candle in the band, and ending 10 H4 candles rightward of the starting point.

Example #2: –5,L will plot a line/box starting at the leftmost QP candle in the band, and ending 5 candles leftward of the starting point, using the timeframe of the current chart.

Example #3: 0 will plot a line/box starting at the leftmost QP candle in the band, an end with the rightmost candle in the chart.

David
Quoting hanover
@lock.n.load, @everybody,

I've also attached the mq4 source file to post #1.

The RefreshEveryXMins setting now accepts values like M1, M5, D1, etc.

The LineOrBoxLength setting now accepts three values, separated by commas:

Wow, thanks a real lot David, an already sensational indicator made even better.

I'll give the new version a go this week. Also thank you for sharing your hard work.

All the best
lnl
Quoting hanover
@everybody,

The RefreshEveryXMins setting now accepts values like M1, M5, D1, etc.

The LineOrBoxLength setting now accepts three values, separated by commas:

Example #1: 10,R,H4 will plot a line/box starting at the rightmost QP candle in the band, and ending 10 H4 candles rightward of the starting point.

Example #2: –5,L will plot a line/box starting at the leftmost QP candle in the band, and ending 5 candles leftward of the starting point, using the timeframe of the current chart.

Example #3: 0...
Hi David,

Thank you very much, got to test it today... Works perfectly as described, and saves many many manual hours of shortening trendlines when doing manual error proned back testing.

Much appreciated,
lnl
Quoting lock.n.load
Hi David,

Thank you very much, got to test it today... Works perfectly as described, and saves many many manual hours of shortening trendlines when doing manual error proned back testing.

Much appreciated,
lnl
LnL,

Thanks for the feedback. Good to know that the SR indy continues to work correctly.

David
Quoting hanover
I have indicators that work 100% on my WinXP computer, but behave erratically on my business partner's Win7 computer. Same code, same br0ker (Pepperstone), same MT4 build...... very strange.

Example #1: 10,R,H4 will plot a line/box starting at the rightmost QP candle in the band, and ending 10 H4 candles rightward of the starting point.
Hi David,

A little note, for some reason the most recent version of the indicator when using Example #1: 24,R,H1

It plots 19 / 20 trendlines correctly but then the 1 incorrect runs for a random number of candles ... but always greater than 24.

Other settings that may be of use....
TimeFrame H1
LookbackCandles 2400
Frequency 1
LineWidth 5
visibility 2,2
VisCompletionRequired true


It also seems to often happen near where there might be multiple times that the level has satisfied the QP requirements....


However, even though I ran version 1.09 without a problem, my OS is Windows 7, 64 bit, which could be the problem going by above...

Thanks,
lnl
Quoting lock.n.load
Hi David,

A little note, for some reason the most recent version of the indicator when using Example #1: 24,R,H1

It plots 19 / 20 trendlines correctly but then the 1 incorrect runs for a random number of candles ... but always greater than 24.

Other settings that may be of use....
TimeFrame H1
LookbackCandles 2400
Frequency 1
LineWidth 5
visibility 2,2
VisCompletionRequired true


It also seems to often happen near where there might be multiple times that the level has satisfied the QP requirements....


However, even though I...
Hi,

Some thoughts, just off the top of my head:

Are you sure that there isn't another QP to the right of the one which appears to be the most recent one (see my note in blue typeface, below)?

The LookbackCandles value of 2400 might be too high for the indy to cope with. Does reducing it to something like 200 solve the problem?

Also, what is the TF of the chart to which the indy is attached (as opposed to the TimeFrame setting in the indy)?

And what br0ker/MT4 build are you using? (so that I can try to reproduce the problem).

I'll have a look when I get some spare time.

[EDIT]
I've just attached the indy to an EURUSD,H1 chart with your settings (including 2400 lookback) and can't see any obvious problem. I guess you're aware that, even if two QPs are (for example) several hundred candles apart, the indy will still draw a line from the leftmost QP, to the rightmost QP plus the number of candles you specify, which can make for a very long line? That's the best that the indy can do, at least without a complete rewrite, because all it stores currently is the time of the leftmost QP (start bar), and the time of the rightmost QP (last bar), within each price band. Then it plots a line/box between these points, extended to the right by the number of candles you specify. To plot multiple lines as we move across a given price band, the indy would need to keep track of the candle time of every QP, in every price band. That would potentially add a significant CPU/RAM overhead to the process, especially as some users have multiple instances of the indy (to plot different types of S/R) per chart, on more than 30 different price charts.

There is also the possibility that missing data could affect the indy. For example, if you're plotting D1 S/R on a H1 chart, and some D1 candles are missing, when the indy counts N candles on the D1 chart (given the available data), this might not represent exactly 24xN H1 candles, thereby affecting the line/box lengths accordingly.

David
@lock.n.load,

Please read the material in blue typeface in my previous post. Then download and install the latest version (v1.11) of the indy from post #1, and unzip the content of the attached ZIP into your ...../(MT4)/experts/files folder.

Then, when you attach the Recent SR indy to your chart, type TST as the ParameterFile. This will load all of the parameters from the file Presets---Recent SR.TST that you unzipped, saving you the need to have to re-type them every time you attach the indy to a chart. (You can edit the parameter file using Notepad, and also copy/rename it to create additional parameter files, and then edit them, as your needs dictate).

Due to the OutputFile setting in the parameter file, the indy will now output a file named Recent SR.OUT into your ...../(MT4)/experts/files folder. You can view the content of this file using an app like Notepad or Excel.

This file lists every price band, along with its reference number**, price level, number of QPs, and the candle# and date/time of the leftmost and rightmost QPs.

** If you hover the mouse cursor over a generated SR line/box on the MT4 chart, the object name is shown as Recent SR-xxxxxx-yyy, where yyy matches the reference number in the output file. That enables you to match a plotted line/box on the chart with its corresponding row in the output file. (Note: if you have multiple instances of Recent SR attached to the same chart, the value xxxxxx will differ for each instance, ensuring unique object names).

From this, you should be able to verify that the leftmost and rightmost QPs refer to the correct candles (match the date/time on the MT4 chart with the date/time in the output file), according to your SR criteria (frequency, visibility, etc), and that the line/box is being extended the correct number of candles to the right of the rightmost QP.

I've run some spot tests along these lines and I can't fault the indy, using the settings in the attached parameter file. I'm running WinXP SP2, and Pepperstone MT4 build 427.

David
Attached File(s)
File Type: zip Presets---Recent SR.zip   < 1 KB | 1,556 downloads
Quoting hanover
Are you sure that there isn't another QP to the right of the one which appears to be the most recent one (see my note in blue typeface, below)?
Yes, I use the SR to identify fractal highs and lows mainly but on multiple TFs.

Quoting hanover
The LookbackCandles value of 2400 might be too high for the indy to cope with. Does reducing it to something like 200 solve the problem?
At 600 I got the first one and instead of going for 24hr (1 trading day) it went for 9 trading days exactly. (Had 2 weekends in between)

Quoting hanover
Also, what is the TF of the chart to which the indy is attached (as opposed to the TimeFrame setting in the indy)?
M5

Quoting hanover
And what br0ker/MT4 build are you using? (so that I can try to reproduce the problem).
GoMarkets -- Build 432


Quoting hanover
Quoting hanover
I've just attached the indy to an EURUSD,H1 chart with your settings (including 2400 lookback) and can't see any obvious problem. I guess you're aware that, even if two QPs are (for example) several hundred candles apart, the indy will still draw a line from the leftmost QP, to the rightmost QP plus the number of candles you specify, which can make for a very long line?
I only have 1 QP, which also means its easy to identify if a second line should be starting or not.



Quoting hanover
There is also the possibility that missing data could affect the indy. For example, if you're plotting D1 S/R on a H1 chart, and some D1 candles are missing, when the indy counts N candles on the D1 chart (given the available data), this might not represent exactly 24xN H1 candles, thereby affecting the line/box lengths accordingly.
I think this is unlikely as the I have noticed that longer bars appear to go for a multiple of the 24 hours that I am asking for it to go.

Thank you very much for your replies...
I have had a very busy week but will test this out on other timeframes in the next few days.

Thank you

lnl
0 traders viewing now