snowbird

Went hiking as well... Hell's Canyon... saw nobody, bought nothing, brought back some great memories! snowbird

Agreed, I find this rings true, especially in the case of revenge trades. Personally I also find I need to be cautious of over-trading after several wins (overconfidence). In the case of mistakes, where the desire/ worth ethic is to "fix it", one would be better served documenting what the mistake was as well as what they were "feeling" at the time. (this is hard for me because I hate documentation, obviously know what the mistake was at that time and do not feel good about it). Return to your journal every so often and review to identify patterns of reoccurring emotions affecting your decisions. snowbird

Thanks Uli, I'm actually using the range "Expansion" bars which are not available in tradestation. You will probably laugh when you hear how I am using them... My major issue is patience and discipline (I tend to jump the gun too early and overtrade). I've been using the range expansion bars in three ways to help: 1. Don't trade the chop (blue rectangle on chart, where you get an up/down/up sequence of expanded bars 2. Wait for a "signal" range expansion bar (each of the 3 green bars in a range downtrend on this chart are what I use as "signal" bars , and then I wait for a break below the low of the previous bar in this case to enter (3 yellow arrow trend re-entries on the chart) 3. But my favorites are the breakouts from consolidations. These are where significant time elapses between range expansion bars (green and red rectangles in the chart). I try and set the expansion factor at ~2x the ATR (been thinking about possible changes to the code to make this automatic! I was also wondering what criteria you use for color coding bars between range expansion bars? ... and as you can see... I still have not completely figured out color coding of the EMA (issue is due to the smoothing algorithm I believe). TAMS has been a great help as I now have portions that turn both red and green... its the parts in-between I'm missing! Thanks again, snowbird

Wow... quick response TAM's!! I was definatly making it too hard (can you tell I'm NOT a coder) but unfortunately the code simplification still does not work (I believe it has to do either with how often Uli samples the Array, or his smoothing algorithm in line #69 EMA34[1] = EMA34[2] + SmoothingFactor * (RBclose[1] - EMA34[2]); Don't know if this will port to MT... but that's what it might take to figure this one out... I posted a chart that shows the MA color changes in the indicator with your code... never does go red... but we do get patches of green! I do not know why Uli uses plot1[1]... but figured it had something to do with his array setup and calculations. If you eliminate the [1] then the MA just plots green (up and down!) snowbird

I'm stuck on what I thought would be a simple coding task for Uli's range bar expansion indicator. My goal was to color code the two moving averages EMA34 and LSMA red and magenta respectively when slope is down; green and blue when slope is up. Full original code is posted below. My attempt to color code EMA34 by it's slope (shown next) failed: original plot line (17 lines from the end): if plotEMA34 then plot1[1](EMA34[value1],"LBEMA34") my failed code attempt (just turns MA green): if plotema34 and EMA34[value1] > EMA34[value1-1]then plot1[1](EMA34[value1],"LBEMA34",Green) else if plotema34 and EMA34[value1] < EMA34[value1-1]then plot1[1](EMA34[value1],"LBEMA34",red); I believe the problem has to do with the fact that this is built within an array. Any savy coders able to lend some ideas? Thanks in advance!, snowbird ------------------------------------------------- //Range Expansion Bars by Uli Schmuli inputs: BarRange(3.75), PlotRangeBars(true), PlotExpansionBars(true), PlotExpansionPotential(true), BullBarColor(green), BearBarColor(red), RBThickness(3), PlotEMA34(true), PlotLSMA(true); var:RangeHigh(0), RangeLow(0), RangeOpen(open), RangeClose(0), RBcolor(green), LBLow(0), LBHigh(0), LBOpen(0), LBClose(0), offset(0), LBxAvg(0), SmoothingFactor(2/35), LSMAtemp(0); Array: EMA34[100](0), RBHigh[100](close), RBLow[100](close), RBOpen[100](Close), RBClose[100](close), LSMA[100](close); if barnumber = 1 then //1st bar initialization begin if range < BarRange then begin RangeHigh = high; RangeLow = Low; end; if range > BarRange then begin RangeHigh = High; RangeLow = Low; end; LSMA[1] = close; EMA34[1] = close; RBclose[1] = close; LSMA[1] = close; LBopen = open; end else //all other bars Begin if date <> date[1] then //new day, begin new bar & close out prior bar begin LBHigh = RangeHigh; LBlow = RangeLow; LBOpen = RangeOpen; LBclose = iff(close<RBclose[1],RangeLow,RangeHigh); For Value1 = 100 downto 2 begin EMA34[value1] = EMA34[value1-1]; RBHigh[value1] = RBHigh[Value1-1]; RBLow[value1] = RBLow[Value1-1]; RBOpen[value1] = RBOpen[Value1-1]; RBClose[value1] = RBClose[value1-1]; LSMA[value1] = LSMA[value1-1]; end; RBHigh[1] = LBHigh; RBLow[1] = LBLow; RBOpen[1] = LBOpen; RBClose[1] = LBClose; EMA34[1] = EMA34[2] + SmoothingFactor * (RBclose[1] - EMA34[2]); value1 = LinRegArray(RBClose,25, 0, value2, value3,value4, LSMAtemp); LSMA[1] = LSMAtemp; RangeOpen = Open; RangeHigh = High; RangeLow = low; RangeClose = close; offset = 1; end; if offset[1] = 1 and date = date[1] then offset = 0; if low >= rangelow and high <= rangehigh then //Bar totally in barrange begin end; if high > Rangehigh and low >= rangelow then //new high value begin rangehigh = high; If high - rangelow > barrange then //New Higher bar detected begin LBlow = RangeLow; LBHigh = RangeLow + BarRange; LBOpen = RangeOpen; LBclose = LBHigh; For Value1 = 100 downto 2 begin EMA34[value1] = EMA34[value1-1]; RBHigh[value1] = RBHigh[Value1-1]; RBLow[value1] = RBLow[Value1-1]; RBOpen[value1] = RBOpen[Value1-1]; RBClose[value1] = RBClose[value1-1]; LSMA[value1] = LSMA[value1-1]; end; RBHigh[1] = LBHigh; RBLow[1] = LBLow; RBOpen[1] = LBOpen; RBClose[1] = LBClose; EMA34[1] = EMA34[2] + SmoothingFactor * (RBclose[1] - EMA34[2]); value1 = LinRegArray(RBClose,25, 0, value2, value3,value4, LSMAtemp); LSMA[1] = LSMAtemp; rangeopen = Rangelow + barrange; rangeLow = Rangelow + barrange; RangeClose = rangeopen; offset = 1; end; end; if low < RangeLow and high <= rangehigh then//new low value begin Rangelow = low; if rangehigh - low > barrange then //New lower bar detected begin LBHigh = RangeHigh; LBlow = RangeHigh - barrange; LBOpen = RangeOpen; LBclose = LBlow; For Value1 = 100 downto 2 begin EMA34[value1] = EMA34[value1-1]; RBHigh[value1] = RBHigh[Value1-1]; RBLow[value1] = RBLow[Value1-1]; RBOpen[value1] = RBOpen[Value1-1]; RBClose[value1] = RBClose[value1-1]; LSMA[value1] = LSMA[value1-1]; end; RBHigh[1] = LBHigh; RBLow[1] = LBLow; RBOpen[1] = LBOpen; RBClose[1] = LBClose; EMA34[1] = EMA34[2] + SmoothingFactor * (RBclose[1] - EMA34[2]); value1 = LinRegArray(RBClose,25, 0, value2, value3,value4, LSMAtemp); LSMA[1] = LSMAtemp; RangeOpen = LBclose; RangeHigh = LBclose; RangeLow = low; RangeClose = close; offset = 1; end; end; if high > RangeHigh and Low < RangeLow and rangehigh - rangelow > barrange then//engulfing bar begin RangeLow = low; RangeHigh = high; end; end; begin if offset = 1 then //new bar begun begin if RBclose[1] < RBclose[2] then RBcolor = BearBarColor else RBcolor = BullBarColor; plot15[1](RBHigh[value1],"RBHighL",RBColor,default,RBthickness); plot16[1](RBLow[value1],"RBLowL",RBcolor,default,RBthickness); plot17[1](RBopen[value1],"RBopenL",RBcolor,default,RBthickness); Plot18[1](RBClose[value1],"RBcloseL",RBColor,default,RBthickness); if plotEMA34 then plot1[1](EMA34[value1],"LBEMA34") if plotLSMA then plot5[1](LSMA[Value1],"LSMA"); end; if close < LBclose then RBcolor = darkred else RBcolor = darkgreen; if PlotExpansionBars then begin plot20(rangehigh,"chigh",RBColor,default,1); plot21(rangelow,"clow",RBcolor,default,1); plot22(rangeopen,"copen",RBcolor,default,1); Plot23(Close,"cclose",RBColor,default,1); end; if PlotExpansionPotential then begin Plot24(rangehigh-barrange,"PotLow"); Plot25(RangeLow+barrange,"PotHigh"); end; end;

Ahh... that it does! excellent explanation. Another thing I noticed as I've looked at the differences... it appears that with the BB momentum BO signal (BB SQ = true) alert, that if the close of the BO bar is outside the BB/Keltner channel, it often pays to wait for a retrace back within the channel towards the Keltner center line before buying/selling the BO in the direction of the squeeze. This will often get you in at a closer entry to what the PBF alert signal would have, but with many fewer false signals/whipsaws. snowbird

Gapless squeeze is a great addition to the indicator. Signal line appears to operate different from the version I have been using (pbf). Can anyone elaborate on the application this particular signal line is based on... it appears to go red in consolidations/transitions. Thanks, snowbird

Rgaind, I'm interested in more details on how you use a fast and slow chart to help avoid chop. Snowbird

50 MA should definately help.... and also keep you out of some bad trades (pass on signals or be very carefull if the 50 MA is flat/directionless) snowbird

I also believe this method has merit. Many of the trades will be out of consolidations, allowing a small stop loss and greater risk/reward potential. I've heard some traders look for trades within consolidations or when ADX drops to a very low # for this very reason. The tricky part of course being not knowing in advance which way price will break out of consolidation. The trendline break entry you show appears to let price action confirm the direction out of consolidation. snowbird

Very interesting programmer. Would you be able to give a brief update on how you find these useful in your own trading. I noticed that some of the balance point pivots (like the "Today" white pivot lines are hard coded with solid lines, and others you allow an input for toggling and/or dashed lines. Is this because you have found some balance points are typically not as stong as others? Do you also find that an "untouched" balance point typically serves as stronger S/R similar to virgin POC's? Your insight is appreciated. Thanks for the post... it is obvious that you spent some time on the code. Snowbird

gassah, Regarding Rays method, I don't understand how the POC hit count is made, since the POC can move as the range after the flagpole builds out. Is the calculation basically only performed at any one given point in time? For instance, take a look at point B in chart #3. Assuming the POC was not drastically different from what is currently shown at that time, there were appromimately 1/2 the number of POC hits (18). Therefore the cause = 18/23*.57 = .45 (still a buy)? Thanks in advance for clarification. snowbird

Here's the eld. 1st time I've tried an attachment so hope it works. Can't help you if it doesn't work on your charts/ts version, just know that it works on mine. snowbird 24HRPIVOTS.ELD

Turtle system works great when markets trend, abut can suffer long periods of draw downs when they don't. Are you trading the exact turtle rules? Have you looked at what draw down you might have to stomach during several days/weeks of sideways movement? snowbird

Here is one of my favorites to start out 2009... a tribute to all those who contribute to these forums... and especially those who host and moderate them. "Burn brightly without burning out. Richard Biggs"

VolumeJedi, I am also interested in jperls reply, I imagine you can treat all these HUPs identically, and rather than targeting the additional 3 day SD2, just re-analyze price action at each HUP and make a decision as to hold or exit depending on how many contracts you have on. I also imagine if multiple HUP's were to align at the same spot, you may choose just to exit. On a seperate note: It appears you may be one of the first to apply jperls strategies to forex. I'm interested if anyone else has also experimented with pvp and vwap using market statistics with any of the currency pairs, and if so, what their experience has been. Specifically, are there any tradestation users on the thread who have figured out the right code changes/array parameters neccesary to alter dbtinas original PVP & VWAP code to work on the currency pairs? Happy New Year All... wishing you a great 2009!!!! snowbird

One of my favorites: "Even if you are on the right track, you'll get run over if you just sit there" Will Rogers