What I am trying to do is use the last 3 or 4 of the highs and lows along with BarsSince of the last low to produce a pattern for trading, and yes I need for the highs and lows to change accordingly as price and time changes.
I fail to see the relevance of bar 5 if today's bar is 500 to determine a future leak as I am only using the last 3 or 4 of the highs and lows for a pattern. The code that I have now does not report a future leak in Code Check so I will proceed with using Scan and Expore to aid in RT as the pattern develops. I had not planned on backtesting but since you brought it up; I would like to know why using a limited number of bars to fit a pattern of highs and lows can be a future leak. I thought I knew what a future leak is but I am not so sure anymore. If this pattern showed up on bar 5, it would have to be back in time and was probably bar 500 at that time. As time progressed and it became bar 5 then I would be looking at bar 500 now and it would not be relevant to the pattern. So I would be grateful if someone would take the time to explain it to me. --- In [email protected], "Mike" <sfclimb...@...> wrote: > > "Using the value of highs" for what? > > If all you want to do is chart, then go for it. The chart will look fine. It > just won't look the same! It will constantly update as new bars come in. > > If you want to use it for discretionary trading *with the understanding* that > the signals you're trading will get revised as more data comes in. Fine. > > But, if you want to run a backtest, you cannot use the values. Full stop. No > way around it. > > If at any bar you find yourself making use of information based upon later > bars, then you've got a future leak and your implementation is only good for > charting. It cannot be traded, and any backtest would be meaningless. > > For example; At bar 5 you *cannot* be allowed to know that the last swing > high takes place on bar 500. So, yes, I see something wrong with using the > values after the loop. > > Finally, using BarsSince is fine. Just so long as you don't reference any of > its values beyond the current bar. > > Mike > > --- In [email protected], "booker_1324" <booker_1324@> wrote: > > > > Hi Mike, > > > > Using your code > > > > ... > > if (bigHigh[bar]) { > > lookingForHigh = false; // now looking for low > > PlotText("HH" + highs, bar, High[bar], colorGreen); > > highs++; > > } > > ... > > > > Do you see anything wrong with using the value of highs after the loop > > as the last swing high and (highs -1) as the second to last swing high and > > (highs -2) as the third last swing high and doing the same with lows? > > > > Also, is it feasible to use BarsSince(low)? > > > > --- In [email protected], "Mike" <sfclimbers@> wrote: > > > > > > Sure, just initialize a variable to track the number of highs then use > > > PlotText to write out the count. Do the same for lows. > > > > > > e.g. (untested) > > > > > > highs = 1; > > > > > > ... > > > if (bigHigh[bar]) { > > > lookingForHigh = false; // now looking for low > > > PlotText("HH" + highs, bar, High[bar], colorGreen); > > > highs++; > > > } > > > ... > > > > > > Mike > > > > > > --- In [email protected], "booker_1324" <booker_1324@> wrote: > > > > > > > > Nice code Mike, to take this a step farther, is it posible to attach a > > > > label to each HHV and LLV such as HH1, HH2, HH3, LL1, LL2, and LL3 > > > > without referencing future quotes? > > > > > > > > --- In [email protected], "Mike" <sfclimbers@> wrote: > > > > > > > > > > What makes you think that you are changing the step size? From what I > > > > > see, you're still advancing a single bar at a time. > > > > > > > > > > bigHigh = high >Ref (hhv(high,50),-1); > > > > > smallLow = low < Ref (llv(low,50),-1); > > > > > lookingForHigh = true; > > > > > > > > > > for (bar = 0; bar < BarCount; bar++) { > > > > > if (lookingForHigh) { > > > > > if (bigHigh[bar]) { > > > > > lookingForHigh = false; // now looking for low > > > > > } > > > > > } else { > > > > > if (smallLow[bar]) { > > > > > lookingForHigh = true; > > > > > } > > > > > } > > > > > } > > > > > > > > > > Mike > > > > > > > > > > --- In [email protected], "Markus Witzler" <funnybiz@> wrote: > > > > > > > > > > > > Hello, > > > > > > > > > > > > I wonder if I can step thru a loop where the step size is being > > > > > > computed WITHIN the loop. > > > > > > > > > > > > An example: > > > > > > > > > > > > I want the loop to check for every bar until high >Ref > > > > > > (hhv(high,50),-1). > > > > > > > > > > > > From THAT bar on, the loop should check if low < Ref > > > > > > (llv(low,50),-1) occured. > > > > > > > > > > > > Say, the first condition is true on bar 50, the loop should > > > > > > afterwards start to check for the second ccondition from bar 51 > > > > > > until that condition is fullfilled, say on bar 80. > > > > > > > > > > > > From THAT bar on, it again should check for the first condition etc. > > > > > > > > > > > > The thing is that I can´t tell the loop the step size in ADVANCE > > > > > > and it may differ over the whole data range, depending on WHEN the > > > > > > condition beign checked for is true. > > > > > > > > > > > > Any ideas on this? > > > > > > > > > > > > Thanks > > > > > > > > > > > > Markus > > > > > > > > > > > > > > > > > > > > >
