disbellj wrote:It gives ZigZag on current H1 timeframe (H1 in this case, number 1, blacked out), gives white for timeframe 240 (H4, number 2, White), gives magenta for timeframe 1440 (D1, number 3, Pink).

coolncalm wrote:A graphical summary of the volatility pair grouping is attached.

coolncalm wrote:

atharmian wrote:Coolncalm,

I read through your and NB10.2A strategies and also looked at NB10.2A indys (TMA Slope and DWM Pivots), comparing them with yours.

So, is there anything in your strategy that prevents it from being used in all TFs? Do we necessarily have to use Extreme/Fast TMA indys in TFs lower than H4/D1 but use TMA for H4/D1?

Basically, is there a way to combine NB into your CTS? The main philosophy difference I see pertains to you trading ranges, which in NB would be CT (S)- counter trading strategy, a minor confusion with your CTS. I say minor because range trading may not always imply counter trend trading.

Regards,
Athar.

Hi Athar,

The notes do say there shouldn't be anything preventing you from using the strategy on other timeframes as the principles are not necessarily H1-specific. Its just that the lower you go, the easier it is to get whipped and the higher you go, the harder it is to get into trends early. But the choice is yours.

That said, I am not sure what specifically you may be seeking to combine - entry, exit, direction? If you place both strategies side by side, you will see a lot of similarities (full trend pivot definitions, trend-following, pullback entry, etc) and then you can mix and match based on your preferences. Or do you mean asking Bob if we can write a single strategy that contains both elements? There are so many different ways that people trade that a single document may not be able to illustrate all of the combinations of both strategies equally for all kinds of traders. For me the only viable solution for seamlessly combining and trading both strategies is an EA that is written to trade both strategies.

MultiBob by Baluda is a bot that aspires to make it possible to trade NB10.2, NB10.2a and CTS altogether! You can contribute on its thread to ensure that it achieves that grand objective while the effort here continues to aim at a CTS-only development.

Cheers,
CC

atharmian wrote:Coolncalm,

Great job Looks like Don would be looking at this too.

BTW, NanningBob recently posted the attached as zip on his 10.2A forum in response to my query.
I think the the RANGES OF PAIRS is a new file (Oct 2008 vs Apr 2009) while the 300 file is the same old from 10.2 docs.

Cheers,
Athar.

coolncalm wrote:A graphical summary of the volatility pair grouping is attached.

disbellj wrote:CC,

I don't want to keep going over this ZigZag thing either. Truth is, I don't care for one version of ZigZag over another. I need you to understand that this is all we are talking about: ZigZag. No matter if we'er talking ZigZag, SEMA4X, #_Level_ZZ_Semafor, ATeam, etc. It's all just ZIGZAG.

A ZigZag is a ZigZag is a ZigZag. Choose settings for ExtDepth, ExDeviation, and ExtBackstep, for each timeframe, and we'll be fine. Otherwise, I'll just use Semafor 2 on each timeframe H4 and up (NOT H1 because Semafor 3 is only 34 ExtDepth while your SEMA4X which I have no feelings for or against has ExtDepth of 96 and in your words still alerts too early, so answer is obvious "get rid of the too early signal on H1, and use the White number 2 that represents ZigZag default settings on H4) and be done with it.

But then you talk about about using "3'. White is not "3", but "2". "3" means to use D1. On H1, D1 ZZ is Pink and colored 3.

I'll just have to talk about this later. Gotta go for now.

Kindest regards,

Don