Quote from HedgefunTrader2:
My concern is that what I would need requires a program to follow the SPY second by second, and once my specific pattern appears, a trade is taken. Is that too complicated?
No, it's not really complicated.
Quote data is normally just ticks, not time bars or something the like.
Congrats.
In my view strategies based on tick data are the ones that are worthwhile.
No algo that is moving big amounts of money is based on e.g. 1 minute bars.
Quote from HedgefunTrader2:
Theoretically, I'm not really sure why a 1 min chart and a 60 sec chart should show any differences. Does anyone know?
They can differ because with some quote sources ticks don't carry time information.
Therefore they may be assigned arbitrarily to different time intervals depending on the algorithm.
One more reason why tick based algos are better:
They are more objective.
Quote from sma202:
To people who use tick data, my question is on how you select the appropriate timeframe for backtesting. Do you look at 1 day's worth of tick data or multiple days or just use several hours? If multiple days, it's a given that you will run out of memory soon enough. What are the approaches to backtest a few months of tick data?
Memory problems:
Not necessarily.
If you look e.g. at DAX futures you'll find 40k trades per day on average.
Assume 1 year worth of data: 200 days x 40k x 20Bytes/trade = 160 MB. If you have 2 GB main memory that's less than 10% memory usage.
Backtesting / timeframe:
It makes no sense to look 10 years back.
The advent of always smarter algos changes the trading environment pretty fast.
Though it certainly is helpful to look 1 or 2 years back in order to get a sufficient data base.
Backtesting in general:
For tick data you can do something better:
Calculate probabilities for the occurence of certain conditions.
This can give you a guidance in realtime.