Multiple CCI and a MTF Heatmap. Or, how to filter three periods - 5, 21, 89 - for the best opportunities (Please see link for sample charts and tables: http://bit.ly/1kmszDg)PROBLEM: When trading on a laptop, or w/just one screen, w/modest RAM and CPU, it's difficult or impossible to do visual scans of dozens of pairs, and multiple timeframes in a timely manner. The result is spending hours staring at the screen waiting for the right setup, or forcing trades, and missing the best setups.
SOLUTION: One partial solution is sortable table of all pairs meeting filter requirements of the multiple CCI indicator,
http://www.fxcodebase.com/code/viewtopi ... CCI#p93332, coded by Apprentice, w/option to have popup alerts when conditions are met. Tables may be placed on the individual chart or stay on a separate 'Dashboard' page.
Elements to include:
A. Possible to include a thumbnails view of the 3CCI indicator windows.
B. Possible to include a thumbnail views of three WMAs, that is 5WMA, 21WMA, 55WMA
http://bit.ly/1kmszDgMultiple CCI and a MTF Heatmap. Or, how to filter three periods - 5, 21, 89 - for the best opportunities
Tables are to have sortable CCI columns for periods 5, 21, and 89 in order to show CCI and the slope of CCI, with the purpose of filtering the fastest moving pairs:
http://bit.ly/1kmszDgAnother possible option is to sort each timeframe based on the sum positve of the three CCI averages, w/ a ranking of greater / lesser weight for each timeframe. In the case below, the highest rank is given to the timeframes at the top of the table. (Optional to leave out the slope of the CCI)
http://bit.ly/1kmszDgPossible option to select the pairs to sort, for example, only the AUD pairs, or only the JPY pairs, etc. Or to filter the pairs based on ROC and volatility, or other filters. And option to choose only 1M, or only 5M, etc. Each cell has the values of three CCI periods, w/ the total score for the pair at that timeframe. Possible to color code the text of the ranking for each of the three CCI periods to represent to slope, instead of including the slope value.
http://bit.ly/1kmszDg