Search

Categories

Show

Help

Search Results

Submitted by cclsys
Found 10 matching entries

Entries

CCLBetterVolume2 V1

Lifted from the BetterVolume2 Indicator available on the Ninja Forum and originally written by Barry Taylor and available for free, this one features a few additions including:
some of Cory's volume stop work;
some additional patterns (many of them experimental) which track various combination such as down bar, then churn, then up bar. Small-size wingdings are used to highlight such signals which can easily be turned off once they are learned and/or different ones added.

This is not nearly as sophisticated as many of the live-updating buysell/delta indies out there. The Tradestation version of BetterVolume does a good job of reading up and down ticks but this is much tricker in Ninja and this indicator was not programmed that way (though at this point I think it could/should be) with less difficulty than a year or so ago since more independent programmers out there have shared so much stuff.

To activate the volume signals, change the MA Period from 20 to 21. Then read through the Descriptions for the other options. It's fairly straightforward.

The attached pic shows two version of BetterVolume2 which I had up to ensure this latest version with a different name (so as not to over-write the original BetterVolume2 on others computers) was working correctly.

COMPATIBILITY:
NinjaTrader 6.5: YES
NinjaTrader 7.0: NOT TESTED [feedback]

Category NinjaTrader 6.5 Indicators

Details: CCLBetterVolume2 V1
Category: NinjaTrader 6.5 Indicators

February 11th, 2010
Size: 17.19 KB
Downloaded: 602 times

Keywords: patterns paintbar cclsys volume bettervolume

CCLBands

This is the final version of the older CCLFibBands. I took Fib out of the title because it is much more than Fibs and indeed Fibs are not necessarily a core component. Users can input Fib ratios for the band widths but apart from that it's really a multi-band-type tool which can be used in a wide variety of ways.

1. Mean price based on various types of MA including BMT collective and other collectives, vwap (24 hr).
2. Mean based on day-range midprice or manually input price such as the Open, Yesterday Close or whatever you like.
3. Several types of band: ATR-based, StD based or custom default which is combination of ATR and percentage of price; also can be more or less responsive to short-term volatility; also can be based on looking back to see average maximum ranges over time to fix the outer bands and work the inner ones back from there.
4. One more minor wrinkle: can average any midline with the vwap. Also dynamic PVP is available as a mean.
5. Has target printing capability as DataSeries onetime plot dots or more extended text prints (which cannot be autoscale = falsed unfortunately), based on instant crossover of a band or later confirmed swing points (in Calc Bar Close mode only for swing option).

As far as I can tell, the indicator works well with no errors. When choosing any option involving the targets based on swing, have to keep indy in CalconBarClose = true; that confused me for a while. This because the Swing Indicator used to determine swing prices is calconbarclose only.

The attached picture shows Jan 6 am action in Gold with the mean price based on the POC/PVP price from yesterday afternoon. This is using the Manual MAtype and having a price typed into the ManualOverridePrice input. Also in this case I had the Lookback option on the band calculations. The Std bands probably would have contained price better but the purpose of this setup was to gauge whether or not the morning was looking like a rangebound day or a trend day. The price charging way above the old PVP and the outer bands clearly indicated a trend day. So in this case not used for trading signals per se, simply perspective on market situation.

There are many ways this indicator can be used. Hopefully the comments are helpful given how many options there are, but hopefully also anyone who finds bands helpful will take the time to simply experiment with different options.

NinjaTrader 6.5: YES
NinjaTrader 7.0: NO (sam028)

Category The Elite Circle

Details: CCLBands
Category: The Elite Circle

January 6th, 2010
Size: 85.01 KB
Downloaded: 693 times

Keywords: collectivema envelope vwap cclsys

dValueArea v 2.3 with new dynamic PVP/POC plot

DeanV on the NT forum recently posted this new edition which features ability to plot dynamic PVP, i.e. it shows when the PVP/POC 'flipped' during any session. Works live but also on historical charts which is a godsend for review work.

Attached pic has a few extra things on it, but the dynamic PVP is the red hash plot. (The magenta bands are from the new hVWAP and are different from the dValueArea indicator. Also there are other bands there that are different too.)
Note: my version in the chart has some different colors from the one uploaded which is the original from Deanv.

COMPATIBILITY:
NinjaTrader 6.5: YES
NinjaTrader 7.0: NOT TESTED [feedback]

Category NinjaTrader 6.5 Indicators

Details: dValueArea v 2.3 with new dynamic PVP/POC plot
Category: NinjaTrader 6.5 Indicators

December 21st, 2009
Size: 11.14 KB
Downloaded: 768 times

Keywords: area cclsys ninjatrader poc pvp value

hVWAP version 1

A recent modification of the VWAP that allows you to save start and end times in templates, plus has multipliers for the SD bands and a couple of other features.

Picture shows a few other things, but the new hVWAP is the thick Magenta line and its SD bands are in similar color.

COMPATIBILITY:
NinjaTrader 6.5: YES
NinjaTrader 7.0: NOT TESTED [feedback]

Category NinjaTrader 6.5 Indicators

Details: hVWAP version 1
Category: NinjaTrader 6.5 Indicators

December 21st, 2009
Size: 6.40 KB
Downloaded: 426 times

Keywords: cclsys ninjatrader vwap

CCL SR & CCLATRDonch - SR and expansion/contraction guages

This is a work in progress although probably mainly done.

Two indicators, the first based on the second which has limited helpfulness although it does show things that the first (SR) does not.
...

Details here.

COMPATIBILITY:
NinjaTrader 6.5: YES
NinjaTrader 7.0: NOT TESTED [feedback]

Category The Elite Circle

Details: CCL SR & CCLATRDonch - SR and expansion/contraction guages
Category: The Elite Circle

December 4th, 2009
Size: 19.23 KB
Downloaded: 366 times

Keywords: cclsys channel donchian sr

CCL Bar Pack

CCL is abbreviation for 'Confirmed CLose'. Years ago I rejected indicators - which I now I have a more friendly relationship with btw- and went into bars. The only trading seminar I went to was by Kent Calhoun who developed his 5 vertical bar trading pattern, essentially a 3 bar swing with some rules, but from which he designed some very effective strategies.

I modified his pattern to feature a 'confirmed close' meaning that only if the close takes out the low of the #4 bar (in a forming high swing) is the pattern verified. Very simple. But not so easy to code. Once that was done, you have the ShowMe included which plots confirmed by close (ccl) swing highs and lows color coded such that higher highs and higher lows are bullish color (for me yellow), LL and LH bearish and a swing whose high or low penetrates a previous one but whose close does not confirm is red, i.e. neither bullish nor bearish and often indicative of trend exhaustion, new trend change etc.

Then there are some Fib levels from those swings.

Also a set that project targets.

There's another one somewhere that determines long term trends by keep track of 'Active Highs' and 'Active Lows', i.e. a low whose developing swing made a higher high is Active until it is penetrated or a higher active low is formed. The trend is up until an active low is penetrated. In this way a bull market is defined as higher highs, and a bear market is defined as lower lows in that a bear market only starts if an active low is penetrated and a bull if an active high is penetrated. If/when I find it I will post it here without further explanation.

Picture shows the attached files in action. Colors are garish by TS8 and Ninja standards but some might find the swing patterns of interest. TS8 users will find they can be made to look quite elegant.

Also, they can be helpful for developing wave and other calculations because the swing points can be referenced. That said, Ninja has a very good swing high/low function, although I must say that the confirmed close business does filter out many bad swings, but doesn't always need multiples of ATR's (and 5-10 bars) to determine them.

Category TradeStation (hidden)

Details: CCL Bar Pack
Category: TradeStation (hidden)

November 22nd, 2009
Size: 67.41 KB
Downloaded: 1088 times

Keywords: tradestation

Weekly Universal Seasonality Indicator V1.

I have worked with long terms seasonals for a while as part of developing a futures portfolio system - hopefully for institutional clients at some point.

Although never used for the system, it was an attempt to almost eliminate optimization by applying a universal seasonal indicator to every instrument. It actually works, and well, the results were not good enough for me and so although I use it as a visual indicator, it is not part of any entry rule algorithm.

Ideally, this would be coded in arrays but I lack the skills to work with them in a context that combines text and numbers. Over my pay grade coding-wise!

In any case, it tracks the percentage move each week (this only works on weekly charts) and then puts them together in such a way that when an RSI of those values is plotted it instantly reveals whether or not there are regular or particular seasonal patterns.

In the picture attached you will see signals generated from a different seasonal system (part of my portfolio system) that has 59% successful trades going back over more then 20 years with 7% max drawdown. Not bad. But on the picture you can see the signals and compare how the indicator reads at the same time. As you can see, they are often in agreement. And this indicator will plot automatically on any weekly chart instantly revealing whether or not there are significant seasonal tendencies.

I suspect the same type of approach could be used for daily and intraday charts, albeit with the latter you might be looking for days-of-the-week, and/or hours of the day type behavior. Again, ability to code in arrays is key.

For those not using Tradestation, I paste in the code below.

Note on the picture: there is also an Equity indicator that shows current account balance from starting balance input, current trade P/L, current drawdown from maximum account high, and during DD's the histogram bars get progressively darker. It can also assume compounding in terms of the percentage drawdowns (i.e. of starting balance or the current balance after many years).

The ATR indicator shows either $$ or percentage of instrument ATR and also includes a money-management formula recommending nr. of contracts to trade.

If anyone wants either of these, let me know and I will gladly post them here.

PS. I am hoping some enterprising coder will want to translate this into Ninja script and/or use this as an kick starter to look into day-of-week or time-of-day type analysis. It's not rocket science, but you need to be good at coding arrays which I am not.

+++++++++++++++++++++

Pasted in Code

Indicator:
+++++++++++++++++++++

{***************************************
Written by: ccl-trading-systems.com
Description: Seasonal Indicator without Loop but using new Function
****************************************}
inputs: Rsilen(9),RunorNew(false),highline(70),lowline(30);
vars: runline(0),av(0),slow(0),count(0),slower(0),newrun(0),rsiline(0);

If currentbar >=43 then Begin

runline = VSeasRun2;
if (runline > 0 and runline[1] > 0) or (runline < 0 and runline[1] < 0) then newrun = runline + newrun[1] else newrun = runline;

If RunorNew then slow = averagefc(runline,3) else slow = averagefc(newrun,3);
rsiline = rsi(slow,rsilen);

vars: color(0);
Color = month(d); if color = 1 then color = darkgray;

Plot1 (highline,"hiline",lightgray);
Plot2(lowline,"lowline",lightgray);
Plot3 (50,"0line",color);
Plot4 (rsiline,"rsi-seas",color,color,1);

End; {current bar}

+++++++++++++++++++++++++++

Function:

+++++++++++++++++++++++++++

{***************************************
Written by: ccl-trading-systems.com
Description: Seasonal Indicator without Arrays, last 10 times attempt
****************************************}

vars: TDN(500),SDay(0);
vars:
TDNTot1(0),Count1(0),TDNAv1(0),
TDNTot2(0),Count2(0),TDNAv2(0),
TDNTot3(0),Count3(0),TDNAv3(0),
TDNTot4(0),Count4(0),TDNAv4(0),
TDNTot5(0),Count5(0),TDNAv5(0),
TDNTot6(0),Count6(0),TDNAv6(0),
TDNTot7(0),Count7(0),TDNAv7(0),
TDNTot8(0),Count8(0),TDNAv8(0),
TDNTot9(0),Count9(0),TDNAv9(0),
TDNTot10(0),Count10(0),TDNAv10(0),
TDNTot11(0),Count11(0),TDNAv11(0),
TDNTot12(0),Count12(0),TDNAv12(0),
TDNTot13(0),Count13(0),TDNAv13(0),
TDNTot14(0),Count14(0),TDNAv14(0),
TDNTot15(0),Count15(0),TDNAv15(0),
TDNTot16(0),Count16(0),TDNAv16(0),
TDNTot17(0),Count17(0),TDNAv17(0),
TDNTot18(0),Count18(0),TDNAv18(0),
TDNTot19(0),Count19(0),TDNAv19(0),
TDNTot20(0),Count20(0),TDNAv20(0),
TDNTot21(0),Count21(0),TDNAv21(0),
TDNTot22(0),Count22(0),TDNAv22(0),
TDNTot23(0),Count23(0),TDNAv23(0),
TDNTot24(0),Count24(0),TDNAv24(0),
TDNTot25(0),Count25(0),TDNAv25(0),
TDNTot26(0),Count26(0),TDNAv26(0),
TDNTot27(0),Count27(0),TDNAv27(0),
TDNTot28(0),Count28(0),TDNAv28(0),
TDNTot29(0),Count29(0),TDNAv29(0),
TDNTot30(0),Count30(0),TDNAv30(0),
TDNTot31(0),Count31(0),TDNAv31(0),
TDNTot32(0),Count32(0),TDNAv32(0),
TDNTot33(0),Count33(0),TDNAv33(0),
TDNTot34(0),Count34(0),TDNAv34(0),
TDNTot35(0),Count35(0),TDNAv35(0),
TDNTot36(0),Count36(0),TDNAv36(0),
TDNTot37(0),Count37(0),TDNAv37(0),
TDNTot38(0),Count38(0),TDNAv38(0),
TDNTot39(0),Count39(0),TDNAv39(0),
TDNTot40(0),Count40(0),TDNAv40(0),
TDNTot41(0),Count41(0),TDNAv41(0),
TDNTot42(0),Count42(0),TDNAv42(0),
TDNTot43(0),Count43(0),TDNAv43(0),
TDNTot44(0),Count44(0),TDNAv44(0),
TDNTot45(0),Count45(0),TDNAv45(0),
TDNTot46(0),Count46(0),TDNAv46(0),
TDNTot47(0),Count47(0),TDNAv47(0),
TDNTot48(0),Count48(0),TDNAv48(0),
TDNTot49(0),Count49(0),TDNAv49(0),
TDNTot50(0),Count50(0),TDNAv50(0),
TDNTot51(0),Count51(0),TDNAv51(0),
TDNTot52(0),Count52(0),TDNAv52(0),
TDNTot53(0),Count53(0),TDNAv53(0),
TDNTot54(0),Count54(0),TDNAv54(0);

If currentbar >=43 then Begin

If year(d)>(year(d))[1] then TDN = 0; TDN = TDN+1;

{SDay = (c-c[1])/c[1]*100 ;}
SDay = ((c-c[1])/c[1]) ;

If TDN = 1 then begin TDNTot1 = TDNTot1 + Sday; Count1 = Count1+1; TDNAv1 = TDNTot1/Count1; end;
If TDN = 2 then begin TDNTot2 = TDNTot2 + Sday; Count2 = Count2+1; TDNAv2 = TDNTot2/Count2; end;
If TDN = 3 then begin TDNTot3 = TDNTot3 + Sday; Count3 = Count3+1; TDNAv3 = TDNTot3/Count3; end;
If TDN = 4 then begin TDNTot4 = TDNTot4 + Sday; Count4 = Count4+1; TDNAv4 = TDNTot4/Count4; end;
If TDN = 5 then begin TDNTot5 = TDNTot5 + Sday; Count5 = Count5+1; TDNAv5 = TDNTot5/Count5; end;
If TDN = 6 then begin TDNTot6 = TDNTot6 + Sday; Count6 = Count6+1; TDNAv6 = TDNTot6/Count6; end;
If TDN = 7 then begin TDNTot7 = TDNTot7 + Sday; Count7 = Count7+1; TDNAv7 = TDNTot7/Count7; end;
If TDN = 8 then begin TDNTot8 = TDNTot8 + Sday; Count8 = Count8+1; TDNAv8 = TDNTot8/Count8; end;
If TDN = 9 then begin TDNTot9 = TDNTot9 + Sday; Count9 = Count9+1; TDNAv9 = TDNTot9/Count9; end;
If TDN = 10 then begin TDNTot10 = TDNTot10 + Sday; Count10 = Count10+1; TDNAv10 = TDNTot10/Count10; end;
If TDN = 11 then begin TDNTot11 = TDNTot11 + Sday; Count11 = Count11+1; TDNAv11 = TDNTot11/Count11; end;
If TDN = 12 then begin TDNTot12 = TDNTot12 + Sday; Count12 = Count12+1; TDNAv12 = TDNTot12/Count12; end;
If TDN = 13 then begin TDNTot13 = TDNTot13 + Sday; Count13 = Count13+1; TDNAv13 = TDNTot13/Count13; end;
If TDN = 14 then begin TDNTot14 = TDNTot14 + Sday; Count14 = Count14+1; TDNAv14 = TDNTot14/Count14; end;
If TDN = 15 then begin TDNTot15 = TDNTot15 + Sday; Count15 = Count15+1; TDNAv15 = TDNTot15/Count15; end;
If TDN = 16 then begin TDNTot16 = TDNTot16 + Sday; Count16 = Count16+1; TDNAv16 = TDNTot16/Count16; end;
If TDN = 17 then begin TDNTot17 = TDNTot17 + Sday; Count17 = Count17+1; TDNAv17 = TDNTot17/Count17; end;
If TDN = 29 then begin TDNTot18 = TDNTot18 + Sday; Count18 = Count18+1; TDNAv18 = TDNTot18/Count18; end;
If TDN = 29 then begin TDNTot19 = TDNTot19 + Sday; Count19 = Count19+1; TDNAv19 = TDNTot19/Count19; end;
If TDN = 20 then begin TDNTot20 = TDNTot20 + Sday; Count20 = Count20+1; TDNAv20 = TDNTot20/Count20; end;
If TDN = 21 then begin TDNTot21 = TDNTot21 + Sday; Count21 = Count21+1; TDNAv21 = TDNTot21/Count21; end;
If TDN = 22 then begin TDNTot22 = TDNTot22 + Sday; Count22 = Count22+1; TDNAv22 = TDNTot22/Count22; end;
If TDN = 23 then begin TDNTot23 = TDNTot23 + Sday; Count23 = Count23+1; TDNAv23 = TDNTot23/Count23; end;
If TDN = 24 then begin TDNTot24 = TDNTot24 + Sday; Count24 = Count24+1; TDNAv24 = TDNTot24/Count24; end;
If TDN = 25 then begin TDNTot25 = TDNTot25 + Sday; Count25 = Count25+1; TDNAv25 = TDNTot25/Count25; end;
If TDN = 26 then begin TDNTot26 = TDNTot26 + Sday; Count26 = Count26+1; TDNAv26 = TDNTot26/Count26; end;
If TDN = 27 then begin TDNTot27 = TDNTot27 + Sday; Count27 = Count27+1; TDNAv27 = TDNTot27/Count27; end;
If TDN = 28 then begin TDNTot28 = TDNTot28 + Sday; Count28 = Count28+1; TDNAv28 = TDNTot28/Count28; end;
If TDN = 29 then begin TDNTot29 = TDNTot29 + Sday; Count29 = Count29+1; TDNAv29 = TDNTot29/Count29; end;
If TDN = 30 then begin TDNTot30 = TDNTot30 + Sday; Count30 = Count30+1; TDNAv30 = TDNTot30/Count30; end;
If TDN = 31 then begin TDNTot31 = TDNTot31 + Sday; Count31 = Count31+1; TDNAv31 = TDNTot31/Count31; end;
If TDN = 32 then begin TDNTot32 = TDNTot32 + Sday; Count32 = Count32+1; TDNAv32 = TDNTot32/Count32; end;
If TDN = 33 then begin TDNTot33 = TDNTot33 + Sday; Count33 = Count33+1; TDNAv33 = TDNTot33/Count33; end;
If TDN = 34 then begin TDNTot34 = TDNTot34 + Sday; Count34 = Count34+1; TDNAv34 = TDNTot34/Count34; end;
If TDN = 35 then begin TDNTot35 = TDNTot35 + Sday; Count35 = Count35+1; TDNAv35 = TDNTot35/Count35; end;
If TDN = 36 then begin TDNTot36 = TDNTot36 + Sday; Count36 = Count36+1; TDNAv36 = TDNTot36/Count36; end;
If TDN = 37 then begin TDNTot37 = TDNTot37 + Sday; Count37 = Count37+1; TDNAv37 = TDNTot37/Count37; end;
If TDN = 38 then begin TDNTot38 = TDNTot38 + Sday; Count38 = Count38+1; TDNAv38 = TDNTot38/Count38; end;
If TDN = 39 then begin TDNTot39 = TDNTot39 + Sday; Count39 = Count39+1; TDNAv39 = TDNTot39/Count39; end;
If TDN = 40 then begin TDNTot40 = TDNTot40 + Sday; Count40 = Count40+1; TDNAv40 = TDNTot40/Count40; end;
If TDN = 41 then begin TDNTot41 = TDNTot41 + Sday; Count41 = Count41+1; TDNAv41 = TDNTot41/Count41; end;
If TDN = 42 then begin TDNTot42 = TDNTot42 + Sday; Count42 = Count42+1; TDNAv42 = TDNTot42/Count42; end;
If TDN = 43 then begin TDNTot43 = TDNTot43 + Sday; Count43 = Count43+1; TDNAv43 = TDNTot43/Count43; end;
If TDN = 44 then begin TDNTot44 = TDNTot44 + Sday; Count44 = Count44+1; TDNAv44 = TDNTot44/Count44; end;
If TDN = 45 then begin TDNTot45 = TDNTot45 + Sday; Count45 = Count45+1; TDNAv45 = TDNTot45/Count45; end;
If TDN = 46 then begin TDNTot46 = TDNTot46 + Sday; Count46 = Count46+1; TDNAv46 = TDNTot46/Count46; end;
If TDN = 47 then begin TDNTot47 = TDNTot47 + Sday; Count47 = Count47+1; TDNAv47 = TDNTot47/Count47; end;
If TDN = 48 then begin TDNTot48 = TDNTot48 + Sday; Count48 = Count48+1; TDNAv48 = TDNTot48/Count48; end;
If TDN = 49 then begin TDNTot49 = TDNTot49 + Sday; Count49 = Count49+1; TDNAv49 = TDNTot49/Count49; end;
If TDN = 50 then begin TDNTot50 = TDNTot50 + Sday; Count50 = Count50+1; TDNAv50 = TDNTot50/Count50; end;
If TDN = 51 then begin TDNTot51 = TDNTot51 + Sday; Count51 = Count51+1; TDNAv51 = TDNTot51/Count51; end;
If TDN = 52 then begin TDNTot52 = TDNTot52 + Sday; Count52 = Count52+1; TDNAv52 = TDNTot52/Count52; end;
If TDN = 53 then begin TDNTot53 = TDNTot53 + Sday; Count53 = Count53+1; TDNAv53 = TDNTot53/Count53; end;
If TDN = 54 then begin TDNTot54 = TDNTot54 + Sday; Count54 = Count54+1; TDNAv54 = TDNTot54/Count54; end;

vars: runline(0),runlineav(0);

If TDN = 1 then begin Runline = TDNAv1; runlineav = averagefc(tdnav1,10); end;
If TDN = 2 then begin Runline = TDNAv2; runlineav = averagefc(tdnav2,10);end;
If TDN = 3 then begin Runline = TDNAv3; runlineav = averagefc(tdnav3,10);end;
If TDN = 4 then begin Runline = TDNAv4; runlineav = averagefc(tdnav4,10);end;
If TDN = 5 then begin Runline = TDNAv5; runlineav = averagefc(tdnav5,10);end;
If TDN = 6 then begin Runline = TDNAv6; runlineav = averagefc(tdnav6,10);end;
If TDN = 7 then begin Runline = TDNAv7; runlineav = averagefc(tdnav7,10);end;
If TDN = 8 then begin Runline = TDNAv8; runlineav = averagefc(tdnav8,10);end;
If TDN = 9 then begin Runline = TDNAv9; runlineav = averagefc(tdnav9,10);end;
If TDN = 10 then begin Runline = TDNAv10; runlineav = averagefc(tdnav10,10); end;
If TDN = 11 then begin Runline = TDNAv11; runlineav = averagefc(tdnav11,10); end;
If TDN = 12 then begin Runline = TDNAv12; runlineav = averagefc(tdnav12,10); end;
If TDN = 13 then begin Runline = TDNAv13; runlineav = averagefc(tdnav13,10); end;
If TDN = 14 then begin Runline = TDNAv14; runlineav = averagefc(tdnav14,10); end;
If TDN = 15 then begin Runline = TDNAv15; runlineav = averagefc(tdnav15,10); end;
If TDN = 16 then begin Runline = TDNAv16; runlineav = averagefc(tdnav16,10); end;
If TDN = 17 then begin Runline = TDNAv17; runlineav = averagefc(tdnav17,10); end;
If TDN = 18 then begin Runline = TDNAv18; runlineav = averagefc(tdnav18,10); end;
If TDN = 19 then begin Runline = TDNAv19; runlineav = averagefc(tdnav19,10); end;
If TDN = 20 then begin Runline = TDNAv20; runlineav = averagefc(tdnav20,10); end;
If TDN = 21 then begin Runline = TDNAv21; runlineav = averagefc(tdnav21,10); end;
If TDN = 22 then begin Runline = TDNAv22; runlineav = averagefc(tdnav22,10); end;
If TDN = 23 then begin Runline = TDNAv23; runlineav = averagefc(tdnav23,10); end;
If TDN = 24 then begin Runline = TDNAv24; runlineav = averagefc(tdnav24,10); end;
If TDN = 25 then begin Runline = TDNAv25; runlineav = averagefc(tdnav25,10); end;
If TDN = 26 then begin Runline = TDNAv26; runlineav = averagefc(tdnav26,10); end;
If TDN = 27 then begin Runline = TDNAv27; runlineav = averagefc(tdnav27,10); end;
If TDN = 28 then begin Runline = TDNAv28; runlineav = averagefc(tdnav28,10); end;
If TDN = 29 then begin Runline = TDNAv29; runlineav = averagefc(tdnav29,10); end;
If TDN = 30 then begin Runline = TDNAv30; runlineav = averagefc(tdnav30,10); end;
If TDN = 31 then begin Runline = TDNAv31; runlineav = averagefc(tdnav31,10); end;
If TDN = 32 then begin Runline = TDNAv32; runlineav = averagefc(tdnav32,10); end;
If TDN = 33 then begin Runline = TDNAv33; runlineav = averagefc(tdnav33,10); end;
If TDN = 34 then begin Runline = TDNAv34; runlineav = averagefc(tdnav34,10); end;
If TDN = 35 then begin Runline = TDNAv35; runlineav = averagefc(tdnav35,10); end;
If TDN = 36 then begin Runline = TDNAv36; runlineav = averagefc(tdnav36,10); end;
If TDN = 37 then begin Runline = TDNAv37; runlineav = averagefc(tdnav37,10); end;
If TDN = 38 then begin Runline = TDNAv38; runlineav = averagefc(tdnav38,10); end;
If TDN = 39 then begin Runline = TDNAv39; runlineav = averagefc(tdnav39,10); end;
If TDN = 40 then begin Runline = TDNAv40; runlineav = averagefc(tdnav40,10); end;
If TDN = 41 then begin Runline = TDNAv41; runlineav = averagefc(tdnav41,10); end;
If TDN = 42 then begin Runline = TDNAv42; runlineav = averagefc(tdnav42,10); end;
If TDN = 43 then begin Runline = TDNAv43; runlineav = averagefc(tdnav43,10); end;
If TDN = 44 then begin Runline = TDNAv44; runlineav = averagefc(tdnav44,10); end;
If TDN = 45 then begin Runline = TDNAv45; runlineav = averagefc(tdnav45,10); end;
If TDN = 46 then begin Runline = TDNAv46; runlineav = averagefc(tdnav46,10); end;
If TDN = 47 then begin Runline = TDNAv47; runlineav = averagefc(tdnav47,10); end;
If TDN = 48 then begin Runline = TDNAv48; runlineav = averagefc(tdnav48,10); end;
If TDN = 49 then begin Runline = TDNAv49; runlineav = averagefc(tdnav49,10); end;
If TDN = 50 then begin Runline = TDNAv50; runlineav = averagefc(tdnav50,10); end;
If TDN = 51 then begin Runline = TDNAv51; runlineav = averagefc(tdnav51,10); end;
If TDN = 52 then begin Runline = TDNAv52; runlineav = averagefc(tdnav52,10); end;
If TDN = 53 then begin Runline = TDNAv53; runlineav = averagefc(tdnav53,10); end;
If TDN = 54 then begin Runline = TDNAv54; runlineav = averagefc(tdnav54,10); end;

End; {current bar}

VSeasRun2 = runline;

Category TradeStation (hidden)

Details: Weekly Universal Seasonality Indicator V1.
Category: TradeStation (hidden)

November 22nd, 2009
Size: 18.38 KB
Downloaded: 680 times

Keywords: tradestation

Ichomoku Kinkyo Ho Pack V1.2

I have developed a modification of the venerable Ichimoku Indicators.
( https://www.kumotrader.com/ichimoku_wiki/ )

In this case, there is a third longer term line 3* the usual 2nd line (Kijun). Why? Because it will line up with a longer term chart 3* higher (i.e. trading chart 150 ticks, LT 450 ticks, or 5 and 15 mins).

Also because the longer term line will often line up exactly with the Clouds that are drawn 27 bars ahead based on current action. The LT Clouds are drawn 81 bars ahead and are the equivalent to the Clouds in the LT chart. This way you don't really need the LT chart but also you see the relationship of shorter and longer term cycles/trends on the same screen which is helpful.

The Ichi3Lines indicator has (too) many bells and whistles such as a Bollinger 'tunnel', triangles that show simple pattern pullbacks within an Ichi trend. But it also has aspects of the official method not available in other indicators such as:

Circles plotted when the Clouds (Senkou Spans) cross up or down, and in my case with slightly different colors so you know immediately whether it's a long term cross or short term cross (these are happening off the screen in the 'future').

There is also a diamond plotted along with an optional line when there is a 'Chikou' cross, which is the current price crossing above or below the Chikou line which is plotted 27 bars in the past. This line is not on the chart because when viewing an historical chart it is very messy. In actual trading that line is in the past and is fine.

There are arrows indicating the basic 9-27 cross (tenkan-kijun).

There are pink arrows indicating when the longer term Kijun (KijunLT) which I have added (darker green plot) crosses above or below the cloud plot. These are strong confirmations of a strong trend indicating longer term breakouts.

There are also many back color options which only work on lighter screens so this picture with black background does not show them.

On this picture, to reduce screen noise, I also did not plot the basic Tenkan and Kijuns (sacriledge!) and only plotted the Kijun LT (dark green dash line) and my own 'equilibrium line' (pink dotted line) which is the average of the Tenkan(9), Kijun(27) and KijunLT (81) medians, the idea being that this is the current equilibrium price. It is around this price that the oscillator is built.

The oscillator: in addition, there is an Ichi 'Squeeze' Oscillator which is quite good but which unfortunately has a small glitch in that sometimes the lines don't plot and I can't figure out why. Also, it seems to happen only with minute bars. They used to work and now they don't and I must have changed something at some point and now can't find out what.

It is designed to help in identifying the longer and shorter term trends together, when they are lined up or not, but also has a faster line (Combo) that is pretty effective at showing extreme OB and OS conditions. There are three lines in the usual 0, OB and OS areas which display the ST, Medium Term and LT slopes of the Tenkan(9), Kijun(27) and KijunLT(81) medians respectively. There are also thicker lines above and below which show when all three trends are lined up.

The oscillator bars plot green when the Tenkan and Kijun slopes are not in agreement, i.e. often during consolidation or retracement zones and indicate caution/indecision. Also excellent for possible pullback/retracement entries in direction of overall trend which has not yet changed but is being challenged.

So for those who like the Ichimoku approach or those who wish to study it, this will prove helpful.

Best to disable most of the bells and whistles such as the Bollingers, pullback arrows and triangles and just work with the lines, Chikou span crosses (diamonds on close), Senkou Span crosses (cloud crosses that are in the clouds indicator and always plot), and the main signal arrows.

Oh. there is also an extreme OB/OS plot (pink diamonds) when the price has moved unusually far from the Kijun (middle green line) based on ATR and that distance. They are quite effective at indicating when a market has got ahead of itself.

Also, you can select paintbars, including divergence. The divergence colors are hard coded as red (in bull mkts) and magenta (in bears) so for those who have red down bars this won't be very helpful!

For trend trading, Ichis are truly superior. If you have a bearish cross or situation and the price has gone beneath both the ST and LT clouds, something which you will have been watching develop for quite some time because the clouds are drawn ahead of time, there is a strong probability of a sustained trend for a while. Similarly, early pullbacks in that situation often present low risk shorting opportunities, especially if the price retraces to the cloud bottom(s) and stops and especially if they are long, flat bottoms, indicating there was a long period of congestion at equilibrium and that value area is now about to change as all the action that was needed to happen there is past, or new perceptions have entered the market valuation matrix.

If anyone can fix the glitch in the Squeeze, I'd be grateful!

Note on Colors: apart from the fact that most were designed on white backgrounds whereas now I am going back to black, a note on the trend colors. I use what could be called a daoist system of colors which might be confusing: bullish colors are light and rising, bearish colors are darker and heavier so falling, so in my case I use golds and yellows for bullish (lighter, brighter) and blues for bearish (like water, heavier). Reds and Greens are neutral usually used for basic bars, longer term indicators, though often red is for some sort of extreme. For people used to red = bearish blue = bullish this can be confusing.

COMPATIBILITY:
NinjaTrader 6.5: YES
NinjaTrader 7.0: NO (tested by sam028)

Category NinjaTrader 6.5 Indicators

Details: Ichomoku Kinkyo Ho Pack V1.2
Category: NinjaTrader 6.5 Indicators

November 22nd, 2009
Size: 54.75 KB
Downloaded: 830 times

Keywords: cclsys chikou ichimoku ninjatrader

Range Bar High Low Current Bar Indicator v2

This indicator plots the maximum high or minimum low of a forming Range Bar. The plots disappear as soon as a new bar forms or the current bar has filled its required range.

Nov 5th: have fixed coding problem so that it will no longer function when you change to other chart formats. Right now is good for Range Bar and RangeAlt. If someone tells me the coding for the RangeNoGap I can add that in.

COMPATIBILITY:
NinjaTrader 6.5: YES
NinjaTrader 7.0: Yes

Category NinjaTrader 6.5 Indicators NinjaTrader 7 Indicators

Details: Range Bar High Low Current Bar Indicator v2
Category: NinjaTrader 6.5 Indicators NinjaTrader 7 Indicators

November 1st, 2009
Size: 2.13 KB
Downloaded: 1404 times

Keywords: ninjatrader high cclsys range low current bar

RPM: Range Per Minute (in Ticks) V 1.2

Especially helpful for non-time-based bar charts (though also good for them too), this indicator shows the Range Per Minute - expressed in ticks. To avoid huge bars during report times, the coding has a simple governor limitation to reduce the display value, but otherwise is accurate. There is also an optional alarm when RPM accelerates. You will probably have to go into the code to put in a sound file that you have in the Ninja/Sounds directory on the main system partition (not in the MyDocuments area).

Code cleaned up, new Scalping indicators and back color options. If the speed is accelerating above the average (default 6) and it's an up bar, a little wingding arrow will appear below the low and keep plotting on subsequent bars until there is a reversal or a new acceleration.

I find I can load it into the same panel as a volume indicator because the values are so low. Meanwhile if you enable price markers, the current RPM in ticks is displayed as text in the bottom right. The backcolors show that often shortly after acceleration there is a new move or climax of current move so it works as a leading indicator in some cases or confirmation of entry possibility in longer pattern setups.

The alarm can be disabled or a different sound file from the Sounds Directory in the Ninja System folders (not My Docs area).

Small, simple indicator but giving simple, factual information not often shown in others.

COMPATIBILITY:
NinjaTrader 6.5: YES
NinjaTrader 7.0: NOT TESTED [feedback]

Category NinjaTrader 6.5 Indicators

Details: RPM: Range Per Minute (in Ticks) V 1.2
Category: NinjaTrader 6.5 Indicators

November 1st, 2009
Size: 10.95 KB
Downloaded: 826 times

Keywords: minute ninjatrader range per