After manually reviewing tick by tick data for a few hours, along with their respective bid x ask levels and number of contracts, I've determined that there is a method to come up with the ultimate moving average.
First, let's review what a moving average is -- a moving average is simply an average of X previous time-periods that constantly moves along with current price data. There is candle moving averages that are based on either the close, open, high, low, high-low / 2, etc. There are also exponential, triangular, variable, weighted and simple moving averages.
Now, a moving average on a 1, 2, 5, 10, 30 minute-- whatever -- is not always a good representation of reality. Why?
Here is an example. Let's say there is a wide range of movement within a 2 minute candle. Now, if the price is 890.50 for a long time and then spikes up to 891.25 for a second and then falls back down, that 891.25 will be used within some moving averages, even though it is more of an anomoly and doesn't deserve the same "weight" as the other numbers.
Even tick data is imperfect. What if you have this scenerio:
802.50 x 802.75 [1 contract x 193 contracts] -- Well, if someone actively sells into that 1 contract bid, the next tick gets knocked down to 802.25 x 802.50.
So, I'm going to program a moving average that gives weight to each tick of data and is adjusted by the bid and ask weight. I think this will be far more reliable.
I'll let you know what I come up with.
aphie
First, let's review what a moving average is -- a moving average is simply an average of X previous time-periods that constantly moves along with current price data. There is candle moving averages that are based on either the close, open, high, low, high-low / 2, etc. There are also exponential, triangular, variable, weighted and simple moving averages.
Now, a moving average on a 1, 2, 5, 10, 30 minute-- whatever -- is not always a good representation of reality. Why?
Here is an example. Let's say there is a wide range of movement within a 2 minute candle. Now, if the price is 890.50 for a long time and then spikes up to 891.25 for a second and then falls back down, that 891.25 will be used within some moving averages, even though it is more of an anomoly and doesn't deserve the same "weight" as the other numbers.
Even tick data is imperfect. What if you have this scenerio:
802.50 x 802.75 [1 contract x 193 contracts] -- Well, if someone actively sells into that 1 contract bid, the next tick gets knocked down to 802.25 x 802.50.
So, I'm going to program a moving average that gives weight to each tick of data and is adjusted by the bid and ask weight. I think this will be far more reliable.
I'll let you know what I come up with.
aphie
