<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Market Turbulence</title>
	<atom:link href="http://marketturbulence.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://marketturbulence.com</link>
	<description>Contrariness is a virtue</description>
	<lastBuildDate>Fri, 17 Feb 2012 01:19:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Sequential Buy Setup to Watch: AMZN by Paul Stiles</title>
		<link>http://marketturbulence.com/2012/02/16/sequential-buy-setup-to-watch-amzn/#comment-561</link>
		<dc:creator>Paul Stiles</dc:creator>
		<pubDate>Fri, 17 Feb 2012 01:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://marketturbulence.com/?p=3049#comment-561</guid>
		<description>It is definitely invalid if you compare it to the TD Sequential.  I&#039;m interested in buying lows and shorting highs and I use customized rules that help me identify them in market-wide screens.  For the way I use the indicator, it does not matter which countdown or setup is valid as long as the price is testing lows on light volume.  The low of 12/29 would be my buy point if my count completes, so I would be buying while you would be adding to your existing position that you put on in December.  The stop loss would be exactly the same too.  </description>
		<content:encoded><![CDATA[<p>It is definitely invalid if you compare it to the TD Sequential.  I&#8217;m interested in buying lows and shorting highs and I use customized rules that help me identify them in market-wide screens.  For the way I use the indicator, it does not matter which countdown or setup is valid as long as the price is testing lows on light volume.  The low of 12/29 would be my buy point if my count completes, so I would be buying while you would be adding to your existing position that you put on in December.  The stop loss would be exactly the same too.  </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Critical Levels in a Critical Week by Portfolio Update &#124; Market Turbulence</title>
		<link>http://marketturbulence.com/2012/02/12/critical-levels-in-a-critical-week/#comment-560</link>
		<dc:creator>Portfolio Update &#124; Market Turbulence</dc:creator>
		<pubDate>Thu, 16 Feb 2012 18:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://marketturbulence.com/?p=2950#comment-560</guid>
		<description>[...] on Feb 16, 2012 in Long, Trades &#124; 0 comments                            If you took my advice and bought CLR around 76, your 3:1 price target of 84 was blown away today.  Right now you are looking at a 4 to 1 [...]</description>
		<content:encoded><![CDATA[<p>[...] on Feb 16, 2012 in Long, Trades | 0 comments                            If you took my advice and bought CLR around 76, your 3:1 price target of 84 was blown away today.  Right now you are looking at a 4 to 1 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sequential Buy Setup to Watch: AMZN by Pthegr8</title>
		<link>http://marketturbulence.com/2012/02/16/sequential-buy-setup-to-watch-amzn/#comment-559</link>
		<dc:creator>Pthegr8</dc:creator>
		<pubDate>Thu, 16 Feb 2012 13:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://marketturbulence.com/?p=3049#comment-559</guid>
		<description>imo, the current countdown you&#039;re showing is invalid. The range of the previous buy setup, which finished on 10/31 had a countdown finishing on 12/19. the second buy setup finished on 12/16. since the range of the previous buy setup was larger, its countdown is valid. the 2nd setup was &quot;perfected&quot; on 12/29, so a 9-13-9 buy setup. followed 1 bar later by a finished &quot;combo&quot; buy. 
http://screencast.com/t/lwUJFo3JFaA</description>
		<content:encoded><![CDATA[<p>imo, the current countdown you&#8217;re showing is invalid. The range of the previous buy setup, which finished on 10/31 had a countdown finishing on 12/19. the second buy setup finished on 12/16. since the range of the previous buy setup was larger, its countdown is valid. the 2nd setup was &#8220;perfected&#8221; on 12/29, so a 9-13-9 buy setup. followed 1 bar later by a finished &#8220;combo&#8221; buy.<br />
<a href="http://screencast.com/t/lwUJFo3JFaA" rel="nofollow">http://screencast.com/t/lwUJFo3JFaA</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Trade to watch by Sequential Breakdown works again - ELON &#124; Market Turbulence</title>
		<link>http://marketturbulence.com/2012/01/24/trade-to-watch/#comment-557</link>
		<dc:creator>Sequential Breakdown works again - ELON &#124; Market Turbulence</dc:creator>
		<pubDate>Sat, 11 Feb 2012 04:24:15 +0000</pubDate>
		<guid isPermaLink="false">http://marketturbulence.com/?p=2437#comment-557</guid>
		<description>[...] is a follow-up from a previous post I made regarding ELON and the Sequential Breakdown short setup. In that blurb, I said to keep an eye on it and look for [...]</description>
		<content:encoded><![CDATA[<p>[...] is a follow-up from a previous post I made regarding ELON and the Sequential Breakdown short setup. In that blurb, I said to keep an eye on it and look for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sequential Breakouts as Day Trade Setups by Netgear Trading plan NTGR &#124; Market Turbulence</title>
		<link>http://marketturbulence.com/2012/02/02/sequential-breakouts-as-day-trade-setups/#comment-556</link>
		<dc:creator>Netgear Trading plan NTGR &#124; Market Turbulence</dc:creator>
		<pubDate>Thu, 09 Feb 2012 04:32:41 +0000</pubDate>
		<guid isPermaLink="false">http://marketturbulence.com/?p=2599#comment-556</guid>
		<description>[...] week I wrote about a nice setup for NTGR and laid out a complete trade plan including entry, stop loss, and price target. Unfortunately, [...]</description>
		<content:encoded><![CDATA[<p>[...] week I wrote about a nice setup for NTGR and laid out a complete trade plan including entry, stop loss, and price target. Unfortunately, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The dangers of buying breakouts &#8211; SWI case study by Becky</title>
		<link>http://marketturbulence.com/2012/02/07/the-danger-of-buying-breakouts-swi-case-study/#comment-555</link>
		<dc:creator>Becky</dc:creator>
		<pubDate>Wed, 08 Feb 2012 20:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://marketturbulence.com/?p=2845#comment-555</guid>
		<description>Nice one!</description>
		<content:encoded><![CDATA[<p>Nice one!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Website upgrade by Paul Stiles</title>
		<link>http://marketturbulence.com/2012/02/07/website-upgrade/#comment-552</link>
		<dc:creator>Paul Stiles</dc:creator>
		<pubDate>Wed, 08 Feb 2012 14:25:27 +0000</pubDate>
		<guid isPermaLink="false">http://marketturbulence.com/?p=2693#comment-552</guid>
		<description>Thanks Brian.  The numbers for the site have grown dramatically over the last 8 weeks.  Analytics tell me that others are equally loyal to the site.  Thanks everyone.</description>
		<content:encoded><![CDATA[<p>Thanks Brian.  The numbers for the site have grown dramatically over the last 8 weeks.  Analytics tell me that others are equally loyal to the site.  Thanks everyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Website upgrade by Brian Wilson</title>
		<link>http://marketturbulence.com/2012/02/07/website-upgrade/#comment-550</link>
		<dc:creator>Brian Wilson</dc:creator>
		<pubDate>Wed, 08 Feb 2012 05:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://marketturbulence.com/?p=2693#comment-550</guid>
		<description>Thanks for all the work you&#039;ve been doing on the site. I don&#039;t comment often, but I check the site each day.</description>
		<content:encoded><![CDATA[<p>Thanks for all the work you&#8217;ve been doing on the site. I don&#8217;t comment often, but I check the site each day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Sequential signals with classic patterns by Trade update for SWI and KLAC &#124; Market Turbulence</title>
		<link>http://marketturbulence.com/2012/01/17/using-sequential-signals-with-classic-patterns/#comment-549</link>
		<dc:creator>Trade update for SWI and KLAC &#124; Market Turbulence</dc:creator>
		<pubDate>Tue, 07 Feb 2012 16:35:33 +0000</pubDate>
		<guid isPermaLink="false">http://marketturbulence.com/?p=2303#comment-549</guid>
		<description>[...] also wanted to point out the breakout from KLAC, which I wrote about a few days ago.  Look for a pullback to the breakout area and if volume is [...]</description>
		<content:encoded><![CDATA[<p>[...] also wanted to point out the breakout from KLAC, which I wrote about a few days ago.  Look for a pullback to the breakout area and if volume is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Sequential Signals to Scan for Classic Support and Resistance Levels by Market breadth and health of the S&#38;P 500 &#124; Market Turbulence</title>
		<link>http://marketturbulence.com/2012/01/22/using-sequential-signals-to-scan-for-classic-support-and-resistance-levels/#comment-521</link>
		<dc:creator>Market breadth and health of the S&#38;P 500 &#124; Market Turbulence</dc:creator>
		<pubDate>Mon, 23 Jan 2012 16:15:12 +0000</pubDate>
		<guid isPermaLink="false">http://marketturbulence.com/?p=2382#comment-521</guid>
		<description>[...] market will be when the leading stocks come back and test the breakout levels.  For example, if EL and CSCO pull back and bounce off support, I would expect the market to hold.  If these charts, [...]</description>
		<content:encoded><![CDATA[<p>[...] market will be when the leading stocks come back and test the breakout levels.  For example, if EL and CSCO pull back and bounce off support, I would expect the market to hold.  If these charts, [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

