HGI used with Hurst charts

[TraderJoeForex]

Cherry - yellow is the color I choose to represent the +- range which can be set to what you chose. I have this set to 0 as I am using the OBV_TMAtrueslope to highlight the shift in angle of slope of the TMA - I am not concerned with the slope value just whether the slope angle is heading up or down compared with the previous candles so this is why the bars on my chart are either red (heading down) or blue (heading up).

Pipstubborn - yes same as you, using next higher timeframe as a filter only trading in that direction.

I've attached my H1 template along with TMA bands and OBV_TMAtrueslope indicators - the rest I've taken from those posted on this thread. If trading a different timeframe just need to change the TMA timeframes to the next higher if you wish to use them this way.

[slowkey]

Pips400 Hi and Happy New Year ...

Hurst was not showing up on some of the time periods. I think you left out "timeframe" in the following code which was present in Radar's 1a version and seems to work right. Line 268 ...

Code: Select all

  while ( iCustom (NULL,TimeFrame,TMA_centered_name,TMA_fast_value,0,x) < iCustom 

 ------ >(NULL,0,TMA_centered_name,TMA_slow_value,0,x) )   

// Radar's version has ------> 
while ( iCustom (NULL,TimeFrame,TMA_centered_name,TMA_fast_value,0,x) < iCustom 

------->(NULL,TimeFrame,TMA_centered_name,TMA_slow_value,0,x) )

With this change the indicator shows up on all time periods.

Cheers,
Doug

[global]

Happy New Year to All!

Thanks for making all these fantastic indicators available. The MTF Hurst Target and MTF Hurst Target v1a make trading decisions so much easier. However, I would like to see the price points of the hurstextensionline1,hurstextensionline2 and hurstextensionline3 lines for any candle in the past to visually and also via iCustom calls, observe how the price reacted in relation to these levels in the past.

I suppose that to modify those indicators to add that feature would require putting their current code in a loop and writing the hurstextensionline1,hurstextensionline2 and hurstextensionline3 values to three buffers for each candle we check in the loop but I'm really not sure how to do that, especially with the upgraded Empty4 language.

If it's easy for any of you coders to add that functionality, I'll really appreciate it if you can. Thanks

[Cherry]

Cherry - yellow is the color I choose to represent the +- range which can be set to what you chose. I have this set to 0 as I am using the OBV_TMAtrueslope to highlight the shift in angle of slope of the TMA - I am not concerned with the slope value just whether the slope angle is heading up or down compared with the previous candles so this is why the bars on my chart are either red (heading down) or blue (heading up).

Pipstubborn - yes same as you, using next higher timeframe as a filter only trading in that direction.

I've attached my H1 template along with TMA bands and OBV_TMAtrueslope indicators - the rest I've taken from those posted on this thread. If trading a different timeframe just need to change the TMA timeframes to the next higher if you wish to use them this way.

Thanks for your reply, I see now where I missed the change of parameters to 0 to cancel the range colour.

Looking at your H1 template you have one OBV_TMA with setting for 5 on the current timeframe and the other with setting of 11 on the D1 (1440) timeframe.
I sorry if I'm dense here but in your explanation it sounds as though you use both 5 and 11 for the current timeframe (**current timeframe 5 and 11TMA slope must be shifting in the same direction (i.e. OBV_TMATrueSlope previous closed bar is blue for both 5 and 11 for a buy or red for both 5 and 11 for a sell ) and then also 5 and 11 for the higher timeframe but using the TMA bands to see this. (I use the TMA band to show a higher timeframe picture for 5 and 11 as a guide)

I hope you don't mind confirming for me if both the OBV indi's should be for the current timeframe with the 2 different settings or if in fact you do use the HTF for the 11.

Happy New Year to yourself and all here.
Cherry

[pips400]

Pips400 Hi and Happy New Year ...

Hurst was not showing up on some of the time periods. I think you left out "timeframe" in the following code which was present in Radar's 1a version and seems to work right. Line 268 ...

Code: Select all

  while ( iCustom (NULL,TimeFrame,TMA_centered_name,TMA_fast_value,0,x) < iCustom 

 ------ >(NULL,0,TMA_centered_name,TMA_slow_value,0,x) )   

// Radar's version has ------> 
while ( iCustom (NULL,TimeFrame,TMA_centered_name,TMA_fast_value,0,x) < iCustom 

------->(NULL,TimeFrame,TMA_centered_name,TMA_slow_value,0,x) )

With this change the indicator shows up on all time periods.

Cheers,
Doug

Thanks again Doug, have no idea how that happened as I only fixed the previous bug and didn't touch that part of the code. Anyway, important thing is it's fixed.

Happy New Year

Pips400

[Radar]

Hey Pips400,

Yeah, that was my quick & nasty "find & replace" bug from the first MTF version... I thought I killed it in the 1a version, though

I have embedded the indy into a MTF EA, and am creating a 14 sample SMA of the extension for every timeframe... Not the best idea, really, 'cos it has taken over 16 hours to get through 3 months' of data, and still have a couple more years worth to get through

Time to overload a function (tma_centred_value), I reckon

Have fun!

Radar =8^)

[slowkey]

Hey Pips400,

Yeah, that was my quick & nasty "find & replace" bug from the first MTF version... I thought I killed it in the 1a version, though

I have embedded the indy into a MTF EA, and am creating a 14 sample SMA of the extension for every timeframe... Not the best idea, really, 'cos it has taken over 16 hours to get through 3 months' of data, and still have a couple more years worth to get through

Time to overload a function (tma_centred_value), I reckon

Have fun!

Radar =8^)

Oh this is what happened. There was a version one Hurst Targets by Pips. Second a MTF version you put out. Third another version 1a that corrected timeframe that you put out. The 4th version Pips put with a fix of his code using your first MTF version not seeing the second 1a version you put out. That made a 4th version that did not include your code correction from the 1a version. Now finally this version has both of the code corrections by you and Pips. This makes the 4th version of the MTF Hurst Target. I did not know that Pips had not seen the 1a version of the code. This must be what happened. So this is version 4 folks and all who downloaded the previous versions of the MTF Hurst Target should get rid of them and download this version. Probably should give this a version number like V4 or something. Code look solid now at first glance. So if one of you want to do that it will be less confusing for those who read this thread historically.

Pedro may want to post this in post 1 since this is a really nice indicator. I appreciate both of your work on this because now I can see the 4 hour Hurst on the 15 minute chart which makes a nice intraday trading direction and a wonderful tool to trade Nadex options. You can buy options based on realistic targets. Very sweet. This is actually the best option tool I have ever seen.

Cheers and Happy New Year to both of you. God Bless.

Doug

[Radar]

Nicely explained, Doug

Thanks for that

I'll leave it with Pips400... He's a much better coder than I'll ever be

Have a good one.

Radar =8^)

[TraderJoeForex]

Cherry, both OBV_TMATrueslopes are current timeframe and 5 and 11 respectively - both can also display the slope of a higher timeframe but I have this font as background color as have no need to display (so this could just be left as 0 rather than 1440).

Hope this clarifies.

[Cherry]

Cherry, both OBV_TMATrueslopes are current timeframe and 5 and 11 respectively - both can also display the slope of a higher timeframe but I have this font as background color as have no need to display (so this could just be left as 0 rather than 1440).

Hope this clarifies.

Yes thanks, I get it now. Just thought the extra timeframe meant another timeframe would be displayed on that indi inplace of the current one. I didn't really tune into what the text was saying.. so now it all makes sense to my thick head!!