11-26-2008, 03:04 PM
|
 |
Senior Member
|
|
Join Date: Mar 2007
Posts: 657
|
|
:: Thanks! Going to look into it... but whatever it is, it can't be time based, a tick per tick system doesn't care about "per minute" or "per time frame" ... it just waits for the next tick, that perhaps it loops to hard to get it ... not logic 
IN10TION
Quote:
Originally Posted by m.mil
IN10TION HI, I enclosed a picture of the meter tiksperminute and a second meter ...
I was saying the first creates considerable problems of overloading the cpu and need to continually restart because of continuous crashes, also is not very precise and does not offer an average reference (for example, the average of 15 candles ticks above) it gives only 10 candles worth of ticks ...
The second counter is very accurate but unfortunately it is TF dependent and also does not offer us an average reference ...
Unfortunately I was unable to find the source codes of the two indicators ...
these are the only instruments close to the concept of speed detector, then we go to the concepts of range and volatility, more or less we are talking about the same thing but the results are very different (think !!!)...
please forgive me if I give you discomfort, good day ...
|
|