"...CAD with the wind..." — Sandy is gone, so let's check the first prediction about the CAD a day after the prediction (31 Oct, 2012) till last weekend: CADCHF - check against "Hard" currency (+170 pips). CADJPY - check against ...

The gg53 "Killing Zone"

Sabrina, This is a very good and safe (low risk) trade. I would have entered this trade about 8-12 hours earlier with confirmation from Gadi_OBV. I don't use Support/Resistance in my trading unless they are some price's round numbers. G. Edit: I ...

The gg53 "Killing Zone"

alij79, Both v2.0 & v2.1 are displaying the correct channel from channel start to channel end. The "problem" is that after channel "end" it continues to update the channel min./max. . Next update will ignore channel changes after channel "end". G.

The gg53 "Killing Zone"

Pat1, You are right. I wasn't paying attention to what's happening after the channel close. Please ignore both v2.0 & v2.1. G.

The gg53 "Killing Zone"

Is Gadi_OBV v2.0 Ok by itself between start/end of its channel? Is there a BUG in its calculation? I'm not comparing codes and indicators. G.

The gg53 "Killing Zone"

Gadi_OBV - Updated — Gadi_OBV is now v2.1. Added features: MTF Channel Start/End can be set in Hours/Minutes. Channel times disply on chart. Enjoy. G.

The gg53 "Killing Zone"

Gadi_OBV - Update — Gadi_OBV updated to v2.0. Added features: Show Asian session channel. Session Start - in hours. Session End - in hours. Percent increase - Safety level (in percent fraction). Blue line - Channel High Red line - Channel Low ...

The gg53 "Killing Zone"

Pat, The "something wrong" is the session "end". if you specify "8" it will refere to the bar that "open" at 08:00 but closes at 09:00 on H1 chart. "Looping" - I'm just calculating for LATEST session and not all bars: if (jStart>0 && jEnd>0) exit; ...

The gg53 "Killing Zone"

Pat1, Your indi is doing someting wrong at the last bar of the Asian session. G.

The gg53 "Killing Zone"

Pat1, My version is a bit simpler: // Minimum/Maximum latest Asian session Gadi_OBV for(int k=0; k<=Hist; k++) { if (TimeHour(Time[k])==AsianStart && TimeMinute(Time[k])==0) jStart=k; if (TimeHour(Time[k])==AsianEnd && TimeMinute(Time[k])==0) ...

The gg53 "Killing Zone"

Middleastern, AFAIK - current bar is 0, previous bar is 1, etc. So if you start from StartHour the next bar will be StartHour -1 hour. G.

The gg53 "Killing Zone"

Middleastern, Isn't "a++" in the above code going backward from StartHour instead of forward? G.

The gg53 "Killing Zone"

fxprotrader, Ok, later on I'll look a bit closer. G.

The gg53 "Killing Zone"

Middleastern, I briefly reviewed your code. I think that you meant this EA to work on H1 - but in fact everyone is trying it on lower TF's. I think that the following is for H1 only (" a=1; a<9 " - seeking 8 previous bars) : ...

The gg53 "Killing Zone"

To EA or not... — fxprotrader, Hammondz, Middleeastern, I'm willing to check this EA out - but I can't "endorse" this EA. My system is based, first of all, on the principal of "Forex is a game of DEFENCE" - and the "Killing Zone" and low ...

The gg53 "Killing Zone"

sabrys5769, Ok, now I see it... We should change the bars from green/red to black/white... image G.

The gg53 "Killing Zone"

alij79, "Dominate the Denominator" post. G.

The gg53 "Killing Zone"

kapybara, The problem with Troughs and Peaks is that in order for them to form - they already include some of the opposite move. In a pullback after sharp move - you might be too late... G.

The gg53 "Killing Zone"

Jason, Read again... "...in mn_KillingZone.mq4". G.

The gg53 "Killing Zone"

kapybara, The CounterTrend (my version from previous post) is now +34 pips. G.

The gg53 "Killing Zone"