Requests & Ideas - page 275

 
rayphua:
Hi Mladen, wanted to make sure you understood what I wrote?

Here is a version that does that. But it does not use only the current close price - it uses current high, low and open for the projection too (since all 4 prices are needed for the calculation of volatility quality). To mark what is a subject of change, you have a colored square on the indicator

 
mladen:
Here is a version that does that. But it does not use only the current close price - it uses current high, low and open for the projection too (since all 4 prices are needed for the calculation of volatility quality). To mark what is a subject of change, you have a colored square on the indicator

Thanks Mladen, just installed and testing it.

1. Is this a one bar projection, somehow it looks like a two bar projection.

2. I suppose when price changes, projection would also change?

3. Regarding the use of current high and low, instead of just the close, I think projections will almost always be an increase if it is below zero, and a decrease if it is above zero. Is there anyway to avoid using the high and the low?

 
rayphua:
Thanks Mladen, just installed and testing it.

1. Is this a one bar projection, somehow it looks like a two bar projection.

2. I suppose when price changes, projection would also change?

3. Regarding the use of current high and low, instead of just the close, I think projections will almost always be an increase if it is below zero, and a decrease if it is above zero. Is there anyway to avoid using the high and the low?

rayphua

1. it is one bar projection

2. yes, if the price changes the projection changes too

3. it can not be done. Some parts of the calculation of VQ would be a constant 0 if only close price would be used and it would make the projection a constant 0 - hence it would be useless

 
mladen:
rayphua

1. it is one bar projection

2. yes, if the price changes the projection changes too

3. it can not be done. Some parts of the calculation of VQ would be a constant 0 if only close price would be used and it would make the projection a constant 0 - hence it would be useless

I think I have a solution. What if we fix the projected candle's open/close/high/low price as the current candle's price?

 
rayphua:
I think I have a solution. What if we fix the projected candle's open/close/high/low price as the current candle's price?

rayphua

It is using current open,close,high/low in calculation now for the projection

 
mladen:
rayphua It is using current open,close,high/low in calculation now for the projection

Yes I know. Instead, can we use the current candle's close = projected candle's current open/close/high/low, to calculate?

 
rayphua:
Yes I know. Instead, can we use the current candle's close = projected candle's current open/close/high/low, to calculate?

rayphua

As I alerady explained : no it can not be done. It is the nature of how VQ is calculated and if you use only one price (close) in the calculation the result will be a constant 0

 
mladen:
rayphua As I alerady explained : no it can not be done. It is the nature of how VQ is calculated and if you use only one price (close) in the calculation the result will be a constant 0

My bad. Okay, then can we use current candle's close = project candle's open and close. And projected candle's high = current candle close + 1 pip, and projected candle's low = current candle's close - 1 pip.

Would that not be possible?

 
rayphua:
My bad. Okay, then can we use current candle's close = project candle's open and close. And projected candle's high = current candle close + 1 pip, and projected candle's low = current candle's close - 1 pip. Would that not be possible?

rayphua

This is the way how VW is calculated. Please take a look at it in try to imagine what will happen if you replace any of the prices with other

double cHigh = iMA(NULL,0,PriceSmoothing,0,PriceSmoothingMethod,PRICE_HIGH ,MathMax(i-1,0));

double cLow = iMA(NULL,0,PriceSmoothing,0,PriceSmoothingMethod,PRICE_LOW ,MathMax(i-1,0));

double cOpen = iMA(NULL,0,PriceSmoothing,0,PriceSmoothingMethod,PRICE_OPEN ,MathMax(i-1,0));

double cClose = iMA(NULL,0,PriceSmoothing,0,PriceSmoothingMethod,PRICE_CLOSE,MathMax(i-1,0));

double pClose = iMA(NULL,0,PriceSmoothing,0,PriceSmoothingMethod,PRICE_CLOSE,i);

double trueRange = MathMax(cHigh,pClose)-MathMin(cLow,pClose);

double range = cHigh-cLow;

if (range != 0 && trueRange!=0)

double vqi = ((cClose-pClose)/trueRange + (cClose-cOpen)/range)*0.5;

else vqi = Vqi[r-1];

 

Hi Mr Tools or Mladen, can you add Take Profit and Stop Loss parameters to this EA please? This one seems very interesting and might be worth further developing. I noticed that it does close trades at the right time to minimize loss so if you can keep that feature independent from a stop loss field, it would be wonderful (say if stop loss=0, nothing happens and it continues to work as before).

It also takes profit but sometimes too late and misses the mark so a TP field would be the most important thing. Thanks.

Files:
doubleup2.mq4  4 kb
Reason: