ADAPTING NB10.2A FOR LOWER TF & RM TRADING - 10.2A CTS

[coolncalm]

Don,

Is your explanation coming from the charts or from the code?
Please look first at the chart before the code.

NB: I blacked out the level 1 whites, not the original author, 'cos it was not very useful for CTS trading. Also, I added the Sema4x to the most recent template ONLY for its box and sound alerts to let traders know when price may be approaching a high/low soon. Its alerts are rather too early so it trade value is low hence why it is blacked out too. The ATeam white alerts are more tradeable. If you want to base your coding on the Sema4x, its fine as long as you know why it is there and what it is being used for. You will probably need to tweak the Sema4x code to give more-representative later alerts before it will become trader-usable.

[coolncalm]

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).

No. It gives white for H1 (on levels 1, 2 & 3 with 1 blacked out), magenta for timeframe 240 - when on H1 TF. When on H4 Tf, it gives white for timeframe 240 (H4) and gives magenta for timeframe 1440 (G1).

Don, rather than endlessly loop this issue, can I please ask you to do one thing?
Load the template on any H1 TF, mark all the white alerts with a white vertical line and the white/magenta alerts with a magenta vertical line. Then flip over to the H4 TF. You will find the white lines have no alerts and the magenta line has a white alert. Next mark any white/magenta alert on that H4 TF with a red vertical line then flip to the D1 TF. you will find the red line has a white line.

[GT3RS]

Be aware everyone. Potentially lots of bias changes when the new MP prints at New York close.....

[atharmian]

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.

A graphical summary of the volatility pair grouping is attached.

[atharmian]

Coolncalm,

Thanks for your remarks.. you just reminded me that MultiBob is going to include CTS as a one-stop-shop !

Cheers,
Athar.

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

[disbellj]

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

[fire580]

disbellj- great video explains a lot about what you are trying to do.... I especially like the alert that popped up during the video will that be available as well as the information you showed on the chart itself?

[atharmian]

The video in .mov seems unable to be handled by Win Player on my Windows 7 machine.

[coolncalm]

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.

A graphical summary of the volatility pair grouping is attached.

Thank, Athar. Looks quite helpful.

[coolncalm]

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

Okay, Don. Let's try it any way you want (even if its different from the manual trading version). The end results may be the same.

You apparently have no interest in the little chart exercise I suggested to put us together on one page (if you knew how the level 2 whites appear when the level 1's are blacked out, it could help in coding with any semafor you decide, you know?)