Hearst index - page 30

 

Rinat once wrote that roughly Volume=(Open-2*Low+2*High-Close)*pow(10,Digits)+1

;)

 
avatara: Rinat once wrote that roughly Volume=(Open-2*Low+2*High-Close)*pow(10,Digits)+1

The formula is for a bearish candle and a bullish candle will have different tick volumes, I made my own indicator using the formula:

#property indicator_separate_window
#property indicator_buffers 2
#property indicator_color1 Red
#property indicator_color2 DarkTurquoise
double vol_math[],vol_mt4[];//--- buffers
//________________________________________________
int init(){
   SetIndexStyle(0,DRAW_LINE);
   SetIndexBuffer(0,vol_math);
   SetIndexStyle(1,DRAW_LINE);
   SetIndexBuffer(1,vol_mt4);
return(0);
}
//________________________________________________
int start(){
   int    i,limit,counted_bars;
   counted_bars=IndicatorCounted();
   if(counted_bars>0) counted_bars--;
   limit=Bars-counted_bars;
   for(i=limit; i>=0; i--){
      vol_math[i] = (MathAbs(Open[i] - Close[i]) + 2*(High[i]-Low[i])) * MathPow(10,Digits) + 1;
      vol_mt4[i] = Volume[i];
   }
return(0);
}
 

Some more stats.

Time between ticks

Amplitude

Files:
haxz.zip  6 kb
 
IgorM:
The minus is kind of missing before MathAbs
 
Rorschach: Before MathAbs it is kind of minuscule

perhaps, but it is easier to adjust this formula for a specific TF using MathPow(10,Digits), on M5 on Alp...and like MathPow(11,Digits)

WZZ: If we seriously consider tick volumes, it is easier to teach NS to tick volumes on the basis of OHLC and then no matter what DT draw the results of NS.

 
avatara:

On the four marks, the same period and asset should have been looked at.

Rounding up

int sz = MathRound(MathAbs(Close[j]-Open[j])/Point/10)*10;


 
alsu:

Rounding up

I don't know about a 4-digit DT, but simply rounding has no effect.
 
avatara:

Rinat once wrote that roughly Volume=(Open-2*Low+2*High-Close)*pow(10,Digits)+1

;)

Well, it's just approximation counting on the fact, that the price went from Open to Low, then to High and returned to Close... But the meaning is completely lost, if we approximate the movement inside the bar by three segments...
 
Rorschach:

Some more stats.

Time between ticks

Amplitude

How about "time between ticks depending on bar volume already achieved"? Would have made the point clearer straight away.
 
alsu:
How about "time between ticks depending on bar volume already achieved"? Would clarify the point right away.


Unfortunately there is no such thing((.

Can

int sz = MathAbs(High[j]-Low[j])/Point;
Have a look at it?