October 14th, 2010, 6:01 pm
QuoteOriginally posted by: tomericowhat in your building process - is refering to the volatility ?I don't turn ticks into volatility, and then volatility into ticks. I just use the ticks, meaning the bar-to-bar changes. The assumption that the volatility is the sum of random ticks, and dictated by their size - which is captured pretty well over a pretty small sample - is flawed. But this same sort of assumption is used in any monte carlo.You could say it is a weakness or a strength that I don't have to come up with some single volatility number, and then translate that into the various jump sizes you actually see. I just use the types of jumps we have seen recently, at the frequency they have occurred recently.You could use other simple enhancements, like sample at random from a pool limited to bars were in the past preceded by bars of the current jump size. This would create intervals of autocorrelated volatility, whether high or low, like in real life. But without having to come up with some crazy model and plug in parameters that are totally made up.The only fitting you might want to do is the adjustor, which increase or decreased volatility by adding jumps to the monte carlo. In theory, there is a possibility of bigger jumps than occured in the sample interval. But you can run a backtest to find a general adjustor. Perhaps stringing together 130 moves from the last 100 bars generally predicts volatility over the next 100 bars.Also, this simple program is designed to self adjust to fast and slow times of day. But you could really easily say well it is late afternoon, and I think the next hour will be less volatile than the last hour, and use and adjustor of .8. You might say hey, that is not real quanting, that .8 you just pulled out of the sky. But nothing is real, it is as good as anything else, this is the tragic nature of the world.